OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: ETRN too fast!
From: Alain Thivillon (Alain.Thivillonhsc.fr)
Date: Tue Sep 26 2000 - 12:43:48 CDT

Wietse Venema <wietseporcupine.org> écrivait (wrote) :

> There is no guarantee for how long it will take to deliver queued
> up mail. That depends on how busy the mail system is, and obviously,
> that also depends on what mail is queued up for that client.

        This depends also in standard setup how many different domains
you have waiting in the queue. ETRN flush all queue, so if you have a
high number of domains, all smtp daemons can be used before flusing
of desired domain.

        For this case i use a special transport in master.cf and in
transport table for each ETRN-ed domain, and thus when this domain
issues ETRN, you can be sure that some postfix smtp clients will be
available. OK, this is unmanageable with more than a few domains.

 ==== master.cf ====
smtpyoko unix - - y - 10 smtp
 
 ==== /etc/postfix/transport =====
yoko.hsc.fr smtpyoko:[yoko.hsc.fr]

        Maybe this method can be a incremental step to full ETRN support
in postfix : wake up only transports corresponding to ETRN domain (i
dont't know if is's easier to implement, just an idea :).