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=[email protected]> to <[email protected]>
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?
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=[email protected]> to <[email protected]>
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 '[email protected]' <REDACTED1>
Aug 12 21:37:38 d-11-1 synchronet: mail 0000 SEND Message #4944 (383 of 383) from 'Deon George' <bt.e2013xrc30=4ns5qw4x12kd=[email protected]> to '[email protected]' <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=[email protected]>
Aug 12 21:37:41 d-11-1 synchronet: mail 0180 SEND !Delivery failure notification (message #4945) created for <bt.e2013xrc30=4ns5qw4x12kd=[email protected]>
I assuming the forwarding failed, because the email wasnt actually from [email protected], it was from <REDACTED>
Anyway to fix that?
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 "..".
I assuming the forwarding failed, because the email wasnt actually from [email protected], it was from <REDACTED>You want to change the from address for fowarded messages?
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 '[email protected]' <REDACTED1>
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 [email protected], it was from <REDACTED>You want to change the from address for fowarded messages?
No.
The "actual" from addresss is [email protected], but for some reason an upstream mailer is probably setting some headers, that is making synchronet think it is "from" bt.e2013xrc30=4ns5qw4x12kd=[email protected], 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 [email protected], 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 '[email protected]' <REDACTED1>
IE: If the message is from [email protected] to [email protected], and you configure synchronet to forward [email protected] to [email protected], is looks like synchronet is attempt to send it as [email protected] to [email protected], 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 [email protected].
It should be forwarding the message from [email protected] to [email protected].
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.
Create an issue on gitlab.synchro.net with those details and I'll try to reproduce and resolve that issue later.
| Sysop: | Coz |
|---|---|
| Location: | Anoka, MN |
| Users: | 2 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 112:38:14 |
| Calls: | 162 |
| Files: | 5,327 |
| Messages: | 222,469 |