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 "4suse%growngizmo.de@localhost" into "4suse@growngizmo.de" (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.
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.
<4suse@growngizmo.de> (expanded from <4suse%growngizmo.de@localhost>): 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
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. -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org