hi,
this post could go either way, so i am posting to the qmailadmin list
first. if not correct, i will post to vchkpw list.
please instruct me if this is the case.
-----
i need to understand why this occurs:
vpopmail (5.4.16 compiled with --enable-valias)
qmailadmin (1.2.10, fresh compile)
aliases are stored in the database, however:
when in qmailadmin, click on a real mailbox, click 'forward to' and put
'[EMAIL PROTECTED]' in there.
qmailadmin creates a .qmail file.
1) why would it do this, even when valias is enabled in vpopmail ?
2) isn't the purpose of valias table to rid the server of .qmail files ?
what ive done to test:
create a mailbox '[EMAIL PROTECTED]'
add a forward to the real account, as above using qmailadmin.
run valias -s domain.com
output:
[EMAIL PROTECTED]: ~ # valias -s domain.com
[EMAIL PROTECTED] -> &[EMAIL PROTECTED]
now...
remove that forward from qmailadmin, and run the following:
[EMAIL PROTECTED]: ~ # valias -i \&[EMAIL PROTECTED] [EMAIL PROTECTED]
after running that, the output of valias -s domain.com is identical, but
qmailadmin does not know about the forward now. understandable, since
qmailadmin is clearly reading/writing .qmail files within the users maildir.
but the forward works just fine.
so.: why does qmailadmin write .qmail files when it can use the valias
table ? i suppose theres a fundamental thing i am missing here. but im
leaning towards not using the valias thing at all if i am stuck with
.qmail files strewn everywhere anyway. the valias table does not have
much advantage if only 'most' of the configuration is stored there.
cross-reference:
http://www.mail-archive.com/qmailadmin@inter7.com/msg06336.html
thoughts ?
--
aichains
