Quantcast
Channel: Symantec Connect - Email Security.cloud - Discussions
Viewing all 853 articles
Browse latest View live

Organizations unable to email us

$
0
0
I need a solution

Good Morning All,

We have an organization that is unable to email us even though we have white listed them. I can email them but they can not email us. Error message on the bounce back email they get is below. Please help.

<myemailaddress>: host cluster6.us.messagelabs.com[67.219.250.196]

    said: 553-Message filtered. Refer to the Troubleshooting page at

    553-http://www.symanteccloud.com/troubleshooting for more 553 information.

    (#5.7.1) (in reply to end of DATA command)

0

Blacklist Removal Request

$
0
0
I need a solution

Hi,

We found out that one of our server ip addresses is on your list.

We had an issue with one client on december (his email account was used to send spam) but this issue was fixed very soon, we have checked the entire server and found no issues, also we check all of our ips against some of the most popular blacklists checkers and we aren't listed on any (over 100 lists checked) but yours.

Please could you please delist our IP address: 51.38.181.24 we have a lot of clients complaining about emails not being delivered properly.

Best Regards.

0

Unable to email clients using Symantec email security

$
0
0
I need a solution

Hi there,

   For the last week now we have a client who is unable to email anyone that uses Symantec Email Security. They constantly get the below message -:

550 5.0.350 Remote server returned an error -> 553 Message filtered. Refer to the Troubleshooting page at;http://www.symanteccloud.com/troubleshooting for more;information. (#5.7.1)

  They use Office 365 and all DNS is correct for SPF and DKIM. They do not show as blacklisted anywhere and the majority of emails have no attachments. Strangley though if they email from the Office365 web portal the email sometimes gets through. 

 I submitted several emails last week and the week before to be checked for false positives but have had no response. 

 This is causing major disruption for the business as they are finding that more and more suppliers use theis sytem for email filtering. They have had 1 customer whitelist them which allowed email through but they do not want to have to do this with dozens of other clients.

 Any help would be appreciated

 Kind regards,

0

Can't receive emails from clients using symantec

$
0
0
I need a solution

Hi, 

For nearly 1/2 year now, we've been unable to receive emails from clients using higher-levels of symantec security. We had an issue last year with an infected machine that appears to have given us a negative reputation (Case 00013827), but we had this lifted late last year and we still don't receive emails.

Here's an example:

Diagnostic information for administrators:

Generating server: LV-EX01.lismore.local

rebecca@armsign.com.au
server-18.tower-403.messagelabs.com
Remote Server returned '550 Invalid recipient <rebecca@armsign.com.au> (#5.1.1)'

Original message headers:

Received: from LV-EX01.lismore.local (10.1.2.18) by LV-EX01.lismore.local

(10.1.2.18) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 27 Nov 2018

12:05:35 +1100

Received: from LV-EX01.lismore.local ([fe80::a1e0:dede:77a3:156d]) by

LV-EX01.lismore.local ([fe80::a1e0:dede:77a3:156d%16]) with mapi id

15.00.1367.000; Tue, 27 Nov 2018 12:05:35 +1100

From: Kate Steel <Kate.Steel@lismore.nsw.gov.au>

To: "'rebecca@armsign.com.au'"<rebecca@armsign.com.au>

Subject: test

Thread-Topic: test

Thread-Index: AdSF7UupFZy6WiA5Sf66pQIm+USZgA==

Date: Tue, 27 Nov 2018 01:05:35 +0000

Message-ID: <ad5f04ab2f1e4a3097ad423beff6146e@LV-EX01.lismore.local>

Accept-Language: en-AU, en-US

Content-Language: en-US

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

catalogueonsend: False

x-ms-exchange-transport-fromentityheader: Hosted

x-originating-ip: [10.10.2.112]

Content-Type: multipart/alternative;

        boundary="_000_ad5f04ab2f1e4a3097ad423beff6146eLVEX01lismorelocal_"

MIME-Version: 1.0

This issue is now happening with other clients who are using symantec products. We are unable to send/receive pretty much with everyone using your products. Can we get this resolved?

0

Returned '400 4.4.7 Message delayed' from MessageLabs.com

$
0
0
I need a solution

When we send emails to many customers who are using Symantec's service, we receive refunds, such as

供管理员使用的诊断信息:

生成服务器: CDSSRVDCEX02.hkdc.cds-net.com
接收服务器: cluster5a.eu.messagelabs.com (18.194.106.207)
 

blau@plumproducts.com
Remote Server at cluster5a.eu.messagelabs.com (18.194.106.207) returned '400 4.4.7 Message delayed'
1/24/2019 10:45:09 AM - Remote Server at cluster5a.eu.messagelabs.com (18.194.106.207) returned '451 4.4.0 Primary target IP address responded with: "421 4.4.1 Connection timed out." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 18.194.106.207:25'

原始邮件头:

Received: from CDSSRVDCEX01.hkdc.cds-net.com (10.1.1.33) by
 CDSSRVDCEX02.hkdc.cds-net.com (10.1.1.64) with Microsoft SMTP Server (TLS) id
 15.0.1367.3; Thu, 24 Jan 2019 14:52:39 +0800
Received: from CDSSRVDCEX01.hkdc.cds-net.com ([fe80::41b3:7f32:d22f:6b81]) by
 CDSSRVDCEX01.hkdc.cds-net.com ([fe80::41b3:7f32:d22f:6b81%16]) with mapi id
 15.00.1367.000; Thu, 24 Jan 2019 14:52:38 +0800
From: April Shao <aprilshao@cdsshanghai.com.cn>
To: "op@fanfeitrans.com"<op@fanfeitrans.com>
CC: "blau@plumproducts.com"<blau@plumproducts.com>
Subject: CTCVANL06138SH0
Thread-Topic: CTCVANL06138SH0
Thread-Index: AdSzsUJdsk09dD0MRRSTWf5Qunf96A==
Date: Thu, 24 Jan 2019 06:52:38 +0000
Message-ID: <60de1864092a42339ddefd0e1bf213d3@CDSSRVDCEX01.hkdc.cds-net.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [221.133.242.163]
Content-Type: multipart/related;
       boundary="_004_60de1864092a42339ddefd0e1bf213d3CDSSRVDCEX01hkdccdsnetc_";
       type="multipart/alternative"
MIME-Version: 1.0
 

We try to solve this problem with smart hosts, but it can't solve all the problems in the end.

Our domain:cds.com.hk,cdsshanghai.com.cn, cdsningbo.com,cdsqingdao.com,cdsxiamen.com

Our exchange servers IP : 175.45.36.68-70

0

My client can't receive email from us.

$
0
0
I need a solution

Dear Support Symantec.

Our client using messagelabs the statuses was 2.5.0 OK but our client doesn't receive the email.
Can you help to check? We using relay from mailchannels. They can sent us an email. But everytime we reply, the email not receiving on our client.

Here's the status.

Delivered
2019-01-28 11:24 AM
Subject:Re: Mohon informasi pembayaran
Size:48,000 bytes
Duration:2.58 seconds
SMTP Response:250 ok 1548649474 qp 23789 server-26.tower-385.messagelabs.com!1548649471!1537214!1
From:c***ier@subahtera.com
To:a***ni.re@pg.com a***sa.h@pg.com no***ana.nn@pg.com p**ri.p*@pg.com ram**ani.f*@pg.com
 
What should i do?
 
 
0

one of our domains is being email bombed by messagelabs daily

$
0
0
I need a solution

For the last week daily from 4PM-5PM PST our mail server has been bombed by 10-15K emails, all being sent from messagelabs.com mail servers, namely mail2.bemta23.messagelabs.com and mail2.bemta24.messagelabs.com. We have attempted to contact messagelabs to resolve this but cannot make our way through Symantec support to contact messagelabs (thry claim we can't talk to messagelabs unless we purchase a support contract). Does anybody know how we can contact them to stop the daily email attacks their servers are subjecting us to?

2019-01-27 17:10:12
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.218]
 
 
2019-01-27 17:10:11
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.217]
 
 
2019-01-27 17:10:11
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.220]
 
 
2019-01-27 17:10:11
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.217]
 
 
2019-01-27 17:10:11
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.121]
 
 
2019-01-27 17:10:11
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.122]
 
 
2019-01-27 17:10:11
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.122]
 
 
2019-01-27 17:10:10
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.9]
 
 
2019-01-27 17:10:10
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.9]
 
 
2019-01-27 17:10:10
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.9]
 
 
2019-01-27 17:10:10
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.120]
 
 
2019-01-27 17:10:09
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.216]
 
 
2019-01-27 17:10:09
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.216]
 
 
2019-01-27 17:10:09
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta23.messagelabs.com[67.219.246.216]
 
 
2019-01-27 17:10:08
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.14]
 
 
2019-01-27 17:10:08
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.124]
 
 
2019-01-27 17:10:08
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.14]
 
 
2019-01-27 17:10:08
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.124]
 
 
2019-01-27 17:10:07
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.217]
 
 
2019-01-27 17:10:07
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.217]
 
 
2019-01-27 17:10:07
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.217]
 
 
2019-01-27 17:10:07
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.217]
 
 
2019-01-27 17:10:07
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail2.bemta24.messagelabs.com[67.219.250.217]
 
 
2019-01-27 17:10:07
 
TicketTimeLimitRecheck@compleat.com
 
 
Blocked
Invalid Domain
 
mail
0

Remote Server returned '< #5.4.7 smtp; 554 5.4.7 [internal] exceeded max time without delivery>'

$
0
0
I need a solution

I am receiving Time out NDRs, but only if they hit one of the "eu-west-1.aws.symcld.net" servers... but if they go through one of the " eu-central-1.aws.symcld.net" servers they are delivered. I am trying to troubleshoot the issue, is there some place I could find the server IPs for the "eu-west" servers?  here are some of the servers we received NDRs from:

server-1.bemta.az-a.eu-west-1.aws.symcld.net

server-2.bemta.az-c.eu-west-1.aws.symcld.net

server-3.bemta.az-a.eu-west-1.aws.symcld.net

server-3.bemta.az-b.eu-west-1.aws.symcld.net

server-4.bemta.az-a.eu-west-1.aws.symcld.net

I think I saw somewhere that the "eu-west-1" ips are out of Ireland and the "eu-central-1" is out of Frankfurt.

We use ProofPoint and want to check to see if they are blocked there..

Diagnostic information for administrators:

Generating server: server-3.bemta.az-a.eu-west-1.aws.symcld.net

email address....

Remote Server returned '< #5.4.7 smtp; 554 5.4.7 [internal] exceeded max time without delivery>'

thank you

Rob

0

Needs Attention Warning at My Services Dashboard

$
0
0
I need a solution

Hello,

This new dashboard is displaying at My Services since a couple of days ago.

Anybody knows what does 'Needs Attention'in red warning means? Is it like the service is down or something? I don't get it.

Thanks

0

553 you are trying to use me as a relay

$
0
0
I need a solution

Hi,

We have all inbound mail being routed through MessageLabs, then to our Office365 tenant.

All email is being delivered OK except for a specific circumstance.

Our domain is contoso.com.au.

If I create a DL, TestDL@contoso.com.au that has an external contact in it, user@yahoo.com.

If I send an email to that DL from my internal contoso address, it gets delivred OK.

If I send an email from an external address, eg from me@gmail.com to TestDL@contoso.com;

  • The email goes through MessageLabs
  • Then goes to Office365. Office365 sees that it needs to go back out to deliver to that external address.
  • Gets to MessageLabs, and MessageLabs returns "550 5.0.350 Remote server returned an error -> 553 you are trying to use me [server-17.tower-423.messagelab;s.com] as a relay, but I have not been configured to let you [104.47.116.56, mail-me1aus01lp2056.outbound.protection.outlook.com] do this. Please visit www.symanteccloud.com/troubleshooting for more details;about this error message and instructions to resolve;this issue. (#5.7.1)".

Within MessageLabs, we have configured the Office 365 hosted mail service in our outbound routes, so not sure what the problem is.

I've got cases open with both Microsoft and Symantec, but not getting very far.

Does anyone have any experience with this?

Thanks.

0

Blacklist removal

$
0
0
I need a solution

Hi, please can you help

We are having issues emailing our customers that use Symantec.cloud.

Not always, but quite oftlen we receive the response...

cluster5.eu.messagelabs.com #<cluster5.eu.messagelabs.com #5.0.0 smtp; 553-Sorry, your email address XXXXX@justtechgroup.com has 553-been blacklisted. 

We haev checked blacklistings, but we do not appear.  please can you assist.

Best regards

Steve

0

Use SPF in Dashboard > Services > Email Services > Anti-Spam not working

$
0
0
I need a solution

Hello,

I have this checkbox enabled for one of my domains and have sent myself gmail spoofed email on purpose to generate an SPF error, but the spam filter just passes it through.  The email track and trace report shows it passing all anti-spam tests.  Here is part of the header:

Authentication-Results: mx.messagelabs.com; spf=softfail (server-2.tower-343.messagelabs.com: transitioning domain of gmail.com does not designate 216.*.*.* as permitted sender)

The setting is set at "Use SPF in Dashboard > Services > Email Services > Anti-Spam" and I am requesting it append to the subject line.

One source I consulted says that the anti-spam detection setting for SPF only flags hard failures, not "softfails".

Any help appreciated.

Guy

 
0

Unable to Send Email

$
0
0
I need a solution

Attepts to send email to aramark.com domain fail with error: "The server has tried to deliver this message, without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk."

Cannot find any obvious errors and do not see my sending IP/domain on any blacklist.  

Any assistance would be appreciated.  Thanks much!

Mail Server: mail.Poquoson.k12.va.us

sending IP: 108.17.129.26

0

Emails not getting through to MessageLabs clients; 250 response, no bounce

$
0
0
I need a solution

For the last few months, emails from our users have not been getting through to MessageLab mailboxes. Messages are all DKIM signed, and we have checked the SPF records are valid. No issues sending emails to Office365 or GMail. In all cases, the MessageLabs servers respond with a 250 - but the mail is never received by your users. No bounce/NDR is received. : delivery via cluster6.us.messagelabs.com[67.219.247.52]:25: 250 ok 1549884095 qp 13400 server-18.tower-424.messagelabs.com!1549884092!1152510!1 Action: relayed Status: 2.0.0 Remote-MTA: dns; cluster6.us.messagelabs.com Diagnostic-Code: smtp; 250 ok 1549884095 qp 13400 server-18.tower-424.messagelabs.com!1549884092!1152510!1 We have tried raising a support ticket with your support officer "Ashok Singh", but he has refused to raise a ticket. This appears to be a similar issue to ref:_00D30jPy._50038rHwPj:ref.

0

Messages Accepted by MessageLabs but not recieved by client

$
0
0
I need a solution

I have noticed that customers attempting to email users on the Symantec message labs platform have their emails apparently accepted by eu2.messagelabs.com but they do not show up in their inbox.

Our mail server does not send out spam, and we have constant checking to enable us to catch spam before it is sent.

However, some users have had mail forwarding loops in the past which may be responsible for the spam classification.

It would be nice if the messagelabs system actually rejected mail it had no intention of delivering to the final user so that IT teams can investigate issues with non-delivery. It has taken me two weeks to figure out where the problem is with mail as delivery appears to be "accepted" and normal on our end.

Edit: I also am not getting a confirmation that this message to request an investigation for the IP is being received by the web page at https://ipremoval.sms.symantec.com/

Any assitance in this matter would be greatly appreciated.

Kind regards,
Jessica

0

Unable to Send Email to Certain Domains

$
0
0
I need a solution

Hi Support,

Currently our domain is unable to send any emails to all domains administrered by Message Labs. We receive a bounce back email saying it was blocked due to message filtering. I have searched and was unable to find a way to get our domain unblocked. My question is how do I go about getting our domain unblocked to all domains administered by Message Labs as we arent able to get a direct contact without already being a customer.

0

Emails being blocked by Symantec filtering

$
0
0
I need a solution

Hi

We are having emails from our company domain blocked by several other companies using Symantec cloud - Error 553 - message filtered. We are sending emails through Gmail

I have checked the link provided by Symantec support but none of our MX records are showing as being blocked

I don't want to post IPs and domain names - Could a Symantec employee PM me to determine why emails are being blocked
Thanks

0

messagelabs.com blocking our mail

$
0
0
I need a solution

Can anyone help me?  Messages to tgasourcing.com and kasasia.com are blocked by messagelabs.

What can I do to unblock it.

I would appreciate it if someone could investigate this asap.

Enclosed is the capture from the smtpdiag checking.

0

421 Service Temporarily unavailable

$
0
0
I need a solution

Same issue I am seeing on other threads, but with no answer.  Emails stuck in queue with 421 service temporarily unavailable. 

1) Emailed investigation@review.symantec.com and their response is "The IP address is not blocked or bring throttled by our reputation services" so sending IP isn't blocked.

2) Check MX record configuration on receipt domain that is utilizing Symantec Email Security.  Looks right to me.

5    cluster1.us.messagelabs.com
10    cluster1a.us.messagelabs.com

3) Running NSLOOKUP from my server shows that DNS is resolving properly.

> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> set type=mx
> abr.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
abr.com MX preference = 5, mail exchanger = cluster1.us.messagelabs.com
abr.com MX preference = 10, mail exchanger = cluster1a.us.messagelabs.com
>

4) SMTP logs shows the following lines.  

421 Service Temporarily Unavailable,
attempting to connect
,QUIT,
,221 mail555.messagelabs.com closing connection,

Originally though it was a TLS negotiation issue so created a separate send connector without using TLS.  This seems to have worked with a few of the domains using Symantec Email Security.  Others are still stuck in the queue.  

Any assistance appreciated.

0

MessageLabs Passive Screening causing false positives on click through

$
0
0
I need a solution

We have several customers that receive emails from various sources that require tracking of clicked URL's by end users.

These domains and IP's were whitelisted and everything worked well as Messagelabs passed the emails through as expected.

Now the release of the Passive Screening feature has been introduced, these links are now being clicked/activated by the sandboxing/scans and causing many headaches.

This Passive Screening ignores whitelisting and scans/opens every link it appears - is this correct?

How can they get MessageLabs to bypass passive screening for whitelisted domains/IP's?  

This is such an issue, several are looking to move to Mimecast or similar.

Within ForcePoint's email sandbox environment you can configure:

 

Thoughts?

0
Viewing all 853 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>