[Something odd is happening with linux-net; I got Kaz's reply before
this message.]
Juergen Fiedler wrote:
> I still haven't completely figured out my last problem and I'm already
> back for more. The situation is this: We have an ISP account, and we get
> mail forwarded to it. Mail for [EMAIL PROTECTED],
> [EMAIL PROTECTED] and [EMAIL PROTECTED] all lands in
> [EMAIL PROTECTED]
That's usually because fetchmail has no idea who the recipient is.
> For debugging purposes, I call fetchmail manually as root. The problem is
> that the mail always lands in root's mailbox. Is there a way to convince
> fetchmail to drop the mail to the appropriate box?
It has to know who the recipient is. If your ISP stores the recipient
address in an `X-Envelope-To:' header (which they probably don't; if
they did, it would all work automatically), fetchmail will use that.
If they use some other header (e.g. `Delivered-To:'), you can specify
this with -E (or --envelope, or the `envelope' directive).
Recent versions of fetchmail can also scan Received: headers for
recipient addresses (using `envelope "Received"'). This will only work
if your ISP's MTA adds the recipient address to the Received: headers,
though.
As a last resort, sendmail will scan the To:, CC: etc headers for
addresses which appear local. You have to tell it which domains are
local, though. Note that this last approach won't work for mailing
lists, or for messages where the recipient has been BCC'd.
For more details, see the fetchmail(1) manpage, specifically the
section entitled `Use and Abuse of Multidrop Mailboxes'.
--
Glynn Clements <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
