On Fri, Jul 30, 2004 at 06:22:00PM -0600, Warren Block wrote:
On Fri, 30 Jul 2004, Tim Schutt wrote:
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
On Fri, 30 Jul 2004 13:42:00 -0400, Tim Schutt [EMAIL PROTECTED] wrote:
I've got postfix/amavisd/clamav configured on my mailserver, but I am
having trouble getting the notification emails to format properly.
Virus and spam notifications are a bad idea. Both types of email
forge the sender
Logan Ashby [EMAIL PROTECTED] wrote:
On Fri, 30 Jul 2004 13:42:00 -0400, Tim Schutt [EMAIL PROTECTED] wrote:
I've got postfix/amavisd/clamav configured on my mailserver, but I am
having trouble getting the notification emails to format properly.
Virus and spam notifications are a bad
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
On Fri, 30 Jul 2004 16:43:33 -0400, Tim Schutt
[EMAIL PROTECTED] wrote:
Lame reason, maybe... but there is reasonable logic behind me wanting
to do this.
That's understandable, but it may well backfire on you. I would be
just as irritated at receiving hundreds, possibly thousands of notices
On Fri, 30 Jul 2004, Tim Schutt wrote:
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
