On 29/07/2006, at 08:45, John Simpson wrote:

On 2006-07-27, at 0817, Charles Butcher wrote:

A few power users within a virtual email domain have shell login access to the server. I want their mail to be delivered to their home directory, not to a vpopmail account. I also want the .qmail-ext mechanisms to work for them, under their control.

i've never gotten this to work, at least not directly... the closest i was able to do was tell them to configure pine/elm/mutt as an IMAP client. i'm the only "power user" on my server who understands .qmail files well enough to mess with them, and i do my own custom .qmail file edits as root.

you may want to try adding "localhost" to the /var/qmail/locals file (send a HUP to qmail-send) and create a ~vpopmail/domains/domain.xyz/.qmail-userid file containing "&[EMAIL PROTECTED]", so that their incoming mail is re-delivered to their system userid.

Thanks, John,

I did some experiments and worked out the following:

if ~vpopmail/domains/domain.xyz/.qmail-userid is edited to contain:


and you then link .qmail-userid-default to .qmail-userid then it all works as expected:


and the exact same file contents work for any value of userid so I could conceivably just link as many different .qmail-userid and .qmail-userid-default to the same "master" file as I want.... (Note that symlinks do not show up in qmailadmin's forwards list, but if you use hard links they do)

qmailadmin 1.2.10 will not let you put the |forward statement in the .qmail file directly, but once you have manually edited it, qmailadmin shows the forwarding line in italics (without the leading |). So at least you can see what the file contains.

I'm thinking of making these special .qmail files owned by root and group vckpw read-only so they can't be accidentally modified with qmailadmin.


Reply via email to