i have a few entries in control/badmailfrom. a few days ago a message got caught by this magic, but it didn't quite work as expected, because the 553 error from qmail-smatpd thrown back to the pop3 popper (fetchmail) came only =after= it had asked for the recipient. this is the dialogue: SMTP> MAIL FROM:<[EMAIL PROTECTED]> BODY=8BITMIME SMTP< 250 ok why does qmail-smtpd say 250 ok? at that time it has already checked control/badmailfrom, but instead of complaining immedeatly it accepts the recipient's address! SMTP> RCPT TO:<local@localhost> SMTP< 553 sorry, your envelope sender is in my badmailfrom list (#5.7.1) that's too late! no wonder the pop3 client associates the 553 response with the recipient, which is wrong wrong wrong! SMTP listener doesn't like recipient address `local@localhost' SMTP> RCPT TO:<postmaster@localhost> SMTP< 553 sorry, your envelope sender is in my badmailfrom list (#5.7.1) can't even send to postmaster! and why this? postmaster@localhost is defined. has qmail-smtpd not done enough damage? POP3> QUIT POP3< This is a MIME-encapsulated message SMTP transaction error while fetching from pop.gmx.de Query status=10 what do i expect? fetchmail is confused and stops processing this batch. had i not checked the log, the same batch of messages would have been rejected until hours later my logg-scanning program had brought this to my immediate attention. by that time my mailbox at my isp could have overflowed with resulting loss of messages. i checked the source and the 553 reply could be placed a few lines earlier with no consequences other than reducing codesize a few bytes, because setting and checking a flag to deferr complaining about the sender until after the recipient address is changed, which is how it is done at present, could just be dropped and forgotten. why? what for? -- clemens [EMAIL PROTECTED]
