Hi,
I was digging around on the qmail web-page when I came across the
announcement of Bruce Guenter's mini-qmail implementation "nullmailer"
which is described as having "...a queue for more reliablity".
What is meant by "more reliable" in this example? Is the standard
mini-qmail setup "unreliable"?
Our incoming mail uses the following setup:
incoming +---------+ +-----------+
smtp | bastion | qmqp | internal |
--------> | host | ------> | mail host |
+---------+ +-----------+
mini-qmail full qmail
( mail received ( mail received
by qmail-smtpd ) by qmail-qmqpd )
>From reading the qmqpd documentation, this process should be fail-safe,
ie the remote host making the SMTP connection only gets the "all clear"
when the mail has been successfully delivered into the remote queue.
Am I missing something, or is there a potential blackhole somewhere in
this setup that a queue on the bastion host would prevent?
R.
PS. I *think* I've got my news2mail gateway working properly now, ie
the header should now be correct and not contain any "internal"
addresses. Please let me know if you think something is still wrong.
One problem I still have is filtering out Cancel messages. Currently,
if I post to my internal newsgroup and then cancel the message, both the
original message and the cancel message are sent back to the list.
Simple workaround: don't cancel any messages! However, I'd prefer
something a little more fool proof. Is there any program that looks in
the headers for a specified field, ie a bit like "iftocc" but for a
specific header? In this case, I could look out for either:
Subject: cancel ...
or
Control: cancel ...
It would probably not be a bad idea to consign all control messages to
the bit bucket; any suggestions as to how?
--
Two rules to success in life:
1. Don't tell people everything you know.
-- Sassan Tat
