>> [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, >> why? As most of your authenticated end-users are connecting to your >> Internet mail server from dialup (DUL) addresses, it makes no sense to >> run SA against their email (if SA is configured to do RBL checks that is). >> >> > The mail is sent to its destination, another qmail machine running SA >> > Here, SA assigns score to DUL lists, and to a numeric ip in helo (which >> > was only added by qmail-scanner, The HOST_EQ_D_D_D_D and HOST_EQ_D_D_D_DB >> > entries also seem to be triggered by the qmail-scanner header >> > >> > >> HOST_EQ_D_D_D_D isn't part of standard SA - where did that come from? >> >>
Hi Jason, 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 recipients' mailbox The SA markup was generated on the server that this machine was sending to The HOST_EQ_D_D_D_D rule seems to live on rulesemporium Regards Wolfgang Hamann
