[EMAIL PROTECTED] wrote:
One example:
The sender is one user of virtual host. The recipient is yahoo.ca.
When smtp-forward plugin is used to forward to another smtp server in
local network, Qpsmtp got error:
24825 Plugin queue::smtp_2dforward, hook queue returned DECLINED, Unable
to queue message ()
24825 451 Unable to queue message ()
Debug information from smtp-forward plugin
Net::SMTP=GLOB(0x84af338)<<< 454 <[EMAIL PROTECTED]>: Recipient address
rejected: Relay access denied
This isn't a qpsmtpd problem /per se/. The internal SMTP server is
denying the external SMTP server the ability to relay to a completely
external domain (yahoo.ca).
If you want to do this (and I'm still not sure I understand why the
external server doesn't just do the external relaying on its own), you
will have to rewrite the smtp-forward to use SMTP AUTH (using the stored
information from the original AUTH request). Alternatively, you can
just set the external SMTP server as being in the internal server's
relay list. I'm going to assume /a priori/ that the latter method is
inherently more likely to be insecure, so I can't recommend it.
If I was doing this, I would use the remote SMTP authentication to
verify the users, then just have the external server do the external
relay (there is no benefit I can see to an additional bounce).
Actually, what I am doing is that my two external MX hosts only handle
inbound mail, and don't support AUTH at all. Then the one server that
acts both as IMAP host and SMTP outbound supports AUTH/TLS. That way, I
have clear boundaries between inbound and outbound mail.
HTH
John
