Email Security.cloud

 View Only
Back to discussions
Expand all | Collapse all

ipremoval from Symantec blacklist (again)

  • 1.  ipremoval from Symantec blacklist (again)

    Posted Feb 21, 2017 10:52 AM

    Dear sirs

    It's almost a week that I found again every day our mail server listed in your blacklist with a bad reputation. Each day I request an investigation at http://ipremoval.sms.symantec.com/lookup/ and the problem seems to be resolved till the next day. The reason provided for the assessment is “The host is unauthorized to send email directly to email servers” but this message cannot help me in any way to figure out what the actual problem is.This issue is costing to our company a lot of problems with our customer using Symantec mail security and so rejecting our emails. There is no spam coming out from our mail server, there is no virus on our mail server and no other pc in our network is sending spam nor is infected. Please keep in mind that our mail server is not listed in any worldwide blacklist but your one. The problem looked like to be solved a couple of months ago

    Would you please help me to actually work out this problem ?

    Thank you in advance

    Kind regards

    Marco Della Torre



  • 2.  RE: ipremoval from Symantec blacklist (again)

    Broadcom Employee
    Posted Feb 22, 2017 05:14 AM

    Hi Marco

    Could you please tell me your IP so I can look into this?

    Thanks

    Ian Tiller

    Tier 2 Senior Technical Support Engineer



  • 3.  RE: ipremoval from Symantec blacklist (again)

    Posted Feb 22, 2017 05:28 AM

    Hi Ian

     

    Our IP address is 93.145.174.220 (mail.afsoluzioni.it)

     

    regards

     

    Marco



  • 4.  RE: ipremoval from Symantec blacklist (again)

    Broadcom Employee
    Posted Feb 22, 2017 05:59 AM

    Hi

    I checked the IP and can see that currently this is not listed in any blasklists or being throttled in any way.

    Can you let me know if the issue recurs again and I will look into it further for you.

    Thank you

    Ian Tiller

    Tier 2 Senior Technical Support Engineer



  • 5.  RE: ipremoval from Symantec blacklist (again)

    Posted Feb 22, 2017 06:33 AM

    Ok,

    I'll let you know if it'll be blacklisted again

    Thank you

     

    regards

     

    Marco

     



  • 6.  RE: ipremoval from Symantec blacklist (again)

    Posted Feb 24, 2017 12:39 PM

    Hello, We have this problem too, please you help me on this. Every day our email server in your blacklist with a bad reputation

    please you help me.

    thanks



  • 7.  RE: ipremoval from Symantec blacklist (again)

    Posted Feb 24, 2017 03:22 PM

    Hi,

    I am experiencing the same problem.
    Our server IP is 198.255.38.2

    The server logs have been checked thorouhgly and no spam is or has been sent from our server. But it keeps turning up in the symantec blacklist.
    Please help me here because it is causing much inconvenience for our company and our clients and also for the mail servers that use the blacklist for filtering their mail.

    PLEASE HELP ME

    Thanks in advance.



  • 8.  RE: ipremoval from Symantec blacklist (again)

    Broadcom Employee
    Posted Feb 28, 2017 05:22 AM

    Hi Heiko,

    I have checked your IP address on all of our systems and can see nothing in place to prevent your email connections

    Can you retest this and advise if you are still having the problem?

    Any bounce backs, error messages etc would be really helpful if you are still seeing the problem

    Kind Regards

    Richard Brittain
    Tier2 Senior Technical Support Engineer,
    Symantec Corporation



  • 9.  RE: ipremoval from Symantec blacklist (again)

    Posted Mar 16, 2017 11:23 AM

    We have been blacklisted again. This is kind of annoying. What does exactly "The host is unauthorized to send email directly to email servers" mean and how can I solve this issue ? Symantec is the only one to blacklist our mail server and we don't know why this happens.

     

    Regards

     

    Marco



  • 10.  RE: ipremoval from Symantec blacklist (again)

    Posted Mar 16, 2017 12:07 PM

    We urgently need a solution for this issue. This problem is costing us time and money.

     

     

    Regards

     

    Marco



  • 11.  RE: ipremoval from Symantec blacklist (again)

    Broadcom Employee
    Posted Mar 17, 2017 03:56 AM

    Hi Marco,

    Checking back earlier in this thread I can see the IP you were having problems with from your side was 93.145.174.220

    I have tested this IP address this morning and can see nothing in place that would restrict you ability to connect to us,

    Are you able to provide bounce back messages or verbose SMTP logs showing the SMTP connection to us this would greatly help me in tracking down the problem

    Kind Regards

    Richard Brittain
    Tier2 Senior Technical Support Engineer,
    Symantec Corporation



  • 12.  RE: ipremoval from Symantec blacklist (again)

    Posted Mar 17, 2017 06:26 AM

    Hi Richard,

    You cannot see anything probably because I've requested another delisting. This morning our ip has been blacklisted again. (I checked at http://ipremoval.sms.symantec.com)

    In our mail server log there are plenty of these records:

    Mar 16 10:28:51 xxxxx postfix/smtp[27929]: 4ED3980811: to=<xxxx@yyyyyy.zzz>, relay=aaa.bbbbbb.cc[999.999.999.999]:25, delay=3.8, delays=3.1/0/0.72/0, dsn=4.7.1, status=deferred (host aaa.bbbbbb.cc[999.999.999.999] refused to talk to me: 554 5.7.1 You are not allowed to connect.)

    Please, keep in mind that

    1) Symantec the only to blacklist our mail server. 

    2) There's no spam coming out from our mail server

    3) There's no virus on our mail server

    4) Our mail server is not an open relay

    5) Our mail server has not a dynamic IP  

    6)  Our mail server does not allow authentication on port 25 but only on port 587

    Please help us to understand what else is missing on our mail server because this issue is costing us a lot of time and money

     

    Thank you in advance

    best regards

     

    Marco

     



  • 13.  RE: ipremoval from Symantec blacklist (again)
    Best Answer

    Broadcom Employee
    Posted Mar 17, 2017 09:41 AM

    Hi Marco,

    Unfortuently due to the way the systems work here unless you currently being blocked in some way it is very difficult for us to advise to why.

    If the block comes back again on this IP address please let us know straight away and we will have one of the security team here review it manually, hopefully this will give us some more insight

    Kind Regards

    Richard Brittain
    Tier2 Senior Technical Support Engineer,
    Symantec Corporation

     



  • 14.  RE: ipremoval from Symantec blacklist (again)

    Posted Oct 12, 2020 08:54 AM
    Hi Richard,

    Exactly the same
    5.254.113.34
    about every day the server appears in your blacklist, one removal request a day, a couple of hours out of the list and again and again.
    1) Symantec is the only to blacklist our mail server.
    2) There's no spam coming out from our mail server
    3) There's no virus on our mail server
    4) Our mail server are not open relays
    5) Our mail server has not dynamic IPs
    6) Our inverse records are correcly registered
    7) Our SPF records are present and working

    Please help us to understand what else is missing on our mail server because this issue is costing us a lot of time and money

    Original Message


  • 15.  RE: ipremoval from Symantec blacklist (again)

    Posted Mar 23, 2017 05:30 AM

    Dear Sirs,

    our IP 193.77.36.20 is also blacklisted for the last almost 72 hours even though we sent already several IP removal requests to Symantec. Until now there was no response form your side, we still cannot send the emails to the companies using your software and this is causing us huge business damage.

    We checked our servers and are not infected, we are not sending spam or any other possible reasons.

    Therefore I would like to ask you to remove our IP from your black list where it was put already twice in the past 2 months.

    Thank you-1

    We get the following meesage back:

    20.3.2017 15:17:45 - Remote Server at XXX.XXX.com (xxx.xxx.xxx.xx) returned '451 4.4.0 Primary target IP address responded with: "554 5.7.1 You are not allowed to connect.." 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 xxx.xxx.xxx.xx'

     



  • 16.  RE: ipremoval from Symantec blacklist (again)

    Posted Mar 24, 2017 10:25 AM

    Hello,

    we have a new dedicated server at HOSTFORWEB, ip 66.225.229.38 , just 10 days old.  Its ip is listed at the blacklist and i have asked for removal over 5 times last 10 days and it was not delisted.  The bad reputation belongs to old owner of the IP.

    at other blacklists i found over 1.000.000 spam emails sent by this ip, but many many years ago, some from 2009.

    Please remove our ip above from your list. 

    We are a legitimate company and many of our customers are Ford suppliers and all of them are getting blocked.  We are in trouble over here.  Many suppliers cant send official documentation for over a week and have already said they will cancel our contract, and its not our fault.

     



  • 17.  RE: ipremoval from Symantec blacklist (again)

    Posted Apr 13, 2017 08:24 AM

    Hi Richard,


    Because of connectivity problems somewhere in the US, we changed our mailserver IP to 198.255.39.11.
    Immediately after the change the IP showed up as been blacklisted by Symantec Bad Senders.
    This seems to be the same issue as in February.
    Can you please check this again?



  • 18.  RE: ipremoval from Symantec blacklist (again)

    Posted Apr 18, 2017 03:50 AM

    Hi Richard

    i have same problem! are many mount that symatec give bad reputation to my server!

    I have a ecommerce web site with dedicated server and every week we send mail to over than 30.000 costumer

    i leave here an example of error

    This message was created automatically by mail delivery software.

    A message that you sent could not be delivered to one or more of its
    recipients. This is a permanent error. The following address(es) failed:

      -----@alice.it
        host smtp.aliceposta.it [82.57.200.133]
        SMTP error from remote mail server after pipelined MAIL FROM:<-----------@hlifepoint.it> SIZE=27594:
        550 mail not accepted from blacklisted IP address [195.154.33.80]

    Action: failed
    Final-Recipient: rfc822;-------------@alice.it
    Status: 5.0.0
    Remote-MTA: dns; smtp.aliceposta.it
    Diagnostic-Code: smtp; 550 mail not accepted from blacklisted IP address [195.154.33.80]
     

    Please, keep in mind that

    1) Symantec the only to blacklist our mail server. 

    2) There's no spam coming out from our mail server

    3) There's no virus on our mail server

    4) Our mail server is not an open relay

    5) Our mail server has not a dynamic IP  

    Hoping you can help me

    Thank 

    Luca



  • 19.  RE: ipremoval from Symantec blacklist (again)

    Posted May 08, 2017 03:36 AM

    Same problem here, 149.202.68.205

    It's the third day that the server appears in your blacklist, one removal request a day, a couple of hours out of the list and again and again.

    1) Symantec is the only to blacklist our mail server. 

    2) There's no spam coming out from our mail server

    3) There's no virus on our mail server

    4) Our mail server is not an open relay

    5) Our mail server has not a dynamic IP

    ¿Next steps?

    Thank you 

    David



  • 20.  RE: ipremoval from Symantec blacklist (again)

    Posted May 09, 2017 05:10 AM

    Exactly the same

    5.196.99.35

    about every day the server appears in your blacklist, one removal request a day, a couple of hours out of the list and again and again.

    1) Symantec is the only to blacklist our mail server. 

    2) There's no spam coming out from our mail server

    3) There's no virus on our mail server

    4) Our mail server is not an open relay

    5) Our mail server has not a dynamic IP

    6) the server is NOT used for newsletter but only for one to one commenications



  • 21.  RE: ipremoval from Symantec blacklist (again)

    Posted May 09, 2017 01:32 PM

    I have the same problem with my ip. I have contacted symantec multiple times with no response.

    Im extremely dissapointed with lack of professionalism on part of symantec.

     



  • 22.  RE: ipremoval from Symantec blacklist (again)

    Posted May 10, 2017 11:49 AM

    Exactly the same another time....I think Symantec has problems in managing this structure....now in my agenda I added "check symantec" every day....

    not so nice.....

    5.196.99.35

    about every day the server appears in your blacklist, one removal request a day, a couple of hours out of the list and again and again.

    1) Symantec is the only to blacklist our mail server. 

    2) There's no spam coming out from our mail server

    3) There's no virus on our mail server

    4) Our mail server is not an open relay

    5) Our mail server has not a dynamic IP

    6) the server is NOT used for newsletter but only for one to one communications



  • 23.  RE: ipremoval from Symantec blacklist (again)

    Posted May 10, 2017 01:57 PM

    I also think Symantec has issues managing their infrastructure. Worst part is that they are making it difficult for legit ESPs to get their emails to the inbox.



  • 24.  RE: ipremoval from Symantec blacklist (again)

    Posted May 21, 2017 04:36 AM

    Same here, wrote a post asking for them to resolve the issue and its not been published

    tried to send a very basic message to the forum and admin and am greeted with

    'Your submission has triggered the spam filter and will not be accepted'

    How many millions $$$ Symantec make and such dismal support!



  • 25.  RE: ipremoval from Symantec blacklist (again)

    Posted May 21, 2017 05:25 AM

    Hi,

    we just transferred our mail servers to a new IP in OVH that we discovered ( after) it has been blacklisted. 

    our IP are 92.222.116.147 92.222.116.148.

    I checked and requested three times in the last week to be delisted, every two days our IP's come back to  blacklist.

    as the other peolpe writing here :

    1) Symantec is the only to blacklist our mail server. 

    2) There's no spam coming out from our mail server

    3) There's no virus on our mail server

    4) Our mail server are not open relays

    5) Our mail server has not dynamic IPs

    6) Our inverse records are correcly registered

    7) Our SPF records are present and working

    If I relay every email from new IP addresses through old mailservers everything works and they don'get listed, so it's not the traffic going out from new that rise alarms.

    Please help me,

    BR



  • 26.  RE: ipremoval from Symantec blacklist (again)

    Posted May 22, 2017 10:54 AM

    Hi, Steffano Gatto,

    I had a post here at Symantec and they deleted it !!!

    Our IP at OVH is 92.222.106.120 to 127

    and we are having the same problems!

    Symantec and OVH are both playing stupid!



  • 27.  RE: ipremoval from Symantec blacklist (again)

    Broadcom Employee
    Posted May 23, 2017 04:30 AM

    Hi Stefano,

    I have replied to you already in the other thread,

    Andreas, I'm sorry your happy with the support you have received so far, I want you to know that I have raised a job manaual investigation to be done on your IP range to see what is going on here and I will feedback to you as soon as I can

    Kind Regards

    Richard Brittain
    Tier2 Senior Technical Support Engineer,
    Symantec Corporation



  • 28.  RE: ipremoval from Symantec blacklist (again)

    Posted May 23, 2017 05:07 AM

    Hi Richard,

    we were informed by OVH that they had esculated our ticket and that someone at 'OVH Security' would be contacting Symantec regards this issue.

    Dear Customer,

    As per our phone call I have escalated this issue to our security team directly.  They should be in contact with symeantec to remove blacklist.  As soon as I receive a response I will let you know.

    You have a typo in your message, we definately are NOT happy with the support we have received so far.

    Who would be happy if the only thread they had created pointing out the issue was deleted ?

    Hope to hear some positive news from either Symantec or OVH with regards to this senseless tarnishing of our IPs

    Thanks

     



  • 29.  RE: ipremoval from Symantec blacklist (again)

    Posted May 23, 2017 10:17 AM

    you have been lucky, OVH Italy told me that they can't do anything for my problem... I hope now symantec can do something to delist and rise reputation of the IPs to avoid this problem



  • 30.  RE: ipremoval from Symantec blacklist (again)

    Posted May 23, 2017 10:29 AM

    I'm very sorry but I didn't see your reply, can you point me to the other thread pls?

    OK saw it now... sorry... missing page refresh....



  • 31.  RE: ipremoval from Symantec blacklist (again)

    Broadcom Employee
    Posted May 24, 2017 05:05 AM

    Hi Andreas,

    Can you retest for me and let me know if you have any further problems

    Hopefully your IP will no longer be restricted

    Kind Regards

    Richard Brittain
    Tier2 Senior Technical Support Engineer,
    Symantec Corporation



  • 32.  RE: ipremoval from Symantec blacklist (again)

    Posted May 26, 2017 06:03 AM

    Hi Richard,

    Unfortunately your iplookup tool is no longer working so I cant check from that resource.

    I started a thread, with yet no answer ............

    https://www.symantec.com/connect/forums/symantec-ip-removal-lookup-url

    Found another Symantec resource in the mean time.

    http://www.symantec.com/security_response/landing/spam/

    Here our IP is showing as neutral for a few days now.

    Any other IP adjacent of our block is showing as bad, so I assume Symantec have now correctly identified our IP block as being OK.

    Stefano, you IP is showing a neutral also, OVH should be honest with you about the issue!

    Regards

    Andreas

    ** EDIT **

    Mail still being delivered to one of our clients who use Symantec as email gateway

    :-)

     

     



  • 33.  RE: ipremoval from Symantec blacklist (again)

    Posted May 30, 2017 09:06 AM

    please whitelist ip 164.132.192.183 is not sending spam !!!



  • 34.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 15, 2017 12:24 PM 
    Hi there ,

    I'm having the issue of blocked ip address. My server's IP is 66.96.213.90

    the error is "connect to cluster3.eu.messagelabs.com[85.158.136.35]:25: Connection timed out"

    Could you please have a look at it?

    Best regards

    Justin

    IndoChine Group Singapore



  • 35.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 19, 2017 06:20 AM

    Hi Justin,

    I have now reset the confidence of that IP across our infrastructure and your Emails should no longer be blocked.

    Kind regards


    Kevin Brosnan
    Tier 2 Senior Technical Support Engineer

    CompTIA Security+ Certified

     



  • 36.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 22, 2017 09:55 AM

    Hi Marco,

    Just following up on this topic and wondered if you need any further assistance on this matter.

    If the issue has since been resolved. Please can you set this thread as resolved to prevent others adding to it.

    Kind regards

    Kevin Brosnan
    Tier 2 Senior Technical Support Engineer

    CompTIA Security+ Certified



  • 37.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 23, 2017 11:32 AM

    Kevin - This is an issue with us as well.  This seems to be a widespread issue that Symantec needs to fix.  We have the same symptoms as other users above.  Submit to http://ipremoval.sms.symantec.com/lookup/ This works for several days in a row, now our IP is no longer being removed.  This is negatively impacting our business. We are on no blacklists, not sending spam, etc.  

    Please advise how to permanently resolve this issue.



  • 38.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 28, 2017 03:52 PM

    I am getting sick and tired of this blacklist, it keeps popping up while no other blacklists have us listed also I can't find this blacklist amongst any other blacklist inquiry service like spamhaus or MXtoolbox. Why the hell doesn't symantec appear on these lists? 

    I am losing customers that complain about not being able to send mail to their clients. Delisting is useless because it will come back up on the list in no time without any good reason. We're running SSL on our mail server, we got DKIM signaturing and all possible security precautions you can think of, if anything our server is one of the most secure servers in the country. 

    I'm done with this crap, never buying anything from symantec, ever again.



  • 39.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 29, 2017 11:47 AM

    Still on the blacklist Symantec, fix this my clients are getting frustrated. If I was an American I would sue your f'ing asses for this.



  • 40.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 30, 2017 02:35 AM

    Hi Dave,

    So sorry that you feel this way. However its very hard to guess your sending IP and without it I am unable to look into this for you?

    Kind regards

    Kevin Brosnan
    Tier 2 Senior Technical Support Engineer

    CompTIA Security+ Certified
     



  • 41.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 30, 2017 02:44 AM

    More than a month ago I started to receive this message when I check if my server is blacklisted:

     "The IP address you submitted, 149.202.68.205, does not have a negative reputation and therefore cannot be submitted for investigation." 

     

    So, not in the blacklist, but ... I can't send messages because they get blocked

     

    Symantec, we all need a solution, our customer are not able to understand that such a big company as Symantec can behave this way if we are not sending spam

    Please, we need a solution



  • 42.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 30, 2017 02:54 AM

    Hi David,

    I have checked your IP and this is not listed on the .cloud blacklist and we would not be blocking your connections. Could you provide the senders and recipients full email address (Of a failed email) so I can investigate further.

    Also if possible can you start up a new topic to avoid multiple different issues appearing under this one thread.

    Kind regards

    Kevin Brosnan
    Tier 2 Senior Technical Support Engineer

    CompTIA Security+ Certified



  • 43.  RE: ipremoval from Symantec blacklist (again)

    Posted Jun 30, 2017 04:42 PM

    Hi

    My IP "162.214.16.233" also keeps getting blacklisted daily. Its currently not on any other blacklist apart from symantec. This is the bounce back email:

    This is the mail delivery agent at Symantec Email Security.cloud.

     

    I was unable to deliver your message to the following addresses:

     

    arti.asharma@vodafone.com.fj

     

    Reason: 550 Message refused by Trustwave SEG SpamProfiler

     

    The message subject was: [Suspected Spam]: VODAFONE FIJI LTD The message date was: Thu, 15 Jun 2017 12:31:47 +1200 The message identifier was: 8C/03-01999-9F3D1495 The message reference was: server-12.tower-188.messagelabs.com!1497486323!113655423!9

     

    Please do not reply to this email as it is sent from an unattended mailbox.

    Contact your email administrator if you need more information, or instructions for resolving this issue.

     

    Please help resolve this

     

     



  • 44.  RE: ipremoval from Symantec blacklist (again)

    Posted Jul 03, 2017 04:07 AM

    Good morning,

    After months of research I came to this thread since writing does not answer anyone.
    As I have been saying for months we are penalized on many VIRUS FREE, NO OPEN RELAY servers that comply with all the security rules without sending spam as your filter as it can be seen from all users who write DO NOT WORK.

    Now if something does not work, the simplest thing to do is turn it off and turn it back on once.

    I will send you all our IPs for which you only consider to be malicious and for which I am looking forward to being removed from the black list:

     

    51.255.23.164

    51.255.23.165

    37.59.129.124

    37.59.129.125

    37.59.129.126

    37.59.129.127

     

    193.70.58.176

    193.70.58.177

    193.70.58.178

    193.70.58.179

     

     

     



  • 45.  RE: ipremoval from Symantec blacklist (again)

    Posted Nov 29, 2017 01:53 AM

    Mail from our mail server IP address (138.201.136.178 (mail1.alloy.ee)) is being rejected for the past 1 week. The IP does not exist on any blacklist, including your own. I have sent mail to Investigation@review.symantec.com twice, but there's no response.

    This mail server does not send any SPAM. We have hundreds of mail in our queue, and since this is a relay that for corporate customers it is causing tremendous problems.

    I find it ridiculous that the rules take 1 week to propagate across your clusters.

    Sample reject messages follows - full email address redacted for privacy:

    Nov 29 08:43:50 mail1 postfix/error[18139]: DE6E91682236: to=<a....a@jindalaluminium.com>, relay=none, delay=0.17, delays=0.05/0/0/0.11, dsn=4.0.0, status=deferred (delivery temporarily suspended: host cluster6.us.messagelabs.com[216.82.249.212] refused to talk to me: 501 Connection rejected by policy [7.7] 21914, please visit www.messagelabs.com/support for more details about this error message.)
    Nov 29 08:43:50 mail1 postfix/error[18139]: DE6E91682236: to=<a....a@jindalaluminium.com>, relay=none, delay=0.17, delays=0.05/0/0/0.12, dsn=4.0.0, status=deferred (delivery temporarily suspended: host cluster6.us.messagelabs.com[216.82.249.212] refused to talk to me: 501 Connection rejected by policy [7.7] 21914, please visit www.messagelabs.com/support for more details about this error message.)

    Bharath Chari

     



  • 46.  RE: ipremoval from Symantec blacklist (again)

    Posted Dec 13, 2017 07:58 AM

    I am experiencing the same problem.
    Our server IP is 185.132.124.98

    The server logs have been checked thorouhgly and no spam is or has been sent from our server.

    But it keeps turning up in the symantec blacklist.


    Please help me here because it is causing much inconvenience for our company and our clients and also for the mail servers that use the blacklist for filtering their mail.

    PLEASE HELP ME

    Thanks in advance.



  • 47.  RE: ipremoval from Symantec blacklist (again)

    Posted Apr 22, 2020 12:12 PM
    Gentlemen,

    we are a softwarehouse that has developed a program for family doctors to send drug recipes to their patients at home.

    This need occurred by resolution of the Ministry of Health to avoid COVID-19 infections

    We had to implement a mail server for this need, and it has valid SPF, DMARC and DKIM records.

    It has no problems with anyone but only with SYMANTEC, and for this reason we have requested automatic delisting dozens of times but without result.

    Therefore, we are asking for the deletion of our IP from your BlackList database
    The request, given the moment, is of absolute urgency as many users do not receive mail

    Our IP is the following: 172.107.204.139

    THANK YOU !
    Original Message


  • 48.  RE: ipremoval from Symantec blacklist (again)

    Posted Apr 23, 2020 07:14 AM

    YOU STILL BLOCKED US!


    THEY REPORTED US FOR INTERRUPTION OF PUBLIC SERVICE, BUT DO YOU ACKNOWLEDGE THAT YOU RESET THE BLACKLIST EVERY DAY?

    OUR IP IS 172.107.204.139, PLEASE UNLOCK IT DEFINITELY


    Original Message


  • 49.  RE: ipremoval from Symantec blacklist (again)

    Posted Oct 16, 2020 05:34 PM
    Also our IP 80.211.102.132 was blocked for "bad reputation".
    We have repeatedly requested removal via https://ipremoval.sms.symantec.com/ipr/lookup without success.
    I don't understand why it is being blocked. How can we remove it?
    I also sent a request email to 'Investigation@review.symantec.com' but they didn't reply.
    Thank you
    Original Message


  • 50.  RE: ipremoval from Symantec blacklist (again)

    Posted Oct 16, 2020 05:34 PM
    Also our IP 80.211.102.132 was blocked for "has a bad reputation".
    We have repeatedly requested removal via the form https://ipremoval.sms.symantec.com/ipr/lookup without success.
    I don't understand why it is being blocked. How can we remove it?
    I also sent a request email to 'Investigation@review.symantec.com' but they didn't reply.
    Thank you
    Original Message


  • 51.  RE: ipremoval from Symantec blacklist (again)

    Broadcom Employee
    Posted Oct 19, 2020 09:28 AM
    Hello Ruben;

    I ran the IP you provided through the IP Removal Page.  It states the IP is being listed due to the following reasons:

    The host has been observed sending spam in a format that is similar to snow shoe ( Hit & Run) spamming techniques.
    The host is unauthorized to send email directly to email servers.

    This occurs when we observe a large amount of messages being sent with characteristics of Spam.  You may also wish to ensure your mail server has not been compromised and that the authorized systems sending mail through it have been checked to ensure they have not been compromised. 
    When you request the IP to be removed on the IP removal page, you can also submit a sample of a message to further assist in the investigation. 

    Please note that a removed IP will be re-added any time we observe it sending large amounts of messages with characteristics of spam.

    Best Regards,
    John F.
    Broadcom
    Original Message


  • 52.  RE: ipremoval from Symantec blacklist (again)

    Posted Oct 19, 2020 12:09 PM
    My IPs 74.63.237.112, 74.63.237.113, 74.63.237.115 are listed as same reason, but the server which uses this IP has been closed all email related ports, and it has never sent email for 1 year and more.
    Also, these IPs are not listed in any black lists.
    Of course, these IPs are NOT obviously related to "snow shoe technique". Also, these IPs mustn't have any claims from Symantec customers because it does not have any access from outside and nobody knows.
    Thus, the reason described as "The host has been observed sending spam in a format that is similar to snow shoe spamming techniques. The host is unauthorized to send email directly to email servers." is Untrustworthy at all.
    Original Message