-----BEGIN PGP SIGNED MESSAGE-----

Hello Peter,

Friday, September 28, 2001, 3:43:48 PM, you wrote:

GA>> - - I think vadddomain() doesn't need to take care of an
eventually
GA>>   existing the rcpthosts entry cause that one wouldn't hurt if
GA>> someone
GA>>   tries to add a domain, right?
> No but it would if you delete the domain sometime later and it _is_
> listed twice unless you're checking for _EVERY_ existence of
> 'domain' in rctphosts or morercpthosts.

- From what I've gathered while my vpopmail hacking, the update API
call
will remove all duplicate lines on its own anyway.

'echo "domain" >>>/var/qmail/control/rcpthosts && killall -HUP
qmail-send'
> or
'echo "domain" >>>/var/qmail/control/rcpthosts && svc -h qmail'
> The lesser only if you're running qmail via supervise scripts.
> Next thing would be to add a line to 'smtproutes' too.

Not necessarily. It's quite sufficient for qmail to have proper MX
records in the DNS.

> Nevertheless this kind of backup-MX ain't very usefull, if primary
> MX is down servers should hold mails in queue for several days. if
> them use the backup-MX and this backup-MX also only "streches" the
> queue a bit the win is only a few second/minutes (or even let it be
> hours) of time, unless you don't set queuetime on that backup-MX to
> a very high value (what I would not recommend).  

I think it should speed up mail delivery after an outage on the
primary as most mail is already on the secondary. Tell qmail to
iterate over its queue and your mails get delivered to the right
place. I for myself know pretty well that mails don't get lost that
easily if a mailserver is down for a few hours, but customers won't
ever understand that for some reason...

> In that case you vadddomain() on that local computer and need to
> tell the gateway to rcpthosts that domain too, but that's quite
> more simple done 'by hand' than via API-call :-)
> Easiest would be a

I certainly don't want to do any offline mailservers ;-).



Best regards,
 Gabriel
bÀ8o­

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5i

iQEVAwUBO7SBDMZa2WpymlDxAQHflQf+NgvcD3sxmjfhGwraCcyq1qdIVmAI4+Ot
ZOQ9VC+SkZ+OumdGTaABCPaBU4AD4BjLZ9nR36VA/oSou2tZxzPrbMMzqepngww+
/bov8p2+QZ231WIrtgYpViN/pW+Uj9iot358EYXZibf3PlDAK1ZKGoYMn7aMqdTf
zDccGiqSUn9gXJlYI5DSzqiKnNcu+N1lhUCT1U8VQgEXqvb5f3vCTiZziiyIvtv/
T0pclCIEC7vUN9dyULHrULw/IcU1c0T4r/qJkaOwY3kYG9W0unYXxB0SXo6JJ9CA
baJXkO0q5aZjULnXYcrptY45tUd0sOEq0WIl538v7YIRIXj3Muccsg==
=HAfp
-----END PGP SIGNATURE-----

Reply via email to