-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Sunday 2007-03-04 at 01:42 +0100, Sandy Drobic wrote:
> > Maybe his postfix tried to send to "[EMAIL PROTECTED]", instead of
> > taking it locally, as was intended. He is "growngizmo.de" (I think), but
> > his mail is handled by mailin.rzone.de, which refused his client being
> > dynamic... so finally, postfix, not knowing how to send to
> > "[EMAIL PROTECTED]" bounces back to us.
> >
> > Does it sound reasonable?
>
> That could be, though the real question is why anything he polled with
> fetchmail was bouncing back at all. I don't like fetchmail and don't use
> it, but AFAIK you can set it up not to bounce anything and instead
> redirect it to a postmaster account.
As I read it, fetchmail did it right, but it does a translation:
| Received: from post.strato.de [192.67.198.2]
| by dothangizmo.gk.lan with POP3 (fetchmail-6.3.2)
| for <[EMAIL PROTECTED]> (single-drop); Sat, 03 Mar 2007 01:42:57 +0100
(CET)
|
Probably because it is configured to translate the "remote" username (ie,
[EMAIL PROTECTED]) to a local name of "4suse%growngizmo.de
@localhost". Maybe it is a multidrop.
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 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:
<[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.
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.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFF6ie+tTMYHG2NR9URAoUOAJ4nOstIqgYbqo6Ae+ggmcVMvsK9sQCfdsN0
GBidHu8okP24RayPnQPVRmo=
=03tQ
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
