Deliver Email

I need a solution

Problems Delivering email

LOG: MAIN
  cwd=/usr/local/cpanel/whostmgr/docroot 4 args: exim -v -M 1iXvli-0006PP-3o
delivering 1iXvli-0006PP-3o
LOG: MAIN
  Sender identification U=interpar D=interpartesdemexico.com S=licitaciones@interpartesdemexico.com
Connecting to cluster9.us.messagelabs.com [67.219.247.54]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-13.tower-426.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.247.54]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.246.102]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-11.tower-386.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.246.102]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.251.54]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-22.tower-366.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.251.54]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.250.198]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-6.tower-346.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.250.198]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.250.102]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-2.tower-326.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.250.102]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.246.198]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-22.tower-406.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.246.198]: Remote host closed connection in response to EHLO s1
Connecting to cluster9a.us.messagelabs.com [3.222.201.247]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-12-131.us-east-1.aws.symcld.net [100.112.12.131]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
LOG: MAIN
  H=cluster9a.us.messagelabs.com [3.222.201.247]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster9a.us.messagelabs.com [34.237.164.170]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-14-77.us-east-1.aws.symcld.net [100.112.14.77]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
LOG: MAIN
  H=cluster9a.us.messagelabs.com [34.237.164.170]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster9a.us.messagelabs.com [52.73.243.182]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-13-247.us-east-1.aws.symcld.net [100.112.13.247]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  == humberto.villalobos@regalsprings.com R=dkim_lookuphost T=dkim_remote_smtp defer (-44) H=cluster9a.us.messagelabs.com [52.73.243.182]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
0

Related:

421 Service Temporarily Unavailable

I do not need a solution (just sharing information)

Good day

My client always send message from  programacion.pampilla @ cargotransportperu.com to repsolpampilla @ repsol.com.

Today when cargotransportperu.com send mails to repsol.com receive an error message this message:

== repsolpampilla@repsol.com R=lookuphost T=remote_smtp defer (-44) H=cluster1a.eu.messagelabs.com [3.123.158.38]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 421 Service Temporarily Unavailable

Thanks in advance for your help

Here full header:

LOG: MAIN
  cwd=/usr/local/cpanel/whostmgr/docroot 4 args: /usr/sbin/exim -v -M 1iK1A0-003783-Tu
delivering 1iK1A0-003783-Tu
LOG: MAIN
  Sender identification U=cargotra D=cargotransportperu.com S=programacion.pampilla@cargotransportperu.com
Connecting to cluster1.eu.messagelabs.com [85.158.142.97]:25 from 184.154.61.59 … connected
  SMTP<< 220 server-20.tower-222.messagelabs.com ESMTP
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-server-20.tower-222.messagelabs.com
         250-STARTTLS
         250-PIPELINING
         250 8BITMIME
  SMTP>> STARTTLS
  SMTP<< 220 ready for TLS
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-server-20.tower-222.messagelabs.com
         250-PIPELINING
         250 8BITMIME
  SMTP>> MAIL FROM:<programacion.pampilla@cargotransportperu.com>
  SMTP>> RCPT TO:<repsolpampilla@repsol.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 450-Requested action aborted [9] 222-20, please visit
         450-http://www.symanteccloud.com/troubleshooting for more
         450 details about this error message.
LOG: MAIN
  H=cluster1.eu.messagelabs.com [85.158.142.97]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 450-Requested action aborted [9] 222-20, please visitn450-http://www.symanteccloud.com/troubleshooting for moren450 details about this error message.
  SMTP<< 503 RCPT first (#5.5.1)
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster1.eu.messagelabs.com [85.158.142.196]:25 from 184.154.61.59 … connected
  SMTP<< 220 server-13.tower-241.messagelabs.com ESMTP
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-server-13.tower-241.messagelabs.com
         250-STARTTLS
         250-PIPELINING
         250 8BITMIME
  SMTP>> STARTTLS
  SMTP<< 220 ready for TLS
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-server-13.tower-241.messagelabs.com
         250-PIPELINING
         250 8BITMIME
  SMTP>> MAIL FROM:<programacion.pampilla@cargotransportperu.com>
  SMTP>> RCPT TO:<repsolpampilla@repsol.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 450-Requested action aborted [9] 241-13, please visit
         450-http://www.symanteccloud.com/troubleshooting for more
         450 details about this error message.
LOG: MAIN
  H=cluster1.eu.messagelabs.com [85.158.142.196]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 450-Requested action aborted [9] 241-13, please visitn450-http://www.symanteccloud.com/troubleshooting for moren450 details about this error message.
  SMTP<< 503 RCPT first (#5.5.1)
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster1a.eu.messagelabs.com [52.58.21.128]:25 from 184.154.61.59 … connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Mon, 14 Oct 2019 16:05:38 +0000
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-113-12-211.eu-central-1.aws.symcld.net [100.113.12.211]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<programacion.pampilla@cargotransportperu.com> SIZE=3602907
  SMTP>> RCPT TO:<repsolpampilla@repsol.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
LOG: MAIN
  H=cluster1a.eu.messagelabs.com [52.58.21.128]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster1a.eu.messagelabs.com [3.123.158.38]:25 from 184.154.61.59 … connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Mon, 14 Oct 2019 16:05:38 +0000
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-113-13-49.eu-central-1.aws.symcld.net [100.113.13.49]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<programacion.pampilla@cargotransportperu.com> SIZE=3602907
  SMTP>> RCPT TO:<repsolpampilla@repsol.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  == repsolpampilla@repsol.com R=lookuphost T=remote_smtp defer (-44) H=cluster1a.eu.messagelabs.com [3.123.158.38]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 421 Service Temporarily Unavailable
 

0

Related:

Reporting Delivery Option

I need a solution

We just setup CCS Vulnerability Manager (12.8.0.191 rev 3560). I’m working with reporting and trying to setup scheduled emailed reports. Currently the email option is greyed out with “SQL Reporting Services is not configured for report server email. You can configure the SMTP server and sender in the “email settings” section of the Reporting Services Configuration Manager” noted.

Going to Settings> Analytics & Reporting > Configuration

Using the Configuration Wizard, there isn’t an option to configure SMTP as you walk through the wizard, and I’m not seeing an option to set that elsewhere.

Can anyone get me pointed in the right direction please? Thanks!

0

Related:

Unable to receive email after Enforced TLS enabled

I need a solution

Hi All,

i’m hoping someone can help me, I’ve tried emailing support@messaglabs.com but got an auto reply saying they no longer respond to emails.

My company provides email services to a company that is a customer of a UK bank that uses messagelabs. The Bank recently enabled enfored TLS for this customers domain, however ever since no emails have come through.

I’ve been sent a bounceback which looks like this – 

X-Supplementary-Info: < #4.7.5 smtp; 454 4.7.5 [internal] verify
 error:num=21:unable to verify the first certificate:depth=0:/OU=Domain
 Control Validated/CN=*.vesk.com>

I’ve read a few things that suggest that Symantec don’t support wildcard certificates, however I was hoping to get some kind of definitive answer before I suggest we go and buy a new Certificate, only to find out that wasn’t the isssue.

Can anyone give me some help as to what the above error means?

Many Thanks 

0

Related:

421 Service Temporarily unavailable Mails rejected Protocol/SocketError

I need a solution

We have the same issue as others.

We can‘t send any mails from our domain d-parts.de.
Tried sending logs to investigation@review.symantec.com but failed with error “554 5.1.2 Recipient address rejected: User unknown”.

Please fix problems or set our ip 213.179.142.110 to your global whitelist.

Our mail server IP is not listed at any RBLs and we already checked Symantec‘s advisory from previous posts.

Below is the SMTP log from our server trying to connect to Symantec‘s server. Same problem with any mail addresses using messagelabs.com

SMTP,symantec.com,+,DnsConnectorDelivery 61e74520-c04c-4aac-940f-8c3ed6c76a61;QueueLength=TQ=1;RL=1;.
SMTP,symantec.com,>,”cluster4.us.messagelabs.com[67.219.251.49, 67.219.246.193, 67.219.250.97, 67.219.250.193, 67.219.247.49, 67.219.246.97], cluster4a.us.messagelabs.com[54.174.147.140, 52.73.243.182, 50.19.165.100]”
SMTP,symantec.com,>,Established connection to 67.219.251.49
SMTP,symantec.com,-,Messages: 0 Bytes: 0 (Attempting next target)
SMTP,symantec.com,*,Session Failover; previous session id = 08D696A6F7ADC705; reason = ProtocolError
SMTP,symantec.com,+,DnsConnectorDelivery 61e74520-c04c-4aac-940f-8c3ed6c76a61;QueueLength=TQ=0;AN=1;.
SMTP,symantec.com,>,Established connection to 67.219.246.193
SMTP,symantec.com,-,Messages: 0 Bytes: 0 (Attempting next target)
SMTP,symantec.com,*,Session Failover; previous session id = 08D696A6F7ADC706; reason = ProtocolError
SMTP,symantec.com,+,DnsConnectorDelivery 61e74520-c04c-4aac-940f-8c3ed6c76a61;QueueLength=TQ=0;AN=1;.
SMTP,symantec.com,>,Established connection to 67.219.250.97
SMTP,symantec.com,-,Messages: 0 Bytes: 0 (Attempting next target)
SMTP,symantec.com,*,Session Failover; previous session id = 08D696A6F7ADC707; reason = ProtocolError
SMTP,symantec.com,+,DnsConnectorDelivery 61e74520-c04c-4aac-940f-8c3ed6c76a61;QueueLength=TQ=0;AN=1;.
SMTP,symantec.com,>,Established connection to 67.219.250.193
SMTP,symantec.com,-,Messages: 0 Bytes: 0 (Attempting next target)
SMTP,symantec.com,*,Session Failover; previous session id = 08D696A6F7ADC708; reason = ProtocolError
SMTP,symantec.com,+,DnsConnectorDelivery 61e74520-c04c-4aac-940f-8c3ed6c76a61;QueueLength=TQ=0;AN=1;.
SMTP,symantec.com,>,Established connection to 67.219.247.49
SMTP,symantec.com,-,Messages: 0 Bytes: 0 (Attempting next target)
SMTP,symantec.com,*,Session Failover; previous session id = 08D696A6F7ADC709; reason = ProtocolError
SMTP,symantec.com,+,DnsConnectorDelivery 61e74520-c04c-4aac-940f-8c3ed6c76a61;QueueLength=TQ=0;AN=1;.
SMTP,symantec.com,>,Established connection to 67.219.246.97
SMTP,symantec.com,-,Messages: 0 Bytes: 0 (Attempting next target)
SMTP,symantec.com,*,Session Failover; previous session id = 08D696A6F7ADC70A; reason = ProtocolError
SMTP,symantec.com,+,DnsConnectorDelivery 61e74520-c04c-4aac-940f-8c3ed6c76a61;QueueLength=TQ=0;AN=1;.
SMTP,symantec.com,>,Established connection to 54.174.147.140
SMTP,symantec.com,-,Messages: 0 Bytes: 106 ()

0

Related:

Avamar: Avamar Callhome is not working after migration to Office365

To setup an SMTP Relay on Office365

In Office365, click Admin, then click Exchange to arrive on the Exchange Admin Center

Click mail flow, and then connectors

User-added image


Use the “+” to start the wizard to create a new connector:

– From = your organisation’s email server

– To = Office 365

– Enter a name for SMTP Relay

– By verifying that the IP address of the sending server matches one of these IP addresses that belong to your organization sender’s IP address = all Avamar utility nodes that are configured on customer site (IP should match public IP address of location sending email).

And click save to create the connector.

Then you can test it by doing the telnet command:

telnet <smtp office365> 25

EHLO

MAIL FROM:avamar_user_configurated@xxxx.com

It return now:

250 2.1.0 Sender OK

Avamar callhome and dialhome is now working.

Related:

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:

#5.7.1 smtp; 550 5.7.1 Relaying denied> #SMTP#

I need a solution

Hi Folks 

I wonder if there is any Message Labs gurus out there taht can give me some advise:

We recently moved over to 365 email system and ever since any of our previous senders on message labs are getting bounce back messages with an error 

Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.

The #< #5.7.1 smtp; 550 5.7.1 <>… Relaying denied> #SMTP#

any help would be apprecated 

 
0

Related: