Am 10.01.2015 um 18:14 schrieb Steve:
On 10/01/2015 14:35, Jeff Mincy wrote:use blacklist_to bogus_us...@mydomain.com ... This will lead to hits on USER_IN_BLACKLIST_TOThat works perfectly to blacklist 'completely bogus' "To" addresses. Many thanks. On 10/01/2015 14:36, Reindl Harald wrote:it can work like below by let add postfix a custom header and use that as anchor for a SA rule smtpd_recipient_restrictions = reject_non_fqdn_recipient reject_non_fqdn_sender reject_unauth_destination reject_unlisted_recipient check_recipient_access pcre:/etc/postfix/x_envelope_to.cf /etc/postfix/x_envelope_to.cf /(.*)/ prepend X-Local-Envelope-To: <$1> header CUST_LESS_SPAM_TO X-Local-Envelope-To =~ /^(\<h\.reindl\@thelounge\.net\>|\<UnwantedRubbish\@mydomain\.com\>)$/i score CUST_LESS_SPAM_TO 4.0 describe CUST_LESS_SPAM_TO Custom ScoringI don't think I understand... Is this a strategy to allow me to reject emails to list-specific email addresses (in the absence of the expected "List-Id" header) - or something else?
Uhm - no * Postfix adds the X-Local-Envelope-To header with the rcpt inside <>because parse out the envelope-rcpt from reveived headers is error prone and BCC mails don't contain To-Headers which would need to be parsed too because it contains not only the email * CUST_LESS_SPAM_TO contains a Regex for that header * if it matches 4.0 points are added to whatever result by other rules well, i generate such rules from a database with a webui
signature.asc
Description: OpenPGP digital signature
