Hi Michelle, > To: [EMAIL PROTECTED], "Users <users"@<81>! > Its possible that, if the To: header line contained a sentence, that Postfix address rewriting will add "@example.com" to every word, fail to find these mailboxes and bounce the message as a result.
However, I've found another way to upset Postfix too.... I get mail from my ISP with fetchmail 6.3.7. I run it in single drop mode and use its "mda" facility to pass the mail through a pipeline: spamc| spamkiller| sendmail Spamkiller is my own code. It just drops mail that SA marks as spam and passes the rest to sendmail for delivery to Postfix. Fetchmail passes routing information to sendmail via its command line by using a string like "-f sender_address_from_envelope -- user" where 'user' is the destination mailbox. Yesterday I found that fetchmail will sometimes corrupt the sendmail arguments by adding spurious spaces and/or a byte in the range 0x01 - 0x1F to the end of the final argument. This will also cause Postfix to reject the message after its rewritten the delivery address to, say "[EMAIL PROTECTED]" or "[EMAIL PROTECTED]". So, I've written another filter to clean up the argument string while I collect evidence to submit a bug report. > the "Subject: No Subject" so he has accidently typed the text in the > Subject field. > Or equally likely, he put it in the To: field, but I agree that "No subject" means that header was left blank. Best regards, Martin Gregorie
