Now this will sound silly and picky, but NOD32 AV and ESS are inserting an Eset ID code like "X-EsetId: 3D31132BC2823C326F72" into the headers or at the end of some mail/spam messages that I receive. The problem is that I am an avid antispammer. I report every un-requested message to various places around the net, request domain removal from their registrars, request their name servers be null routed,etc.... Now this sounds like a job and it is, but many of the operations are automated. The problem comes in that Eset just inserts their code where ever and they don't pad it with a line return or even a space. This results in a lot of the information being misread by the reporting software because it sees X-EsetID as part of the address or header. This causes the lookups to fail meaning the report doesn't get generated or I have to do it manually. I don't think the code itself is causing any issues, but the way they insert it is very bad. It forces me to do way more manual processing of this spam junk. Could somebody at Eset look into how you are inserting these codes and pad them a bit so they don't join themselves on to valid information?