> Thanks for the info. As I suspected its time to
> turn off notifications to
> senders.
This may not be necessary. I made the following two
changes and the Klez situation is much better now.
1) Enable the sub-sender-cache.pl from the crontrib
folder.
2) Add the source IP address to the heade
> I understand the problem, but cannot think of a way
> to solve it without
> possibly causing loops. Any suggestions appreciated
> :-)
How about adding just the source IP as part of the
standard headers output?
source ip = x.x.x.x
to:
from:
subject:
date:
I think this along with a customized n
Would it be possible for q-s to dump the full original
headers to the end of a warning message and not just
the various to and from fields? I think this woudl
greatly assign client service and repair departments,
and the people receiving the message so they can
dertermine if the source IP is the
> > > In real life, q-s is sending the warning to
> > ADDRESS-C,
> > > the envelope from, the header that viruses like
> > > make up. (eep!)
> > > This results in many warnings going to innocent
> > > bystanders. That is the problem.
> > This is true for the Magistr virus, but what about
> > the
--- Joel Michael <[EMAIL PROTECTED]> wrote:
> On Wed, 2002-05-01 at 12:05, Surly Zek wrote:
> > In real life, q-s is sending the warning to
> ADDRESS-C,
> > the envelope from, the header that viruses like to
> > make up. (eep!)
> >
> > This
I agree with you, and you agreed with me, but I think
that you missed my point.
In the example I gave, both myself and q-s think that
the from address listed in the second set of "headers"
(not the envelope from) should receive the warning.
We both believe that ADDRESS-A should be getting t
Hello,
I think there is a problem with at least q-s 1.10 and
1.11. When a warning is sent, and q-s has detected
different "envelope from" and "header from" addresses,
q-s sends the warning to the wrong from address.
Even though q-s identifies that it thinks it is
contacting ADDRESS-A (see the a
