On Mon, 27 Mar 2000, Marilyn Davis wrote:
> Well, I can tell you what happened to me recently. We use MMDF here,
> which certainly colors the picture a little. What was happening here
> was that MMDF was verifying the validity of the whole mailing list
> before returning from the Submit call.
Exim will not do that, if you are just passing over the name of a list
that Exim is going to expand. All it will check is the list name. (And
indeed, it will only do that if Majordomo is submitting using SMTP.) But
if Majordomo is submitting a large number of addresses, then each one
gets verified as it is given in the SMTP dialogue (if receiver_verify is
set).
You could try turning on log_arguments for a short while to determine
with what arguments Exim is being called by MD - i.e. if it *is* using
SMTP or not.
> The thing calling the Submit
> would time out and close, but the Submit itself would still be running
I can see how that might happen if MD works in a certain way, but I
don't know how MD actually works.
> The solution for us was MMDF-specific. We used a different channel
> for submission and delivery, one which deliberately doesn't verify the
> addresses before accepting a job.
If MajorDomo *is* using SMTP submission for large lists of addresses,
then you can make use of receiver_verify_hosts to except your own host
from this verification.
> There have been many reports from Linux users complaining about
> duplicate mail. The problem seems to be that flock() under Linux is
> broken.
Exim does not use flock(). It uses fcntl() for locking (which is
compatible with lockf(), not flock()).
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
