Haines, If you are collecting ALL the mail in the mail box on the ISP server to go to a SINGLE mailbox on your local server then you can force fetchmail to rewrite the new To: header sent to sendmail with the --smtpname switch on the command line (or the relevant keyword in the fetchmailconf file). This doesn't explain how 127.0.0.1 got in the To: header but will stop it from happening again.
Regards Carl -- At 11:09 11/12/2002 -0800, you wrote: >Haines -- It is hard to diagnose anything from this bounce, without information about >what the original message looked like. A ways down in the bounce report is this >information: > >>Date: Tue, 10 Dec 2002 13:58:47 -0500 >>Message-Id: <[EMAIL PROTECTED]> >>From: Haines Brown <[EMAIL PROTECTED]> >>To: 127.0.0.1 >>Subject: test from lo 10 dec 13:58 >>Reply-to: [EMAIL PROTECTED] > >The first question you need to answer is -- how did 127.0.0.1 get into the "To:" >header? Was it an addressing error on your part, or did something rewrite it to that >value? I'd suggest you check the outbox of whatever program you used to send the >message. If the "To: 127.0.0.1" line appears in your original, then it was just a >typo and of no significance to your troubleshooting (that is, the reject is correct). >If the original has a different To: line, then post a followup with the details -- >what MUA, which system (hard disk) you were using, and what the original To: line >said. - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
