[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Zmailer 2.99.27 & Gigo/2
> I've been having a number of problems here ever since I replaced sendmail
> with zmailer 2.99.27. I'm running Red Hat Linux 2.1 with a 1.2.13
> kernel. The problems are as follows:
I have rearranged some questions -- for all of them I don't
have answers, though. Oh yes, "zmail" is rather recent
mail-user-client program, "ZMailer" is the mailer.
> 4) Despite the fact I configured Zmailer to use a single router task, it
> seems to be starting multiple routers. And worse, they seem to stay
> around for a very long time.
NROUTERS=4 ? (at /etc/zmailer.conf, if you use default location)
They are SERVERS, not something that is spawned up for every
message, like the sendmail does. They stay around and run
for weeks / months. (Restart recommended, if you do changes
at the mailer related databases -- "zmailer router" -command.)
> 3) Zmail seems to be having trouble sending messages to some systems. Even
> though sendmail was able to send them without difficulty. The messages
> are getting stuck in the queue, as zmail tries repeatedly to send them
> until they eventually reach their expiration date.
Of "zmail" I can't say... but do check where your ZMailer logs go.
Those do contain valuable trace information. ( $LOGDIR/smtp for
example -- if configured at $MAILSHARE/scheduler.conf )
Send the log to me ( firstname.lastname@example.org ) if you need help at
Also you may try sending mail with a verbose trace:
linux> Mail -v email@example.com
( Then wait, and watch... a xterm with long scroll-back buffer
warmly suggested. )
> 1) When sending mail via smtp to Gigo/2 on the OS2 machine, the message
> intermittently gets sent 2 or more times. And worse yet, if one of
> the recipients is the local zmail machine, it will sometimes send them
> over, and over again!
What do the "Received:" -headers tell about the movement of
those messages ? zmailer->gigi->zmailer->gigo->zmailer ??
I get a creepy feeling that the Gigo/2 does look at the message
headers for addresses, where it should NEVER do such!
The address routeing decissions are to be made with transport
envelope addresses, and only with those.
( Just yesterday I gave a lecture about email technology, and
there I said that it is a sign of poor user-agent design
that mailers need to look at the message headers for
recipient addresses. Message submission from user-agent
should give recipient information separate from the message
headers; like sendmail (and ZMailer compability mode) does:
/usr/lib/sendmail recipient1 recipient2 recipient3 ...
<message headers in stdinput>
<message body in stdinput>
That way the recipient addresses need not have anything to do
with the apparent headers... )
> 2) Worse yet, it seems when messages are arriving from multiple sources
> the TO: headers are getting switched. i.e. messages sent to person-a
> get sent to person-b, and worst yet messages sent to list-a are getting
> sent to list-b. Or from person-a to list-b, etc... This is a REAL
> big concern.
Multiple sources into gigo ? Or into ZMailer ?
(That is, simultaneous incoming SMTP sessions ? Somehow I can
be confident that Linux ZMailer is not in trouble with it :-) )
> Anyway, I'm hoping someone on either of the lists this message is
> addressed to may have some idea what is causing these problems!
/Matti Aarnio <firstname.lastname@example.org> <email@example.com>