mailman sending to existing subscribers but new subscribe doesn't work

Hello,
We recently moved our list to a new server. Same domain name.
Emails to the list work fine for existing subscribers but we can't add new subscribers. The mass subscription seems to work and the new users appear in the list but don't receive email, even though they receive the welcome email.
Possibly related, nothing appears on the moderation page for admins even though they receive a notice of pending items to moderate.
I've run check_perms and moved the files by rsync so permissions should be ok.
One other difference from the old server, the web pages are hosted using nginx which passes the requests to Apache.
Any ideas?
Thanks,
Dave

On 09/02/2014 01:28 PM, David Whited-Ford wrote:
We recently moved our list to a new server. Same domain name.
Emails to the list work fine for existing subscribers but we can't add new subscribers. The mass subscription seems to work and the new users appear in the list but don't receive email, even though they receive the welcome email.
There appear to be DNS issues. I.e Mail to the list is going to the old server, not the new.
Possibly related, nothing appears on the moderation page for admins even though they receive a notice of pending items to moderate.
The notice probably comes from the old server and the web URL goes to the new server.
See the FAQ at <http://wiki.list.org/x/EoCE>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Mark,
Thanks for the post.
Indeed, the pending moderation is on the old server so that question is answered. Is that just a case of DNS not updating for some users? We do have that site running as a subdomain old.thatsite.coop.
But what about the subscription problem? Is that DNS related as well?
Thanks,
Dave
-----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+david.whited-ford=organicvalley.coop@python.org] On Behalf Of Mark Sapiro Sent: Wednesday, September 03, 2014 1:08 AM To: mailman-users@python.org Subject: Re: [Mailman-Users] mailman sending to existing subscribers but new subscribe doesn't work
On 09/02/2014 01:28 PM, David Whited-Ford wrote:
We recently moved our list to a new server. Same domain name.
Emails to the list work fine for existing subscribers but we can't add new subscribers. The mass subscription seems to work and the new users appear in the list but don't receive email, even though they receive the welcome email.
There appear to be DNS issues. I.e Mail to the list is going to the old server, not the new.
Possibly related, nothing appears on the moderation page for admins even though they receive a notice of pending items to moderate.
The notice probably comes from the old server and the web URL goes to the new server.
See the FAQ at <http://wiki.list.org/x/EoCE>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/david.whited-ford%40or...

On 09/03/2014 04:11 AM, David Whited-Ford wrote:
But what about the subscription problem? Is that DNS related as well?
My guess is that new members are added to the list on the new server, but the MX for the list domain still points to the old server so that posts to the list go to the old server where the new members aren't on the list.
It could also be that DNS has been updated but the old MX and/or A records had long time to live and haven't aged out of some users' DNS caches yet, but this seems unlikely.
You could check Mailman's 'post' log on both servers to see which one is processing posts.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
David Whited-Ford
-
Mark Sapiro