Jonathon wrote:
There are indeed two entries in there. Seems to be a bug in my control
panel, web interface that handles the creation of mailing lists.
I've removed the duplicate entry in
/etc/courier/.courier-:xalias/[EMAIL PROTECTED] Do I have to run
something like `makealiases'?
You don't have to, but when you do, the problem will come back. The
xalias files are created when you put delivery commands in aliases.
I'm still getting duplicate entries in the log. Along the way, can you
help check my understanding of the logs? Thanks.
Track down the source of the problem. If you removed the line from the
xalias file and the problem hasn't changed, my first guess would be that
your web UI set up a cron job that runs "makealiases" when it was installed.
Ok, let me get this straight. For Task A, courierd received a post from
user_a to mylist.
Pretty much, yes. Technically, courieresmtpd (I assume) "received" and
queued a message from user_a to mylist. courierd delivered that message
according to the instructions in the xalias file.
Then courierd spawns Task B to send to everyone on the list. Then
courierlocal picks up Task B and actually performs it. Then courierd
reports that Task B is completed. Finally, both courierlocal and
courierd reports that Task A is completed
Not really... Courier handed the message to each of the recipients
listed in the xalias file (which may now contain the mailing list
software twice, again). That's the end of task A.
Separately, the mailing list software determined who the list
subscribers were and submitted a new message to courier. It looks like
this is the program that connected to courieresmtpd on 127.0.0.1.
Assuming that the list software really is listed twice in that file, a
second copy of the message was given to the list software, which again
expanded the subscriber list and sent another copy of the message to the
subscribers using courieresmtpd.
Don't let the timing confuse you. Task A is entirely separate from task
B. The fact that its completion was logged after B's completion doesn't
mean much.
I'm suspecting that Task A is some kinda "manager task", and Task B will
be the "worker task". Am I right?
No. Delivery attempts don't stack. Messages are submitted to courier's
queue by input programs that call submit(8). When submit puts messages
in the queue, it notifies courierd, if courierd is running. courierd
reads the control files and schedules the delivery of the message. If
one of the recipients of the message, such as list software, submits new
messages into the queue, there's no relationship between that new
message and the one that was first in the queue.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
