Re: [qmailadmin-devel] alias/valias recap

[Jeff H. <jef...@ma...>]

Benjamin Tomhave wrote:
> -Any use of /Maildir/, whether it be in .qmail or valias, will result in
> bypassing other .qmail directives, such as for .qmail-default or for .qmail
> user files.  This is a Bad Thing (tm) since it means messages would bypass
> spam filtering, etc.  Thus, the *best* way to do "aliases" is by doing
> everything as an &us...@do... forward, which then causes the message to
> be re-injected, and thus processed correctly.

Correct, which is why the current qmailadmin development version 
(>=1.0.21) writes aliases as &us...@do...

> -QA needs to be aware and provide support for both .qmail (cdb) and valias
> (vmysql) configurations, probably by default.  It will probably be necessary
> to have configure flag(s) to determine which behaviour should be default
> (???), though I would imagine that if vpopmail is using a sql back end, then
> valias should be the default.

QA (when valias support is added) will read from both sources always. 
As Bill Shupp mentioned earlier, there is no reason to have a configure 
flag to turn valias on -- it can be automatically determined if vpopmail 
was configured with valias support (not just if vpopmail is using a sql 
backend).

> -There is a tool, vcalias, that can convert from .qmail aliases to valias
> aliases.

Correct.

> -My personal thought: if QA defaults to writing valias format, then it
> should also auto-detect .qmail aliases and either automagically convert it
> to valias, or at least prompt the admin to convert to the new format.

There's no reason to do that, if the person decides to start using 
valias instead of .qmail files, they can run the vcalias application.

Jeff
-- 

   /\  /\              ..    ..    ..    jef...@ma...
  /  \/  \ a t r i x  .  .  .  .  .  .  .           (770) 794-7233
  s o f t w a r e  i n c  ..    ..    ..   http://www.matrixsi.com