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

Relay works, mail from XG fails?

17.5.5 MR-5,  MTA mode with smarthost and host based relay.

 

Mail logs show all relayed mail is delivered just fine, but mail from the XG itself bounces. Hovering over the "bounced" in the mail logs shows: R=smart_host_route, T=smarthost_smtp defer (-42): authentication required but authentication attempt(s) failed.

 

This used to work just fine, as I would get daily reports from the XG.  I believe a firmware update caused this, but I need to do some digging to confirm.

 

I'm by no means an expert in MTA or mail relays, but shouldn't the XG smtp server use the exact same mechanism to send both internally generated mail and relayed mail? This has me utterly confused and I have no clue where to even begin looking.



This thread was automatically locked due to age.
  • So, watching the smtpd_main.log on the XG, I see these differences between what works (relay) and what doesn't (local)

     

    Relay Local
    22464 changed uid/gid: remote delivery to ****@********.net with transport=smarthost_smtp
    22464   uid=0 gid=0 pid=22464
    22464   auxiliary group list: <none>
    22464 set_process_info: 22464 delivering 4atc6Z-9qL0As-r7 using smarthost_smtp
    22464 T: smarthost_smtp: for ****@********.net
    22464 smarthost_smtp transport entered
    23030 changed uid/gid: remote delivery to ****@********.net with transport=smarthost_smtp
    23030   uid=0 gid=0 pid=23030
    23030   auxiliary group list: <none>
    23030 set_process_info: 23030 delivering pfM4HI-bsQ6Bp-7U using smarthost_smtp
    23030 T: smarthost_smtp: for ****@********.net
    23030 smarthost_smtp transport entered

    .... [lots of other stuff here] ....

    ... [lots of other stuff here] ...
    22464 173.194.204.108 in hosts_require_auth? yes (matched "*")
    22464 scanning authentication mechanisms
    22464   SMTP>> AUTH PLAIN ********************************************
    22464 cmd buf flush 57 bytes
    22464 tls_write(0xff7cea28, 57)
    22464 SSL_write(SSL, 0xff7cea28, 57)
    22464 outbytes=57 error=0
    22464 Calling SSL_read(0x9465650, 0xff7cda28, 4096)
    22464 read response data: size=20
    22464   SMTP<< 235 2.7.0 Accepted
    22464 server_plain authenticator yielded 0
    23030 173.194.206.109 in hosts_require_auth? yes (matched "*")
    23030 scanning authentication mechanisms
    23030   SMTP>> AUTH PLAIN ****
    23030 cmd buf flush 17 bytes
    23030 tls_write(0xffdfaaf8, 17)
    23030 SSL_write(SSL, 0xffdfaaf8, 17)
    23030 outbytes=17 error=0
    23030 Calling SSL_read(0x880d650, 0xffdf9af8, 4096)
    23030 read response data: size=61
    23030   SMTP<< 501 5.5.2 Cannot Decode response t80sm3082107qka.87 - gsmtp
    23030 server_plain authenticator yielded 2

     

    It looks like mail generated locally on the XG is using some unknown password value for smarthost authentication. Why would it be doing this and how can I get it to stop?

  • This sounds like an old Bug in V17.5

    Do you use MR5? 

    Could be still an open Bug, but i am not quite sure.

    I would expect MR6 come out soon - So there are other fixes. Maybe this will fix your issue. 

  • Yes, running MR5.

    Is there a list of fixes that will be addressed in MR6?

     

    Thanks,

    -GP