Guys,

Something a bit weird.


I got the POP3 service on at sbbs.ini
---
[Mail] SMTP/POP3 Mail Server
AutoStart=true
MaxClients=10
MaxInactivity=120
Interface=public_ip_address
LinesPerYield=10
MaxDeliveryAttempts=50
MaxRecipients=100


MaxMsgSize=20MB
MaxMsgsWaiting=100
RescanFrequency=3600
SMTPPort=25
SubmissionPort=587
TLSSubmissionPort=465
POP3Interface=public_ip_address
POP3Port=110
TLSPOP3Port=995
DefaultCharset=IBM437
DefaultUser=
DNSBlacklistHeader=X-DNSBL
DNSBlacklistSubject=SPAM
RelayServer=public_ip_address
RelayPort=25
; The following 2 keys are used if the RelayServer requires authentication (SMTP AUTH)
; Must also set one of the RELAY_AUTH opt

Re: Weird issue with POP mail
By: Rmh to All on Tue Jun 19 2018 08:52 pm

Guys,

Something a bit weird.

I got the POP3 service on at sbbs.ini

1. When you put tear-lines ("---") in your messages, that makes them difficult to quote. Use more or fewer dashes to fix that.

2. If you have POP3 enabled, it'd look something like this in your sbbs.ini:

Options=ALLOW_POP3

(you didn't paste the "Options" value from the [mail] section of your sbbs.ini).

3. POP3 has nothing to do with outbound or inbound email.

4. Why do you have "public_ip_address" for your RelayServer address? This the address of a mail server through which you are choosing to relay mail - usually not *your* IP address or host name and often you don't need to relay at all.

digital man

Synchronet "Real Fact" #18:
Rob Swindell first learned to program in C by hacking on WWIV BBS software. Norco, CA WX: 62.9oF, 83.0% humidity, 3 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: Digital Man to Rmh on Tue Jun 19 2018 10:40 pm

1. When you put tear-lines ("---") in your messages, that makes them difficult to quote. Use more or fewer dashes to fix that.

Apologies Digital Man, I will improve that part.

2. If you have POP3 enabled, it'd look something like this in your sbbs.ini:

Options=DNSBL_REFUSE | DNSBL_IGNORE |DNSBL_BADUSER | DNSBL_THROTTLE | DNSBL_SPAMHASH | DEBUG_TX | DEBUG_POP | ALLOW_POP3

(apologies again for the incomplete of the provided information)

3. POP3 has nothing to do with outbound or inbound email.

I cannot know Digital Man, I haven't looked into the source code. Only bringing up what I am experiencing.

4. Why do you have "public_ip_address" for your RelayServer address This the address of a mail server through which you are choosing to relay mail - usually not *your* IP address or host name and often you don't need to relay at all.

That was another test I was running last night and I forgot to remove when pasting, please, ignore that setting.

Thanks for your help Rob.

RainManHood<---

---
* Synchronet * UNICYBER BBS -- bbs.unicyber.co.uk:2323::ssh bbs.unicyber.co.uk 2424
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 2018 Jun 19 22:40:10, you wrote to Rmh:

Guys,

Something a bit weird.


I got the POP3 service on at sbbs.ini

1. When you put tear-lines ("---") in your messages, that makes them difficult to quote. Use more or fewer dashes to fix that.

FWIW: FTN tear lines are three dashes and a space... not just three dashes ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Spam on Wonder bread.
---
* Origin: (1:3634/12.73)

Re: Weird issue with POP mail
By: mark lewis to Digital Man on Wed Jun 20 2018 12:01 pm

On 2018 Jun 19 22:40:10, you wrote to Rmh:

Guys,

Something a bit weird.


I got the POP3 service on at sbbs.ini

1. When you put tear-lines ("---") in your messages, that makes them difficult to quote. Use more or fewer dashes to fix that.

FWIW: FTN tear lines are three dashes and a space... not just three dashes ;)

That is an interesting observation, but I don't think that's actually part of any standard or FTSC specification (e.g. http://ftsc.org/docs/fts-0004.001) - or is it?

digital man

This Is Spinal Tap quote #20:
Well, I'm sure I'd feel much worse if I weren't under such heavy sedation. Norco, CA WX: 76.6oF, 59.0% humidity, 7 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: mark lewis to Digital Man on Wed Jun 20 2018 12:01 pm

1. When you put tear-lines ("---") in your messages, that makes them
difficult to quote. Use more or fewer dashes to fix that.

FWIW: FTN tear lines are three dashes and a space... not just three dashes ;)

Everybody calming down please..... We only need to piss Digital Man off..

the dashing thing has been done only with the intention of splitting the code bits from the rest of the conversation. Obviously without succeeding .

I will try to improve that part in the future as I wasn't aware of the dificulties that was generating.

Digital Man et all, if there are any other expectation in the way I communicate I accept comments as I would like to make all this fluid and I understand Rob (Digital Man) can get a bit frustrated with crappy style posts.

Anything at all, please, just cascade on. No harm on it.

Many thanks..

RainManHood<---

---
* Synchronet * UNICYBER BBS -- bbs.unicyber.co.uk:2323::ssh bbs.unicyber.co.uk 2424
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 2018 Jun 20 11:26:50, you wrote to me:

FWIW: FTN tear lines are three dashes and a space... not just three
dashes ;)

That is an interesting observation, but I don't think that's actually
part of any standard or FTSC specification (e.g. http://ftsc.org/docs/fts-0004.001) - or is it?

all FTN related software that i know of code a tear line as "--- " and then add
a possible banner of some kind... the trick when looking for them while displaying or replying to a message is to only deal with them if they are in the first column and if the 4th character is a space... i guess in your case, you are processing it only when it is in the first column and it is "three dashes" or "three dashes, a space and a possible banner"?

would it be less code to only look for "--- " starting in the first column and processing that as a tear line, banner or no?

eg: if substr(0,4,lineX) == "--- " then do #process tear line end;

removing unnecessary code is a GoodThing<tm> :)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... The bonds of matrimony are a good investment if the interest is kept up. ---
* Origin: (1:3634/12.73)

On 2018 Jun 20 17:29:32, you wrote to me:

1. When you put tear-lines ("---") in your messages, that makes them
difficult to quote. Use more or fewer dashes to fix that.

FWIW: FTN tear lines are three dashes and a space... not just three
dashes ;)

Everybody calming down please..... We only need to piss Digital Man off..

hehehe...

the dashing thing has been done only with the intention of splitting
the code bits from the rest of the conversation. Obviously without succeeding .

we understand that... the problem is that some editors try to be helpful and will tear off everything below what it thinks is a tear line...

I will try to improve that part in the future as I wasn't aware of the dificulties that was generating.

it is ok :)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Remember that the customs of your tribe are not laws of nature!
---
* Origin: (1:3634/12.73)

Re: Weird issue with POP mail
By: mark lewis to Digital Man on Wed Jun 20 2018 03:40 pm

On 2018 Jun 20 11:26:50, you wrote to me:

FWIW: FTN tear lines are three dashes and a space... not just three
dashes ;)

That is an interesting observation, but I don't think that's actually part of any standard or FTSC specification (e.g. http://ftsc.org/docs/fts-0004.001) - or is it?

all FTN related software that i know of code a tear line as "--- " and then add
a possible banner of some kind...

Okay, but doesn't make it an FTN standard.

the trick when looking for them while
displaying or replying to a message is to only deal with them if they are in the first column and if the 4th character is a space... i guess in your case, you are processing it only when it is in the first column and it is "three dashes" or "three dashes, a space and a possible banner"?

3 dashes startin column 1 followed by a space or a newline.

would it be less code to only look for "--- " starting in the first column and processing that as a tear line, banner or no?

It might, but I think "\r---\r" is a perfectly valid FTS-4 compliant tear line and my FTN-comliant software (e.g. SBBSecho) should recognize them, like it already does.

In any case, I think the message in question came in via QWK, where again, I treat both "\n---\n" and "\n--- " as valid tear-lines (and \n may be \r or the QWK-equivalent).

eg: if substr(0,4,lineX) == "--- " then do #process tear line end;

removing unnecessary code is a GoodThing<tm> :)

Not if it introduces a bug.

digital man

This Is Spinal Tap quote #46:
"Not an Exit" - we don't want an exit. Well that's true.
Norco, CA WX: 85.6oF, 45.0% humidity, 5 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: Rmh to mark lewis on Wed Jun 20 2018 05:29 pm

Everybody calming down please.....

Everybody's calm. :-)

digital man

Synchronet "Real Fact" #93:
Synchronet v3.16c was released in August of 2015 (5 years after v3.15b).
Norco, CA WX: 85.6oF, 45.0% humidity, 5 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: mark lewis to Rmh on Wed Jun 20 2018 04:49 pm

On 2018 Jun 20 17:29:32, you wrote to me:

1. When you put tear-lines ("---") in your messages, that makes them
difficult to quote. Use more or fewer dashes to fix that.

FWIW: FTN tear lines are three dashes and a space... not just three
dashes ;)

Everybody calming down please..... We only need to piss Digital Man off..

hehehe...

the dashing thing has been done only with the intention of splitting the code bits from the rest of the conversation. Obviously without succeeding .

we understand that... the problem is that some editors try to be helpful and will tear off everything below what it thinks is a tear line...

In this case, it's the message-importing code in Synchronet (specifically, for QWK, but the FTN msg import code in SBBSecho does the same): The Synchronet message base (SMB) stores message "bodies" and message "tails" separately to make processing them separately, easy (no additional parsing of tear/tag/origin lines needed when quoting or whatever). In this case, Rmh's message imported/stored as follows:

data field[0] TEXT_BODY, offset 0, length 76
data field[1] TEXT_TAIL, offset 76, length 2296

As you can, a very small message body (76 chars) and a large/long tail (the first "---" tear line on down). And when replying and quoting a message, only the message *body* text is included in the quoted text (normally). It's a rare problem, but it can happen.

digital man

Synchronet/BBS Terminology Definition #31:
ISDN = Integrated Services Digital Network
Norco, CA WX: 86.4oF, 43.0% humidity, 8 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: Rmh to Digital Man on Wed Jun 20 2018 08:23 am

Full configuration below:

[Mail] SMTP/POP3 Mail Server
AutoStart=true
MaxClients=10
MaxInactivity=120
Interface=89.47.163.252
LinesPerYield=10
MaxDeliveryAttempts=50
MaxRecipients=100
MaxMsgSize=20MB
MaxMsgsWaiting=100
RescanFrequency=3600
SMTPPort=25
SubmissionPort=587
TLSSubmissionPort=465
POP3Interface=89.47.163.252
POP3Port=110
TLSPOP3Port=995
DefaultCharset=IBM437
DefaultUser=
DNSBlacklistHeader=X-DNSBL
DNSBlacklistSubject=SPAM
RelayServer=
RelayPort=25
RelayUsername=
RelayPassword=
DNSServer=
POP3Sound=
InboundSound=
OutboundSound=
ConnectTimeout=30
Options=DNSBL_REFUSE | DNSBL_IGNORE |DNSBL_BADUSER | DNSBL_THROTTLE | DNSBL_SPAMHASH | DEBUG_TX | DEBUG_POP | ALLOW_POP3
MaxClients=10
MaxInactivity=300
QwkTimeout=600
MinFileSize=0
MaxFileSize=0
Interface=89.47.163.252

Digital Man, above mail COnfiguration. (getting back to the question as I got emails stuck trying to send through 127.0.0.1)

Suggestions?
Possiblities of using some other interface rather than the loopback?

Many thanks

RainManHood<---

---
* Synchronet * UNICYBER BBS -- bbs.unicyber.co.uk:2323::ssh bbs.unicyber.co.uk 2424
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: Rmh to Digital Man on Thu Jun 21 2018 05:16 am

Re: Weird issue with POP mail
By: Rmh to Digital Man on Wed Jun 20 2018 08:23 am

Full configuration below:

[Mail] SMTP/POP3 Mail Server
AutoStart=true
MaxClients=10
MaxInactivity=120
Interface=89.47.163.252
LinesPerYield=10
MaxDeliveryAttempts=50
MaxRecipients=100
MaxMsgSize=20MB
MaxMsgsWaiting=100
RescanFrequency=3600
SMTPPort=25
SubmissionPort=587
TLSSubmissionPort=465
POP3Interface=89.47.163.252
POP3Port=110
TLSPOP3Port=995
DefaultCharset=IBM437
DefaultUser=
DNSBlacklistHeader=X-DNSBL
DNSBlacklistSubject=SPAM
RelayServer=
RelayPort=25
RelayUsername=
RelayPassword=
DNSServer=
POP3Sound=
InboundSound=
OutboundSound=
ConnectTimeout=30
Options=DNSBL_REFUSE | DNSBL_IGNORE |DNSBL_BADUSER | DNSBL_THROTTLE | DNSBL_SPAMHASH | DEBUG_TX | DEBUG_POP | ALLOW_POP3
MaxClients=10
MaxInactivity=300

The following key=value pairs look like they should be part of the [ftp] section of your sbbs.ini (not in the [mail] section):

QwkTimeout=600
MinFileSize=0
MaxFileSize=0
Interface=89.47.163.252

Digital Man, above mail COnfiguration.

I don't notice anything wrong with the mail server configuration.

(getting back to the question as I
got emails stuck trying to send through 127.0.0.1)

Suggestions?
Possiblities of using some other interface rather than the loopback?

Please send the relevant log lines. Sending email is not related to POP3 or "POP mail".

digital man

This Is Spinal Tap quote #16:
David St. Hubbins: I believe virtually everything I read...
Norco, CA WX: 85.0oF, 48.0% humidity, 8 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 2018 Jun 20 14:23:18, you wrote to me:

FWIW: FTN tear lines are three dashes and a space... not just three
dashes ;)

That is an interesting observation, but I don't think that's
actually part of any standard or FTSC specification (e.g.
http://ftsc.org/docs/fts-0004.001) - or is it?

all FTN related software that i know of code a tear line as "--- "
and then add a possible banner of some kind...

Okay, but doesn't make it an FTN standard.

-=B-) ok, so a psuedo standard... that is, after all, how all fidonet standards come about ;)

the trick when looking for them while displaying or replying to a
message is to only deal with them if they are in the first column and
if the 4th character is a space... i guess in your case, you are
processing it only when it is in the first column and it is "three
dashes" or "three dashes, a space and a possible banner"?

3 dashes startin column 1 followed by a space or a newline.

yeah, that's what i was trying to say...

would it be less code to only look for "--- " starting in the first
column and processing that as a tear line, banner or no?

It might, but I think "\r---\r" is a perfectly valid FTS-4 compliant
tear line and my FTN-comliant software (e.g. SBBSecho) should
recognize them, like it already does.

yeah, "\r--- (\r)?" might be a better match?

In any case, I think the message in question came in via QWK, where
again, I treat both "\n---\n" and "\n--- " as valid tear-lines (and \n
may be \r or the QWK-equivalent).

yeah, QWK does throw some hoops into things, doesn't it :)

eg: if substr(0,4,lineX) == "--- " then do #process tear line end;

removing unnecessary code is a GoodThing<tm> :)

Not if it introduces a bug.

there is that :)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... We are professionals: don't attempt this on your own PC!
---
* Origin: (1:3634/12.73)

On 2018 Jun 20 14:30:44, you wrote to me:

the dashing thing has been done only with the intention of splitting
the code bits from the rest of the conversation. Obviously without
succeeding .

we understand that... the problem is that some editors try to be
helpful and will tear off everything below what it thinks is a tear
line...

In this case, it's the message-importing code in Synchronet (specifically, for QWK, but the FTN msg import code in SBBSecho does the same):

believe it or not, the tear line in fidonet was originally used exactly for tearing off everything below it during message importing... this was to save precious drive space back then... folks only wanted the header and the actual message content... no signatures, signature blocks or tag lines (which really didn't even exist back then)...

The Synchronet message base (SMB) stores message "bodies" and message "tails" separately to make processing them separately, easy (no
additional parsing of tear/tag/origin lines needed when quoting or whatever).

sounds kinda similar to JAM message bases :)

JAM puts the message body, including the tear, tag, and origin lines into the JDT file... the header and control data go into the JHR file... then there's a JDX index file holding pointers into the JDT and JHR files and lastly a JLR contain the two last read pointers for each user...

In this case, Rmh's message imported/stored as follows:

data field[0] TEXT_BODY, offset 0, length 76
data field[1] TEXT_TAIL, offset 76, length 2296

yeah! hehehe...

As you can, a very small message body (76 chars) and a large/long tail (the first "---" tear line on down). And when replying and quoting a message, only the message *body* text is included in the quoted text (normally). It's a rare problem, but it can happen.

yeah, i think i've seen it before... kinda like the one format of messages that
we had/have to use RAW mode to view them properly... i forget the details on that but we discussed it several years back :)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Assumption is the mother of all screwups.
---
* Origin: (1:3634/12.73)

Re: Weird issue with POP mail
By: Digital Man to Rmh on Thu Jun 21 2018 02:35 pm

Please send the relevant log lines. Sending email is not related to POP3 or "POP mail".

22 06:51:51 34819 sbbs: 6/22 06:51:51 term Node 2 sysopo sent Internet Mail to user (user@bbs.Unicyber.Co.Uk)
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0000 SEND Message #386 (1 of 2) from sysopo #1 sysopo@bbs.unicyber.co.uk to user [user@bbs.Unicyber.Co.Uk]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 SEND connecting to port 25 on 127.0.0.1 [127.0.0.1]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND ERROR 111 connecting to SMTP server: 127.0.0.1
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND Delivery attempt #45 FAILED (ERROR 111 connecting to SMTP server: 127.0.0.1) for message #386 from sysopo to user@bbs.Unicyber.Co.Uk
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0000 SEND Message #389 (2 of 2) from sysopo #1 sysopo@bbs.unicyber.co.uk to user [user@bbs.Unicyber.Co.Uk]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 SEND skipping failed SMTP server: Error 111 connecting to port 25 on 127.0.0.1 [127.0.0.1]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND Delivery attempt #1 FAILED (Error 111 connecting to port 25 on 127.0.0.1 [127.0.0.1]) for message #389 from sysopo to user@bbs.Unicyber.Co.Uk


Sending emails to users registered in the BBS, "apparently" it uses the localhost . (I cannot be completely sure, but that's what it looks like..)

Many thanks Digital Man.

RainManHood<---

---
* Synchronet * UNICYBER BBS -- bbs.unicyber.co.uk:2323::ssh bbs.unicyber.co.uk 2424
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: mark lewis to Digital Man on Thu Jun 21 2018 12:15 pm

The Synchronet message base (SMB) stores message "bodies" and message "tails" separately to make processing them separately, easy (no additional parsing of tear/tag/origin lines needed when quoting or whatever).

sounds kinda similar to JAM message bases :)

I don't recall that detail about JAM. I definitely looked at JAM (and Squish and others) before creating SMB and took some inspirations from them but have since forgot the details of those other message base formats.

digital man

Synchronet "Real Fact" #96:
Synchronet v3.13a was released in September of 2005 (9 months after v3.12a). Norco, CA WX: 60.5oF, 93.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: Rmh to Digital Man on Fri Jun 22 2018 06:59 am

Re: Weird issue with POP mail
By: Digital Man to Rmh on Thu Jun 21 2018 02:35 pm

Please send the relevant log lines. Sending email is not related to POP3 or "POP mail".

22 06:51:51 34819 sbbs: 6/22 06:51:51 term Node 2 sysopo sent Internet Mail to user (user@bbs.Unicyber.Co.Uk)

Is "bbs.unicyber.co.uk" your BBS's address? If so, I'm not clear why would do this.

Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0000 SEND Message #386 (1 of 2) from sysopo #1 sysopo@bbs.unicyber.co.uk to user [user@bbs.Unicyber.Co.Uk]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 SEND connecting to port 25 on 127.0.0.1 [127.0.0.1]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND ERROR 111 connecting to SMTP server: 127.0.0.1
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND Delivery attempt #45 FAILED (ERROR 111 connecting to SMTP server: 127.0.0.1) for message #386 from sysopo to user@bbs.Unicyber.Co.Uk
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0000 SEND Message #389 (2 of 2) from sysopo #1 sysopo@bbs.unicyber.co.uk to user [user@bbs.Unicyber.Co.Uk]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 SEND skipping failed SMTP server: Error 111 connecting to port 25 on 127.0.0.1 [127.0.0.1]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND Delivery attempt #1 FAILED (Error 111 connecting to port 25 on 127.0.0.1 [127.0.0.1]) for message #389 from sysopo to user@bbs.Unicyber.Co.Uk

Sending emails to users registered in the BBS, "apparently" it uses the localhost . (I cannot be completely sure, but that's what it looks like..)

Yes, if you your mail server sees an *outbound* email destined for one of the domain names listed in your ctrl/domains.cfg file or the address from SCFG->Internet->Address, it just connects to localhost to deliver it.

If you want to send email to the users of your BBS, don't "netmail" from the terminal server (e.g. to "user@somewhere"), just regular email to "user".

digital man

Synchronet "Real Fact" #40:
Synchronet has been ported to FreeBSD, NetBSD, OpenBSD, Solaris, QNX, and MacOS.
Norco, CA WX: 60.4oF, 93.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.05-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: Rmh to Digital Man on Fri Jun 22 2018 06:59 am

Re: Weird issue with POP mail
By: Digital Man to Rmh on Thu Jun 21 2018 02:35 pm

Please send the relevant log lines. Sending email is not related to
POP3 or "POP mail".

22 06:51:51 34819 sbbs: 6/22 06:51:51 term Node 2 sysopo sent Internet Mail to user (user@bbs.Unicyber.Co.Uk)
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0000 SEND Message #386 (1 of 2) from sysopo #1 sysopo@bbs.unicyber.co.uk to user [user@bbs.Unicyber.Co.Uk] Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 SEND connecting to port 25 on 127.0.0.1 [127.0.0.1]
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND ERROR 111 connecting to SMTP server: 127.0.0.1
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND Delivery attempt #45 FAILED (ERROR 111 connecting to SMTP server: 127.0.0.1) for message #386 from sysopo to user@bbs.Unicyber.Co.Uk
Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0000 SEND Message #389 (2 of 2) from sysopo #1 sysopo@bbs.unicyber.co.uk to user [user@bbs.Unicyber.Co.Uk] Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 SEND skipping failed SMTP server: Error 111 connecting to port 25 on 127.0.0.1 [127.0.0.1] Jun 22 06:51:53 34819 sbbs: 6/22 06:51:53 mail 0046 !SEND Delivery attempt #1 FAILED (Error 111 connecting to port 25 on 127.0.0.1 [127.0.0.1]) for message #389 from sysopo to user@bbs.Unicyber.Co.Uk

src/sbbs3/mailsrvr.c

SAFEPRINTF(domain_list,"%sdomains.cfg",scfg.ctrl_dir);
if(stricmp(p,scfg.sys_inetaddr)==0
|| stricmp(p,startup->host_name)==0
|| findstr(p,domain_list)) {
/* This is a local message... no need to send to remote */
port = startup->smtp_port;
/* TODO: IPv6 */
if(startup->outgoing4.s_addr==0)
server="127.0.0.1";
else {
SAFEPRINTF4(numeric_ip, "%u.%u.%u.%u"
, startup->outgoing4.s_addr >> 24
, (startup->outgoing4.s_addr >> 16) & 0xff
, (startup->outgoing4.s_addr >> 8) & 0xff
, startup->outgoing4.s_addr & 0xff);
server = numeric_ip;
}
sending_locally=TRUE;
}


maybe to have a choice whether to send the email from another interface? to setup the "server" as another variable being localhost the default one?

Many thanks Digital Man.

RainManHood<---

---
* Synchronet * UNICYBER BBS -- bbs.unicyber.co.uk:2323::ssh bbs.unicyber.co.uk 2424
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Weird issue with POP mail
By: Digital Man to Rmh on Fri Jun 22 2018 01:42 am

Sending emails to users registered in the BBS, "apparently" it uses
the
localhost . (I cannot be completely sure, but that's what it looks like..)

Yes, if you your mail server sees an *outbound* email destined for one of the domain names listed in your ctrl/domains.cfg file or the address from SCFG->Internet->Address, it just connects to localhost to deliver it.

aha!! Detail I was missing... (recording that bit..)

If you want to send email to the users of your BBS, don't "netmail" from the terminal server (e.g. to "user@somewhere"), just regular email to "user".

Ok then.... I will do that.
Yes, I was try to send an email from the terminal (not a netmail), so it was trying to use the SMTP for localhost which I do not have available for sbbs.

Note that I got multiple interfaces and I am dedicating just one entirely to SBBS , reason why I wanted to use that interface instead of the localhost as I am sure you can understand. That has been the core reason for my question and what I wanted to achieve.

I might change that bit only for my particular scenario but I understand what you mean .

Very much appreciated Digital Man.

RainManHood<---

---
* Synchronet * UNICYBER BBS -- bbs.unicyber.co.uk:2323::ssh bbs.unicyber.co.uk 2424
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 06-22-18 14:26, Rmh wrote to Digital Man <=-

Note that I got multiple interfaces and I am dedicating just one
entirely to SBBS , reason why I wanted to use that interface instead of the localhost as I am sure you can understand. That has been the core reason for my question and what I wanted to achieve.

I would have the same problem. Normally, all mail servers loop up MX records, or are able to have known domains (like the local system) configured. Assuming localhost doesn't always work. I haven't actually struck that issue, because I haven't tried to email myself (something I would normally only do for a test, or occasionally as a memory jog).


... You may start by impressing - _ME_ !! - Worf
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)