Section One BBS

Welcome, Guest.


Subject: Email marked as Spam. Date: Wed Aug 24 2022 06:50 pm
From: Digital Man 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 c
an also experiment with the JavaScript system.findstr("spamblock_exempt.cfg", <i
p-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 reprodu
ce and resolve that issue later.

I'm pretty sure there's no change to message headers when forwarding email messa
ges 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

---
 ■ SynchronetVertrauen Home of Synchronet [vert/cvs/bbs].synchro.net

Previous Message       Next Message
In Reply To: Email marked as Spam. (deon)
Replies: Email marked as Spam. (deon)