Re: [Mailman-Users] Monthly Reminder Question
Thanks for the reply. Yes, it does the same thing. Is there a debug option for this?
On 3/20/2011 10:19 AM, Andrew Hodgson wrote:
Hi,
Have you tried it without any arguments? I just ran it on a virtual machine here and it worked fine. I don't know much details about the program if it should write to stderr/stdout etc.
Andrew.
-----Original Message----- From: Dennis Putnam [mailto:dap1@bellsouth.net] Sent: 20 March 2011 00:01 To: Andrew Hodgson Subject: Re: [Mailman-Users] Monthly Reminder Question
I tried running that command from CLI and while it didn't output any errors, it also didn't produce any email that I could find. I have a test list with just me as a member ('python -S /usr/lib/mailman/cron/mailpasswds -l testlist'). I never received anything. Should the command write to 'stderr' if something is wrong? Should it write anything to 'stdout'?
On 3/18/2011 7:28 PM, Andrew Hodgson wrote:
Dennis Putnam wrote:
What triggers the monthly reminder? I cannot find any config parameter that lets me set what day or date in each month to send it. Does this >have t be done manually with a cron job? If so what is the command? It is in Cron - see the file in ~/cron/crontab.in:
[...] |# 5 AM on the first of each month, mail out password reminders. |0 5 1 * * /usr/bin/python -S /usr/local/mailman/cron/mailpasswds
See this section of the installation guide:
http://www.gnu.org/software/mailman/mailman-install/node41.html
Thanks. Andrew.
On 3/20/2011 5:35 PM, Dennis Putnam wrote:
Thanks for the reply. Yes, it does the same thing. Is there a debug option for this?
On 3/20/2011 10:19 AM, Andrew Hodgson wrote:
Hi,
Have you tried it without any arguments? I just ran it on a virtual machine here and it worked fine. I don't know much details about the program if it should write to stderr/stdout etc.
If the site list is missing, it writes a message to stderr and logs it to Mailman's 'error' log. If a member doesn't have a password, it logs that to Mailman's 'error' log.
If any uncaught exceptions occur, it writes a traceback to stderr.
Otherwise, it is silent.
It will not mail any reminders at all for a list if the list's General Options -> send_reminders is No. It will not mail to a user whose "Get password reminder email for this list?" option is no.
Otherwise, it will generate the mail and queue it in the virgin queue, and if VirginRunner, IncomingRunner and OutgoingRunner are all running and there is no error (logged in Mailman's error log) the mail will be sent.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks for the reply. I have verified all the settings, please see embedded comments below.
On 3/20/2011 10:16 PM, Mark Sapiro wrote:
On 3/20/2011 5:35 PM, Dennis Putnam wrote:
Thanks for the reply. Yes, it does the same thing. Is there a debug option for this?
On 3/20/2011 10:19 AM, Andrew Hodgson wrote:
Hi,
Have you tried it without any arguments? I just ran it on a virtual machine here and it worked fine. I don't know much details about the program if it should write to stderr/stdout etc.
If the site list is missing, it writes a message to stderr and logs it to Mailman's 'error' log. If a member doesn't have a password, it logs that to Mailman's 'error' log. Its empty. If any uncaught exceptions occur, it writes a traceback to stderr.
Otherwise, it is silent. It was silent. It will not mail any reminders at all for a list if the list's General Options -> send_reminders is No. It will not mail to a user whose "Get password reminder email for this list?" option is no. Both are set to yes. Otherwise, it will generate the mail and queue it in the virgin queue, and if VirginRunner, IncomingRunner and OutgoingRunner are all running and there is no error (logged in Mailman's error log) the mail will be sent.
They are all running.
On 3/21/2011 6:20 AM, Dennis Putnam wrote:
On 3/20/2011 10:16 PM, Mark Sapiro wrote:
If the site list is missing, it writes a message to stderr and logs it to Mailman's 'error' log. If a member doesn't have a password, it logs that to Mailman's 'error' log.
Its empty.
If any uncaught exceptions occur, it writes a traceback to stderr.
Otherwise, it is silent. It was silent. It will not mail any reminders at all for a list if the list's General Options -> send_reminders is No. It will not mail to a user whose "Get password reminder email for this list?" option is no. Both are set to yes. Otherwise, it will generate the mail and queue it in the virgin queue, and if VirginRunner, IncomingRunner and OutgoingRunner are all running and there is no error (logged in Mailman's error log) the mail will be sent.
They are all running.
Just to be sure, check qfiles/virgin/ for any message entries (.pck files).
Also check Mailman's smtp log for the time you ran cron/mailpasswds. There should be an "smtp to mailman for 1 recips" entry for each reminder sent. If there aren't any, check the smtp-failure log. If there are smtp log entries, check the MTA logs.
Also, check the spam/junk folders of the recipients.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 3/21/2011 6:20 AM, Dennis Putnam wrote:
On 3/20/2011 10:16 PM, Mark Sapiro wrote:
If the site list is missing, it writes a message to stderr and logs it to Mailman's 'error' log. If a member doesn't have a password, it logs that to Mailman's 'error' log. Its empty. If any uncaught exceptions occur, it writes a traceback to stderr.
Otherwise, it is silent. It was silent. It will not mail any reminders at all for a list if the list's General Options -> send_reminders is No. It will not mail to a user whose "Get password reminder email for this list?" option is no. Both are set to yes. Otherwise, it will generate the mail and queue it in the virgin queue, and if VirginRunner, IncomingRunner and OutgoingRunner are all running and there is no error (logged in Mailman's error log) the mail will be sent.
They are all running.
Just to be sure, check qfiles/virgin/ for any message entries (.pck files). That directory is empty. Also check Mailman's smtp log for the time you ran cron/mailpasswds. There should be an "smtp to mailman for 1 recips" entry for each reminder sent. Yes, its there. If there aren't any, check the smtp-failure log. If there are smtp log entries, check the MTA logs. The only SMTP log that has anything in it is the info log (error and warning are both empty). I guess that makes sense when everything is working, Postfix-wise. However, I think I see the message, if it is from
On 3/21/2011 8:38 PM, Mark Sapiro wrote: listname-bounces. The problem is, I don't see who it is to (I think I may have the Postfix logging set wrong) so I don't know for sure if it really is the message and there is no indication it was sent, just removed.
Also, check the spam/junk folders of the recipients.
That is always the first place I check for missing email.
Dennis Putnam wrote:
On 3/21/2011 8:38 PM, Mark Sapiro wrote:
Also check Mailman's smtp log for the time you ran cron/mailpasswds. There should be an "smtp to mailman for 1 recips" entry for each reminder sent. Yes, its there.
"its" implies only one password reminder. Is this what you expect?
If there aren't any, check the smtp-failure log. If there are smtp log entries, check the MTA logs. The only SMTP log that has anything in it is the info log (error and warning are both empty). I guess that makes sense when everything is working, Postfix-wise. However, I think I see the message, if it is from listname-bounces.
It's from mailman-bounces or from mailman-bounces+user=example.com if VERP_PASSWORD_REMINDERS is Yes.
The problem is, I don't see who it is to (I think I may have the Postfix logging set wrong) so I don't know for sure if it really is the message and there is no indication it was sent, just removed.
I'm not familiar with Postfix logging configurations. In my case, I have
mail.* -/var/log/maillog
in /etc/syslog.conf and it logs everything to /var/log/maillog. If I grep /var/log/maillog for the message-id from Mailman's smtp log, I see a message like
Mar 1 05:00:21 sbh16 postfix/cleanup[25087]: C993B6902CE: message-id=<mailman.534.1298984420.25039.mailman@sbh16.songbird.com>
and if I then grep the log for the Postfix queue ID (C993B6902CE in this case), I see all the relevant messages. Well actually my situation is more complex as I run MailScanner so at some point Mailscanner requeues the message and I have to grep the second queue id too, but ultimately I see a log message with the disposition as in
Mar 1 05:40:12 sbh16 postfix/smtp[26370]: 196C7690104: to=<user@yahoo.com>, relay=i.mx.mail.yahoo.com[74.6.140.64]:25, delay=2390, delays=2385/0.25/0.58/4.2, dsn=2.0.0, status=sent (250 ok dirdel)
where 196C7690104 is requeue id from MailScanner and the 2390 second delay was due to Yahoo's greylisting in this case.
In any case, if you see the message arrive in the Postfix log and the queue entry ultimately removed, only Postfix can tell you what it did with it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Dennis Putnam -
Mark Sapiro