Look at the message below: Aug-24-16 12:15:32 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> info: found message size announcement: 19.47 kByte Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] Whitelisted sender Domain: [email protected] Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] Whitelisted sender address: [email protected] for recipient [email protected] Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] info: found known good HELO 'mailing.plopsafun.be' - weight is -2 Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] Message-Score: added -40 for KnownGoodHelo, total score for this message is now -40 Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] strictspf Regex: strictSPFRe '@gmail.com' Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] blockspf Regex: blockstrictSPFRe '@gmail.com' Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] [scoring] SPF: softfail ip=176.62.160.58 [email protected] helo=mailing.plopsafun.be Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] Message-Score: added 21 (spfValencePB) for SPF softfail, total score for this message is now -19 Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] [SPF] 176.62.160.58 <[email protected]> to: [email protected] [spam found] (SPF softfail - strict) [RE Korting] -> /var/db/assp/spam/RE_Korting--44072.eml; Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] [SMTP Error] 554 5.7.1 failed SPF: gmail.com ... _spf.google.com: Sender is not authorized by default to use '[email protected]' in 'mfrom' identity, however domain is not currently prepared for false failures (mechanism '~all' matched) Aug-24-16 12:15:33 m1-33732-13084 [Worker_3] 176.62.160.58 <[email protected]> to: [email protected] info: PB-IP-Score for '176.62.160.0' is 21, added 21 in this session
How can I whitelist this particular kind of messages so it won't get blocked by blockstringSPFRe? The company "plopsa.be", which is a themepark in Belgium is using a @gmail.com address in the sender envelope when sending it's newsletter. Customers are complaining because they do not receive these message anymore but it's normal because SPF fails for gmail.com and I have gmail.com in blockstrictSPFRe in order to block spam. I have added [email protected] to the whitelist as you can see, and [email protected] is also whitelisted but ASSP is still blocking it. Any way to prevent this from happening? Thanks ------------------------------------------------------------------------------ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
