Squirrelmail webmail not sending

[xprt5]

You dont need to change the squirrelmail configuration to sendmail.

Try stopping/flushing your firewall (iptables) then test sending email from squirrelmail and it should work.

service iptables stop
iptables -F

[SageBrian]

It does seem firewall related.
I did not change anything in CSF.
When upgrading cPanel, something changed. Not sure if sqMail was using sendmail, and the update changed it back to 'false', or something else happened.

# Block outgoing SMTP except for root, exim and mailman (forces scripts/users
# to use the exim/sendmail binary instead of sockets access). This adds the
# protection as WHM > Tweak Settings > SMTP Tweaks, which are lost when using a
# firewall configuration script
SMTP_BLOCK = 1
# If SMTP_BLOCK is enabled but you want to allow local connections to port 25
# on the server (e.g. for web scripts) then enable this option too
SMTP_ALLOWLOCAL = 0

I do see this in CSF. Again, I did not change any settings. So, either cpanel changed something, or maybe CSF switched ALLOWLOCAL by itself.

I see the fix as either set sqMail to use SendMail, or set CSF to allow local scripts.

Would not the more secure answer by 'useSendMail' ?

[xprt5]

cPanel has not changed the squirrelmail configuration, the firewall rules had to have changed which started blocking SMTP access for Squirrelmail.

Completely firewall related.

[bamm]

I have not changed any firewalls across any of my servers...period.

This started happening after a cpanel update.

I just received a response from cpanel again. After going through a level 3 tech?...the 3rd level tech has logged it as a bug with the cpanel developers, and advised me that I will need to continue to edit the squirrel config file manually until they address the bug.

[sparek-3]

What version of cPanel is affected by this?

I'm running 11.11.0-RELEASE_16983 on all of our servers and the Squirrelmail config file is showing:

$useSendmail            = true;

Not sure what affect this would have on this discussion. It looks to me like cPanel changed the way Squirrelmail works by setting this to false in a later build.

[bamm]

WHM 11.11.0 cPanel 11.12.0-C17158

[sparek-3]

Maybe I'm wrong here, but this would seem to be something that cPanel changed. Now whether or not if that was to fix something else, I cannot say. But if in the latest Release (Sept 10) $useSendmail was set to True, then in the latest Current (Sept 19) it is set to False, then the point about who changed something would seem to be resolved.

If somebody from cPanel could clarify why this was changed or if it was just a mix up somewhere and will be fixed in a future release, that would be helpful. I don't think this has anything to do with CSF or any firewall settings.

At least that what I gather from this discussion.

[xprt5]

http://bugzilla.cpanel.net/show_bug.cgi?id=5917

Changes to the squirrelmail config can be saved by consulting the documentation
in cpanel/src/3rdparty/gpl/README-squirrelmail

[Bruce]

This whole thing makes no sense. Two servers, I had to change to "TRUE" in order to get them to send and the third is $useSendmail = false; and works with no problem.
Go figure !

[BoZz]

I also have two cpanel box's after a cpanel upgrade one is still working and the other broken? My first server is running RedHat EN which works and the second is running Cent OS which is broken. Shouldn't make a difference but have added this comment just in case it helps resolve this weird issue. I also have CSF on both box's but have not touched the settings at all.


Brett

[bamm]

I had opened a ticket as I expressed in one of my above posts, it was passed to 3 levels of techs and the last response I received was from the level 3 tech who said he was passing it on to one of the developers.

Yesterday I received an email stating the ticket has been closed due to no response from me in 120 hours and that if I continue to have issues to open a new ticket. Not sure what I was suppose to respond to since the issue was passed on to a developer.

I did notice this issue was fixed for a few days prior to them closing the ticket, but now its back.

Time to open yet another ticket I am guessing.

[cPanelDavidG]

I had opened a ticket as I expressed in one of my above posts, it was passed to 3 levels of techs and the last response I received was from the level 3 tech who said he was passing it on to one of the developers.

Yesterday I received an email stating the ticket has been closed due to no response from me in 120 hours and that if I continue to have issues to open a new ticket. Not sure what I was suppose to respond to since the issue was passed on to a developer.

I did notice this issue was fixed for a few days prior to them closing the ticket, but now its back.

Time to open yet another ticket I am guessing.

When you get the "This ticket will be closed in 60 hours if you do not respond" message, if the issue has not been resolved, please let us know. Otherwise, the ticket will automatically be closed by our ticketing system assuming everything has been taken care of.

[bamm]

So I should have responded to tell you that your other tech passed it on to your developers in order to keep the ticket open?

I am truly sorry, I was not aware that we needed to keep you informed that you were still working on the issue.

I'll open another ticket and be sure that I do that next time...again, I apologize.

[velda]

I've got this too, came with a cpanel update. Changing my firewall settings is a work-around, but we like to block port 25 from local scripts.

What's more, we saw this a few months back and it was the same sort of thing. If anyone picks up a CP update the puts squirrel back and using sendmail, please upate! )

[Silver_2000]

As of this morning I getting the same errors with squirrel mail

Connection refused
Server replied: 111 Can't open SMTP stream.

tried flushing the iptables

didnt work

$useSendmail = true; did work

I would love to know what changes were pushed that broke CPanel

Im also running the CSF firewall