Am 28.01.2015 um 17:10 schrieb deoren:
On 2015-01-28 08:33, li...@rhsoft.net wrote:
Am 28.01.2015 um 15:28 schrieb deoren:
I searched via Google and via the mailing list archives, but I didn't
find a post which matched my specific situation.
I see those warnings in the logs when the system goes down for a reboot.
Is the mail lost? Should I be using a different approach when rebooting
a server running Postfix? Does the client receive an error and it's then
up to it to try again?
you need to provide the loglines before *and* after that message
Thanks, and you're right, I should have included more information. I was
attempting to trim the message down to just the relevant portion and
trimmed too far.
Jan 27 16:27:56 screech postfix/cleanup[1140]: warning:
mysql:/etc/postfix/mysql-pfix-no-srs-virtual-mailbox-maps.cf lookup
error for "fail2ban-l...@example.com"
Jan 27 16:27:56 screech postfix/cleanup[1140]: warning: C0150213F8:
sender_canonical_maps map lookup problem for fail2ban-l...@example.com
Jan 27 16:27:56 screech postfix/pickup[1134]: warning:
maildrop/D754B212B1: error writing C0150213F8: queue file write error
Jan 27 16:27:56 screech postfix/pickup[1134]: C1FCE213F8: uid=0
from=<fail2ban>
I looked further and within the stunnel logs on this box I noted that
the connection between this box and the database server wasn't live yet,
so that's why the lookup problem for the destination address occurred. I
was under the mistaken impression that Postfix would have temporarily
accepted/held the mail and tried to perform additional lookup requests
before giving up, but evidently I don't have a solid understanding of
the intake process. I'll do further research in that area
postfix *must not act* that way
you can't accept/held something when half of your lookup-tables are not
available because they may contain rules to clearly reject a message
there is no "temporarily accept"
if you accept a message you issue 250 OK to the sender and after that
you have to deliver it or create a bounce which makes you to a
backscatter and leads in blacklisting
the only sane thing a MTA can do in doubt is *temporary reject* with 4xx
and so the sender tries again later
