FAQ
Dear list,

I'm sorry if this is a stupid question.

A following message keep appearing in /var/log/mailman/vette
at around 12:00 every day.

---
Mailman post from root at example.co.jp held, message-id=<20100
42900100.xxxxxx0 at example.co.jp>: Post by non-member to a members-only list
---

This seems to be related to a cron job(senddigest), so, one way to make this
stopped is to comment out the line regarding senddigest in
/usr/lib/mailman/cron/cron.in.

#0 12 * * * mailman /usr/lib/mailman/cron/senddigests

However, what is that member to a members-only list? If I remember right,
the 'mailman' mailing list created by default, and then administrator's
password
was asked to the list.

How could I add a member to a members-only list to stop that message?

Sincerely,

Masaharu Kawada

Search Discussions

  • Mark Sapiro at May 12, 2010 at 2:34 pm

    Masaharu Kawada wrote:
    A following message keep appearing in /var/log/mailman/vette
    at around 12:00 every day.

    ---
    Mailman post from root at example.co.jp held, message-id=<20100
    42900100.xxxxxx0 at example.co.jp>: Post by non-member to a members-only list
    ---

    This seems to be related to a cron job(senddigest), so, one way to make this
    stopped is to comment out the line regarding senddigest in
    /usr/lib/mailman/cron/cron.in.

    #0 12 * * * mailman /usr/lib/mailman/cron/senddigests

    However, what is that member to a members-only list? If I remember right,
    the 'mailman' mailing list created by default, and then administrator's
    password
    was asked to the list.

    How could I add a member to a members-only list to stop that message?

    Mailman's cron/senddigests runs as the mailman user and is encountering
    an error and producing output. This output is being mailed by crond to
    'mailman' and is being delivered to the 'mailman' list. It is from
    'root at ...'. The mailman list in turn is set with
    generic_nonmember_action = Hold and 'root at ...' is not a member of the
    mailman list, so the 'post' is held for moderator approval and the
    hold is logged in the vette log.

    You need to go to the admindb interface of the mailman list and see
    some of these posts and find and fix the problem in senddigests.

    You can add 'root at ...' as a member of the mailman list the same way you
    add members to any other list, but I don't recommend that.

    I recommend you do the following:

    1) Set the 'mailman' list's generic_nonmember_action to Accept.

    2) Make sure the mailman site admin is a non-digest member of the
    'mailman' list with delivery enabled.

    and optionally,

    3)Add 'MAILTO=the_address_of_the_mailman_site_admin' to Mailman's
    crontab so errors will be mailed directly to the admin instead of to
    the list.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Masaharu Kawada at May 13, 2010 at 1:07 am
    Hello Mark-san,

    Thank you very much for your help. Could I ask one more thing that is
    regarding one of your answers?
    You can add 'root at ...' as a member of the mailman list the same way you
    add members to any other list, but I don't recommend that.
    Why don't you recommend that? I just make sure the reason. Could you kindy
    answer this, please?

    Sincerely,


    Mark Sapiro wrote:
    Masaharu Kawada wrote:
    A following message keep appearing in /var/log/mailman/vette
    at around 12:00 every day.

    ---
    Mailman post from root at example.co.jp held, message-id=<20100
    42900100.xxxxxx0 at example.co.jp>: Post by non-member to a members-only list
    ---

    This seems to be related to a cron job(senddigest), so, one way to make this
    stopped is to comment out the line regarding senddigest in
    /usr/lib/mailman/cron/cron.in.

    #0 12 * * * mailman /usr/lib/mailman/cron/senddigests

    However, what is that member to a members-only list? If I remember right,
    the 'mailman' mailing list created by default, and then administrator's
    password
    was asked to the list.

    How could I add a member to a members-only list to stop that message?

    Mailman's cron/senddigests runs as the mailman user and is encountering
    an error and producing output. This output is being mailed by crond to
    'mailman' and is being delivered to the 'mailman' list. It is from
    'root at ...'. The mailman list in turn is set with
    generic_nonmember_action = Hold and 'root at ...' is not a member of the
    mailman list, so the 'post' is held for moderator approval and the
    hold is logged in the vette log.

    You need to go to the admindb interface of the mailman list and see
    some of these posts and find and fix the problem in senddigests.

    You can add 'root at ...' as a member of the mailman list the same way you
    add members to any other list, but I don't recommend that.

    I recommend you do the following:

    1) Set the 'mailman' list's generic_nonmember_action to Accept.

    2) Make sure the mailman site admin is a non-digest member of the
    'mailman' list with delivery enabled.

    and optionally,

    3)Add 'MAILTO=the_address_of_the_mailman_site_admin' to Mailman's
    crontab so errors will be mailed directly to the admin instead of to
    the list.
  • Mark Sapiro at May 13, 2010 at 2:12 am

    Masaharu Kawada wrote:
    Thank you very much for your help. Could I ask one more thing that is
    regarding one of your answers?
    You can add 'root at ...' as a member of the mailman list the same way you
    add members to any other list, but I don't recommend that.
    Why don't you recommend that? I just make sure the reason. Could you kindy
    answer this, please?

    Because I recommend opening the mailman list to posts from non-members
    and the people who should receive this mail are the Mailman site
    administrators who should be members of the site list. In most
    installations, mail to root would go to the overall system
    administrator(s) who normally would not be the best people the receive
    mail to mailman at ...

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Masaharu Kawada at May 13, 2010 at 3:07 am
    Mark-san,

    Thank you very much! I very much appreciate your help.

    Sincerely,

    Mark Sapiro wrote:
    Masaharu Kawada wrote:
    Thank you very much for your help. Could I ask one more thing that is
    regarding one of your answers?

    You can add 'root at ...' as a member of the mailman list the same way you
    add members to any other list, but I don't recommend that.
    Why don't you recommend that? I just make sure the reason. Could you kindy
    answer this, please?

    Because I recommend opening the mailman list to posts from non-members
    and the people who should receive this mail are the Mailman site
    administrators who should be members of the site list. In most
    installations, mail to root would go to the overall system
    administrator(s) who normally would not be the best people the receive
    mail to mailman at ...
  • Masaharu Kawada at May 19, 2010 at 9:31 am
    Hi Mark-san,

    Very sorry to ask you on this again. I'm a bit confused on the steps that
    you led me know before.
    I recommend you do the following:

    1) Set the 'mailman' list's generic_nonmember_action to Accept.

    2) Make sure the mailman site admin is a non-digest member of the
    'mailman' list with delivery enabled.

    and optionally,

    3)Add 'MAILTO=the_address_of_the_mailman_site_admin' to Mailman's
    crontab so errors will be mailed directly to the admin instead of to
    the list.
    As for the step 3, in this case, 'root@' should be set on the 'MAILTO='
    line in mailman's crontab? 'The_address_of_the_mailman_site_admin' is 'mailman@' though.

    Sincerely,


    Mark Sapiro wrote:
    Masaharu Kawada wrote:
    Thank you very much for your help. Could I ask one more thing that is
    regarding one of your answers?

    You can add 'root at ...' as a member of the mailman list the same way you
    add members to any other list, but I don't recommend that.
    Why don't you recommend that? I just make sure the reason. Could you kindy
    answer this, please?

    Because I recommend opening the mailman list to posts from non-members
    and the people who should receive this mail are the Mailman site
    administrators who should be members of the site list. In most
    installations, mail to root would go to the overall system
    administrator(s) who normally would not be the best people the receive
    mail to mailman at ...
  • Mark Sapiro at May 19, 2010 at 1:30 pm

    Masaharu Kawada quoted me and wrote:

    and optionally,

    3)Add 'MAILTO=the_address_of_the_mailman_site_admin' to Mailman's
    crontab so errors will be mailed directly to the admin instead of to
    the list.
    As for the step 3, in this case, 'root@' should be set on the 'MAILTO='
    line in mailman's crontab? 'The_address_of_the_mailman_site_admin' is 'mailman@' though.

    mailman at ... is a list, not a person. There is no point in adding
    MAILTO=mailman at ... to Mailman's crontab as that is where the mail goes
    by default anyway and steps 1 and 2 should ensure that the appropiate
    person/people receive it.

    Step 3 is only if you want to bypass the mailman list entirely and
    deliver these cron errors directly to a person, but for ease of
    maintenance, it is probably better not to do this and to deliver the
    errors to the site list as long as it's configured so someone actually
    recieves the mail.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Masaharu Kawada at May 20, 2010 at 12:28 am
    Hello Mark-san,

    Thank you very much for your answer.

    Sincerely,

    Mark Sapiro wrote:
    Masaharu Kawada quoted me and wrote:
    and optionally,

    3)Add 'MAILTO=the_address_of_the_mailman_site_admin' to Mailman's
    crontab so errors will be mailed directly to the admin instead of to
    the list.
    As for the step 3, in this case, 'root@' should be set on the 'MAILTO='
    line in mailman's crontab? 'The_address_of_the_mailman_site_admin' is 'mailman@' though.

    mailman at ... is a list, not a person. There is no point in adding
    MAILTO=mailman at ... to Mailman's crontab as that is where the mail goes
    by default anyway and steps 1 and 2 should ensure that the appropiate
    person/people receive it.

    Step 3 is only if you want to bypass the mailman list entirely and
    deliver these cron errors directly to a person, but for ease of
    maintenance, it is probably better not to do this and to deliver the
    errors to the site list as long as it's configured so someone actually
    recieves the mail.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedMay 12, '10 at 7:17a
activeMay 20, '10 at 12:28a
posts8
users2
websitelist.org

2 users in discussion

Masaharu Kawada: 5 posts Mark Sapiro: 3 posts

People

Translate

site design / logo © 2022 Grokbase