On 3/30/2010 4:08 PM, Matt Sergeant wrote:
On Tue, 30 Mar 2010, Charlie Brady wrote:
On Thu, 25 Mar 2010, Jason Mills wrote:
I wrote this plugin to help me with my local debugging.
Basically a heavily modified version of smtp-foward.
I'd recommend you search the archives and find some earlier comments by me
about smtp-forward. It really should be rewritten to hook into more than just
the queue hook, and pass sender and recipient addresses to the backend as
they are provided by the connecting client, and relay responses back to the
client.
I think some people might not want that, as they want to reduce the load
on their main SMTP server... I agree it should be an option though.
Perhaps we need queue/smtp-passthru.
It's a fairly complex thing to do in a single plugin in a way
sufficiently flexible for a variety of setups. For example, how do you
do your RCPT TO lookups? Call forwards? Flat files? LDAP? ActiveX?
Async complexities. Eep!
I recommend, instead, strong warnings in SMTP forwarding that you should
have additional plugins to do your RCPT TO checks.
In other words, indicate that a set of building block plugins are needed
to do forwarding "correctly". Don't try to bundle the whole thing
together, otherwise, the forwarder plugin isn't going to be as well used
as it could.
Yes, you can have the forwarder relay the backend's rejection messages
to the sender, but sending mail servers are going to not interpret, say,
RCPT TO failures correctly, after they sent the DATA.
