[Dovecot] What does mailman do with a 'post' command?
Dear list,
I am sorry if this question should not be posted here, but I believe that there are many experts of postfix or any other thing such as mailing lists in this list. I am kind of in hurry and need some advices to know about my questions. Could anyone in this list please answer my questions if you know.
My questions are about routing work of mailman. As I am not quite fimiliar with the use of mailman, I am sorry if this is a stupid question.
One of my customer gets the following log message into /var/log/maillog at around 12:00 every day.
---</var/log/maillog>--- 12:00:04 relay postfix/pickup[6279]: 244811C805C: uid=41 from=<mailman> 12:00:04 relay postfix/cleanup[21529]: 244811C805C: message-id=<20100215030004.244811C805C@example.co.jp> 12:00:04 relay postfix/qmgr[20068]: 244811C805C: from=<mailman@example.co.jp>, size=1728, nrcpt=1 (queue active) 12:00:04 relay postfix/local[21232]: 244811C805C: to=<mailman@example.co.jp>, orig_to=<mailman>, relay=local, delay=0.17, delays=0.05/0/0/0.12, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post mailman)
This message seems that it delivers a command '/usr/lib/mailman/mail/mailman post' to execute against the mailman mailing list, however, the customer never use mailman mailing list on their system. One thing that I doubt is that a cronjob in /etc/cron.d/mailman does something relevant of this because the post time of the messages is always reight after the following work.
---</etc/cron.d/mailman>--- 0 12 * * * mailman /usr/lib/mailman/cron/senddigests
or
0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman /usr/lib/mailman/cron/gate_news
I'm afraid that I don't have /etc/mailman/aliases file of cutomer's, but by default(in my test env), it should looks like below.
</etc/mailman/aliease>
STANZA START: mailman
CREATED: Mon Jan 25 16:48:18 2010
mailman: "|/usr/lib/mailman/mail/mailman post mailman" mailman-admin: "|/usr/lib/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman" mailman-join: "|/usr/lib/mailman/mail/mailman join mailman" mailman-leave: "|/usr/lib/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/lib/mailman/mail/mailman owner mailman" mailman-request: "|/usr/lib/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/lib/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman"
STANZA END: mailman
My questions are as follows.
1.What exactly is the cause the message in /var/log/maillog? 2.Why does the messages send to mailman(mailman@example.co.jp) user even though that mailing list never be used?
OS:RHEL5 postfix-2.3.3-2.1.el5_2 mailman-2.1.9-4.el5
Any comments would be greatly appreciated.
Best Regards,
--
Masaharu Kawada Associate Technical Support Engineer Red Hat K K Ebisu Neonato 5F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482
On 02/26/2010 04:50 AM Masaharu Kawada wrote:
Dear list,
I am sorry if this question should not be posted here, but I believe that there are many experts of postfix or any other thing such as mailing lists in this list. I am kind of in hurry and need some advices to know about my questions. Could anyone in this list please answer my questions if you know.
Still no feedback? Maybe really the wrong list here. The list, that you are searching, seems to be listed at: http://www.list.org/lists.html
Regards, Pascal
The trapper recommends today: c01dcafe.1005715@localdomain.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 26 Feb 2010, Masaharu Kawada wrote:
to execute against the mailman mailing list, however, the customer never use mailman mailing list on their system. One thing that I doubt is that
"mailman" is the administrative, contact queue of Mailman (well, call it as you like). In previous versions this address used to be just a mail address, in newer versions this is a list like any other.
Therefore "post" can happen, if someone from the outside tries to mail/spam you, a problem is forwarded to a site admin etc.pp.
Regards,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBS4fbOL+Vh58GPL/cAQL3fQgAia0HyMk92pHVSKx39iSRYT7v6cC2JikC uXRrI3iqvkLkYQ8iJskNcpGOGdASg1D8Q4Cas0qUksDfDc7oQBl5b2+lE58K8Mb3 z2mZ6TlbgK0w56FxD3FGxTWWRL5/sO7EyCsdhD/9fxtxlE8002oRnEYJ4NsAaHuq uPYovLbnCGDBPtz0HsAbqbzLGDNRAYlUijOLwytUUwO1XiDoE3Jf9T+Lh+vHZEkN Berh6h/IXSWO8NLfOaN8NL3OLb+erqR9vdBgD8fbiXEvnEuDYTYVUAfrDyp66ZIZ cRsH83FFxDdGwPODvdxoTRG7ihnQ87pePlwbUlrJ5VL/RHfEWlKUIQ== =LoJf -----END PGP SIGNATURE-----
On 11:59 AM, Masaharu Kawada wrote:
One of my customer gets the following log message into /var/log/maillog at around 12:00 every day.
---</var/log/maillog>--- 12:00:04 relay postfix/pickup[6279]: 244811C805C: uid=41 from=<mailman> 12:00:04 relay postfix/cleanup[21529]: 244811C805C: message-id=<20100215030004.244811C805C@example.co.jp> 12:00:04 relay postfix/qmgr[20068]: 244811C805C: from=<mailman@example.co.jp>, size=1728, nrcpt=1 (queue active) 12:00:04 relay postfix/local[21232]: 244811C805C: to=<mailman@example.co.jp>, orig_to=<mailman>, relay=local, delay=0.17, delays=0.05/0/0/0.12, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post mailman)
This question should have been posted to mailman-users@python.org, but since I am the Mailman developer that probably would have answered it there, I'll try to answer here.
The above Postfix log entries are from a normal message to a mailman list (such as this one). It is a message that was sent to mailman@example.co.jp from mailman@example.co.jp.
Since it occurs daily at noon, the default time for sending digests, I think it is related to that.
This message seems that it delivers a command '/usr/lib/mailman/mail/mailman post' to execute against the mailman mailing list, however, the customer never use mailman mailing list on their system. One thing that I doubt is that a cronjob in /etc/cron.d/mailman does something relevant of this because the post time of the messages is always reight after the following work.
---</etc/cron.d/mailman>--- 0 12 * * * mailman /usr/lib/mailman/cron/senddigests
or
0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman /usr/lib/mailman/cron/gate_news
It is almost certainly not gate_news. I'm sure it is senddigests.
Every Mailman 2.1.x installation has a site list which is normally named 'mailman'.
I'm afraid that I don't have /etc/mailman/aliases file of cutomer's, but by default(in my test env), it should looks like below.
</etc/mailman/aliease>
STANZA START: mailman
CREATED: Mon Jan 25 16:48:18 2010
mailman: "|/usr/lib/mailman/mail/mailman post mailman" mailman-admin: "|/usr/lib/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman" mailman-join: "|/usr/lib/mailman/mail/mailman join mailman" mailman-leave: "|/usr/lib/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/lib/mailman/mail/mailman owner mailman" mailman-request: "|/usr/lib/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/lib/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman"
STANZA END: mailman
Yes, it would be that.
My questions are as follows.
1.What exactly is the cause the message in /var/log/maillog?
A message sent to mailman@example.co.jp which via the alias above is posted to the 'mailman' list by piping to the command
/usr/lib/mailman/mail/mailman post mailman
2.Why does the messages send to mailman(mailman@example.co.jp) user even though that mailing list never be used?
The mailing list is used. The address is the source of some messages and is also on the listinfo overview page in the message
If you are having trouble using the lists, please contact mailman@example.co.jp.
and on the admin overview page in the message
(Send questions and comments to mailman@example.co.jp.)
What exactly is happening is not clear. My first guess is that mailman@example.co.jp is a member of the mailman@example.co.jp list, and every day, a digest is sent to that member and posted back to the list ensuring there will be another digest the next day, but there is protection in Mailman against this kind of loop, so that probably isn't it.
The bottom line is there is a mailman@example.co.jp list, and someone needs to examine its membership and archives and also Mailman's logs on that machine to figure this out.
If you need to follow up, please join mailman-users@python.org <http://mail.python.org/mailman/listinfo/mailman-users> and follow up there.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Dear list,
Thanks alot for all of you who gave me suggestions on my questions. I appreciate it!
Mark-san,
Thank you for your detailed explanation.
A message sent to mailman@example.co.jp which via the alias above is posted to the 'mailman' list by piping to the command
/usr/lib/mailman/mail/mailman post mailman
I'm sorry that I still have one more thing to ask. Even if the mail(sent to mailman@ via that alias) is because of senddigests, what exaclty does it mean? I mean that what does 'post' commnad do(what is gonna happen if the 'post mailman' executed)?
The mailing list is used. The address is the source of some messages and is also on the listinfo overview page in the message
If you are having trouble using the lists, please contact mailman@example.co.jp.
and on the admin overview page in the message
(Send questions and comments to mailman@example.co.jp.)
As for the above, do you mean that the admin is mailman user which specified as a 'owner' option?
On the other hand, I have joined mailman-users@python.org as you led me know.
Best Regards,
Mark Sapiro wrote:
On 11:59 AM, Masaharu Kawada wrote:
One of my customer gets the following log message into /var/log/maillog at around 12:00 every day.
---</var/log/maillog>--- 12:00:04 relay postfix/pickup[6279]: 244811C805C: uid=41 from=<mailman> 12:00:04 relay postfix/cleanup[21529]: 244811C805C: message-id=<20100215030004.244811C805C@example.co.jp> 12:00:04 relay postfix/qmgr[20068]: 244811C805C: from=<mailman@example.co.jp>, size=1728, nrcpt=1 (queue active) 12:00:04 relay postfix/local[21232]: 244811C805C: to=<mailman@example.co.jp>, orig_to=<mailman>, relay=local, delay=0.17, delays=0.05/0/0/0.12, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post mailman)
This question should have been posted to mailman-users@python.org, but since I am the Mailman developer that probably would have answered it there, I'll try to answer here.
The above Postfix log entries are from a normal message to a mailman list (such as this one). It is a message that was sent to mailman@example.co.jp from mailman@example.co.jp.
Since it occurs daily at noon, the default time for sending digests, I think it is related to that.
This message seems that it delivers a command '/usr/lib/mailman/mail/mailman post' to execute against the mailman mailing list, however, the customer never use mailman mailing list on their system. One thing that I doubt is that a cronjob in /etc/cron.d/mailman does something relevant of this because the post time of the messages is always reight after the following work.
---</etc/cron.d/mailman>--- 0 12 * * * mailman /usr/lib/mailman/cron/senddigests
or
0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman /usr/lib/mailman/cron/gate_news
It is almost certainly not gate_news. I'm sure it is senddigests.
Every Mailman 2.1.x installation has a site list which is normally named 'mailman'.
I'm afraid that I don't have /etc/mailman/aliases file of cutomer's, but by default(in my test env), it should looks like below.
</etc/mailman/aliease>
STANZA START: mailman
CREATED: Mon Jan 25 16:48:18 2010
mailman: "|/usr/lib/mailman/mail/mailman post mailman" mailman-admin: "|/usr/lib/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman" mailman-join: "|/usr/lib/mailman/mail/mailman join mailman" mailman-leave: "|/usr/lib/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/lib/mailman/mail/mailman owner mailman" mailman-request: "|/usr/lib/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/lib/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman"
STANZA END: mailman
Yes, it would be that.
My questions are as follows.
1.What exactly is the cause the message in /var/log/maillog?
A message sent to mailman@example.co.jp which via the alias above is posted to the 'mailman' list by piping to the command
/usr/lib/mailman/mail/mailman post mailman
2.Why does the messages send to mailman(mailman@example.co.jp) user even though that mailing list never be used?
The mailing list is used. The address is the source of some messages and is also on the listinfo overview page in the message
If you are having trouble using the lists, please contact mailman@example.co.jp.
and on the admin overview page in the message
(Send questions and comments to mailman@example.co.jp.)
What exactly is happening is not clear. My first guess is that mailman@example.co.jp is a member of the mailman@example.co.jp list, and every day, a digest is sent to that member and posted back to the list ensuring there will be another digest the next day, but there is protection in Mailman against this kind of loop, so that probably isn't it.
The bottom line is there is a mailman@example.co.jp list, and someone needs to examine its membership and archives and also Mailman's logs on that machine to figure this out.
If you need to follow up, please join mailman-users@python.org <http://mail.python.org/mailman/listinfo/mailman-users> and follow up there.
--
Masaharu Kawada Associate Technical Support Engineer Red Hat K K Ebisu Neonato 5F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482
Masaharu Kawada wrote:
I'm sorry that I still have one more thing to ask. Even if the mail(sent to mailman@ via that alias) is because of senddigests, what exaclty does it mean? I mean that what does 'post' commnad do(what is gonna happen if the 'post mailman' executed)?
The command
/usr/lib/mailman/mail/mailman post mailman
takes the standard input (the message) and creates a queue entry in Mailman's 'in' queue (maybe at /var/lib/mailman/qfiles/in/) containing the message as a 'post' to the 'mailman' list.
All posts to any Mailman lists are handled in exactly the same way - only the list name is different.
The mailing list is used. The address is the source of some messages and is also on the listinfo overview page in the message
If you are having trouble using the lists, please contact mailman@example.co.jp.
and on the admin overview page in the message
(Send questions and comments to mailman@example.co.jp.)
As for the above, do you mean that the admin is mailman user which specified as a 'owner' option?
The above is talking about the Mailman web interface. The "admin overview page" to which I refer is the web page at a URL like
http://your_host/mailman/admin
and the listinfo overview is at something like
http://your_host/mailman/listinfo
On the other hand, I have joined mailman-users@python.org as you led me know.
And any follow-up questions should be posted there, not here as this discussion is way off topic for dovecot.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark-san,
Thank you very much for your response!
I got better understanding on mailman with your explanations. I really appreciate it.
When I next time get something to ask, I will post it to mailman-users@python.org.
Best Regards,
Mark Sapiro wrote:
Masaharu Kawada wrote:
I'm sorry that I still have one more thing to ask. Even if the mail(sent to mailman@ via that alias) is because of senddigests, what exaclty does it mean? I mean that what does 'post' commnad do(what is gonna happen if the 'post mailman' executed)?
The command
/usr/lib/mailman/mail/mailman post mailman
takes the standard input (the message) and creates a queue entry in Mailman's 'in' queue (maybe at /var/lib/mailman/qfiles/in/) containing the message as a 'post' to the 'mailman' list.
All posts to any Mailman lists are handled in exactly the same way - only the list name is different.
The mailing list is used. The address is the source of some messages and is also on the listinfo overview page in the message
If you are having trouble using the lists, please contact mailman@example.co.jp.
and on the admin overview page in the message
(Send questions and comments to mailman@example.co.jp.)
As for the above, do you mean that the admin is mailman user which specified as a 'owner' option?
The above is talking about the Mailman web interface. The "admin overview page" to which I refer is the web page at a URL like
http://your_host/mailman/admin
and the listinfo overview is at something like
http://your_host/mailman/listinfo
On the other hand, I have joined mailman-users@python.org as you led me know.
And any follow-up questions should be posted there, not here as this discussion is way off topic for dovecot.
--
Masaharu Kawada Associate Technical Support Engineer Red Hat K K Ebisu Neonato 5F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482
participants (4)
-
Mark Sapiro
-
Masaharu Kawada
-
Pascal Volk
-
Steffen Kaiser