probably have
to be using a content filter to properly test it.
===
Robert Cohen
Systems & Desktop Services
Division of Information
R.G Menzies Building
Building 2
The Australian National University
Canberra ACT 0200 Australia
T: +61 2 6125 8389
F: +61 2
puremessage.
Its been reported to sophos, so if it is the milter, then they will
doubtless provide a patch.
I assumed it wasn't the milter because restarting postfix even without
restarting the milter fixed the problem, I'm pretty sure.
And the problem didn't occur with sendmail wi
On 14/8/08 12:11 PM, "Wietse Venema" <[EMAIL PROTECTED]> wrote:
> Robert Cohen:
>> ul 27 12:43:23 mailin2 postfix/smtp[29137]: 4CBB07E8009:
>> to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1]:10025, delay=137638,
>> delays=137638/0/0/0, dsn=4
On 14/8/08 11:25 PM, "Wietse Venema" <[EMAIL PROTECTED]> wrote:
> Robert Cohen:
>> So if a filter botches handling one message, postfix gives on sending it
>> anything for up to 15 minutes?
>> That doesn't seem like a particularly graceful way
complain about random spurious keywords appearing
in main.cf
Anyway Ive removed it now, and will report it to puremessage.
Apparently we arent using any smtpd_restriction_classes.
But I can't see why that would be relevant.
On 17/9/08 6:40 PM, "Jan P. Kessler" <[EMAIL PROTECTED
