Unable to Send Email to Certain Domains

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

Related:

  • No Related Posts

Email Archiving Helps Keep Your Business Moving

Nick Scholz

Email Archiving Helps Keep Your Business Moving The lion’s share of business communication and collaboration still happens through email — more than phones, instant messages, texts, and social media combined. Radicati estimates that in 2018, about 124.5 billion business emails were sent and received each day around the globe. The figure is projected to increase …

+read more

The post Email Archiving Helps Keep Your Business Moving appeared first on Cool Solutions. Nick Scholz

Related:

  • No Related Posts

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

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

Related:

  • No Related Posts

GroupWise Resource Archive – January 2019

Advansys

The January 2019 release of the free GroupWise Resource Archive, which provides easy research of the NGW Digest email discussions between GroupWise administrators, partners, and consultants, is now available. Use the high speed text search capabilities to discover invaluable guidance within topics ranging from GroupWise technical issues to Micro Focus/Novell business discussions. The GroupWise Resource Archive can be …

+read more

The post GroupWise Resource Archive – January 2019 appeared first on Cool Solutions. Advansys

Related:

  • No Related Posts

Remote Server returned ”

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

Related:

  • No Related Posts

My client can’t receive email from us.

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

Related:

  • No Related Posts

Returned ‘400 4.4.7 Message delayed’ from MessageLabs.com

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

Related:

  • No Related Posts

Can’t receive emails from clients using symantec

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

Related:

  • No Related Posts

VPLEX: Health-check –full reports Call Home “Error” state post NDU[1]

Article Number: 523118 Article Version: 3 Article Type: Break Fix



VPLEX GeoSynchrony,VPLEX Local,VPLEX Metro,VPLEX Series,VPLEX VS2,VPLEX VS6

An Error is reporting in the commandhealth-check –full post upgrade but the Call Home functions properly.

  • Pre NDU Health-check –full doesn’t report an error.

  • Post NDUHealth-check –full reports “Checking Call Home Status” as Error.

  • ConnectEMC_config.xml file looks the same as pre NDU as post NDU.

  • No issues seen in connectemc related logs.

  • The SMTP service is reachable and non-blocked.

  • Call-Home works right, for every triggered call-home test.

  • SYR / CLM system determine call home alerts have being correctly received. Hence, confirming Connecthome is received.

Comparing PRE & POST Non-Disruptive Upgrade (NDU)

PRE NDU

VPlexcli:/> health-check –full

Configuration (CONF):

Checking VPlexCli connectivity to directors……………….. OK

Checking Directors Commission……………………………. OK

Checking Directors Communication Status…………………… OK

Checking Directors Operation Status………………………. OK

Checking Inter-director management connectivity……………. OK

Checking ports status…………………………………… OK

Checking Call Home……………………………………… OK

Checking Connectivity…………………………………… OK

POST NDU

VPlexcli:/> health-check –full

Configuration (CONF):

Checking VPlexCli connectivity to directors……………….. OK

Checking Directors Commission……………………………. OK

Checking Directors Communication Status…………………… OK

Checking Directors Operation Status………………………. OK

Checking Inter-director management connectivity……………. OK

Checking ports status…………………………………… OK

Checking Call Home Status……………………………….. Error

service@vplexMM:/var/log/VPlex/cli> more health_check_full_scan.log

Configuration (CONF):

Checking VPlexCli connectivity to directors……………….. OK

Checking Directors Commission……………………………. OK

Checking Directors Communication Status…………………… OK

Checking Directors Operation Status………………………. OK

Checking Inter-director management connectivity……………. OK

Checking ports status…………………………………… OK

Checking Call Home Status……………………………….. Error

Email Server under Notification type: ‘onSuccess/onFailure’ is either

Not reachable or invalid.

Check if Email Server IP address: ‘10.1.111.100’ is reachable and valid.

Email Server under Notification type: ‘Primary’ and ‘Failover’ are either

Not reachable or invalid.

Check if Email Server IP address: ‘10.1.111.100’ and ‘10.1.111.100’ are

Reachable and valid.

service@vplexMM:/opt/emc/connectemc> cat ConnectEMC_config.xml

<?xml version=”1.0″ encoding=”UTF-8″ standalone=”no” ?>

<ConnectEMCConfig SchemaVersion=”1.1.0″>

<ConnectConfig Type=”Email”>

<Retries>7</Retries>

<Notification>Primary</Notification>

<Timeout>700</Timeout>

<Description></Description>

<BsafeEncrypt>no</BsafeEncrypt>

<IPProtocol>IPV4</IPProtocol>

<EmailServer>10.1.111.100</EmailServer>

<EmailAddress>emailalert@EMC.com</EmailAddress>

<EmailSender>VPlex_CKM00000000999@EMC.com</EmailSender>

<EmailFormat>ASCII</EmailFormat>

<EmailSubject>Call Home</EmailSubject>

<STARTTLS>no</STARTTLS>

<IncludeCallHomeData>no</IncludeCallHomeData>

<InsertBefore></InsertBefore>

<PreProcess></PreProcess>

<PostProcess></PostProcess>

<HeloParameter></HeloParameter>

</ConnectConfig>

<ConnectConfig Type=”Email”>

<Retries>7</Retries>

<Notification>Failover</Notification>

<Timeout>700</Timeout>

<Description></Description>

<BsafeEncrypt>no</BsafeEncrypt>

<IPProtocol>IPV4</IPProtocol>

<EmailServer>10.1.111.100</EmailServer>

<EmailAddress>emailalert@EMC.com</EmailAddress>

<EmailSender> VPlex_CKM00000000999@EMC.com</EmailSender>

<EmailFormat>ASCII</EmailFormat>

<EmailSubject>Call Home</EmailSubject>

<STARTTLS>no</STARTTLS>

<IncludeCallHomeData>no</IncludeCallHomeData>

<InsertBefore></InsertBefore>

<PreProcess></PreProcess>

<PostProcess></PostProcess>

<HeloParameter></HeloParameter>

</ConnectConfig>

<ConnectConfig Type=”Email”>

<Retries>7</Retries>

<Notification>onSuccess/onFailure</Notification>

<Timeout>700</Timeout>

<Description></Description>

<BsafeEncrypt>no</BsafeEncrypt>

<IPProtocol>IPV4</IPProtocol>

<EmailServer>10.1.111.100</EmailServer>

<EmailAddress>customer@genericemailaddress.com</EmailAddress>

<EmailSender>VPlex_CKM00000000999@EMC.com</EmailSender>

<EmailFormat>ASCII</EmailFormat>

<EmailSubject>Call Home</EmailSubject>

<STARTTLS>no</STARTTLS>

<IncludeCallHomeData>yes</IncludeCallHomeData>

<InsertBefore></InsertBefore>

<PreProcess></PreProcess>

<PostProcess></PostProcess>

<HeloParameter></HeloParameter>

</ConnectConfig>

</ConnectEMCConfig>

service@vplexMM:/var/log/ConnectEMC/logs> ping 10.1.111.100

PING 10.1.111.100 (10.1.111.100) 56(84) bytes of data.

— 10.1.111.100 ping statistics —

6 packets transmitted, 0 received, 100% packet loss, time 5010ms

service@vplexMM:~> telnet 10.1.111.100 25

Trying 10.1.111.100…

Connected to 10.1.111.100

Escape character is ‘^]’.

220 emc.com

helo localhost

250 emc.com

mail from: VPlex_CKM00000000999@EMC.com

250 2.1.0 Ok

rcpt to:customer@genericemailaddress.com

250 2.1.0 Ok

VPlexcli:/notifications/call-home> test

call-home test was successful.


As per the above information, this means that the customer is allowing the SMTP service on port “25” only and not the ICMP “ping”.

This error is expected and can be ignored once you verify that the test call home is working and appearing under /opt/emc/connectemc/archive

service@vplexMM:/opt/emc/connectemc/archive> ll

-rw-r—– 1 service users 2814 Jun 25 13:17 RSC_CKM00000000999_062518_011656000.xml

-rw-r—– 1 service users 2814 Jun 25 10:54 RSC_CKM00000000999_062518_105401000.xml

-rw-r—– 1 service users 2814 Jun 25 11:11 RSC_CKM00000000999_062518_111102000.xml

-rw-r—– 1 service users 2814 Jun 25 11:48 RSC_CKM00000000999_062518_114834000.xml

Checking call home status is part of the health-check — full script which does the following:

1- Check the email server for each notification type in /opt/emc/connectemc/ConnectEMC_config.xml

2- Ping the server. If the server is not pingable for any reason (not reachable via network, server is shutdown, ICMP service is blocked via firewall, the <EmailServer> is a DNS name instead of the name in the ConnectEMC_config.xml file).

As a result, the commandhealth-check –full script will fail and will show the following error:

Checking Call Home Status……………………………….. Error

The current healthcheck script checks if call home is enabled and generates a “Warning” state if it’s disabled.

The healthcheck script also checks if call home has been functioning properly with several verifications such as: checking call homes have been generated; the call home emails have been sent successfully sent; or if SMTP server ping is alive.

If any of these verifications fail, the script’s result will be flagged with an error as shown:

Checking Call Home Status……………………………….. Error

After enabling the ICMP protocol on the firewall level between the VPLEX management server and their selected email server used (ESRS, customer’s email server), the Call Home “Error” status is now clean:

VPlexcli:/> health-check –full

Configuration (CONF):

Checking VPlexCli connectivity to directors……………….. OK

Checking Directors Commission……………………………. OK

Checking Directors Communication Status…………………… OK

Checking Directors Operation Status………………………. OK

Checking Inter-director management connectivity……………. OK

Checking ports status…………………………………… OK

Checking Call Home Status……………………………….. OK

Checking Connectivity…………………………………… OK

Checking COM Port Power Level……………………………. OK

Checking Meta Data Backup……………………………….. OK

Checking Meta Data Slot Usage……………………………. OK

Related:

  • No Related Posts