Postfix error checking (Was *panic* Open relay ...)

From: Clifton Royston (no email)
Date: Mon Apr 01 2002 - 13:54:37 EST


On Mon, Apr 01, 2002 at 11:26:38AM -0500, Wietse Venema wrote:
> Crystone AB / Daniel Sörlöv:
> > Thank you all for your help, solved the problem one hour
> > ago (it was a # which trashed config!)
>
> Newer Postfix versions log a warning and refuse the mail with as
> reason a server configuration error. That is, they err on the safe
> side.
>
> Older versions logged a warning which of course no-one noticed
> but let the mail pass.

Wietse,

  I have one new user's comment on error checking:

  I know you mentioned that it was a design decision to not check for
the existence of referenced files when doing a "postfix check", and to
leave that until the specific daemon processes need to start accessing
the files.

  However, over the course of the past weekend, as I started setting up
more realistic UCE tests, etc. on our test mail server, I've observed
that 80-90% of my mistakes fell into the category of "missing files."
That included typos in the file names, mistyped path names, forgetting
to run "postmap" to make a .db file, naming a file one thing in the
config and something different when I created it, and just about every
other boneheaded error possible.

  Postfix certainly isn't responsible for all of my operator errors!
However, it would have been nice to see more of them caught at the
"postfix check" stage instead of not seeing them until I ran "tail -f
/var/log/maillog" and got a connection to the SMTP port. Please
consider this as a wishlist item, at least.

  -- Clifton

-- 
    Clifton Royston  --  LavaNet Systems Architect --  
"What do we need to make our world come alive?  
   What does it take to make us sing?
 While we're waiting for the next one to arrive..." - Sisters of Mercy
-
To unsubscribe, send mail to  with content
(not subject): unsubscribe postfix-users







Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD