> Le 20 juil. 2015 à 12:46, Wietse Venema <wie...@porcupine.org> a écrit : > > Alexandre Ellert: >> Hello, >> >> I often use sender_bcc_maps to audit suspicious account and it works great. >> Today, I need to have a look at email sent by null sender <> >> >> Here is my relevant configuration : >> >> # grep sender_bcc_maps /etc/postfix/main.cf >> sender_bcc_maps = regexp:/etc/postfix/sender_bcc_maps >> >> # cat /etc/postfix/sender_bcc_maps >> # This one usually works fine >> #/^u...@example.com <mailto:u...@exemple.com>$/ >> au...@example.org >> /^$/ au...@example.org >> /<>/ audit@example. >> <mailto:au...@exemple.com>org > > Postfix does not make queries with empty strings because some > software can't handle it. You can't use /^$/ patterns for any > Postfix lookup table. > > As documented, sender_bcc_maps does not map null query keys to <>. > You can't use <> patterns in sender_bcc_maps. > > Use check_sender_access instead. As documented, it maps null query > keys to <>. > > Wietse
If I understand well your answer and the documentation, this solution should work with Postfix 3.0: 1. remove sender_bcc_maps directive 2. add a check_sender_access. For example : smtpd_recipient_restrictions = check_sender_access regexp:/etc/postfix/sender_bcc_maps_including_null_sender, [other stuff here], reject 3. create /etc/postfix/sender_bcc_maps_including_null_sender with this content : <> BCC au...@example.org <mailto:au...@example.org> Do you agree ? Alexandre
