From martin.hierling at fh-luh.de Tue Nov 7 11:29:11 2006 From: martin.hierling at fh-luh.de (Martin Hierling) Date: Tue, 7 Nov 2006 20:29:11 +0100 Subject: [SA-exim] spamassassin --lint and Greylist Problem Message-ID: <20061107192911.GA10407@cc.fh-luh.de> Hi, am just testing sa-exim and stumbled over the following problem. When i lint my spamassasson rules i get the following warning: [20256] warn: Couldn't get Connecting IP header X-SA-Exim-Connect-IP for message <1162927488 at lint_rules>, skipping greylisting call [20256] warn: lint: 1 issues detected, please rerun with debug enabled for more information and an exit status of "1", which means "false", there are errors. I did like to update my SA rules with rules_du_jour but the script does noting until sa --lint returns "0". Do you have any idea how to get around this? regards Martin From martin.hierling at fh-luh.de Tue Nov 7 11:35:02 2006 From: martin.hierling at fh-luh.de (Martin Hierling) Date: Tue, 7 Nov 2006 20:35:02 +0100 Subject: [SA-exim] Greylist in DB Message-ID: <20061107193502.GB10407@cc.fh-luh.de> Hi, me again, i have read a thread in october about the greylisting information are not nessessary on the mail server but on the SA server. So what if i habe x SA servers? I certainly could share the information via nfs, but that is slow. i have read and seen the case statement in Greylisting.pm where i can enter the DB code. But does anyone know if the code is already written (i cant write perl) and where to download it? regards Martin From marc at merlins.org Tue Nov 7 19:37:33 2006 From: marc at merlins.org (Marc MERLIN) Date: Tue, 7 Nov 2006 19:37:33 -0800 Subject: [SA-exim] spamassassin --lint and Greylist Problem In-Reply-To: <20061107192911.GA10407@cc.fh-luh.de> References: <20061107192911.GA10407@cc.fh-luh.de> Message-ID: <20061108033733.GE15796@merlins.org> On Tue, Nov 07, 2006 at 08:29:11PM +0100, Martin Hierling wrote: > Hi, > > am just testing sa-exim and stumbled over the following problem. > When i lint my spamassasson rules i get the following warning: > > [20256] warn: Couldn't get Connecting IP header X-SA-Exim-Connect-IP for > message <1162927488 at lint_rules>, skipping greylisting call > [20256] warn: lint: 1 issues detected, please rerun with debug enabled > for more information > > and an exit status of "1", which means "false", there are errors. > I did like to update my SA rules with rules_du_jour but the script does > noting until sa --lint returns "0". bummer... And the SA-Exim SA rule is right to complain that it's missing the SA header, so the rule cannot be computed I recommend that you manually edit the SA perl module, and change the return value next to that error message to true to make SA happy Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ From marc at merlins.org Thu Nov 9 07:26:56 2006 From: marc at merlins.org (Marc MERLIN) Date: Thu, 9 Nov 2006 07:26:56 -0800 Subject: [SA-exim] sa-exim's Greylisting.pm doesn't check for local connections In-Reply-To: <87lkmk7jfk.fsf@worf.arundel.trustsec.de> References: <87lkmk7jfk.fsf@worf.arundel.trustsec.de> Message-ID: <20061109152656.GA11896@merlins.org> On Thu, Nov 09, 2006 at 04:01:51PM +0100, Andreas V?gele wrote: > Dear Marc, > > I'd like to scan messages with sa-exim that fetchmail directly > delivers to the MTA with the sendmail command. But Greylisting.pm > from sa-exim v4.2.1 doesn't check whether the message was locally > generated and so I get the following error messages in the log file : > > Nov 2 16:48:20 example spamd[23021]: Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/Plugin/Greylisting.pm line 176. > Nov 2 16:48:20 example spamd[23021]: Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/Plugin/Greylisting.pm line 177. > > Of course, fetchmail could deliver the messages through the local > interface, but for several reasons I prefer to use the sendmail > command. > > I've attached a small patch for Greylisting.pm. The code added by > this patch returns from greylisting() if the variable $connectip > contains the string ''. The header > X-SA-Exim-Connect-IP is set to this string in sa-exim.c if the message > was locally generated. That's interesting. I guess you don't get the same from that as running your own MTA on the net, but that's still a valid use I didn't think about. If/when I have the next version, I'll include this patch. In the meantime, I cced the sa-exim list so that others can benefit Thanks, Marc Content-Description: Check for local connections > --- Greylisting.pm.orig 2006-10-30 10:11:17.000000000 +0100 > +++ Greylisting.pm 2006-11-03 16:17:28.000000000 +0100 > @@ -103,6 +103,11 @@ > return 0; > } > chomp($connectip); > + if ($connectip eq '') > + { > + Mail::SpamAssassin::Plugin::dbg("GREYLISTING: skipping greylisting for locally generated message $mesgid"); > + return 0; > + } > # Clean up input (for security, if you use files/dirs) > $connectip =~ /([\d.:]+)/; > $connectip = ($1 or ""); -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ From marc at merlins.org Thu Nov 9 07:30:47 2006 From: marc at merlins.org (Marc MERLIN) Date: Thu, 9 Nov 2006 07:30:47 -0800 Subject: [SA-exim] Greylist in DB In-Reply-To: <20061107193502.GB10407@cc.fh-luh.de> References: <20061107193502.GB10407@cc.fh-luh.de> Message-ID: <20061109153047.GB11896@merlins.org> On Tue, Nov 07, 2006 at 08:35:02PM +0100, Martin Hierling wrote: > Hi, me again, > > i have read a thread in october about the greylisting information are > not nessessary on the mail server but on the SA server. So what if i > habe x SA servers? I certainly could share the information via nfs, but > that is slow. i have read and seen the case statement in Greylisting.pm > where i can enter the DB code. But does anyone know if the code is > already written (i cant write perl) and where to download it? I haven't heard anyone doing this. Now, if you only have 2, or 3 servers, in your shoes, I wouldn't do anything: if you have 3 servers, after the mail is sent back 4 times to you, at most, you would accept it (3 of the times after the greylist timeout). Now, if you have 20 servers or less, then yes, you would need to share the DB. At that point, you might want to have the greylist info in some database, but I haven't heard of anyone doing this (my personal take on databases is to avoid them as another potential source of problems and failures :) ) Anyway, I think you would be the first to do this, but as you note it's really only 30-50 lines of perl in the greylist module. It shouldn't be that hard to do. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ From avo at trustsec.de Thu Nov 9 09:18:47 2006 From: avo at trustsec.de (Andreas =?iso-8859-1?Q?V=F6gele?=) Date: Thu, 09 Nov 2006 18:18:47 +0100 Subject: [SA-exim] sa-exim's Greylisting.pm doesn't check for local connections References: <87lkmk7jfk.fsf@worf.arundel.trustsec.de> <20061109152656.GA11896@merlins.org> Message-ID: <874pt84jyg.fsf@worf.arundel.trustsec.de> Marc MERLIN writes: > On Thu, Nov 09, 2006 at 04:01:51PM +0100, Andreas V?gele wrote: [...] >> I've attached a small patch for Greylisting.pm. The code added by >> this patch returns from greylisting() if the variable $connectip >> contains the string ''. The header >> X-SA-Exim-Connect-IP is set to this string in sa-exim.c if the >> message was locally generated. > > That's interesting. I guess you don't get the same from that as > running your own MTA on the net, but that's still a valid use I > didn't think about. Actually, I'm using this patch on an MTA which also accepts mail from the net. That's one of the reasons why I decided to use the sendmail command to deliver messages that were fetched with fetchmail. I can now use the Exim ACL acl_not_smtp for the fetchmail messages and keep the fetchmail settings separate from the other ACLs. Here's an example: acl_not_smtp = acl_check_not_smtp acl_check_not_smtp: # Don't scan unless the message was retrieved with fetchmail. warn condition = ${if eq{$sender_ident}{fetchmail}{no}{yes}} set acl_m0 = do-not-scan # Never reject messages that were retrieved with fetchmail. warn condition = ${if eq{$sender_ident}{fetchmail}{yes}{no}} set acl_m0 = do-not-reject accept > If/when I have the next version, I'll include this patch. In the > meantime, I cced the sa-exim list so that others can benefit I tried to post through Gmane but that didn't work since the list is moderated. I've just subscribed to the list but disabled delivery so that I can still use Gmane to read the list. From info at a-wing.co.uk Thu Nov 30 05:56:39 2006 From: info at a-wing.co.uk (Andrew Hutchings) Date: Thu, 30 Nov 2006 13:56:39 +0000 Subject: [SA-exim] Greylisting problem Message-ID: <456EE317.1050203@a-wing.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have just setup sa-exim on my Ubuntu Dapper based server. I have set: SApermreject: 12.0 SAtempreject: 3.5 SAgreylistraisetempreject: 6.0 And done the necessary to setup greylisting in Spamassassin. However tuplets only seem to be getting added when whitelisting. Instead of greylisting it is just temp rejecting. Can you think of anything I might have missed? Regards Andrew - -- Andrew Hutchings (A-Wing) - Linux Jedi A-Wing Internet Services - www.a-wing.co.uk Windows is the path to the darkside...Windows leads to Blue Screen. Blue Screen leads to downtime. Downtime leads to suffering...I sense much Windows in you. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbuMXZ+2Y3WLvbJIRAohIAKCM3aQHTyibK+ZcNc8UrvKnyAaMiwCfXOeU gJuM8bfDq+1Dt6h4Y50NM3w= =hHGc -----END PGP SIGNATURE----- From marc at merlins.org Thu Nov 30 07:24:09 2006 From: marc at merlins.org (Marc MERLIN) Date: Thu, 30 Nov 2006 07:24:09 -0800 Subject: [SA-exim] Greylisting problem In-Reply-To: <456EE317.1050203@a-wing.co.uk> References: <456EE317.1050203@a-wing.co.uk> Message-ID: <20061130152409.GN15210@merlins.org> On Thu, Nov 30, 2006 at 01:56:39PM +0000, Andrew Hutchings wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I have just setup sa-exim on my Ubuntu Dapper based server. > I have set: > SApermreject: 12.0 > SAtempreject: 3.5 > SAgreylistraisetempreject: 6.0 > > And done the necessary to setup greylisting in Spamassassin. However > tuplets only seem to be getting added when whitelisting. Instead of > greylisting it is just temp rejecting. > > Can you think of anything I might have missed? I'm not sure what you mean: are you saying that greylisting is never able to write tuplets, and therefore mails always get temprejected? If so, check your permissions on disk, and your exim/spamassassin logs to see why spamassassin doesn't have perms to write in /var/spool/sa-exim/tuplets/ Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ From info at a-wing.co.uk Thu Nov 30 07:36:51 2006 From: info at a-wing.co.uk (Andrew Hutchings) Date: Thu, 30 Nov 2006 15:36:51 +0000 Subject: [SA-exim] Greylisting problem In-Reply-To: <20061130152409.GN15210@merlins.org> References: <456EE317.1050203@a-wing.co.uk> <20061130152409.GN15210@merlins.org> Message-ID: <456EFA93.6080608@a-wing.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc MERLIN wrote: > On Thu, Nov 30, 2006 at 01:56:39PM +0000, Andrew Hutchings wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi, >> >> I have just setup sa-exim on my Ubuntu Dapper based server. >> I have set: >> SApermreject: 12.0 >> SAtempreject: 3.5 >> SAgreylistraisetempreject: 6.0 >> >> And done the necessary to setup greylisting in Spamassassin. However >> tuplets only seem to be getting added when whitelisting. Instead of >> greylisting it is just temp rejecting. >> >> Can you think of anything I might have missed? > > I'm not sure what you mean: are you saying that greylisting is never able to > write tuplets, and therefore mails always get temprejected? > If so, check your permissions on disk, and your exim/spamassassin logs to > see why spamassassin doesn't have perms to write in > /var/spool/sa-exim/tuplets/ > > Marc - -- Andrew Hutchings (A-Wing) - Linux Jedi A-Wing Internet Services - www.a-wing.co.uk Windows is the path to the darkside...Windows leads to Blue Screen. Blue Screen leads to downtime. Downtime leads to suffering...I sense much Windows in you. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbvqTZ+2Y3WLvbJIRAoxhAKCjoW+RNCTutBTQAB8LeO9JPSSi6ACgw2Ab aaYfPCqcUbcr9NpORTUjfiE= =ZLXG -----END PGP SIGNATURE----- From info at a-wing.co.uk Thu Nov 30 07:43:01 2006 From: info at a-wing.co.uk (Andrew Hutchings) Date: Thu, 30 Nov 2006 15:43:01 +0000 Subject: [SA-exim] Greylisting problem In-Reply-To: <20061130152409.GN15210@merlins.org> References: <456EE317.1050203@a-wing.co.uk> <20061130152409.GN15210@merlins.org> Message-ID: <456EFC05.100@a-wing.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc MERLIN wrote: > On Thu, Nov 30, 2006 at 01:56:39PM +0000, Andrew Hutchings wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi, >> >> I have just setup sa-exim on my Ubuntu Dapper based server. >> I have set: >> SApermreject: 12.0 >> SAtempreject: 3.5 >> SAgreylistraisetempreject: 6.0 >> >> And done the necessary to setup greylisting in Spamassassin. However >> tuplets only seem to be getting added when whitelisting. Instead of >> greylisting it is just temp rejecting. >> >> Can you think of anything I might have missed? > > I'm not sure what you mean: are you saying that greylisting is never able to > write tuplets, and therefore mails always get temprejected? > If so, check your permissions on disk, and your exim/spamassassin logs to > see why spamassassin doesn't have perms to write in > /var/spool/sa-exim/tuplets/ > > Marc (Try again :) Hi Marc, Not quite, it is writing tuplets for whitelisted items (mail with a score <3.5), but it isn't greylisting anything, just constantly temp rejecting if >3.5 && <12 with nothing new in the tuplets. It definitely isn't a permissions problem with /var/spool/sa-exim/tuplets/ Regards Andrew - -- Andrew Hutchings (A-Wing) - Linux Jedi A-Wing Internet Services - www.a-wing.co.uk Windows is the path to the darkside...Windows leads to Blue Screen. Blue Screen leads to downtime. Downtime leads to suffering...I sense much Windows in you. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbvwFZ+2Y3WLvbJIRAqHZAJ4kRC5DcbUMN/ieXjdqyuh81uqLyQCfVdeX opXXdUYnqzEjJMbg7Nam4MU= =4q0Y -----END PGP SIGNATURE----- From marc at merlins.org Thu Nov 30 08:32:59 2006 From: marc at merlins.org (Marc MERLIN) Date: Thu, 30 Nov 2006 08:32:59 -0800 Subject: [SA-exim] Greylisting problem In-Reply-To: <456EFC05.100@a-wing.co.uk> References: <456EE317.1050203@a-wing.co.uk> <20061130152409.GN15210@merlins.org> <456EFC05.100@a-wing.co.uk> Message-ID: <20061130163259.GQ15210@merlins.org> On Thu, Nov 30, 2006 at 03:43:01PM +0000, Andrew Hutchings wrote: > > I'm not sure what you mean: are you saying that greylisting is never able to > > write tuplets, and therefore mails always get temprejected? > > If so, check your permissions on disk, and your exim/spamassassin logs to > > see why spamassassin doesn't have perms to write in > > /var/spool/sa-exim/tuplets/ > > > > Marc > > (Try again :) (actually we got 3 copies :) > Hi Marc, > > Not quite, it is writing tuplets for whitelisted items (mail with a > score <3.5), but it isn't greylisting anything, just constantly temp > rejecting if >3.5 && <12 with nothing new in the tuplets. > It definitely isn't a permissions problem with /var/spool/sa-exim/tuplets/ Ah, I see. Mmmh, beats me. I would say turn on debugging for spamassassin, something like spamassassin -t -D < /tmp/greylistmail and look at the output. If necessary, add prints in the perl module so that it gives you a clue why it's not writing to disk when it enters the greylist code Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ From Mark at atomicpark.com Thu Nov 30 08:44:32 2006 From: Mark at atomicpark.com (Mark Zbikowski) Date: Thu, 30 Nov 2006 10:44:32 -0600 Subject: [SA-exim] Customizing reject messages using variables? Message-ID: <4A28E5DD9634974BBE07BF7D5B47F3341D1D2E@exchange1.ramint.ramdist.cc> I'd like to customize the reject message (SAmsgpermrej) in sa-exim.conf to include the message "please contact postmaster at mydomain.com". My email gateway handles multiple domains, and I'd like the "mydomain.com" portion to reflect the domain name of the intended recipient. Is this possible? I'm running exim 4.63 and sa-exim 4.2 in Debian. Thanks for your help! Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.merlins.org/archives/sa-exim/attachments/20061130/1e0e6b35/attachment.htm From marc at merlins.org Thu Nov 30 09:06:36 2006 From: marc at merlins.org (Marc MERLIN) Date: Thu, 30 Nov 2006 09:06:36 -0800 Subject: [SA-exim] Customizing reject messages using variables? In-Reply-To: <4A28E5DD9634974BBE07BF7D5B47F3341D1D2E@exchange1.ramint.ramdist.cc> References: <4A28E5DD9634974BBE07BF7D5B47F3341D1D2E@exchange1.ramint.ramdist.cc> Message-ID: <20061130170636.GT15210@merlins.org> On Thu, Nov 30, 2006 at 10:44:32AM -0600, Mark Zbikowski wrote: > I'd like to customize the reject message (SAmsgpermrej) in sa-exim.conf > to include the message "please contact postmaster at mydomain.com". > > My email gateway handles multiple domains, and I'd like the > "mydomain.com" portion to reflect the domain name of the intended > recipient. > > Is this possible? I'm afraid not, the string is static and doesn't get any variable substitution. Of course, you could hack that in sa-exim.c in about 10-15mn, but making this a real option with all the configuration variables and substitutions that people could think of, would take a while :) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ From info at a-wing.co.uk Thu Nov 30 12:02:54 2006 From: info at a-wing.co.uk (Andrew Hutchings) Date: Thu, 30 Nov 2006 20:02:54 +0000 Subject: [SA-exim] Greylisting problem In-Reply-To: <20061130163259.GQ15210@merlins.org> References: <456EE317.1050203@a-wing.co.uk> <20061130152409.GN15210@merlins.org> <456EFC05.100@a-wing.co.uk> <20061130163259.GQ15210@merlins.org> Message-ID: <456F38EE.9000805@a-wing.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc MERLIN wrote: >> Not quite, it is writing tuplets for whitelisted items (mail with a >> score <3.5), but it isn't greylisting anything, just constantly temp >> rejecting if >3.5 && <12 with nothing new in the tuplets. >> It definitely isn't a permissions problem with /var/spool/sa-exim/tuplets/ > > Ah, I see. > > Mmmh, beats me. > I would say turn on debugging for spamassassin, something like > spamassassin -t -D < /tmp/greylistmail > and look at the output. > If necessary, add prints in the perl module so that it gives you a clue why > it's not writing to disk when it enters the greylist code > > Marc After reading through the SA module code I figured out where I was going wrong. All spam in question had no from set, and I had the option greylistnullfrom set to 0. Unfortunately this doesn't produce any warn or anything, it just exits gracefully, which made it very hard to debug. So as a feature request, could this output a message to state that there is no from set and greylistnullfrom is 0? Regards Andrew - -- Andrew Hutchings (A-Wing) - Linux Jedi A-Wing Internet Services - www.a-wing.co.uk Windows is the path to the darkside...Windows leads to Blue Screen. Blue Screen leads to downtime. Downtime leads to suffering...I sense much Windows in you. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbzjuZ+2Y3WLvbJIRAuz/AJ9jEo6Odx7sdmwu+tT7HbJpEnlG6ACgvaYN Q07YVq5sqtbh/JrDdVDpJY8= =pfTk -----END PGP SIGNATURE----- From marc at merlins.org Thu Nov 30 12:21:40 2006 From: marc at merlins.org (Marc MERLIN) Date: Thu, 30 Nov 2006 12:21:40 -0800 Subject: [SA-exim] Greylisting problem In-Reply-To: <456F38EE.9000805@a-wing.co.uk> References: <456EE317.1050203@a-wing.co.uk> <20061130152409.GN15210@merlins.org> <456EFC05.100@a-wing.co.uk> <20061130163259.GQ15210@merlins.org> <456F38EE.9000805@a-wing.co.uk> Message-ID: <20061130202140.GA15210@merlins.org> On Thu, Nov 30, 2006 at 08:02:54PM +0000, Andrew Hutchings wrote: > After reading through the SA module code I figured out where I was going > wrong. All spam in question had no from set, and I had the option > greylistnullfrom set to 0. Unfortunately this doesn't produce any warn > or anything, it just exits gracefully, which made it very hard to debug. Oh, I see. > So as a feature request, could this output a message to state that there > is no from set and greylistnullfrom is 0? The small problem here is that spamassassin doesn't have a way to write in the exim logs or to talk to SA-Exim. However, it wouldn't be too hard to have the SA module put out some mail header saying X-Greylisted: No, null from and greylistnullfrom is 0 or some such. That said, people aren't very likely to notice that either, so I'm not sure what makes more sense between better documentation, or that. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ From info at a-wing.co.uk Thu Nov 30 12:45:37 2006 From: info at a-wing.co.uk (Andrew Hutchings) Date: Thu, 30 Nov 2006 20:45:37 +0000 Subject: [SA-exim] Greylisting problem In-Reply-To: <20061130202140.GA15210@merlins.org> References: <456EE317.1050203@a-wing.co.uk> <20061130152409.GN15210@merlins.org> <456EFC05.100@a-wing.co.uk> <20061130163259.GQ15210@merlins.org> <456F38EE.9000805@a-wing.co.uk> <20061130202140.GA15210@merlins.org> Message-ID: <456F42F1.5080402@a-wing.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc MERLIN wrote: >> So as a feature request, could this output a message to state that there >> is no from set and greylistnullfrom is 0? > > The small problem here is that spamassassin doesn't have a way to write in > the exim logs or to talk to SA-Exim. Indeed, sorry, I meant in the spamassassin debugging messages, as most of Greylisting.pm does. > However, it wouldn't be too hard to have the SA module put out some mail > header saying X-Greylisted: No, null from and greylistnullfrom is 0 > or some such. > That said, people aren't very likely to notice that either, so I'm not sure > what makes more sense between better documentation, or that. I think the documentation option may be better. As well as possibly SA debugging messages. Maybe a documentation section on debugging problems using "spamassassin - -t -D" and some test meassages that have the required mail headers already set (such as the IP header). Regards Andrew - -- Andrew Hutchings (A-Wing) - Linux Jedi A-Wing Internet Services - www.a-wing.co.uk Windows is the path to the darkside...Windows leads to Blue Screen. Blue Screen leads to downtime. Downtime leads to suffering...I sense much Windows in you. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFb0LxZ+2Y3WLvbJIRAsqIAJ4m2JtOFXlnsjSmQ3aJdKe0hppoAACgykMB WrFq4oupj+xBs+7wcN5IjvY= =KTy/ -----END PGP SIGNATURE-----