Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ok I apologize if this post is a little vague. Right now I don't have any of the bounce back messages with me to give a specific example of what I'm about to ask.
I've been running a Postfix mail server for about 10 months now. The thing works great and "it" never seems to have a problem. It also never seems to have a problem receiving mail from other Linux mail servers.
I'm using a lot of the Postfix client/sender restrictions. ie: reject_unknown_hostname, reject_non_fqdn, etc. This seems to cause a lot of problems when someone tries to send me an e-mail from an Exchange server.
I've never configured Exchange, and I get the feeling that I'm having issues receiving e-mails from Exchange servers with, well, not so knowledgable administrators. The issue seems to be that the Exchange servers' hostnames don't have DNS entries.
For example, let's say domain.com is being hosted on an Exchange server. The Exchange server's hostname may not be domain.com, it may be cc-exch-win2k3.domain.com. Now domain.com will more than likely have an A record in the company's DNS, however, if they do not include a DNS record for cc-exch-win2k3.domain.com, then my Postfix server will reject the message. The Exchange sender will get a bounce back saying that cc-exch-win2k3.domain.com hostname was unknown.
So is this my fault? Should I just remove the reject_unknown_hostname from my Postfix restrictions? Or is it the job of the Exchange administrator to make sure that his/her server has a valid DNS entry so it doesn't get flagged as spam?
The other issue seems to be that not many mail servers seem to use tight restrictions. So when I bring this up with the Exchange admin he just says "Well we don't have any problems sending to other e-mail addresses, the problem must be with your Postfix server."
So is this my fault? Should I just remove the reject_unknown_hostname from my Postfix restrictions?
You might consider using reject_non_fqdn_hostname instead. There's a link to this page on the postfix site. Here's the relevant part:
Q7. Why don't you use reject_unknown_hostname or
A7. Too many "false positives" (that is: rejects too much non-spam
email), in my experience.
(By the way, Derrick 'dman' Hudson brought up a very
good point in the postfix-users mailing list: If you're
going to use reject_unknown_hostname anyway, you
probably want to put it *after* reject_non_fqdn_hostname
to prevent an unqualified hostname from matching one in
your own domain.)
This point of view is expressed in many places, as you can verify with a google search.