Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 27 subscribers
  • Views 8698 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

does the mta relay have smtp sasl support for upstream rely?

CyberA

Hi,

I recently updated to XG 17-GA and attempting to replace an old mta server that uses SASL authentication with TLS that relays internal mail to an upstream mx server. However I've tried various config options (which seem to be peppered all over the place) and can't seem to get the MTA to rely upstream.

Mail gets queued then fails and I don't see a connection attempt to the upstream server on TCP port 587. From the logs I see connection attempt to port 25 (which is not what I configured) followed by Response: 502 Command not implemented. My goal is to have the XG act as an MTA relay to send email from internal networks to the upstream mx.

Does XG 17 support this configuration?

Thanks.



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to FloSupport

    Thanks for the KB articles, I tried these earlier but I can't get emails to send using the Smarthost settings. For instance the XG MTA never uses port 587 as I've defined it. The XG is accepting my email from LAN but they don't get sent to the upstream mx using the Smarthost settings.This is the problem and I'm wondering if its related to SASL, a misconfiguration or some bug.

    I just want the XG to act as a relayhost sending my mail to the next-hop as defined by the Smarthost, internally all email coming from lan would be accepted on the XG over port 25 anonymously <-- this works, and then send those mails upstream to the relayhost <-- this doesn't work.