Admin Approval Emails Not Sent
Mailman version 2.1.16 Installed via apt-get Server OS is Ubuntu 14.04.3 LTS MTA is postfix version 2.11.0
When a user subscribes to the email list, an approval email is not being sent to the admins/moderators. The variables admin_immed_notify and admin_notify_mchanges are set to yes. The subscribe requests are getting picked up during the daily cron job and an email is then sent at 8:00 AM.
Test emails to -owner work internally from postfix and when sent externally from gmail.
Here's a link to all the log file snippets from the time of the subscribe request: https://gist.github.com/dmofot/c367151ba262f476c2c6
Any ideas where to start troubleshooting this issue?
DT
On 09/10/2015 08:17 AM, DT wrote:
Test emails to -owner work internally from postfix and when sent externally from gmail.
OK.
There are things missing, perhaps because they didn't happen or because you didn't include them. Here's what I see and what I expect.
Your smtp log: Sep 09 14:41:45 2015 (7788) <mailman.0.1441824103.9593.wort@wort.org> smtp to wort for 1 recips, completed in 0.052 seconds
This is the notice being sent to wort-owner. There should be a subsequent entry with the same message-id for 'n' recips where n is the total number of owners and moderators. That is the delivery of the message from wort-owner to the owners and moderators.
log :: mail.log
... Sep 9 14:41:45 davidtodd postfix/pickup[9566]: 79FF9C0727: uid=1001 from=<wort-bounces@wort.org> Sep 9 14:41:45 davidtodd postfix/cleanup[9597]: 79FF9C0727: message-id=<mailman.0.1441824103.9593.wort@wort.org> Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signing table match for 'wort-owner@wort.org' Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signature data Sep 9 14:41:45 davidtodd postfix/qmgr[8528]: 79FF9C0727: from=<wort-bounces@wort.org>, size=1492, nrcpt=1 (queue active) Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=<wort-owner@wort.org>, relay=mailroom5.hostrocket.com[66.147.229.200]:25, delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK id=1ZZkJb-0003U2-Lm) Sep 9 14:41:51 davidtodd postfix/qmgr[8528]: 79FF9C0727: removed
The above is the delivery of the message to wort-owner. It should be delivered to a pipe "|/var/lib/mailman/mail/mailman wort owner" to get to mailman, not relayed to mailroom5.hostrocket.com. This may explain the issue, but then how does mail simply sent to wort-owner work?
log :: error
You apparently have enabled smtplib debugging as in the FAQ at <http://wiki.list.org/x/4030716>, but this tells us nothing new that we don't already see in the smtp and mail.log logs.
log :: syslog
And likewise syslog
Bottom line - If you are showing everything, the notice to wort-owner is being relayed to mailroom5.hostrocket.com and never gets to Mailman for delivery to the actual owner and moderator addresses.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 09/10/2015 05:06 PM, Mark Sapiro wrote:
The above is the delivery of the message to wort-owner. It should be delivered to a pipe "|/var/lib/mailman/mail/mailman wort owner" ...
Actually, the pipe should be something like "|/var/lib/mailman/mail/mailman owner wort" rather than 'wort owner'. This is one of the 10 required aliases for the list unless you deliver to Mailman via some other method.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Ok, so maybe this has to do with the setup. The list is for a club who has shared hosting for web and email at HostRocket for wort.org. The list was always hosted somewhere else. They were having some other issues and I migrated the list to my server, davidtodd.info.
All the wort.org emails (even the list ones) are on the HostRocket server and they forward to the same address with a davidtodd.info domain. So wort-owner@wort.org is at HostRocket and forwards to wort-owner@davidtodd.info where the list is actually hosted. When users post to the list, they send to wort@wort.org, which forwards to wort@davidtodd.info...and on and on.
Users have no issues posting to the list and sending an email to wort-owner@wort.org (which forwards) works. An email to wort-admin@wort.org successfully results in a bounce.
On Thu, Sep 10, 2015 at 8:06 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 09/10/2015 06:01 PM, DT wrote:
OK, so the above message was delivered to mailroom5.hostrocket.com for wort-owner@wort.org with mailroom5.hostrocket.com smtp id 1ZZkJb-0003U2-Lm and should have come back to wort-owner@davidtodd.info.
Did it come back? Was it delivered to Mailman. What do the logs on davidtodd.info say about it?
If it didn't come back, hostrocket accepted it and then discarded it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Nothing in the logs on davidtodd.info indicate that it came back. Unfortunately, HostRocket doesn't allow shared users access to any of the system logs other than apache, so I can't easily check to see if they received it and discarded it. I'll submit a trouble ticket to see if I can get access.
On Thu, Sep 10, 2015 at 9:11 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 09/10/2015 08:39 PM, DT wrote:
This message says they received and accepted it.
Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=<wort-owner@wort.org>, relay=mailroom5.hostrocket.com[66.147.229.200]:25, delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK id=1ZZkJb-0003U2-Lm)
They responded to the SMTP delivery with (250 OK id=1ZZkJb-0003U2-Lm) which means they accepted it at SMTP time. Ask them what happened to this message that they received at Sep 9 14:41:51 with their smtp id 1ZZkJb-0003U2-Lm because it was supposed to be relayed back to wort-owner@davidtodd.info and never arrived.
You might be better off teaching your postfix to deliver Mailman mail directly rather that relaying it through hostrocket.
Given that you said earlier that mail you send directly to wort-owner@wort.org does get properly delivered as does the daily summary, I suspect that hostrocket for some reason thinks the immediate notice is spam and just tosses it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Ok, trouble ticket submitted to see if they can confirm why they are discarding the immediate notice.
Off to read up on postfix to see if I can figure out the teaching it to deliver directly to Mailman. Thanks for the suggestion and I'll be sure to update once I hear back from my ticket.
On Fri, Sep 11, 2015 at 12:02 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 09/10/2015 09:48 PM, DT wrote:
You may find the FAQ article at <http://wiki.list.org/x/10715238> helpful.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Here's a final update now that this is finally sorted out. It was just as Mark said, HostRocket was catching the immediate notifications in some spam filter. After submitting a trouble ticket, they adjusted their filter and it hasn't been a problem since.
You may find the FAQ article at <http://wiki.list.org/x/10715238> helpful.
Thanks again Mark. All the examples appear to be for doing a transport of an entire domain, but I did find this - http://www.docunext.com/blog/2011/01/using-postfix-transport-maps-for-email-...
- which I think will allow me to internally route just the mailman specific addresses for the wort.org domain locally.
On Fri, Sep 11, 2015 at 12:48 AM, DT <dmofot@gmail.com> wrote:
On 09/14/2015 11:47 AM, DT wrote:
Actually, the FAQ article at <http://wiki.list.org/x/10715238> tells you how to modify Mailman's existing postfix integration facility to create transport maps to route list addresses only to Postfix's local transport.
I don't know what you saw in that article, but the third paragraph specifically says "Some people find these features insufficient as they want to use some specific transport or other mapping for Mailman list addresses that is *not* applied to all addresses in the list domain(s). The following is a way to automate the generation of some Postfix map via editing the Mailman generated virtual-mailman file." (emphasis mine)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I must have been confused when first reading through the wiki. Followed the directions and it's working as intended - all mailman specific wort.org emails are delivered locally and all other wort.org emails are relayed to HostRocket. Thanks again Mark!
On Mon, Sep 14, 2015 at 10:55 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 09/10/2015 08:17 AM, DT wrote:
Test emails to -owner work internally from postfix and when sent externally from gmail.
OK.
There are things missing, perhaps because they didn't happen or because you didn't include them. Here's what I see and what I expect.
Your smtp log: Sep 09 14:41:45 2015 (7788) <mailman.0.1441824103.9593.wort@wort.org> smtp to wort for 1 recips, completed in 0.052 seconds
This is the notice being sent to wort-owner. There should be a subsequent entry with the same message-id for 'n' recips where n is the total number of owners and moderators. That is the delivery of the message from wort-owner to the owners and moderators.
log :: mail.log
... Sep 9 14:41:45 davidtodd postfix/pickup[9566]: 79FF9C0727: uid=1001 from=<wort-bounces@wort.org> Sep 9 14:41:45 davidtodd postfix/cleanup[9597]: 79FF9C0727: message-id=<mailman.0.1441824103.9593.wort@wort.org> Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signing table match for 'wort-owner@wort.org' Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signature data Sep 9 14:41:45 davidtodd postfix/qmgr[8528]: 79FF9C0727: from=<wort-bounces@wort.org>, size=1492, nrcpt=1 (queue active) Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=<wort-owner@wort.org>, relay=mailroom5.hostrocket.com[66.147.229.200]:25, delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK id=1ZZkJb-0003U2-Lm) Sep 9 14:41:51 davidtodd postfix/qmgr[8528]: 79FF9C0727: removed
The above is the delivery of the message to wort-owner. It should be delivered to a pipe "|/var/lib/mailman/mail/mailman wort owner" to get to mailman, not relayed to mailroom5.hostrocket.com. This may explain the issue, but then how does mail simply sent to wort-owner work?
log :: error
You apparently have enabled smtplib debugging as in the FAQ at <http://wiki.list.org/x/4030716>, but this tells us nothing new that we don't already see in the smtp and mail.log logs.
log :: syslog
And likewise syslog
Bottom line - If you are showing everything, the notice to wort-owner is being relayed to mailroom5.hostrocket.com and never gets to Mailman for delivery to the actual owner and moderator addresses.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 09/10/2015 05:06 PM, Mark Sapiro wrote:
The above is the delivery of the message to wort-owner. It should be delivered to a pipe "|/var/lib/mailman/mail/mailman wort owner" ...
Actually, the pipe should be something like "|/var/lib/mailman/mail/mailman owner wort" rather than 'wort owner'. This is one of the 10 required aliases for the list unless you deliver to Mailman via some other method.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Ok, so maybe this has to do with the setup. The list is for a club who has shared hosting for web and email at HostRocket for wort.org. The list was always hosted somewhere else. They were having some other issues and I migrated the list to my server, davidtodd.info.
All the wort.org emails (even the list ones) are on the HostRocket server and they forward to the same address with a davidtodd.info domain. So wort-owner@wort.org is at HostRocket and forwards to wort-owner@davidtodd.info where the list is actually hosted. When users post to the list, they send to wort@wort.org, which forwards to wort@davidtodd.info...and on and on.
Users have no issues posting to the list and sending an email to wort-owner@wort.org (which forwards) works. An email to wort-admin@wort.org successfully results in a bounce.
On Thu, Sep 10, 2015 at 8:06 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 09/10/2015 06:01 PM, DT wrote:
OK, so the above message was delivered to mailroom5.hostrocket.com for wort-owner@wort.org with mailroom5.hostrocket.com smtp id 1ZZkJb-0003U2-Lm and should have come back to wort-owner@davidtodd.info.
Did it come back? Was it delivered to Mailman. What do the logs on davidtodd.info say about it?
If it didn't come back, hostrocket accepted it and then discarded it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Nothing in the logs on davidtodd.info indicate that it came back. Unfortunately, HostRocket doesn't allow shared users access to any of the system logs other than apache, so I can't easily check to see if they received it and discarded it. I'll submit a trouble ticket to see if I can get access.
On Thu, Sep 10, 2015 at 9:11 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 09/10/2015 08:39 PM, DT wrote:
This message says they received and accepted it.
Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=<wort-owner@wort.org>, relay=mailroom5.hostrocket.com[66.147.229.200]:25, delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK id=1ZZkJb-0003U2-Lm)
They responded to the SMTP delivery with (250 OK id=1ZZkJb-0003U2-Lm) which means they accepted it at SMTP time. Ask them what happened to this message that they received at Sep 9 14:41:51 with their smtp id 1ZZkJb-0003U2-Lm because it was supposed to be relayed back to wort-owner@davidtodd.info and never arrived.
You might be better off teaching your postfix to deliver Mailman mail directly rather that relaying it through hostrocket.
Given that you said earlier that mail you send directly to wort-owner@wort.org does get properly delivered as does the daily summary, I suspect that hostrocket for some reason thinks the immediate notice is spam and just tosses it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Ok, trouble ticket submitted to see if they can confirm why they are discarding the immediate notice.
Off to read up on postfix to see if I can figure out the teaching it to deliver directly to Mailman. Thanks for the suggestion and I'll be sure to update once I hear back from my ticket.
On Fri, Sep 11, 2015 at 12:02 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 09/10/2015 09:48 PM, DT wrote:
You may find the FAQ article at <http://wiki.list.org/x/10715238> helpful.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Here's a final update now that this is finally sorted out. It was just as Mark said, HostRocket was catching the immediate notifications in some spam filter. After submitting a trouble ticket, they adjusted their filter and it hasn't been a problem since.
You may find the FAQ article at <http://wiki.list.org/x/10715238> helpful.
Thanks again Mark. All the examples appear to be for doing a transport of an entire domain, but I did find this - http://www.docunext.com/blog/2011/01/using-postfix-transport-maps-for-email-...
- which I think will allow me to internally route just the mailman specific addresses for the wort.org domain locally.
On Fri, Sep 11, 2015 at 12:48 AM, DT <dmofot@gmail.com> wrote:
On 09/14/2015 11:47 AM, DT wrote:
Actually, the FAQ article at <http://wiki.list.org/x/10715238> tells you how to modify Mailman's existing postfix integration facility to create transport maps to route list addresses only to Postfix's local transport.
I don't know what you saw in that article, but the third paragraph specifically says "Some people find these features insufficient as they want to use some specific transport or other mapping for Mailman list addresses that is *not* applied to all addresses in the list domain(s). The following is a way to automate the generation of some Postfix map via editing the Mailman generated virtual-mailman file." (emphasis mine)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I must have been confused when first reading through the wiki. Followed the directions and it's working as intended - all mailman specific wort.org emails are delivered locally and all other wort.org emails are relayed to HostRocket. Thanks again Mark!
On Mon, Sep 14, 2015 at 10:55 PM, Mark Sapiro <mark@msapiro.net> wrote:
participants (2)
-
DT -
Mark Sapiro