On Wednesday 12 November 2003 01:14 pm, J.C. Woods wrote:
As for the Mandrake mail servers, they are simply setup with the "smtpd_recipient_restrictions = reject_unknown_client" param. And what the hell does this mean? It means, for one thing, you must have rDNS for the sending mail server's name. See the many postings, made by myself, Pierre, et. al., in the archives about this issue. You are right about one thing. This is a setting that cuts down on spam...
That is not it. Incoming client is Earthlink SMTP server which DOES have rDNS setup and is a registered MX and does have an A record associated with it, etc. The fact that mail that is sent directly through the mail server from a client versus being relayed through the mail server from a local MX should be completely immaterial to the reject_unknown_client param on the mail server.
I was referring to the first poster's setup, and in his case, it did matter that his settings did not meet the basic hostname lookup performed by mandrake's sympa. Granted your case, Bryan, is somewhat unique.
In fact, the helo record is disregarded completely because the client header comes in the initial negotiation which is handed by Earthlink's mail server in both cases, never by Postfix on my end which only ever communicates to Earthlink's mail server and never to the mail server on Mandrake's end. The only difference in those two messages is the addition of one more Received header showing Postfix in the chain when I smart relay through Postfix as opposed to using my client directly to Earthlink's mail server. I can post headers from both types of messages to show that.
I agree, and I'll take your word for it. And I was aware that Earthlink blocked port 25. Could you do as Pierre has done: set postfix to another port?
What I suspect is happening is that Mandrake has some type of filtering system setup and is actively checking for forged Received headers of any type and trashing anything that has a Received header that is not valid. Since my local Postfix server is NOT a real MX, it's Received line appears to be forged because there is not a valid domain to originate there. I suspect that the culprit on the mail server is not the mail server itself, but an actual filtering program that is separate, perhaps a procmail recipe or a mail filter.
Good quess. I am not sure what they are doing. I stay away from sympa as much as posible. But you could still setup postfix to run with a hostname that was "real", and could pass the hostname lookup, yes? So that mandrake would see a "real" name in all header lines.
The reason that I suspect that is that I don't get a bounce message and Postfix, when it rejects a message sends a bounce message back informing you of why. If the reject_unknown_client_param were the culprit, I should be receiving a 553 bounce message when I send. Postfix does not trash invalid messages without a response, it communicates back to the sender so that you can correct your message. I do NOT receive a bounce, my message just never gets posted to the mailing list. Usually, when a message just gets trashed without any response at all, the culprit is almost always some type of body filter that takes over after the message is passed through the MX.
This part of your msg is most interesting to me. Granted, you are right, some msg should be sent back to your maillog/syslog (nice to talk to someone that keeps a vigilant eye on those files). Now, because you do not receive any 553 or any other msg, I would be inclined to infer, as you have done, that this is some function of the mandrake setup *but* it could be something to do with a borked setting on Earthlink's mail server that causes your returns from mandrake to be dropped. I suspect Earthlink to be the culprit. I'll tell you why. When I post response to the mandrake list server, my setup is very simple, compared to what you must do. I run my own mail server with a public interface, named with a "real" hostname that has a registered FQDN, and this hostname can be both resolved using forward and reverse DNS. Now, as expected, my postings get processed very nicely by smtp.mandrake.com. And, I should add that, because I use my current login on this machine to send mail, I am not a member of the mandrake list under this login name But I am a member under my pop3 mail name. So I communicate with the mandrake mail server before my message is sent my pop3 address, and to the list as a whole. It is a process where I am sent back my message, and I am asked to verify it by responding with a confirmation number. Once I respond to this, I get another response from the mandrake mail server telling me that this post has been sent to list. If all this sounds complicated, here is my point, back to the reasons I suspect your Earthlink mail server. All of the foregoing, about my communications with smtp.mandrake.com, indicate a somewhat complicate setup for getting mail to mandrake's list but it always works perfectly. But guess what? I did not see my last post. I know it was posted because you responded to it. Now that happens a lot. I go through the process of communication with the mandrake server, and I am told, after I complete the confirmation process, that my message has been posted to the list, and I know this to be true because you responed to it. But I never see it get to my pop3 server, where I pick up my mail. Now the interesting part: my pop3 server is "pop.sprynet.com". I'll let you do the honors of running some "host" and "dig" queries. You may be surprised at what you find. And you'll understand my suspicions about Earthlink
(sheesh, just some simple thoughts, and it got so wordy. Sorry about that)
drjung
-- J. Craig Woods UNIX Network/System Engineer http://www.trismegistus.net/resume.htm Let him that would move the world, first move himself. --Socrates
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
