I am also trying /etc/courier/aliasdir/
.courier-testlist = "| /usr/bin/couriermlm msg /home/lists/testlist"
.courier-testlist-owner  = "[email protected]"
.courier-testlist-default = "| /usr/bin/couriermlm ctlmsg /home/lists/testlist"

Which I read as being check if nothing else matches. So I removed the 
catch all in my aliases/system file for @nickellson.com, and now I just 
get Unknown User for anything tacked onto 
testlist-<anything>@nickellson.com

Nick


-- 
Nick Ellson
CCIE# 20018
MCSE 2000, Security+, Network+
Network Hobbyist, VFR Private Pilot.


On Wed, 24 Dec 2008, Nick Ellson wrote:

>
>
> I am missing something about how the <listname>-<command>@mydomains is
> parsed:
>
> I did:
>
> couriermlm create /home/lists/testlist [email protected]
> couriermlm sub /home/lists/testlist [email protected]
> <crtl-d>
>
> /etc/courier/aliases/system
>
> <snip>
> @nickellson.com:                         grimm
> [email protected]:                 testlist
> <snip>
>
> MySQL Courier database:
>
> INSERT INTO `passwd` VALUES ('[email protected]','','testlist','Test
> List',3000,100,'/home/lists/testlist','','','')
>
> /home/lists/testlist/.courier
>
> | /usr/bin/couriermlm msg /home/lists/testlist
>
> And when I send mail to this list from "[email protected]" I get "You
> are not a member of the list"
>
> couriermlm lsub /home/lists/testlist
> [email protected] (23-Dec-2008)
>
>
> Now I tried to send a mail to the command channel with
> [email protected] and it get's re-written as
> [email protected] and dropped into my catch all
> alias. When I added a testlist-subscribe in my alias, I aimed it at
> testlist.. so I get a reject because the command directive get's tossed.
>
> How should I be setting up the list aliases/MySQL users, .courier files to
> allot for all the <list>-<command>@<domain> options?
>
> Do I actually make that many users and aliases? (I think it's 4 per list
> that way?)
>
> Nick
>
>
>
>
> -- 
> Nick Ellson
> CCIE# 20018
> MCSE 2000, Security+, Network+
> Network Hobbyist, VFR Private Pilot.
>
>
> On Tue, 23 Dec 2008, Nick Ellson wrote:
>
>>
>>
>> Ok, that helps. I created the mysql entry in passwd, and in system
>> (aliases) and it works sort of.
>>
>> I send a mail to it and I get an undelivered because I am not subscribe to
>> the list. Even after I manually did a "couriermlm sub <dir>
>> [email protected]"
>>
>> When I do an lsub it shows me.
>>
>> Will whack at that some more, but hey, it's talking to my list so I am
>> happier :)
>>
>> And I get all sorts of logs now.
>>
>>
>> Thanks!
>>
>> Nick
>>
>>
>>
>>
>> --
>> Nick Ellson
>> CCIE# 20018
>> MCSE 2000, Security+, Network+
>> Network Hobbyist, VFR Private Pilot.
>>
>>
>> On Tue, 23 Dec 2008, Sam Varshavchik wrote:
>>
>>> Nick Ellson writes:
>>>
>>>>
>>>>  I have several small mailing lists off my domain that I would like to
>>>>  migrate over to courier-mlm as I am going to all courier mail systems.
>>>>
>>>>  Now I am reading the mlm docs but I am getting lost at step 2. dot-courier
>>>>  files.
>>>>
>>>>  I have a mysql database that handles my real users. There are 3 of them.
>>>>  And they have home directories.
>>>>
>>>>  Now if I want to support a list called [email protected] I get
>>>>  that I would do:
>>>>
>>>>  couriermlm create /var/lists/studygroup [email protected]
>>>>
>>>>  Now, for step 2, and I actually creating a user called studygroup in mysql
>>>>  and aiming their home directory at /var/lists/studygroup ??
>>>
>>> Not quite. One account is no different than the other. If you create an
>>> account called 'studygroup', you will then need to create the new account's
>>> home directory, its $HOME, and have it owned by a matching numerical uid/gid
>>> that you have set for the account in the database. Just like for any other
>>> account, and at this point it is no different than any other account. You 
>>> may
>>> even create a $HOME/Maildir in the account's home directory, if you feel 
>>> like
>>> it.
>>>
>>> Then, you would proceed to run couriermlm to create a mailing list 
>>> directory.
>>> The new account's $HOME/mlm would be as good choice as any, as long as, of
>>> course its numerical uid/gid is the same as the account's home directory, 
>>> and
>>> the uid/gid that's set for this account in your account database. After all,
>>> that account has to be able to write to its own mailing list directory.
>>>
>>> At this point, the new account's $HOME/.courier, $HOME/.courier-default, and
>>> any $HOME/.courier file works exactly like any other account's 
>>> $HOME/.courier
>>> file. You can proceed accordingly.
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> courier-users mailing list
>> [email protected]
>> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> courier-users mailing list
> [email protected]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>

------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to