ConfigServer Blog
Please note that support is not provided through this blog - any support related comments will be removed
07 May 08: New MailScanner Front-End (MSFE) v4.22
Changes:
If you're running either of the listed builds above, then you could have a broken MTA. For some bizarre reason, cPanel decided to add a new feature that breaks the standard MTA configuration of sending out all email on a servers main IP address. Their change is to send it out on the IP address of the sending domain. This means that unless all your rDNS PTR records for all of your servers IP addresses are set to your hostname a large number of receiving MTA's on the internet will either treat incoming email as spam or simply bounce it. In their wisdom, cPanel have made this massive MTA change as the new default in EDGE and CURRENT, changing the status quo without your knowledge or indeed control. You cannot currently disable this change and revert back to the way the MTA should work. In the short term, you can delete /etc/mailips and add a line to /scripts/postupcp to remove that file, however this still leaves a window between upcp running /scripts/updateuserdomains and /scripts/postupcp running when your outgoing email could be broken. Apparently this change was made to benefit the use of SPF records. Since that technology has proven to provide little or no benefit, and there are no requirements whatsoever in the MTA RFC's to use SPF, it seems bizarre that cPanel has taken this route as their default configuration. Note: MTA ~ SMTP Server 30 Apr 08: New csf v3.28
Changes:
30 Apr 08: New csf v3.27
Changes:
27 Apr 08: New csf v3.26
Changes:
22 Apr 08: New csf v3.25
Changes:
21 Apr 08: Problems with LWP and access to https URL's
If you're using perl scripts on your server that use LWP and suddenly find them failing with connections to https resources with the following type error: 500 read failed: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number then you've probably got LWP v5.811 installed which breaks SSL connections! The author fixed the problem he created after about two days with v5.812 but the damage was done on many servers. cPanel have put a hold back on cpan module updates for LWP to v5.810 but if your servers already upgraded LWP then you'll need to either upgrade it manually from the cpan source to v5.812 or downgrade to v5.810. 16 Apr 08: New csf v3.24
Changes:
16 Apr 08: New MailScanner Script v2.65
Changes:
14 Apr 08: New ClamAV v0.93
Changelog: http://sourceforge.net/project/shownotes.php?release_id=592112 Upgrade through WHM MSFE. |
Sidebar |



