🚀 go-pugleaf

On 14 Apr, in article <35337029.0@muir-et2.staff.demon.net>
     malcolm@demon.net "Malcolm Muir" wrote:

MM> >>Could you please post an example transaction ?
MM> >
MM> >Since her posting Claire has posted more detail to the Demon Testers
MM> >mailing list.
MM> 
MM> Indeed, we believe we have found the cause (but not the fix) for
MM> this problem. Thanks

Glad that helped!   Until there's a fix at your end (which I do
understand may take time), do you perhaps have any ideas for a
workaround for users?

The only thing I can think of is to ensure that SMTP clients
issue a QUIT if they receive anything other than a 250 response
to an RSET, but the hard-working wonderman who gas developed the
modified KA9Q that I use doesn't think he'll have the time for
a while.

My only solution so far is the ensure that I avoid
pepper.mail.demon.net (the EXIM machines) by explicitly
using as a smarthost either post-10.mail or post-30.mail,
both of which are (I think) MMDF machines.

If a fix to EXIM is going to be slow in coming, would it be
possible to label a non-EXIM cluster that we could specify as
a smarthost, e.g. salt.mail.demon.net to correspond to both
post-10 and post-30?

-- 
Anti-spam address in use.  The address given will be valid
for a few weeks; thereafter, change the username to "c-mac"
when replying