2 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Avoiding the need...
FromSent OnAttachments
Courier UserMay 7, 2003 8:45 am 
James A BakerMay 7, 2003 11:21 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Avoiding the need to put a domain in both locals and hosteddomainsActions...
From:James A Baker (jaba@mac.com)
Date:May 7, 2003 11:21:00 am
List:net.sourceforge.lists.courier-users

On Wednesday, May 7, 2003, at 10:45 US/Central, Courier User wrote:

[ This is a near-repost of an earlier message. I've reworded this version somewhat. ]

I'm using TMDA for a subset of the users on my system. One of the features of this software is that "tagged" and "dated" return addresses can be optionally generated. For example, a hypothetical user named 'misteruser' at 'whateverdomain.org' (a hypothetical virtual domain on my host) might have the following "dated" return address generated for him:

mist@whateverdomain.org

If I want to process messages to this address upon receipt, I know that I can do so via one or more filters that are specified within the .courier-default file in misteruser's HOME directory. However, this only seems to occur on my system when whateverdomain.org is listed in the "locals" file.

But also, on my system there are other users at the whateverdomain.org virtual domain whose locally-defined mailboxes are accessed via fully qualified names such as "anot@whateverdomain.org". That seems to indicate that it's necessary to put whateveruser.org into "hostedddomains".

If all this is true, then I have the following problem: the existence of that domain in both "hosteddomains" and "locals" causes a conflict.

Therefore, I'm wondering if there's a way to cause a user's $HOME/.courier-default file to be used to process addresses like the "dated" one above, without the user's domain needing to be in the "locals" file.

Or am I totally confused about this?

Thanks in advance.

Okay... I don't know. -- Let me preface all my comments with this statement... I don't know anything about the filters and aliases and all that stuff. Simply because I don't use them or even Courier's ESMTP/MSA services.

However, that said... Have you considered making your "real users" into virtual users with the same home/uid information as they have currently as real users? That's what I did. (For different reasons, no doubt. But it works okay for me.)

I've got my system set up to use PostgreSQL for *all* authentication requests. And most accounts are set up to authenticate like this:

te@mboro.org = uid:250, gid:6, home:/var/mail/vhosts/mboro.org/test, maildir:/var/mail/vhosts/mboro.org/test/Maildir/

...where uid:250 is my unix "mailonly" user id, and gid:6 is my "mail" group -- i.e. the virtual mail account on my system.

But in instances like jam@jamescat.net (which is me, at my personal domain), I have it set up to authenticate like this:

james = uid:501, gid:20, home:/Users/james, maildir:Library/Maildir/

...which is using my real unix uid (501), OS X's "staff" group (20, which I'm a part of), the actual home of my "real" account, and the relative path to my Maildir inside my home folder.

I previously had it pointing to a full path in a location outside my home folder -- i.e. /var/mail/vhosts/jamescat.net/james/Maildir/ was the previous location -- and that worked just fine too.

That way I don't have to worry if they're real or virtual... they're all virtual, and I just give them the proper uid/path information.

If you used a similar setup, then all your domains could be in the hosteddomains file, I think. Right?

Now as I said, I don't know... but maybe that or something like it would work for you. *shrug* Maybe it would, maybe it wouldn't. But it's a thought at least.

HTH. =)

-jab