central MX record (hub) for cPanel
Google and hotmail keep redirect our emails for spam folder.
I'm not talking about spam protections, because I DID THEM ALL (12 year experience):
Reverse Name Server
SPF Record
SSL Certificate
X-trace Headers
Sending limits
Anti-virus
Special Sending monitors software (for queue)
Smart Network Data Services (Microsoft)
Junk Mail Reporting Partner Program (Microsoft)
and more measures that I don't recall right now
But still, even if I have a server for one domain that host one email account only
the server IP are not on any spam blacklist, My email still redirected to Spam folder!
I believe it is only a marketing method from google and hotmail to move users to there email service
which is expensive for most normal website, one email account cost more than the hole website hosting!
our big clients are moving eventually to google, they say : cPanel email service is history, unreliable
the future is very dark if we continue on the same method
I rather to pay for cPanel than I buy a "Return Path Certified Whitelist" for $440 annually per server
or buy a reseller at google
My Suggestion is to build an optional central MX record for cpanel itself like:
10 mx1.cpanel.net
20 mx2.cpanel.net
30 mx3.cpanel.net
our emails (accounts, files, browsing) will still be hosted at our servers,
the mx records could work as a router only
so Google will rate spam on domain base not on the hole IP,
also cPanel can make a stand and force some Reciprocity
hope this will be considered in the future plans
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
This is not something that cPanel will be pursuing. The logistics and technical infrastructure to effectively act as the mail exchange for all cPanel & WHM servers would be gargantuan. cPanel & WHM's present focus is as a software developer as opposed to a host of services (be it web hosting, mail services, etc).
I certainly do understand the frustrations of dealing with strict mail services that aim to aggressively protect their user base from spam. This is in part because those services often do not tell you why you were marked as spam (to avoid helping actual spammers from knowing how to get around the anti-spam). Frustratingly, your best bet here is to continue to work with those providers that are marking with you spam and try your best to adhere to all of their best practices.
Remember, it's not always just the qualities of the mail server that are at play, but the contents themselves. Some anti-spam functions will consider spam high risk if an IP address is present (resulting in many "new account setup" emails that contain an IP address being marked a spam).
In short, cPanel will not be pursuing a feature like this as the logistics of such would not only be implausible (logistically and financially), but it likely provide zero benefit at all. I imagine the IP(s) would be blacklisted in short order and become useless for sending mail.
This is not something that cPanel will be pursuing. The logistics and technical infrastructure to effectively act as the mail exchange for all cPanel & WHM servers would be gargantuan. cPanel & WHM's present focus is as a software developer as opposed to a host of services (be it web hosting, mail services, etc).
I certainly do understand the frustrations of dealing with strict mail services that aim to aggressively protect their user base from spam. This is in part because those services often do not tell you why you were marked as spam (to avoid helping actual spammers from knowing how to get around the anti-spam). Frustratingly, your best bet here is to continue to work with those providers that are marking with you spam and try your best to adhere to all of their best practices.
Remember, it's not always just the qualities of the mail server that are at play, but the contents themselves. Some anti-spam functions will consider spam high risk if an IP address is present (resulting in many "new account setup" emails that contain an IP address being marked a spam).
In short, cPanel will not be pursuing a feature like this as the logistics of such would not only be implausible (logistically and financially), but it likely provide zero benefit at all. I imagine the IP(s) would be blacklisted in short order and become useless for sending mail.
This is not something that cPanel will be pursuing. The logistics and technical infrastructure to effectively act as the mail exchange for all cPanel & WHM servers would be gargantuan. cPanel & WHM's present focus is as a software developer as opposed to a host of services (be it web hosting, mail services, etc).
I certainly do understand the frustrations of dealing with strict mail services that aim to aggressively protect their user base from spam. This is in part because those services often do not tell you why you were marked as spam (to avoid helping actual spammers from knowing how to get around the anti-spam). Frustratingly, your best bet here is to continue to work with those providers that are marking with you spam and try your best to adhere to all of their best practices.
Remember, it's not always just the qualities of the mail server that are at play, but the contents themselves. Some anti-spam functions will consider spam high risk if an IP address is present (resulting in many "new account setup" emails that contain an IP address being marked a spam).
In short, cPanel will not be pursuing a feature like this as the logistics of such would not only be implausible (logistically and financially), but it likely provide zero benefit at all. I imagine the IP(s) would be blacklisted in short order and become useless for sending mail.
This is not something that cPanel will be pursuing. The logistics and technical infrastructure to effectively act as the mail exchange for all cPanel & WHM servers would be gargantuan. cPanel & WHM's present focus is as a software developer as opposed to a host of services (be it web hosting, mail services, etc).
I certainly do understand the frustrations of dealing with strict mail services that aim to aggressively protect their user base from spam. This is in part because those services often do not tell you why you were marked as spam (to avoid helping actual spammers from knowing how to get around the anti-spam). Frustratingly, your best bet here is to continue to work with those providers that are marking with you spam and try your best to adhere to all of their best practices.
Remember, it's not always just the qualities of the mail server that are at play, but the contents themselves. Some anti-spam functions will consider spam high risk if an IP address is present (resulting in many "new account setup" emails that contain an IP address being marked a spam).
In short, cPanel will not be pursuing a feature like this as the logistics of such would not only be implausible (logistically and financially), but it likely provide zero benefit at all. I imagine the IP(s) would be blacklisted in short order and become useless for sending mail.
Some of the problems are also provider IP reputation, not just your IP's but all the surrounding IP's. If your provider doesn't track down spammers hard enough then all IP's in their network can have issues.
Since our provider has started blocking IP's that send spam and since we have moved all our outgoing e-mail to SpamExperts private cluster to make sure we no longer send any spam our IP reputation has gone up and all e-mails delever correctly to hotmail and gmail.
We took 48 IP's per server and enabled 5 on each server to keep the others as backup IP's in case any got blocked, since then we have not had a single blokage.
It's true though that cPanl's outgoing antispam is a joke as it is so to prevent spam problems you have to get a good external solution.
Some of the problems are also provider IP reputation, not just your IP's but all the surrounding IP's. If your provider doesn't track down spammers hard enough then all IP's in their network can have issues.
Since our provider has started blocking IP's that send spam and since we have moved all our outgoing e-mail to SpamExperts private cluster to make sure we no longer send any spam our IP reputation has gone up and all e-mails delever correctly to hotmail and gmail.
We took 48 IP's per server and enabled 5 on each server to keep the others as backup IP's in case any got blocked, since then we have not had a single blokage.
It's true though that cPanl's outgoing antispam is a joke as it is so to prevent spam problems you have to get a good external solution.
I believe Google give poor reputation (redirect to spam folder) by default for first time seen IP's, until they proof the opposite
I'm taking about the first email sent from the server, even if the IP wasn't active before (not a mail server anyway)
this specifically issue lead all respected companies to use external mail exchange servers like hotmail or google , no more messages to spam.
in this situation, there was no spam what so ever!
I know it is not a simple thing to create a mail exchange service,
and it is come with many consequences,
but it is already done and dealt with, it is becoming a new business too
yahoo have about 3 Ip's for it is exchange service,
can google block them ?
can google block Microsoft IP's ?
the mail exchange providers make some terms and limitations,
there is a whitelist programs to connect those services as a partners
cpanel can do the same, block servers IP internally, and since the service is optional , no one forced to use it
Google have thousands of server to provide the service , cPanel do not need, the servers is already exists and managed, it only need the hub thing.
In the mean time, I'll keep recommend my VIP clients to move there emails out to google
I believe Google give poor reputation (redirect to spam folder) by default for first time seen IP's, until they proof the opposite
I'm taking about the first email sent from the server, even if the IP wasn't active before (not a mail server anyway)
this specifically issue lead all respected companies to use external mail exchange servers like hotmail or google , no more messages to spam.
in this situation, there was no spam what so ever!
I know it is not a simple thing to create a mail exchange service,
and it is come with many consequences,
but it is already done and dealt with, it is becoming a new business too
yahoo have about 3 Ip's for it is exchange service,
can google block them ?
can google block Microsoft IP's ?
the mail exchange providers make some terms and limitations,
there is a whitelist programs to connect those services as a partners
cpanel can do the same, block servers IP internally, and since the service is optional , no one forced to use it
Google have thousands of server to provide the service , cPanel do not need, the servers is already exists and managed, it only need the hub thing.
In the mean time, I'll keep recommend my VIP clients to move there emails out to google
The blocking on Hotmail, Yahoo has often nothing to do with SPAM but with low volumen IPs. Set up a new mailserver with an IP which is unused for years and still get blocked on the first email to their servers.
I still don't understand the exact feature request. Should cpanel provide mail infrastructure? How would that change the IP blocking or SPAM tag problem. We don't know their algorithms. It often seems that the mail provider don't understand their own blocking system.
I don't see a quick solution for the behaviour of the big freemail companies. The SPAM tagging and whitelist for money business is a problem in the B2C section.
I would like to see a function to use the SMTP server on DNSOnly installations as a SMTP pool. If one SMTP is blacklisted WHM should allow me to reroute the mail queue on a different SMTP server.
The blocking on Hotmail, Yahoo has often nothing to do with SPAM but with low volumen IPs. Set up a new mailserver with an IP which is unused for years and still get blocked on the first email to their servers.
I still don't understand the exact feature request. Should cpanel provide mail infrastructure? How would that change the IP blocking or SPAM tag problem. We don't know their algorithms. It often seems that the mail provider don't understand their own blocking system.
I don't see a quick solution for the behaviour of the big freemail companies. The SPAM tagging and whitelist for money business is a problem in the B2C section.
I would like to see a function to use the SMTP server on DNSOnly installations as a SMTP pool. If one SMTP is blacklisted WHM should allow me to reroute the mail queue on a different SMTP server.
I think the following is a more appropriate feature request that still allows direct control over your e-mail infrastructure, instead of deferring administrative responsibility to a third-party: http://features.cpanel.net/responses/mail-only-version-of-cpanel-whm
I think the following is a more appropriate feature request that still allows direct control over your e-mail infrastructure, instead of deferring administrative responsibility to a third-party: http://features.cpanel.net/responses/mail-only-version-of-cpanel-whm
Replies have been locked on this page!