Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


older | 1 | .... | 38 | 39 | (Page 40) | 41 | 42 | newer

    0 0

    I need a solution

    Hi,

    Our mail server had a small spam issue and is now unable to send to your servers, could you review the below IP for us

    Sep 11 16:32:35 mail postfix/smtp[17049]: connect to cluster6.us.messagelabs.com[67.219.246.100]:25: Connection refused

    Server IP : 202.134.95.226

    Thanks

    0

    0 0
  • 09/18/18--17:19: Messagelab
  • I need a solution

    Dear Sir/Madam

    I can't seem to get emails out due to error .....I manage to clear out other blockage but get this error on the mailbox....

    lost connection with cluster5.us.messagelabs.com[67.219.250.98] while sending end of data -- message may be sent more than once

    my IP Address is 103.43.147.23

    thanks

    0

    0 0
  • 09/25/18--01:30: Redirect emails.
  • I need a solution

    Hello,

    I'm hoping I have the correct forum. I am a developer on IBM systems and have very limited knowledge of email systems. I do not deal with infrastructure or networks. 

    There are three seperate IBM servers all which forward emails to message labs. One IBM server is our production system and the other two are development and test systems.

    Basically we would like to know if it is possible for message labs to be configured to redirect emails that have been sent to message labs from a particual server/domain name.

    e.g

    Sent from IBM server 1, Production: This should allow all emails out to the web.

    Sent from IBM server 2. Development: All emails from this server/domain should be redirected to development email accounts.

    Sent from IBM server 3. Test: All emails from this server/domain should be redirected to test email accounts.

    The above configuration would allow us to test email software on the IBM severs without the emails being sent to real email accounts.

    Apologies for the terminaology I have used. 

    Thank you for any help you can provide.

    Regards,

    Mark.

    0

    0 0

    I need a solution

    We have many messages to vaious messaglabs customers being blocked with the following error:

    [{LED=451 4.4.395 Target host responded with error. -> 421 Service Temporarily Unavailable};{MSG=};{FQDN=cluster1a.us.messagelabs.com};{IP=52.202.136.199};{LRT=9/28/2018 4:45:33 AM}]

    Various recipients and various clients, pointing to various clusterXa.us.messagelabs.com. Thanks!

    0

    0 0

    I need a solution

    How many layers of zip-ing (Assuming and attacker wishes to obsfucate in multiple layers of zip) does Email Security.cloud analyzes?

    0

    0 0

    I need a solution

    Hi, 

    I would like to seek for advise/help on the above stated. As me and my team had already searched many websites for solutions but still none working.

    Here is the problem:

    Same recipient, however ,some emails were able to reach customer's inbox and some were filtered out with "553 Message filtered".

    Any clues on how this is happening?

    Please help and thanks.

    Vic Lee 

    0

    0 0

    I need a solution

    Hello,

    Stupid question alert:  I am a new Symantec Admin and have a group of emails that were quarantined as malware.  I have been asked to review the body of the email to determine if it was a targeted attack or not.  I have googled it, checked the Symantec KB and can't find what I am looking for.  To do this do I need to release the email?  That seems counter productive, so I must be missing something.  Thank you in advance!

    0

    0 0

    I need a solution

    Hello

    We are getting errors

    - 421 Unexpected failure

    - 421 Service Temporary Unavailable

    This is happening with companies that use the following MX Servers

    - cluster4a.us.messagelabs.com.

    - cluster4.us.messagelabs.com.

    our IP  address 115.70.190.58 is not listed on any BlackLists 

    Our Exchange only seems to get errors with domains that use Messagelabs

    Does  MessageLabs have a blacklist for our IP 115.70.190.58 or the domain vatcpa.com.au

    0

    0 0

    I need a solution

    Hi there, 

    Our domain's email-addresses  (ending in globaldiversitypractice.com) are being filtered by Symantec under a 553 - Message filtered error. I've already submitted a copy of the e-mail to the investigation email address but this is quite an urgent enquiry as many of our clients are no longer receiving our e-mails. 

    An example of the error message I received is located below: 

    Original Message Details
    Created Date: 11/10/2018 15:08:33
    Sender Address: waseem.ilyas@globaldiversitypractice.com
    Recipient Address:  
    Error Details
    Reported error: 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)

    Please can you help? I've already used mxtoolbox.com to verify that our SPF, DNS and MX records are all functioning correctly, and have had a look for our domain on any blacklists but it isn't showing up on any that I'm aware of. 

    Thanks,

    Waseem 

    0

    0 0

    I need a solution

    Our EMAIL gateways have been blacklisted by Symantec Cloud. Emails we send to our customers are getting "SPAM BLOCKED" with the reason: 553-Message filtered. Refer to the {hash} page at \n553-http://www.symanteccloud.com/{hash} for more \n553 information. (#5.7.1).

    I hereby request you to please mark our domain and IPs as a good sender. Following are our domain names and Gateway IPs.

    DOMAINS:

    1. eg-monitoring.com

    2. egmonitors.com

    3.egmonitroing.com

    IPs:

    34.211.27.24        
    34.211.27.91
    34.211.27.129
    34.211.27.84

    Thanks in advance for your help.

    Jim Adams

    0

    0 0

    I need a solution

    Hi there,
     
    we can't send email from our IP address 195.223.246.45 to customer using messagelabs (error 451); the ip is not listed in http://ipremoval.sms.symantec.com/lookup/ ; trying a telnet on port 25 on various MX from our Symantec Messaging Gateway appliance return a timeout. 
    10-15 days ago we've had spam activity due to some users victim of phishing attacks; now (and since many days) the situation is ok. 

    Is it possible to check the ip? We're having many gripes

    Thank you very much

    0

    0 0

    I need a solution

    Please remove 65.124.182.160 from your blacklist and/or throttling. 

    We are trying to do business with many customers that use messagelabs.com and we have been unable to email them in over a week. All other customers are fine. These customers have put in tickets with Symantec and are not getting a response.

    Thank you

    0

    0 0

    I need a solution

    HI,

    Our email/IP being block by semantic with the ff error:

    553 Message filtered. Refer to the Troubleshooting page at http://www.symanteccloud.com/troubleshooting for more information. (#5.7.1)

    Please advise on how we can fix this

    0

    0 0

    I need a solution

    Hi

    There is a problem that mail sent from IP address 153.122.62.41 times out.

    >Oct 18 03:30:35 cm-c postfix/smtp[9397]: connect to cluster8.us.messagelabs.com[67.219.250.101]:25: Connection timed out
    >Oct 18 03:31:05 cm-c postfix/smtp[9397]: connect to cluster8.us.messagelabs.com[67.219.250.197]:25: Connection timed out

    I have used this;

    http://ipremoval.sms.symantec.com/lookup/

    By checking our IP you can see that there is no problem with the IP address.

    Please tell me how to solve it.
     

    0
    1541034188

    0 0

    I need a solution

    Receiving 4.2.1 service temporarily unavailable from multiple messalabs cluster servers, when emailing a number of different domains. Not on any blacklist or the Symantec negative reputation listing. Emailed Symantec Brightmail Investigations <investigation@review.symantec.com> Responce below

    "We received your sample message and found no Symantec filter sidelining it, which leads us to believe that Symantec is not doing the filtering against your company's messages.

    Best Regards,

    Symantec Investigation Team"

    Issue is only with messagelasbs servers Originating IP is 74.94.141.33

    Please resolve this issue, it has been over a week.

    0

    0 0

    I need a solution

    We are trying to send  emails to a client that is managed by mail555.messagelabs.com, and its giving a 421 service temporary unavailable error message. would someone please help me. Thank you.

    0

    0 0

    I need a solution

    I am unable to send emails to the listed adresses from my mail server 103.43.144.198.

    *@cpl.com.pg
    *@porgerajv.com
    *@treasury.gov.pg
    *@airniugini.com.pg
    *@nmsa.gov.pg
    *@oktedi.com
    *@apng.com

    Sender address are all user within my domain *@ctsl.com.pg.

    I sent an email to Symantec Brightmail Investigations <investigation@review.symantec.com> and got a reply stating the block had been lifted, however this doesn't seem to be the case as I still have emails sitting in my Exchange mail queue.

    This is a sample of one of the NDR's:

    _____________________________________________
    From: Microsoft Outlook
    Sent: Thursday, November 01, 2018 12:00 PM
    To: Charlie Kama
    Subject: Undeliverable: RE: Overdue ASFA Invoice

    Delivery has failed to these recipients or groups:

    ASFA Learning Admin (learning@superannuation.asn.au)
    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.

     

    Diagnostic information for administrators:

    Generating server: mymailserver.ctsl.local
    Receiving server: cluster8a.us.messagelabs.com (52.21.27.115)

     

    learning@superannuation.asn.au
    11/1/2018 1:59:46 AM - Remote Server at cluster8a.us.messagelabs.com (52.21.27.115) returned '550 4.4.7 QUEUE.Expired; message expired'
    11/1/2018 1:47:57 AM - Remote Server at cluster8a.us.messagelabs.com (52.21.27.115) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "421 4.4.2 Connection dropped due to SocketError." 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 52.21.27.115:25'

    Original message headers:

    Received: from mymailserver.ctsl.local (XXX.XXX.XXX.XXX) by
     ctslmailsvr02.ctsl.local (192.168.0.1) with Microsoft SMTP Server (TLS) id
     15.0.847.32; Tue, 30 Oct 2018 11:57:51 +1000
    Received: from ctslmailsvr02.ctsl.local ([::1]) by ctslmailsvr02.ctsl.local
     ([::1]) with mapi id 15.00.0847.030; Tue, 30 Oct 2018 11:57:51 +1000
    From: Charlie Kama <ckama@ctsl.com.pg>
    To: ASFA Learning Admin <learning@superannuation.asn.au>
    Subject: RE: Overdue ASFA Invoice
    Thread-Topic: Overdue ASFA Invoice
    Thread-Index: AdRpunn4nY5JuA+uSC6JiBc3WMwXgAGNnI5AAAClhoA=
    Date: Tue, 30 Oct 2018 01:57:50 +0000
    Message-ID: <10eef687b70a4966bfdaadad4070849c@ctslmailsvr02.ctsl.local>
    References: <MEAPR01MB2901E8C88A526565237CD7F58EF40@MEAPR01MB2901.ausprd01.prod.outlook.com>
     <MEAPR01MB2901D553AF542E1E8F1E466B8ECC0@MEAPR01MB2901.ausprd01.prod.outlook.com>
    In-Reply-To: <MEAPR01MB2901D553AF542E1E8F1E466B8ECC0@MEAPR01MB2901.ausprd01.prod.outlook.com>
    Accept-Language: en-AU, en-US
    Content-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    x-originating-ip: [192.168.0.53]
    x-kse-serverinfo: ctslmailsvr02.ctsl.local, 9
    x-kse-attachmentfiltering-interceptor-info: protection disabled
    x-kse-antivirus-interceptor-info: scan successful
    x-kse-antivirus-info: Clean, bases: 10/29/2018 8:42:00 PM
    x-kse-bulkmessagesfiltering-scan-result: protection disabled
    Content-Type: multipart/alternative;
                boundary="_000_10eef687b70a4966bfdaadad4070849cctslmailsvr02ctsllocal_"
    MIME-Version: 1.0
    X-KSE-Antivirus-Interceptor-Info: fallback
    X-KSE-AntiSpam-Interceptor-Info: fallback
    X-KSE-Antivirus-Interceptor-Info: scan successful
    X-KSE-Antivirus-Info: Clean, bases: 10/30/2018 11:09:00 PM
    X-KSE-Attachment-Filter-Triggered-Rules: Clean
    X-KSE-Attachment-Filter-Triggered-Filters: Clean
    X-KSE-BulkMessagesFiltering-Scan-Result: protection disabled
    X-KSE-AntiSpam-Outbound-Interceptor-Info: scan successful
    X-KSE-AntiSpam-Version: 5.8.6, Database issued on: 10/31/2018 00:27:19
    X-KSE-AntiSpam-Status: KAS_STATUS_NOT_DETECTED
    X-KSE-AntiSpam-Method: none
    X-KSE-AntiSpam-Rate: 0
    X-KSE-AntiSpam-Info: Lua profiles 130754 [Oct 31 2018]
    X-KSE-AntiSpam-Info: LuaCore: 205 205
     2f584fc5d437d92fc6aea7edaff39b944687648d
    X-KSE-AntiSpam-Info: Version: 5.8.6.0
    X-KSE-AntiSpam-Info: Envelope from: ckama@ctsl.com.pg
    X-KSE-AntiSpam-Info: {Tracking_ZWNJ_symbols}
    X-KSE-AntiSpam-Info: www.superannuation.asn.au:7.1.1;www.ctsl.com.pg:7.1.1;www.superguru.com.au:7.1.1;ctsl.com.pg:7.1.1
    X-KSE-AntiSpam-Info: Auth:dkim=none
    X-KSE-AntiSpam-Info: DmarcAF: none
    X-KSE-AntiSpam-Info: Rate: 0
    X-KSE-AntiSpam-Info: Status: not_detected
    X-KSE-AntiSpam-Info: Method: none
    X-KSE-Antiphishing-Info: Clean
    X-KSE-Antiphishing-Method: None
    X-KSE-Antiphishing-Bases: 10/31/2018 00:31:00
    X-KSE-Antivirus-Interceptor-Info: fallback
    X-KSE-AntiSpam-Interceptor-Info: fallback

     

    0

    0 0

    I need a solution

    Hello.

    My customer receives a 421 status in return to RCPT TO command when trying to send a mail to a messagelabs customer. Please see a log example below.

    Sending mail from mx00.mpac.com, 185.37.248.215, Exchange 2010

    IP Investigation at http://ipremoval.sms.symantec.com/lookup/ did return that it's not blocked.

    Thank you and kind regards,

    Hannes

    2018-11-02T10:31:33.385Z,Internet,08D640ADAEC9E854,2,192.168.2.14:52004,52.29.12.9:25,<,"220 mail555.messagelabs.com ESMTP Fri, 02 Nov 2018 10:31:33 +0000",
    2018-11-02T10:31:33.385Z,Internet,08D640ADAEC9E854,3,192.168.2.14:52004,52.29.12.9:25,>,EHLO mx00.mpac.com,
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,4,192.168.2.14:52004,52.29.12.9:25,<,250-mail555.messagelabs.com Hello ip-100-113-13-169.eu-central-1.aws.symcld.net [100.113.13.169],
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,5,192.168.2.14:52004,52.29.12.9:25,<,250-SIZE 52428800,
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,6,192.168.2.14:52004,52.29.12.9:25,<,250-8BITMIME,
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,7,192.168.2.14:52004,52.29.12.9:25,<,250-PIPELINING,
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,8,192.168.2.14:52004,52.29.12.9:25,<,250-CHUNKING,
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,9,192.168.2.14:52004,52.29.12.9:25,<,250-STARTTLS,
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,10,192.168.2.14:52004,52.29.12.9:25,<,250-PRDR,
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,11,192.168.2.14:52004,52.29.12.9:25,<,250 HELP,
    2018-11-02T10:31:33.401Z,Internet,08D640ADAEC9E854,12,192.168.2.14:52004,52.29.12.9:25,>,STARTTLS,
    2018-11-02T10:31:33.432Z,Internet,08D640ADAEC9E854,13,192.168.2.14:52004,52.29.12.9:25,<,220 TLS go ahead,
    2018-11-02T10:31:33.432Z,Internet,08D640ADAEC9E854,14,192.168.2.14:52004,52.29.12.9:25,*,,Sending certificate
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,20,192.168.2.14:52004,52.29.12.9:25,*,,Remote certificate
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,21,192.168.2.14:52004,52.29.12.9:25,*,"CN=mail555.messagelabs.com, O=Exim Developers, C=UK",Certificate subject
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,22,192.168.2.14:52004,52.29.12.9:25,*,"CN=mail555.messagelabs.com, O=Exim Developers, C=UK",Certificate issuer name
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,23,192.168.2.14:52004,52.29.12.9:25,*,00,Certificate serial number
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,24,192.168.2.14:52004,52.29.12.9:25,*,9387CEF45FD5C3EA68ADA0DDEAF6B6B7F831DA2D,Certificate thumbprint
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,25,192.168.2.14:52004,52.29.12.9:25,*,mail555.messagelabs.com,Certificate alternate names
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,26,192.168.2.14:52004,52.29.12.9:25,*,,"TLS protocol SP_PROT_TLS1_0_CLIENT negotiation succeeded using bulk encryption algorithm CALG_AES_256 with strength 256 bits, MAC hash algorithm CALG_SHA1 with strength 160 bits and key exchange algorithm CALG_ECDHE with strength 256 bits"
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,27,192.168.2.14:52004,52.29.12.9:25,*,,Received certificate
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,28,192.168.2.14:52004,52.29.12.9:25,*,9387CEF45FD5C3EA68ADA0DDEAF6B6B7F831DA2D,Certificate thumbprint
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,29,192.168.2.14:52004,52.29.12.9:25,>,EHLO mx00.mpac.com,
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,30,192.168.2.14:52004,52.29.12.9:25,<,250-mail555.messagelabs.com Hello ip-100-113-13-169.eu-central-1.aws.symcld.net [100.113.13.169],
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,31,192.168.2.14:52004,52.29.12.9:25,<,250-SIZE 52428800,
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,32,192.168.2.14:52004,52.29.12.9:25,<,250-8BITMIME,
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,33,192.168.2.14:52004,52.29.12.9:25,<,250-PIPELINING,
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,34,192.168.2.14:52004,52.29.12.9:25,<,250-CHUNKING,
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,35,192.168.2.14:52004,52.29.12.9:25,<,250-PRDR,
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,36,192.168.2.14:52004,52.29.12.9:25,<,250 HELP,
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,37,192.168.2.14:52004,52.29.12.9:25,*,71,sending message
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,38,192.168.2.14:52004,52.29.12.9:25,>,MAIL FROM:<xxxxxx@mpac.com> SIZE=240433,
    2018-11-02T10:31:33.479Z,Internet,08D640ADAEC9E854,39,192.168.2.14:52004,52.29.12.9:25,>,RCPT TO:<xxxxxxxx@xxxxxxxxx.de>,
    2018-11-02T10:31:33.494Z,Internet,08D640ADAEC9E854,40,192.168.2.14:52004,52.29.12.9:25,<,250 OK,
    2018-11-02T10:31:33.494Z,Internet,08D640ADAEC9E854,41,192.168.2.14:52004,52.29.12.9:25,<,421 Service Temporarily Unavailable,
    2018-11-02T10:31:33.494Z,Internet,08D640ADAEC9E854,42,192.168.2.14:52004,52.29.12.9:25,>,QUIT,
    2018-11-02T10:31:33.494Z,Internet,08D640ADAEC9E854,43,192.168.2.14:52004,52.29.12.9:25,-,,Local
    
    0

    0 0

    I need a solution

    Hi,

    we cannot send emails (several users are experiencing this) to any server under clusterXX.eu.messagelabs.com

    Our IPs are not blacklisted, but still getting our mail hold in the queue with message:
    (lost connection with cluster8.eu.messagelabs.com[46.226.52.98] while performing the EHLO handshake)
    or
    (lost connection with cluster3.eu.messagelabs.com[85.158.142.99] while performing the EHLO handshake)

    Can you please give a look?

    Thanks,

    F:

    0

    0 0

    I need a solution

    I have just started to receive 553 NDR's for replies to a particular domain. If I copy the content out and put it in a new message it is delivered as expected. I am unable to send the failed email as an attachment to investigation@review.symantec.com as I receive another 553 NDR.

    Is there another way to get a sample in for inspection?

    Thanks

    0

older | 1 | .... | 38 | 39 | (Page 40) | 41 | 42 | newer