Daryl C. W. O'Shea wrote: > > > Please post the full received headers of the problem message and your > trusted/internal/msa networks config. If you're paranoid about publicly > posting them you can send them to me directly. > > Daryl > >
Hi Daryl, Email system will not use NAT so IP adressess are not secret and somebody can see almost everything from headers so there is no reason not to post all requested data. Relevant configuration lines are: trusted_networks 212.62.32.0/19 trusted_networks 89.110.192.0/18 trusted_networks 213.137.96.0/19 trusted_networks 82.208.192.0/18 trusted_networks 10.0.0.0/8 internal_networks 212.62.57.32/30 msa_networks 212.62.57.116/30 msa_networks 212.62.57.156/30 msa_networks 212.62.57.36/30 MTA acting as MX is mtain1.isp.ptt.rs 212.62.57.32 and I put it in trusted and internal networks (if relevant). MTA receiving email from clients is mtaout1.isp.ptt.rs 212.62.57.36 and I put it in trusted and msa networks. SpamAssassin is implemented by using spamd running on machine which is also in trusted networks (if it is relevant for anything). Client in example is Outlook Express at 89.110.202.24 also in trusted networks. Here are headers and body of sample email captured as direct communication between spamc and spamd: CHECK SPAMC/1.2 Content-length: 1324 Received: from gigatpc ([89.110.202.24]) by mtaout1.isp.ptt.rs with ESMTP; Sun, 24 Feb 2008 15:11:09 +0100 (CET) Message-ID: <[EMAIL PROTECTED]> From: "Joshua Gigic" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: ovo je email 2 Date: Sun, 24 Feb 2008 15:13:05 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; .boundary="----=_NextPart_000_000A_01C876F7.C1872B80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C876F7.C1872B80 Content-Type: text/plain; .charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable dva su dela ------=_NextPart_000_000A_01C876F7.C1872B80 Content-Type: text/html; .charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV>dva su dela</DIV> <DIV> </DIV></BODY></HTML> ------=_NextPart_000_000A_01C876F7.C1872B80-- This is just sample email, not representing ham or spam which is not so relevant because SpamAssasing fires on every email by DOS_OE_TO_MX. Log line from spamd: Feb 24 15:11:10 localhost spamd[23664]: spamd: result: . 1 - ALL_TRUSTED=-1.44,AWL=-0.294,DOS_OE_TO_MX=2.75,HTML_MESSAGE=0.001 scantime=0.8,size=1324,user=(unknown),uid=1783,required_score=5.0,rhost=mtaout1.isp.ptt.rs,raddr=212.62.57.36,rport=30948,mid=<[EMAIL PROTECTED]>,autolearn=no,shortcircuit=no SpamAssassin has only one non standard patch for logging all scores but same thing is happening with SpamAssassin without any patches so problem must be in my configuration. Regards, Giga -- View this message in context: http://www.nabble.com/ALL_TRUSTED-and-DOS_OE_TO_MX-tp15659736p15665031.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
