On Wednesday 12 November 2003 01:14 pm, J.C. Woods wrote: > You have two different issues at work on this tread. One issue is > basically about setting up postfix. What params to use in main.cf, and > what params not to use. If you choose a do a "hack", just be aware of > the consequences.
Agreed. PA's setup is different from mine, in that I am not attempting to originate mail directly through my own MX, I am always relaying through a real MX that belongs to my ISP. I do not and can not do direct to MX mail on my system as outgoing port 25 is blocked. > 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. 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. 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. 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. -- Bryan Phinney Software Test Engineer
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
