Hi Jason,
it seems the problem is caused by this set of headers:
>> Received: from 84.153.210.199 ([EMAIL PROTECTED]) by shared3 (envelope-from
>> <[EMAIL PROTECTED]>, uid 0) with qmail-scanner-2.01
>> (clamdscan: 0.88.1/1426. hbedv: 6.34.1.27/6.34.1.12. spammassassin: 3.1.1
>> Clear:RC:0(84
[EMAIL PROTECTED] wrote
> I have made my setup such that auth'd users still have their outgoing mails
> scanned.
> After all they are potentially running windows and could be sending virus.
>
> I do not use SA within qmail-scanner at all, but rather run it before mail is
> delivered to
> the reci
>> [EMAIL PROTECTED] wrote:
>> > So what happens: a mail is sent via an authenticated session, to a qmail /
>> > qmail-scanner
>> > setup running at mydomain.de
>> >
>>
>> By default Qmail-Scanner specifically doesn't pass locally generated or
>> authenticated mail to SpamAssassin. Have you
From: "Matt Kettler" <[EMAIL PROTECTED]>
Jason Haar wrote:
HOST_EQ_D_D_D_D isn't part of standard SA - where did that come from?
It appears to come from:
http://www.rulesemporium.com/rules/88_FVGT_headers.cf
header HOST_EQ_D_D_D_D X-Spam-Relays-Untrusted =~ /^[^\]]+ rdns=[^
]+\d{1,3}[^
Jason Haar wrote:
I guess a more generic question would be: how do sites handle calling SA
for validated-but-remote local users? Qmail-Scanner defaults to *not*
calling SA - is that what most others do too?
If not, how do you handle the fact those users are (by definition) going
to be on DUL lis
I guess a more generic question would be: how do sites handle calling SA
for validated-but-remote local users? Qmail-Scanner defaults to *not*
calling SA - is that what most others do too?
If not, how do you handle the fact those users are (by definition) going
to be on DUL lists?
--
Cheers
Jas
Jason Haar wrote:
> HOST_EQ_D_D_D_D isn't part of standard SA - where did that come from?
>
It appears to come from:
http://www.rulesemporium.com/rules/88_FVGT_headers.cf
header HOST_EQ_D_D_D_DX-Spam-Relays-Untrusted =~ /^[^\]]+ rdns=[^
]+\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,3}[^0-9]\d{1,
[EMAIL PROTECTED] wrote:
> So what happens: a mail is sent via an authenticated session, to a qmail /
> qmail-scanner
> setup running at mydomain.de
>
By default Qmail-Scanner specifically doesn't pass locally generated or
authenticated mail to SpamAssassin. Have you overridden that? If so,
