LWN.net Logo

Exim & Postfix flexibility

Exim & Postfix flexibility

Posted Aug 25, 2006 8:27 UTC (Fri) by kleptog (subscriber, #1183)
In reply to: Exim & Postfix flexibility by rfunk
Parent article: A comparison of Mail Transfer Agents - Part One

The thing that annoys me about Postfix while looking at the config file is that it's a lot of options, but from those options I have no idea how the system actually works. With Exim the config file describes the process taken to deliver a mail, from beginning to end. Take for example processing of the .forward file.

In Exim there's a director down the end that specifies the filename and how to handle it (permissions, user, etc). So I know where in the mail delivery process it appears. I can ask for it to check for the .forward files in a central directory, or check in a database if the user is allowed a .forward file. The default postfix configuration doesn't seem to mention the .forward file at all.

If someone comes along wanting special mail routing for domain X, I can just add a stanza matching that domain and add the rules. I can decide if it comes before or after the virtual tables, or anything else.

Maybe postfix can do this too, but from looking at the config file I certainly don't get that impression. It seems to be full of implicit rules, and I hate that.


(Log in to post comments)

Exim & Postfix flexibility

Posted Aug 25, 2006 8:59 UTC (Fri) by ahoh (guest, #17291) [Link]

When I was new to Postfix (that was at a time when the postgresql patch
was a brand new thing) I found the online documentation very helpful. And
it still is.

Don't bother too much with the comments in the config files (they are only
comments after all, usually only focusing on a very specifiy aspect). They
are helpful if you have allready some routine in running Postfix.

Have a look at http://www.postfix.org/documentation.html and dig through
the problem you want to solve there. I bet most of what you want to
configure is described there with the big picture and an overview of all
the corner cases it touches.

Postfix uses more then one file and several databases. That IS different
from a single config file to catch all.

Exim & Postfix flexibility

Posted Aug 25, 2006 18:15 UTC (Fri) by tsr2 (subscriber, #4293) [Link]

If there's a solution there (at http://www.postfix.org/documentation.html) for what I wanted to do with an MTA, it was far from obvious. The solution was relatively easy to find in the Exim documentation, so I went with Exim. IMHO the Exim documentation is significantly easier to use.

As someone who had never set up a proper MTA before, I was quite happy to set up Exim for my work, based on the available documentation, whereas I would not have been happy to do the same with postfix.

I can always find what I need in the Exim Specification or the FAQ, whereas I couldn't easily find what I needed in the postfix docs.

Exim & Postfix flexibility

Posted Aug 25, 2006 12:14 UTC (Fri) by rfunk (subscriber, #4054) [Link]

I like the fact that Postfix doesn't need everything in the config file,
just the stuff different from the default. It keeps simple
configurations simple. That's why I consider Exim and Sendmail to be
more complex to configure.

If you want a config file with *everything*, run the postconf command.
It shows the complete current configuration.

Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds
Powered by Rackspace Managed Hosting.