> But this is a problem of a clueless configured virus scanner on the
> remote side.
> First, it makes no sense to send a warning out to the "sender", since
> the "sender" is faked in almost all cases.
This is only the case in recent times. In former times, viruses were not so smart to use
their own smtp engine like NetSky or Bagle do now. They had to use the applications on
the computer and hung themselves at any mail, the user send. In those times, the
notification made a lot of sense. But the servers do not seem to be configured to respond
to the new development.
> Second, even /if/ they send a warning, this warning shoud be addressed
> neither to the From nor to the Reply-To, but to the Sender (which should
> be somthing like majordomo-owner@listserver)
This assumes that a mail server application is able to distinguish between a "normal"
user address and a list server adress. I don't think this is the case and I presume it's too
difficult to program.