A resultant court judgment brought about by ScanSafe required MessageLabs to notify all prospective clients that the Version 2 service is not based on ScanSafe technology. Overview Issues Contributors Activity. Further reading. Documentaries, videos and podcasts.
Company attributes Industry. My domain and addresses aren't on any blacklists that I can see. The problem I have is that I email a company, it rejects, then I have to contact them via another email address and then somehow convince the person I'm emailing to talk to their IT department, then I have to convince that IT department that my messages aren't problematic.
It's time consuming and annoying. In some cases, the IT department quite rightly refuse to adjust their filters for me.
In addition to my own two mail servers I've been testing out SendGrid and Mandrill as well. Mandrill has been awesome, but I'm finding that MessageLabs is blocking huge amounts of mail coming from SendGrid, leading me to believe that they've grey or black listed SendGrid's Class-C's since no mail from either my own server or via Mandrill is hitting MessageLabs blocks.
Just a heads-up for any SendGrid users. I run several mail servers, none of which are blacklisted on any lists that I can find. I work very hard to keep my servers' reputation positive. I have succeeded at this for many years! I now have a client that received a bounce notification when attempting to email one of their own clients. The message was not very helpful so I had to contact Symantec directly. They were hardly helpful at all. They acknowledged that my server should not be blocked but they refused to take any action based on contact from me because An absolutely ludicrous policy, if you ask me.
Of course, this has not gone down well with my client, and after several attempts at clarifying the issue with his client, they really don't want to know about it. Can't say I blame them. So now I am at the mercy of Symantec's silly policy and there is literally nothing I can do about it. My client is blaming me in part, and can't say I blame them! I'm likely to lose them as a client because of this one incident the client they are trying to communicate with is very valuable to them.
I have made several requests to Symantec, but each time I get the same response: "We must adhere to our policy". It seems that Symantec would like to provide an inconvenience to their clients, rather than a service! Thanks for sharing I hope you have fewer problems with this in future!
I too have the problem with MessageLabs Symantec blocking my email to a customer because of the attachments - "unacceptable attachments" according to Symantec.
The attachments are simple PDF files which have been transmitted without a problem each month for several months up to now.
No satisfaction from Symantec of course and my customer IT dept is not interested. Yet the attachments are the same. If we all complain to our customers about Symantec maybe they will see a problem and look at using a different company.
I'm currently having this exact same issue, but I already have DKIM on, and have for at least a year. I went ahead and re-generated a new entry, but that hasn't seemed to help at all. I am completely without ideas at this point. I looked at the logs in our Admin console and it looks like not every email to a MessageLabs customer gets blocked, just most of them.
This concludes that even Symantec de-lists your IP, it doesn't apply it to their clients' system. If so, I think the issue really is with Symantec to apply the updates onto their clients' system. Very frustrating, what a horrible service Symantec is. RFC 3. Having domains drop the alternative SPF rr has helped. Albeit not conclusive as it being the direct problem, it has helped many clients.
Hi, Same issue here. Error transferring to cluster2. Same issue here. I've already complained on the Symantec forum, along with a dozen of other small outfit? This is a nightmare and goes directly against what an open an transparent internet should be. Google at least is much more descriptive in their refusal messages.
Symantec's servers don't respond at all, they just time out. This is, according to, yet another unhelpful Symantec employee, because the IP address of the sending mailserver has a bad reputation. Which obviously isn't the case, it isn't in their database. This server is being monitored for over a year for several different blacklists and hasn't been listed, ever. Like others in this comment-thread, I enforce very strict security for users on this server, and it's low-traffic anyway.
Symantec is doing their clients a disservice, but OTOH: it's the clients themselves that choose Symantec. No, you're not getting a lot of spam, but unfortunately you're missing a lot of legit e-mail in the same run.
I'm not sure how this messagelabs. Add your list of valid email addresses to ensure that you only receive email for legitimate users in each domain in your organization. Email Security. When Email Services are fully deployed, the AntiVirus service is automatically active and the AntiSpam service may be enabled with default settings. Your inbound email and outbound email, if provisioned automatically passes through the cloud security service scanners. To customize the settings for AntiVirus and AntiSpam, make the necessary configuration changes before you change your MX records.
Spam Quarantine enables your organization's users to view the emails that the Email AntiSpam service has detected as spam. These emails are viewable in a portal called Spam Manager. If this action is not enabled and you want it to be, refer to your confirmation email for contact details. Use the same URL for your new domain. Complete the following MX record changes within five working days of receiving your confirmation email.
When the records are propagated, ensure that there are no back-up MX records left in place. If an external organization e. Lowest MX preference default mail route : MX 10 cluster6.
Second MX preference back-up mail route : MX 20 cluster6a. The emails that are processed are those that are sent to your domain s by other Email Services customers who are provisioned on the same infrastructure as you.
0コメント