David Beveridge wrote:
On Tuesday, Matt Sergeant wrote
On 28 Nov 2005, at 18:03, David Beveridge wrote:
No, the external postfix process opens up a real time
connection to qpsmtpd.
So when you are talking to port 25 (postfix) it is
proxying it through to qpsmtpd,
Kind of like how http requests are proxied through squid.
That is why 550 errors from qpsmtpd end up back at the
original sender.
I'm confused by what this gains you though. Why not just
qpsmtpd->postfix?
SMTP AUTH
STARTTLS
MySQL based Client/Sender/Recipient Access Rules
Sender/Recipient Address Verification
dave
qpsmtpd's plugins are not able to operate to their full
potential, for example check_earlytalker is not functioning
in your system, is it? I guess blacklisting plugins and header
checks could be done without handling the connection, but
not protocol checks--"MAIL before RCPT", check_earlytalker,
things like that.
qpsmtpd has smtp auth, starttls. By "sender/recipient
address verification", you may mean several things.
auth did sender verification, and then if you want to
check later on to see if the sender is the same as auth
sender i.e. login name, we can discuss that(just discussed
that a few days ago. I have a simple plugin to prevent
sharing of login names--login must be sender address).
You may mean de-aliasing and forwarding and cc/bcc/wiretap,
which would be accomplished by a lookup of the recipient
and then depending on the lookup maybe change the
recipient either in rcpt or queue hook plugin.
Then wouldn't any remaining "access rules" be enforced by
using postfix AFTER qpsmtpd, or do you mean user prefs for
content filtering, as well as access rules? If you mean custom
user prefs, you might have some hacking to do in a plugin.
-Bob
