-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Sunday 2007-03-04 at 11:10 +0100, Sandy Drobic wrote:
> Carlos E. R. wrote:
>
> > So far, so good. Or maybe not so good, the local user is not well defined.
> >
> > The next step, is to put that into the local folder, by postfix. But
> > postfix expands "[EMAIL PROTECTED]" into "[EMAIL PROTECTED]"
> > (I have no idea why, I don't know how he has it configured).
> >
> > Next, postfix thinks that the destination of that email is not local (the
> > "localhost" past has been lost), so postfix tries to send it to
> > "growngizmo.de".
>
> And that is most likely the problem. If Postfix doesn't know which domains
> are local it is trying to relay the mail.
Yep, but probably caused by a bad name translation by fetchmail, or
misconfiguration of same.
> > And mail to "growngizmo.de" happens to be handled by "mailin.rzone.de".
> >
> > It is this "growngizmo.de", aka "mailin.rzone.de" who rejects the email
> > for coming from a dynamic address. It is not the combination of
> > fetchmail/postfix who is responsible for the rejection. It is his own ISP
> > who is doing the rejection:
>
> He probably didn't configure smtp auth for the client part of Postfix, so
> Postfix tries to submit the mail directly to the responsible mailserver.
Right.
It is curious, though, because it is his ISP, I think.
> > <[EMAIL PROTECTED]> (expanded from <[EMAIL PROTECTED]>): host
> > mailin.rzone.de[81.169.145.100] said: 550 5.0.0 Dial-Up IP address
> > rejected
> > (in reply to RCPT TO command)
> >
> >
> > What happens now is that our "friend's" postfix now have a rejected
> > email... so it sends it back... to us.
>
> Correct. In my case he tries to send it to me.
>
> 554 5.7.1 <[EMAIL PROTECTED]>: Recipient address
> rejected: Access denied; from=<> to=<[EMAIL PROTECTED]>
> proto=ESMTP helo=<dothangizmo.gk.lan> (total: 45)
> 45 p549B18A2.dip0.t-ipconnect.de
> 554 5.7.1 <[EMAIL PROTECTED]>: Recipient address
> rejected: Access denied; from=<> to=<[EMAIL PROTECTED]>
> proto=ESMTP helo=<dothangizmo.gk.lan> (total: 170)
> 170 p549B18A2.dip0.t-ipconnect.de
Well, I think that first he tries to send to "him", and failing, tries to
bounce to you, which also fails. Hold on, if it fails, you don't have
those emails, do you? You must have the rejections in your logs, but not
the emails themselves.
> > The error is in fetchmail not translating to the correct local user name.
> > Plus, if it is a multidrop, I don't think you can handle it with procmail
> > directly.
> >
> > But the fault is not fetchmail nor postfix: it is our friend's fault for
> > not doing checks and configuring properly his setup.
>
> The usual diagnosis: the problem is sitting in front of the keyboard.
Right :-)
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFF6shKtTMYHG2NR9URAoTmAJ9mqK06E0vwvED4++0pTxTddaDWKQCdHqgd
qXrV6pdWssq2hqpEcrRlZEk=
=yuUr
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
