Ever since SmarterMail 16.3.6535 and up to and including SmarterMail 16.3.6551 there have been more problems created than fixed. What is going on?
I have had tons of complaints about people not getting mail as SM is just dumping it with false flags of Bad SPF...
Specifically mail to an ALIAS that goes to an email on the same domain...
This was sent from a Gmail address to an ALIAS address (We know it should NOT fail with BAD SPF)
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] rsp: 220 mail1.domain.net
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] connected at 12/10/2017 6:26:38 PM
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] cmd: EHLO mail-qt0-f180.google.com
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] rsp: 250-mail1.domain.net Hello [209.85.216.180]250-SIZE 52428800250-AUTH LOGIN CRAM-MD5250-8BITMIME250 OK
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] cmd: MAIL FROM:<originemail@gmail.com> SIZE=2375
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] rsp: 250 OK <originemail@gmail.com> Sender ok
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] cmd: RCPT TO:<aliasaddress@domain.com>
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] rsp: 250 OK <aliasaddress@domain.com> Recipient ok
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] cmd: DATA
[2017.12.10] 18:26:38 [xxx.85.xxx.180][57222228] rsp: 354 Start mail input; end with <CRLF>.<CRLF>
[2017.12.10] 18:26:50 [xxx.85.xxx.180][57222228] rsp: 250 OK
[2017.12.10] 18:26:50 [xxx.85.xxx.180][57222228] Successfully wrote to the HDR file. (d:\SmarterMail\Spool\SubSpool2\14344161.hdr)
[2017.12.10] 18:26:50 [xxx.85.xxx.180][57222228] Data transfer succeeded, writing mail to 14344161.eml
[2017.12.10] 18:26:50 [xxx.85.xxx.180][57222228] cmd: QUIT
[2017.12.10] 18:26:50 [xxx.85.xxx.180][57222228] rsp: 221 Service closing transmission channel
[2017.12.10] 18:26:50 [xxx.85.xxx.180][57222228] disconnected at 12/10/2017 6:26:50 PM
The above was the message to an alias and it never gets delivered proper forwarding address but deleted in the next step for buggy programing reasons... below you can see was failed on SPF which we know it should not...
[2017.12.10] 18:26:56 [44161] Spam check results: [_REVERSEDNSLOOKUP: passed], [_SPF: Fail], [_DK: None], [_DKIM: Pass], [BARRACUDA - BRBL: passed], [CBL - ABUSE SEAT: passed], [HOSTKARMA - BLACKLIST: passed], [HOSTKARMA - BROWNLIST: passed], [MAILSPIKE Z: passed], [SEM-URIBL: passed], [SEM-URIRED: passed], [SORBS - ABUSE: passed], [SORBS - DYNAMIC IP: passed], [SORBS - PROXY: passed], [SORBS - RECENT: failed], [SORBS - SMTP: passed], [SORBS - SOCKS: passed], [SPAMCOP: passed], [SPAMHAUS - CBL: passed], [SPAMHAUS - CSS: passed], [SPAMHAUS - PBL: passed], [SPAMHAUS - PBL2: passed], [SPAMHAUS - SBL: passed], [SPAMRATS: passed], [SURBL - ABUSE BUSTER: passed], [SURBL - JWSPAMSPY: passed], [SURBL - MALWARE: passed], [SURBL - SA BLACKLIST: passed], [SURBL - SPAMCOP WEB: passed], [SURBL -PHISHING: passed], [SURRIEL: passed], [UCEPROTECT LEVEL 1: passed], [UCEPROTECT LEVEL 2: passed], [UCEPROTECT LEVEL 3: passed], [URIBL - BLACK: passed], [URIBL - GREY: passed], [URIBL - MULTI: passed], [URIBL - RED: passed], [VIRUS RBL - MSRBL: passed]
[2017.12.10] 18:26:59 [44161] Starting local delivery to actualaddress@domain.com
[2017.12.10] 18:26:59 [44161] Delivery for to actualaddress@domain.com has completed (Deleted) Filter: Spam (Weight: 21), Action (Global Level): Delete
[2017.12.10] 18:26:59 [44161] End delivery to actualaddress@domain.com
[2017.12.10] 18:26:59 [44161] Delivery finished for at 6:26:59 PM [id:14344161]
SM is failing SPF on who knows how many emails as they are just dumped out of the spool.
Now if the exact same message is sent to the actualaddress@domain.com vs the aliasaddress@domain.com the the mail gets delivered fine... SOMETIMES...
For instance one client gets a lot of mail from ETSY.com for their store... and ever since 16.3.6535 sometimes they get mail other times they don't... sometimes SPF fails other times I don't know where it goes but it does not get delivered...
SmarterMail 16 is becoming unusable in its current state... I have been using SM since version 5 and never had any problems like everyone is having now... the bugs need to be fixed STAT.
Regards,
Mark L. Lee