This sendmail + diald thing has caused me many hours of headache.
I pretty much nailed it down to my liking by running named and
flushing the cache when diald disconnects. But then I still have
the choice between sendmail causing a dial out every time a
message is sent, or:
On Wed, 7 Jul 1999, Gary S. Mackay wrote:
> The only drawback is that while online, anything you send will
> stack up in the queue until you issue another sendmail -q
> command.
This would be rather annoying.
> I'm playing around with some scripts now that copy two different
> copies of sendmail.cf back and forth. One has deliverymode set
> to background so mail will go out immediately while online, and
> one with deferred so it will queue up while offline. Works OK,
> but once in awhile sendmail just disappears. ??
That sounds rather scary ... I'd hate to have to mess with
sendmail that much.
I just had another idea: if diald was set up to ignore packets
which originated from sendmail and were destined to named, then
sendmail would never bring the link up and would work fine when
the link was up. (As long as sendmail deferred delivery when the
name lookup fails.) Running the queue after diald had brought the
link up would work fine too (and would be the preferred way to run
the queue, since sendmail -q at the command line would just defer
again when the name lookups failed). No other modifiications to
the sendmail or diald setups would be required.
It can't be that simple, can it?
Ed
--
Ed Doolittle <mailto:[EMAIL PROTECTED]>
"Everything we do, we do for a reason." -- Peter O'Chiese
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
