1. Forum
  2. USENET
  3. alt.bbs.synchronet

  • Email marked as Spam.

    From deon@deon@ALTERANT.remove-84k-this to Digital Man on Wed Aug 24 21:31:16 2022
    From Newsgroup: alt.bbs.synchronet

    To: Digital Man
    Howdy,

    I've noticed that some of my email, coming from an internal spam filter is being marked as spam:

    Aug 24 21:13:05 d-11-1 synchronet: mail 0082 SMTP DNSBL Query: 9.5.7.9.9.d.e.f.f.f.9.2.c.0.2.0.4.9.4.2.4.1.3.0.0.0.4.3.6.0.4.2.sbl.spamhaus.org resolved to: 127.255.255.254
    Aug 24 21:13:05 d-11-1 synchronet: mail 0082 SMTP [2406:3400:314:2494:20c:29ff:fed9:9759] BLACKLISTED SERVER on sbl.spamhaus.org (see http://www.spamhaus.org/): <no name> = 127.255.255.254
    Aug 24 21:13:06 d-11-1 synchronet: mail 0082 SMTPS [2406:3400:314:2494:20c:29ff:fed9:9759] Receiving mail message from <bt.wubhkdac30=ezymsq56sigp=eh3dkymm2l@em427968.dlcm.co> to <deon.george@bbs.leenooks.net>

    According to spamhaus, 127.255.255.254 is not a confirmation of SPAM (https://www.spamhaus.org/news/article/807/using-our-public-mirrors-check-your-return-codes-now.) , but rather an indication that the system querying its services do not provide a rDNS. So is there a way to not mark this as spam?

    I tried to update the spamblock_exempt.cfg with the relays IPv6 address (..:9759), but it doesnt seem to make a difference. Does this accept IPv6 addresses?

    On a related topic, I tried to enable email forwarding to another email that I read more often, but mail never made it.

    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Forwarding to: <REDACTED1>
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Receiving mail message from <bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co> to <deon.george@bbs.leenooks.net>
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] End of message (body: 22 lines, 902 bytes, header: 67 lines, 4136 bytes)
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] End of message (body: 22 lines, 902 bytes, header: 67 lines, 4136 bytes)
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Executing external mail processor: MailAuth
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Added message header #4944 from 'Deon George' <REDACTED> to 'deon.george@bbs.leenooks.net' <REDACTED1>

    Aug 12 21:37:38 d-11-1 synchronet: mail 0000 SEND Message #4944 (383 of 383) from 'Deon George' <bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co> to 'deon.george@bbs.leenooks.net' <REDACTED1>
    Aug 12 21:37:38 d-11-1 synchronet: mail 0180 SEND connecting to port 2525 on mail.smtp2go.com [173.255.233.87]
    Aug 12 21:37:40 d-11-1 synchronet: mail 0180 SEND TLS Session started successfully
    Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND/TLS !INVALID RESPONSE: '550 app.smtp2go.com.' Expected: '25'
    Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND !Delivery attempt #1 FAILED (mail.smtp2go.com replied with: "550 app.smtp2go.com." instead of the expected reply: "25* ...") for message #4944 from Deon George to REDACTED1
    Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND !Bouncing message back to <bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co>
    Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND !Delivery failure notification (message #4945) created for <bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co>

    I assuming the forwarding failed, because the email wasnt actually from bt.e2013...@...dlcm.co, it was from <REDACTED>

    Anyway to fix that?


    ...ëîåï

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!
    --- Synchronet 3.19c-Linux NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Digital Man@digital.man@vert.synchro.net.remove-6jy-this to deon on Wed Aug 24 12:52:14 2022
    From Newsgroup: alt.bbs.synchronet

    To: deon
    Re: Email marked as Spam.
    By: deon to Digital Man on Wed Aug 24 2022 09:31 pm

    Howdy,

    I've noticed that some of my email, coming from an internal spam filter is being marked as spam:

    Aug 24 21:13:05 d-11-1 synchronet: mail 0082 SMTP DNSBL Query: 9.5.7.9.9.d.e.f. f.f.9.2.c.0.2.0.4.9.4.2.4.1.3.0.0.0.4.3.6.0.4.2.sbl.spamhaus.org resolved to: 127.255.255.254
    Aug 24 21:13:05 d-11-1 synchronet: mail 0082 SMTP [2406:3400:314:2494:20c:29ff:fed9:9759] BLACKLISTED SERVER on sbl.spamhaus.org (see http://www.spamhaus.org/): <no name> = 127.255.255.254 Aug 24 21:13:06 d-11-1 synchronet: mail 0082 SMTPS [2406:3400:314:2494:20c:29ff:fed9:9759] Receiving mail message from <bt.wubhkdac30=ezymsq56sigp=eh3dkymm2l@em427968.dlcm.co> to <deon.george@bbs.leenooks.net>

    According to spamhaus, 127.255.255.254 is not a confirmation of SPAM (https://w ww.spamhaus.org/news/article/807/using-our-public-mirrors-check-y our-return-cod es-now.) , but rather an indication that the system querying its services do not provide a rDNS. So is there a way to not mark this as spam?

    Not in the current Synchronet mail server: it treats any non-zero DNSBL result as "positive".

    I tried to update the spamblock_exempt.cfg with the relays IPv6 address (..:9759), but it doesnt seem to make a difference. Does this accept IPv6 addresses?

    It does appear so, yes. Wildcards should be supported too, but not "..".

    On a related topic, I tried to enable email forwarding to another email that I read more often, but mail never made it.

    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Forwarding to: <REDACTED1>
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Receiving mail message from <bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co> to <deon.george@bbs.leenooks.net>
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] End of message (body: 22 lines, 902 bytes, header: 67 lines, 4136 bytes)
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] End of message (body: 22 lines, 902 bytes, header: 67 lines, 4136 bytes)
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Executing external mail processor: MailAuth
    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Added message header #4944 from 'Deon George' <REDACTED> to 'deon.george@bbs.leenooks.net' <REDACTED1>

    Aug 12 21:37:38 d-11-1 synchronet: mail 0000 SEND Message #4944 (383 of 383) from 'Deon George' <bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co> to 'deon.george@bbs.leenooks.net' <REDACTED1>
    Aug 12 21:37:38 d-11-1 synchronet: mail 0180 SEND connecting to port 2525 on mail.smtp2go.com [173.255.233.87]
    Aug 12 21:37:40 d-11-1 synchronet: mail 0180 SEND TLS Session started successfully
    Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND/TLS !INVALID RESPONSE: '550 app.smtp2go.com.' Expected: '25'
    Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND !Delivery attempt #1 FAILED (mail.smtp2go.com replied with: "550 app.smtp2go.com." instead of the expected reply: "25* ...") for message #4944 from Deon George to REDACTED1 Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND !Bouncing message back to <bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co>
    Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND !Delivery failure notification (message #4945) created for <bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co>

    I assuming the forwarding failed, because the email wasnt actually from bt.e2013...@...dlcm.co, it was from <REDACTED>

    Anyway to fix that?

    You want to change the from address for fowarded messages?
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #5:
    ATASCII = ATARI Standard Code for Information Interchange
    Norco, CA WX: 90.4øF, 48.0% humidity, 4 mph ESE wind, 0.00 inches rain/24hrs --- Synchronet 3.19c-Linux NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From deon@deon@ALTERANT.remove-jau-this to Digital Man on Thu Aug 25 09:00:20 2022
    From Newsgroup: alt.bbs.synchronet

    To: Digital Man
    Re: Email marked as Spam.
    By: Digital Man to deon on Wed Aug 24 2022 12:52 pm

    I tried to update the spamblock_exempt.cfg with the relays IPv6 address (..:9759), but it doesnt seem to make a difference.
    Does this accept IPv6 addresses?

    It does appear so, yes. Wildcards should be supported too, but not "..".

    OK, so it isnt working. (And I'm not using ".." literally, I just didnt want to retype the IPv6 address. It is listed there in full, as well as the /60 CIDR. Mail coming from my relay is still being marked as spam.

    Here is the contents of my spamblock_exempt.cfg
    2406:3400:314:2490::/60
    2406:3400:314:2497:f1d0::1
    2406:3400:314:2494:20c:29ff:fed9

    I assuming the forwarding failed, because the email wasnt actually from bt.e2013...@...dlcm.co, it was from <REDACTED>
    You want to change the from address for fowarded messages?

    No.

    The "actual" from addresss is xxxx@xxx.co, but for some reason an upstream mailer is probably setting some headers, that is making synchronet think it is "from" bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co, or sbbs is using that header as the "from" address when forwarding it on.

    When a receipent "reads" the email, it shows the correct from address xxxx@xxx.co, and even in the logs it reports the correct from address, but it is sending it from the bt.e2... address for some reason:

    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Added message header #4944 from 'Deon George'
    <REDACTED> to 'deon.george@bbs.leenooks.net' <REDACTED1>

    IE: If the message is from bill@example.com to bob@example.com, and you configure synchronet to forward bob@example.com to john@example.com, is looks like synchronet is attempt to send it as interal_tracking@tracking.example.com to john@example.com, and since tracking.example.com is a valid email address used by an upstream provider to track bounces it is rejecting the message because it didnt send an email with that tracking ID to john@example.com.

    It should be forwarding the message from bill@example.com to john@example.com.





    ...ëîåï

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!
    --- Synchronet 3.19c-Linux NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Digital Man@digital.man@vert.synchro.net.remove-ywe-this to deon on Wed Aug 24 18:50:00 2022
    From Newsgroup: alt.bbs.synchronet

    To: deon
    Re: Email marked as Spam.
    By: deon to Digital Man on Thu Aug 25 2022 09:00 am

    Re: Email marked as Spam.
    By: Digital Man to deon on Wed Aug 24 2022 12:52 pm

    I tried to update the spamblock_exempt.cfg with the relays IPv6 address (..:9759), but it doesnt seem to make a difference. Does this accept IPv6 addresses?

    It does appear so, yes. Wildcards should be supported too, but not "..".

    OK, so it isnt working. (And I'm not using ".." literally, I just didnt want to retype the IPv6 address. It is listed there in full, as well as the /60 CIDR.

    The CIDR notation is not currently support for IPv6 addresses.

    Mail coming from my relay is still being marked as spam.

    Here is the contents of my spamblock_exempt.cfg
    2406:3400:314:2490::/60
    2406:3400:314:2497:f1d0::1
    2406:3400:314:2494:20c:29ff:fed9

    The IPv6 address matching in that file is just like any other string match (e.g. "2406:3400:314*" won't match "2406:3400:0314*"), could that be the issue? You can also experiment with the JavaScript system.findstr("spamblock_exempt.cfg", <ip-addr>) to see how/if the matching works. It's the same underlying code used in the mail server to check for exempt addresses.

    I assuming the forwarding failed, because the email wasnt actually from bt.e2013...@...dlcm.co, it was from <REDACTED>
    You want to change the from address for fowarded messages?

    No.

    The "actual" from addresss is xxxx@xxx.co, but for some reason an upstream mailer is probably setting some headers, that is making synchronet think it is "from" bt.e2013xrc30=4ns5qw4x12kd=6lyqyydln5@em427968.dlcm.co, or sbbs is using that header as the "from" address when forwarding it on.

    When a receipent "reads" the email, it shows the correct from address xxxx@xxx.co, and even in the logs it reports the correct from address, but it is sending it from the bt.e2... address for some reason:

    Aug 12 21:37:36 d-11-1 synchronet: mail 0177 SMTPS [2406:3400:314:2497:f1d0::1] Added message header #4944 from 'Deon George' <REDACTED> to 'deon.george@bbs.leenooks.net' <REDACTED1>

    IE: If the message is from bill@example.com to bob@example.com, and you configure synchronet to forward bob@example.com to john@example.com, is looks like synchronet is attempt to send it as interal_tracking@tracking.example.com to john@example.com, and since tracking.example.com is a valid email address used by an upstream provider to track bounces it is rejecting the message because it didnt send an email with that tracking ID to john@example.com.

    It should be forwarding the message from bill@example.com to john@example.com.

    Create an issue on gitlab.synchro.net with those details and I'll try to reproduce and resolve that issue later.

    I'm pretty sure there's no change to message headers when forwarding email messages with the mail server, but perhaps the envelope (the SMTP 'MAIL FROM' address) could change.
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #4:
    ASCIIZ = NUL ('\0') terminated string/array of ASCII characters
    Norco, CA WX: 80.9øF, 61.0% humidity, 5 mph S wind, 0.00 inches rain/24hrs
    --- Synchronet 3.19c-Linux NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From deon@deon@ALTERANT.remove-45p-this to Digital Man on Fri Aug 26 23:00:43 2022
    From Newsgroup: alt.bbs.synchronet

    To: Digital Man
    Re: Email marked as Spam.
    By: Digital Man to deon on Wed Aug 24 2022 06:50 pm

    Mail coming from my relay is still being marked as spam.

    Here is the contents of my spamblock_exempt.cfg
    2406:3400:314:2490::/60
    2406:3400:314:2497:f1d0::1
    2406:3400:314:2494:20c:29ff:fed9

    The IPv6 address matching in that file is just like any other string match (e.g. "2406:3400:314*" won't match
    "2406:3400:0314*"),
    could that be the issue? You can also experiment with the JavaScript system.findstr("spamblock_exempt.cfg", <ip-addr>) to see
    how/if the matching works. It's the same underlying code used in the mail server to check for exempt addresses.

    So I dont think it is the issue:

    I've changed my spamblock_exempt.cfg to have: 2406:3400:314:2494:20c:29ff:fed9:9759
    2406:3400:0314:2494:020c:29ff:fed9:9759

    Aug 26 22:58:25 d-11-1 synchronet: mail 0097 SMTP [2406:3400:314:2494:20c:29ff:fed9:9759] BLACKLISTED SERVER on sbl.spamhaus.org (see http://www.spamhaus.org/): <no name> = 127.255.255.254

    jsexec -r "system.findstr('spamblock_exempt.cfg', '2406:3400:314:2494:20c:29ff:fed9:9759')"
    Result (boolean): true

    jsexec -r "system.findstr('spamblock_exempt.cfg', '2406:3400:0314:2494:020c:29ff:fed9:9759')"
    Result (boolean): true

    Create an issue on gitlab.synchro.net with those details and I'll try to reproduce and resolve that issue later.

    OK, I'll capture a full message with headers as something to work with...



    ...ëîåï

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!
    --- Synchronet 3.19c-Linux NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113