search for: destination_recipient_limit

...ress=.+, sender=.*, recipient=.+ to: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postgrey(\[[0-9]+\])?: ([0-9A-F]+: )?action=.+, reason=.+, (delay=.+, )?client_name=.+, client_address=.+, sender=.*, recipient=.+ The reason is for when a greylisted message has multiple recipients (and possibly only when destination_recipient_limit is set to 1 in postfix, I didn't check whether that makes a difference) the second whitelisted message is slightly different than the first. Thanks. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Ker...

...ectory they thought needed to be made, and just sent the mail to the inbox. That's a reasonable approach, although I wonder if deliver/sieve could be (or perhaps "has been in 2.0") adjusted to more intelligently handle that edge case. Also, I'm wondering about "dovecot_destination_recipient_limit = 1". I have that set in my main.cf, but I'm not 100% positive it's taking effect. # grep dovecot /usr/local/etc/postfix/main.cf dovecot_destination_recipient_limit = 1 virtual_transport = dovecot # grep dovecot /usr/local/etc/postfix/master.cf dovecot unix - n n...