I guess my idea was for a few reasons...

You do not have 200,000 .qmail-user-default files in your domains root directory.
Vdelivermail will follow the - to to user unless there is a .qmail-user-default in the root directory or if user-user exists.
Then tmda kicks in if need be.

Reading the .qmail file in the users directory is plenty and seems safe to me.
The bad part would be using .qmail-default and .qmail files together.

Also, when a user is deleted then the TMDA uninstall is done for that user without the .qmail-default files leftover.

Plus, when using other methods that put users on vacation, etc, it is safer to deal with the one file in the users directory.
Messing with .qmail-default files in the domains root directory (.qmail-default-wrong ) can cause some problems with how your email suddenly begins to be directed.

I have been running for some time with just a .qmail file in the users directory ( and a verbose .tmda/config ) and have not seen any gotchas.
The key being not to allow users to use dashes in there username.

Sam

Tim Legant wrote:
Sam <[EMAIL PROTECTED]> writes:

  
Tim Legant wrote:

    
You need either a test/.qmail-default or a
nesys.it/.qmail-test-default when using TMDA, since replies to
confirmation requests come back to an extension address
(test-confirm-xxx).  Without the -default file they will never get
delivered and thus mail will never get confirmed.
      

  
I do not think you need a .qmail-default if vpopmail is compiled with
the qmail-ext (the - extensions) which hers is.
In my setup all I have is the .qmail file in the users directory and
the user-something is followed because vpopmail now has that feature.
    

This "works" because you have a .qmail-default in each virtual
domain's home directory that calls vdelivermail, which eventually
reads and parses the user's .qmail.  However, as I mentioned in my
description of option 1, vdelivermail doesn't parse and execute .qmail
files the same way that qmail-local does.

I don't remember the specifics, off-hand, but I've read the code and
there are various "gotchas" that can occur.  I made the recommendation
I did because I feel it is safest to keep vdelivermail entirely out of
the picture.

If, in order to use vdelivermail's bounce handling for non-existent
users, you want to call it from the .../<virtualdomain>/.qmail-default
file, you need to ensure that there *isn't* a <user>/.qmail file,
because things really go haywire at that point.

There have been various discussions of this previously that you can
find in the archives, http://mla.libertine.org/tmda-users/ .


Tim

_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users


  

_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users

Reply via email to