[Assp-test] MSGID
I have DoMSGIDsig set to block which seems to be blocking most of the messages I previously sorted out. I have one or two messages that seem to still be getting past the filters, for some reason these seem to be scored rather than blocked. Are there any other settings that would cause a message with the following headers to be scored instead of blocked or is ASSP making a mistake somewhere? 232P Received: from [127.0.0.1] (helo=tfoms.primorye.ru) by mail.smtphost.co.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) id 1TPGbw-00051u-4r for alberta.ikan...@recipient.tld; Fri, 19 Oct 2012 18:43:54 +0100 144P Received: from tfoms.primorye.ru ([212.91.213.66] helo=tfoms.primorye.ru) by mail.smtphost.co.uk with SMTP (2.2.2); 19 Oct 2012 18:43:50 +0100 035F From: postmas...@tfoms.primorye.ru 039T To: alberta.ikan...@recipient.tld 038 Date: Sat, 20 Oct 2012 04:43:43 +1100 018 MIME-Version: 1.0 127 Content-Type: multipart/report; report-type=delivery-status; boundary=9B095B5ADSN=_01CDA7FAC6439896D3C0tfoms.primorye.r 052 X-DSNContext: 335a7efd - 4523 - 0001 - 80040546 050I Message-ID: nvhvy4yt83...@tfoms.primorye.ru 066 Subject: [ Possibly Spam ] Delivery Status Notification (Failure) 052 X-Assp-Version: 2.2.2(12276) on mail.smtphost.co.uk 023 X-Assp-Server-TLS: yes 066 X-Assp-Received-SPF: none ip=212.91.213.66 helo=tfoms.primorye.ru 118 X-Original-Authentication-Results: mail.smtphost.co.uk; spf=none (SPF: none ip=212.91.213.66 helo=tfoms.primorye.ru) 048 X-Assp-Re-BombSubjectRe: PB 6: for Notification 055 X-Assp-Message-Score: 6 (BombSubjectRe 'Notification') 050 X-Assp-IP-Score: 6 (BombSubjectRe 'Notification') 046 X-Assp-ID: mail.smtphost.co.uk m1-68631-09857 056 X-Assp-Intended-For: alberta.ikan...@recipient.tld 050 X-Assp-Redlisted: Yes (bounces are not collected) 064 X-Assp-Original-Subject: Delivery Status Notification (Failure) 069 X-Assp-Message-Score: 40 (MSGID-sig check failed for bounce sender ) 064 X-Assp-IP-Score: 40 (MSGID-sig check failed for bounce sender ) 022 X-Assp-Tag: MSGID-sig 017 X-Assp-Spam: YES 018 X-Spam-Status:yes 062 X-Assp-Spam-Reason: MSGID-sig check failed for bounce sender 030 X-Assp-Message-Totalscore: 46 030 X-Assp-Spam-Level: ** -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
Re: [Assp-test] MSGID
ASSP development mailing list assp-test@lists.sourceforge.net schrei bt: 017 X-Assp-Spam: YES 018 X-Spam-Status:yes 062 X-Assp-Spam-Reason: MSGID-sig check failed for bounce sender Then header are saying, that the mail was caught and considered Spam. Why do you think, it went through? -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
Re: [Assp-test] MSGID
On 20/10/2012 13:03, Fritz Borgstedt wrote: ASSP development mailing list assp-test@lists.sourceforge.net schrei bt: 017 X-Assp-Spam: YES 018 X-Spam-Status:yes 062 X-Assp-Spam-Reason: MSGID-sig check failed for bounce sender Then header are saying, that the mail was caught and considered Spam. Why do you think, it went through? The subject was tagged as [ Possibly Spam ] and the message let past ASSP into my Exim queues. So, the headers are saying that the message should have been blocked when it wasn't. All the best, Colin Waring. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
Re: [Assp-test] MSGID
ASSP development mailing list assp-test@lists.sourceforge.net schrei bt: The subject was tagged as [ Possibly Spam ] and the message let past ASSP into my Exim queues. So, the headers are saying that the message should have been blocked when it wasn't. The tag is Possibly . This is normally the case when the score is in warning range and DoMSGIDsig is set to scoring. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
[Assp-test] Becoming too complicated!
Based on my own experience and that of others (looking at the postings including the current MSGID discussion), I can help but wonder if ASSP configuration has gotten too complex. I'm not suggesting we drop features, but maybe the who way it is configured needs to be rethought!? Instead of hundres of fields to configure (in many categories), could we make this more pictoral? collapsing fields that don't apply? I don't have an answer, but someone has to start the conversation :) -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
