Mailman stopped working - authentication query

[wemail]

When I post to a long-established list, I get "Please turn on SMTP Authentication in your mail client. (xxx.xxx.info) [127.0.0.1]:49248 is not permitted to relay through this server without authentication...."

I have other lists which are working OK.

Is this a new problem or have I missed a change? The email to the list is sent using SMTP on port 465 which implies authentication, I believe.

 

[cPanelMichael]

Hello

Could you provide additional details on the mailing list you are sending an email to? Are the domain names you are sending to and from both handled on the cPanel server? Do either use a remote server for email hosting?

Thank you.

 

[wemail]

Thanks for reply. List is [email protected]. The emails being distributed to by Mailman include just two on the same server (myself and wife), and are otherwise a random selection of yahoo, hotmail, btinternet and other mostly-UK domains. My emails are sent using smtp.domain.com port 465, with a matching SPF record. I have two other mailing lists on the server which are working OK. No other servers are involved (to my knowledge).

 

[cPanelMichael]

Do you have root access to this system in order to review /var/log/exim_mainlog for the messages you send to the list?

Thank you.

 

[wemail]

This problem has I think been resolved by support staff at Memset Ltd in UK, my hosting provider. Apparently the problem was that Mailman itself was not using authentication when sending generated emails, so he has changed the port to 465 and it appears to be OK now. The error messages were implying that the original poster was not using authentication - but I was.

Regards

 

[cPanelMichael]

I am happy to see the issue is now resolved. Thank you for updating us with the outcome.

 

[wemail]

Further to previous on 29 Feb 2016, the problem came back again a few days after. Emails to my lists are shown in the Mailman archive, but are not forwarded to the list members. Previous fix of forcing use of SMTP PORT 465 checked and is still in place, but lists still not working. My hosting provider suggested disabling ASSP X but this re-enables itself immediately and I am unsure how to get round this.

 

[wemail]

I was today asked to submit this problem as a support request. It is now a pending ticket.

 

[cPanelMichael]

I was today asked to submit this problem as a support request. It is now a pending ticket.

Hello

To update, it looks like the issue was related to the specific kernel (3.18-26-x1) installed on this system (CentOS 5.11/Xen PV). The user was advised to switch to the latest 2.6 kernel available.

Thank you.

 

[wemail]

Thanks.

I have been asked to suggest that Mailman's support be asked to solve the problem in a more permanent manner - without requiring use of an old kernel, which might have security issues. I do not know who to contact.

Regards

--
Aidan

 

[cPanelMichael]

Mailman uses launchpad for their bug reports:

Bugs : GNU Mailman

However, note that since this is associated with CentOS 5, it's important to keep in mind the EOL date for this OS with cPanel is March 31, 2017:

Third-Party Software End Of Life Policy for cPanel & WHM - Documentation - cPanel Documentation

Thank you.

 

[wemail]

Indeed, but is there still a problem with CentOS 6 or 7? We are currently considering upgrading to a new server with CentOS 7 - I am expecting the go-ahead over the holiday weekend.

Happy Easter

--
Aidan

 

[cPanelMichael]

Indeed, but is there still a problem with CentOS 6 or 7?

The few cases we have seen all used CentOS 5.x on the Xen PV environment.

Thank you.