Greylisting (WAS: Re: MailScanner ANNOUNCE: 4.57 released)

Glenn Steen glenn.steen at gmail.com
Mon Dec 4 22:51:48 GMT 2006


On 04/12/06, Nerijus Baliunas <nerijus at users.sourceforge.net> wrote:
> On Mon, 04 Dec 2006 22:12:03 +0530 Dhawal Doshy <dhawal at netmagicsolutions.com> wrote:
>
> > Nerijus, Glenn had mentioned that you send some raw samples (where
> > privacy is not critical) of mails pre and post milters to Julian.. did
> > you manage to do that?
>
> If you mean just raw messages - then yes, I sent them to Julian, but if you
> mean queue files - then no (how/where should I take them from?).
>
> Regards,
> Nerijus
That's easy Nerjus.... I'll try be a bit more eloquent than last time:-)....
Stop mailscanner, start postfix, send the testmessage, look in the log
what queue ID it got (or just trawl through "postqueue -p" (a.k.a.
mailq), copy that file (queue ID == filename) from the hold queue
(after all, it's just a file). Then stop Postfix and restart
MailScanner...

Disable the missbehaving milter, repeat the above... And voila, there
you have it, "the same" message in a working and a non-working queue
file. Makes it possible for Jules (or one of us other postfixers:-) to
try see what goes wrong... without having to implement the same exact
setup you have.

Another possibility would be to use the Archive Mail feature, but then
you'd have to make sure it archives to queue files and not decoded and
put in some other format (mbox).

The first method is guaranteed to get us what we want.

Be aware that the queue file might contain information that could be
construed as sensitive (depends on policy, as always:-).

-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se


More information about the MailScanner mailing list