Using '[email protected]' as envelope sender from 176.62.160.58 is WRONG! To receive bounces at this address, it should be used in the 'errors-to:' header line.
This whitelisted mail is checked for SPF because SPFWL is set. To skip the SPF check you have three choices. - unset 'SPFWL' - not recommended - define 'contentOnlyRe' to match the mail - not recommended - define 'bounce\.plopsa\.emailing\@gmail\.com' in 'noSPFRe' - (assumes the envelope sender is always the same) and/or define '176\.62\.160\.58' in 'noSPFRe' - (assumes the sending IP is always the same - don't do this if the IP is one of a large mail provider) and/or define any other unique mail content in 'noSPFRe' - (assumes the content can be found in every such mail) Not a real solution, but a nice trick would be to add the following entry in to the SPFCache (using the GUI) 176.62.160.58 gmail.com|::|[2030-08-18,14:11:00] pass mailing.plopsafun.be The entry will expire after 2030-08-18 - until this date all mail from this IP and gmail.com will pass the SPF check. modifying any DB directly pkey: '176.62.160.58 gmail.com' pvalue: '8999999999 pass mailing.plopsafun.be' both without the quotes 8999999999 is the 2255-03-14,16:59:59 Thomas Von: "Andy Knuts" <[email protected]> An: "For Users of ASSP" <[email protected]> Datum: 25.08.2016 10:03 Betreff: [Assp-user] Whitelist_&_strict_SPF? 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 DISCLAIMER: ******************************************************* This email and any files transmitted with it may be confidential, legally privileged and protected in law and are intended solely for the use of the individual to whom it is addressed. This email was multiple times scanned for viruses. There should be no known virus in this email! *******************************************************
------------------------------------------------------------------------------
_______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
