Hello Wietse, thanks for the clarification, I'd stick to a stable and supported method.
On the QSHAPE_REAME page you say that "try to keep the volume of local mail injection to a moderate level." Can you give me a rough estimation on "moderate level" for such an environment where the only source of messages is the local injection? I mean messages per second or similar. And is there a way to force the smtp utility to send multiple messages through an already established connection? Ie. instead of QUIT, continue with another MAIL FROM command (the recipient address is fixed and the same for all messages). Or the postfix smtp program is smart enough and does so whenever it's possible without instructing it? Albi On Wednesday, October 23, 2013 12:45 PM, Wietse Venema <wie...@porcupine.org> wrote: Kov?cs Albert: >I wouldn't use a regular smtp chat with the postfix smtpd daemon, >because I don't want to block the application until smtpd receives >the message. There is no need to "block the application". Use parallism. >My next idea is to just modify the application, and drop (with the >link() syscall) the message directly to postfix's queue directory, >and hopefully qmgr or something notices that "aha! I've got a new >message to deliver." In that case, you are on your own, with zero support. Translation: unlike the supported SMTP and sendmail iinterfaces that are maintained until eternity, your direct-to-queue submission method will break without any warning as Postfix evolves. Wietse
