asmethurst
July 16th, 2008, 12:26 PM
Hi,
Is anyone else experiencing this problem:
Out of the box, NOD32 v3 appends a footer to outbound emails including the URL www.eset.com. We use Spamhaus Block Lists to assist in spam detection (like many others). Unfortunately some of our inbound replies are marked as spam due to this URL being on the SBL and scored accordingly.
I understand that this can be overcome by removing the footer or modifying our spam detection rules. Unfortunately there are many others using the same block lists, or NOD32 customers that are unaware that they could be sending out messages which might never reach their recipients.
It might be worth checking to make sure this isn't impacting your business. I know this only came to my attention after I was alerted that some important documents were not being received. It only took a few minor SpamAssassin scores to build up before these emails became blocked.
I definitely don't want to rubbish the product or Eset, but would like to share this potential issue with others.
I certainly would like Eset to look into this, and if confirmed, make the necessary actions to have the URL removed from the SBL.
Kind regards,
Andrew
Is anyone else experiencing this problem:
Out of the box, NOD32 v3 appends a footer to outbound emails including the URL www.eset.com. We use Spamhaus Block Lists to assist in spam detection (like many others). Unfortunately some of our inbound replies are marked as spam due to this URL being on the SBL and scored accordingly.
I understand that this can be overcome by removing the footer or modifying our spam detection rules. Unfortunately there are many others using the same block lists, or NOD32 customers that are unaware that they could be sending out messages which might never reach their recipients.
It might be worth checking to make sure this isn't impacting your business. I know this only came to my attention after I was alerted that some important documents were not being received. It only took a few minor SpamAssassin scores to build up before these emails became blocked.
I definitely don't want to rubbish the product or Eset, but would like to share this potential issue with others.
I certainly would like Eset to look into this, and if confirmed, make the necessary actions to have the URL removed from the SBL.
Kind regards,
Andrew