dns alias
Hallo,
ich habe ein Problem, dass fetchmail bestimmte Mails nicht zustellen
kann, weil die Empfängeradresse nicht korrekt zugeordnet werden kann.
Habe hierzu eine FetchmailFAQ gefunden, die darauf hinweist, dass das am
fehlenden DNS alias liegt (siehe unten).
In der Tat ist es hier so, dass die lokale Domäne nicht der Domäne der
eingehenden Mails entspricht.
Hat jemand einen Tip an welcher stelle ich den DNS alias setzen müsste?
Bei Google kommt zum Thema gleich alles mögliche :|
Danke
Stefan Pampel
aus FetchmailFAQ
<snip>
M7. Multidrop mode isn't parsing envelope addresses from my Received
headers as it should.
It may happen that you're getting what appear to be well-formed sendmail
Received headers, but fetchmail can't seem to extract an envelope
address from them. There can be a couple of reasons for this.
Spurious Received lines need to be skipped:
First, fetchmail might be looking at the wrong Received header. Normally
it looks only on the first one it sees, on the theory that that one was
last added and is going to be the one containing your mailserver's
theory of who the message was addressed to.
Some (unusual) mailserver configurations will generate extra Received
lines which you need to skip. To arrange this, use the optional skip
prefix argument of the `envelope' option; you may need to say something
like `envelope 1 Received' or `envelope 2 Received'.
The `by' clause doesn't contain a mailserver alias:
When fetchmail parses a Received line that looks like
Received: from send103.yahoomail.com (send103.yahoomail.com [205.180.60.92])
by iserv.ttns.net (8.8.5/8.8.5) with SMTP id RAA10088
for <ksturgeon@fbceg.org>; Wed, 9 Sep 1998 17:01:59 -0700
it checks to see if `iserv.ttns.net' is a DNS alias of your mailserver
before accepting `ksturgeon@fbceg.org' as an envelope address. This
check might fail if your DNS were misconfigured, or if you were using
`no dns' and had failed to declare iserv.ttns.net as an alias of your
server.
</snip>
Reply to: