On Tue, Jan 05, 1999 at 05:03:21PM +0000, Stuart Ballard wrote:
> I am attempting to configure qmail to handle mail queueing for multiple
> domains, each of which will dial up with _dynamically assigned_ IP
> addresses. The servers themselves use exchange, so I can't rely on any
> features from them ;) (but they can send an ETRN if it helps).
> 
> I have a script written to monitor when they connect and disconnect, and
> keep track of who is connected to what IP at what time. I just need to
> get the mail to be delivered.
> 
> My initial thought was to trigger fetchmail, serialmail or maildir2smtp
> to send the mail from the appropriate user's maildir. But this is likely
> to have problems when the envelope information doesn't match the header
> information, and besides, why reinvent the wheel when qmail already has
> a mail queueing system designed for the purpose rather than cobbled
> together like mine would be.

I'm sorry, but I totally disagree with your conclusion.

You already monitor what "virtual domain server" is connected, and from
which IP?  Then it's trivial to trigger serialmail delivery to that
IP address.

Serialmail handles the envelope information so it's not mangled.

qmail does -not- have a queue'ing system designed for serial connections.

drop all the virtual domain's mail in a maildir.  when the domain connects,
trigger maildirsmtp to the IP of the connecting machine.
 
> Then I found the smtproutes file. "Great!" I thought, "I can just put
> the dynamically assigned IP address for each domain into smtproutes and
> send qmail-send a SIGALRM to trigger immediate delivery". Unfortunately,
> it appears qmail doesn't ever reload this file, and I'd need it to be
> reloaded on a regular basis, whenever a host connects or disconnects.

reloading smtproutes is horrible, when compared to triggering maildirsmtp.
 
> Is there a way to force qmail to reload this file? I'm also unsure how
> to tell qmail to "always hold mail for this domain in the queue" (the
> nearest I can find are concurrencylocal=0 and concurrencyremote=0, but
> again, they're never reloaded, which sounds to me like all mail would be
> held forever).

The files you're talking about get reloaded when qmail restarts.  So you'd
have to kill qmail-send, wait for it to stop, then restart it.

> Am I totally barking up the wrong tree here?

Yup.
 
-- 
John White
[EMAIL PROTECTED]
PGP Public Key: http://www.triceratops.com/john/public-key.pgp

Reply via email to