On Sun, Jan 12, 2003 at 11:44:24PM +0900, Junjiro Okajima wrote: > > Henning Brauer: > > > and the other patch is control/qmqproutes. the feature is as you can > > > guess. > > > > hmmm there was a patch by Johan for qmail introducing control/mailroutes, I > > like that way better. > > qmqp doesnt need queue, file i/o. it is a big advantage.
stop right here, I was thinking qmtp again ;-) however, still a centralized control/mailroutes is the better way IMHO, instead of control/smtproutes, control/qmtproutes and control/qmqproutes... > the way making qmail-remote to speak qmtp still use queue. but it may > be a little more generic method. > > qmqp suits the inside of a large mail system, such as separated many > servers by their functionality. > - receving in-bound messages, queueing and relaying only(in-bound server) > - receiving from in-bound server, queuing and sending out-bound > messages(out-bound server) > - receiving from in-bound server, queuing and writing out to users > Maildir(mail drop server) > > by using qmqp, we can reduce the queue disk on in-bound server. > it is better to use qmqp between in-bound server and outbound/drop, > isnt it? yeah, though thw cluster code solves parts of that already. -- http://2suck.net/hhwl.html Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
