Date: Fri, 30 Jul 2004 16:43:33 -0400 From: Tim Schutt <tim@square1consulting.com> To: freebsd-questions@freebsd.org Subject: Re: amavisd/clamav Virus Recipient email notification template woes Message-ID: <1F94DE30-E269-11D8-8A9E-000A27B47720@square1consulting.com> In-Reply-To: <20040730160947.4fdbe0dd.wmoran@potentialtech.com> References: <12abd8c2040730104259ea346e@mail.gmail.com> <9cd98d120407301237e31f8ef@mail.gmail.com> <20040730160947.4fdbe0dd.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I completely understand where you are coming from, and I am only intending on notifying the intended recipient of the email, not the "sender" for the very reason that you note. If it was just me, I would can the message and be done with it. However, I am in the midst of marketing this service to some highly security conscious people so I would like the reinforcement of the notifications for their piece of mind and a little customer-stroking reminding them how great the service is. :-) Lame reason, maybe... but there is reasonable logic behind me wanting to do this. Tim. On Jul 30, 2004, at 4:09 PM, Bill Moran wrote: > If you're going to send notification, there is only one _proper_ way > to do it: > analyze the Received: headers and find out where the virus _really_ > originated, > then contact the abuse@ address for that domain with the message. > Despite how easy this is to do, it doesn't seem like a lot of AV > packages > bother with it ... > > -- > Bill Moran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1F94DE30-E269-11D8-8A9E-000A27B47720>