everybody will still recall the nuisance with a certain party named:
<[EMAIL PROTECTED]> . to dump these nessages
automatically, i put this host into control/badmailfrom. here's what
happens when fetchmail meets qmail on this topic. it renders the
mechanisms badmailfrom, databytes and the likes useless, if qmail always
blurts out his dismay asynchronically, because like in human interaction:
timing is essential!
fetchmail: POP3> RETR 1
fetchmail: POP3< +OK 4993 octets
fetchmail: reading message 1 of 37 (4993 bytes)
fetchmail: SMTP< 220 spotteswoode.de ESMTP
fetchmail: SMTP> EHLO localhost
fetchmail: SMTP< 250-spotteswoode.de
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250 8BITMIME
fetchmail: forwarding to localhost
fetchmail: SMTP> MAIL FROM:<[EMAIL PROTECTED]> BODY=8BITMIME
fetchmail: SMTP< 250 ok
fetchmail: SMTP> RCPT TO:<root@localhost>
fetchmail: SMTP< 553 sorry, your envelope sender is in my badmailfrom list (#5.7.1)
fetchmail: SMTP listener doesn't like recipient address `root@localhost'
fetchmail: SMTP> RCPT TO:<postmaster@localhost>
fetchmail: SMTP< 553 sorry, your envelope sender is in my badmailfrom list (#5.7.1)
fetchmail: can't even send to postmaster!
fetchmail: POP3> QUIT
fetchmail: POP3< This is a MIME-encapsulated message
fetchmail: SMTP transaction error while fetching from pop.gmx.de
fetchmail: Query status=10
--
clemens [EMAIL PROTECTED]
do D4685B884894C483
