On Mon, May 24, 2004 at 12:55:48PM -0700, Tom?s Rodriguez Orta wrote:
Is the same file log of the fetchmail.log, but I want to cut in two part,
because at the firts I gave an error, and the second small log thats ok, do
you undestain?.
Yes, although I wasn't sure if it was the "protocol error" that was the
problem, because you didn't show the MTA response to the RCPT TO in the
second example.
at the first small log RCPT TO is bad, because the real user is?nt
root(_at_)localhost(_dot_)
The real user is whatever you specify in your .fetchmailrc
That's unless you're trying to use multi-drop mode, in which case I'd say
simply: don't.
If fetchmail gets re-written, then I'd propose that all Received: line
parsing is removed. Then, you can do multidrop only if your MTA adds a
Delivered-To:, Envelope-To: or X-Envelope-To: header.
Multidrop mode simply causes too many problems to be worth it, and in many
cases simply cannot work at all (e.g. one message delivered simultaneously
to two recipients, in which case the Received: line does not contain the
recipient at all)
my question is why the fetchmail dose?nt read the enevelope header when the
mail s from an list of dicussion.
Probably because you have two or more subscribers to that mailing list in
your site.
The incoming mail is
MAIL FROM:<owner-foo(_at_)foo(_dot_)com>
RCPT TO:<user1(_at_)yourdomain(_dot_)com>
RCPT TO:<user2(_at_)yourdomain(_dot_)com>
But the envelope information in this case is not stored in the Received:
header.
I read in the Bulma an article about fetchmail and multidrop, the solution
is add to /root/.fetchmailrc
the line envelope "X-Original-To" localdomains.
I will can solve my problem with this modification in the fetchmailrc?.
No, not unless your MTA happens to add "X-Original-To" containing the
envelope recipients. It's not a header I've come across before. But then I'm
not familiar with Postfix and any non-standard headers it may add.
Brian.