Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 4 subscribers
  • Views 21156 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

Using gmail smtp for notifications fails

stegman

I have set up notifications with smtp.gmail.com as DNS host on the advanced tab

Port 587

TLS activated

Authentication activated

my Gmail address with password but notification does not work, this is part of my log

2016:03:03-12:51:00 4844 exim-out[31196]: 2016-03-03 12:51:00 End queue run: pid=31196

2016:03:03-12:51:07 4844 exim-out[30646]: 2016-03-03 12:51:07 1abRT8-0007Nt-0r deadmail.fw-notify.net [93.189.156.232]:25 Connection timed out

2016:03:03-12:51:07 4844 exim-out[30645]: 2016-03-03 12:51:07 1abRT8-0007Nt-0r == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (110): Connection timed out

2016:03:03-12:51:07 4844 exim-out[31250]: 2016-03-03 12:51:07 1aax1G-0002Wp-6r == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[31252]: 2016-03-03 12:51:07 1aaaXi-0002Rz-F7 == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[31254]: 2016-03-03 12:51:07 1abRCK-0006n1-1x == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[31256]: 2016-03-03 12:51:07 1aax1G-0002Wp-6s == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[31258]: 2016-03-03 12:51:07 1aaMPQ-0002sW-4O == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[31260]: 2016-03-03 12:51:07 1aaMNA-0002nt-4v == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[31262]: 2016-03-03 12:51:07 1abRUb-0007R1-0T == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[31264]: 2016-03-03 12:51:07 1aaaXi-0002Rz-F6 == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[31266]: 2016-03-03 12:51:07 1aaMNA-0002nt-4w == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:51:07 4844 exim-out[30640]: 2016-03-03 12:51:07 End queue run: pid=30640

2016:03:03-12:52:00 4844 exim-out[31307]: 2016-03-03 12:52:00 Start queue run: pid=31307

2016:03:03-12:52:00 4844 exim-out[31309]: 2016-03-03 12:52:00 1abQkN-0005qn-1Y == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31311]: 2016-03-03 12:52:00 1aaaXi-0002Rz-F6 == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31313]: 2016-03-03 12:52:00 1aax1G-0002Wp-6r == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31315]: 2016-03-03 12:52:00 1aaMNA-0002nt-4v == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31317]: 2016-03-03 12:52:00 1aaMPQ-0002sW-4O == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31319]: 2016-03-03 12:52:00 1aaaXi-0002Rz-F7 == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31321]: 2016-03-03 12:52:00 1abRCK-0006n1-1x == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31323]: 2016-03-03 12:52:00 1aax1G-0002Wp-6s == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31325]: 2016-03-03 12:52:00 1abRUb-0007R1-0T == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31327]: 2016-03-03 12:52:00 1abRT8-0007Nt-0r == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31329]: 2016-03-03 12:52:00 1ab5Z6-0003Ru-5p == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31331]: 2016-03-03 12:52:00 1aaMNA-0002nt-4w == xxx@gmail.com R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:52:00 4844 exim-out[31307]: 2016-03-03 12:52:00 End queue run: pid=31307

2016:03:03-12:53:00 4844 exim-out[31389]: 2016-03-03 12:53:00 Start queue run: pid=31389

2016:03:03-12:53:00 4844 exim-out[31391]: 2016-03-03 12:53:00 1abQkN-0005qn-1Y == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:53:00 4844 exim-out[31393]: 2016-03-03 12:53:00 1abRT8-0007Nt-0r == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:53:00 4844 exim-out[31395]: 2016-03-03 12:53:00 1abRUb-0007R1-0T == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

2016:03:03-12:53:50 4844 smtpd[4882]: MASTER[4882]: (Re-)loading configuration from Confd

2016:03:03-12:53:50 4844 smtpd[4882]: MASTER[4882]: QR globally disabled, status one set to 'disabled'

2016:03:03-12:53:50 4844 smtpd[4882]: MASTER[4882]: QR globally disabled, status two set to 'disabled'

2016:03:03-12:53:50 4844 exim-in[5138]: 2016-03-03 12:53:50 pid 5138: SIGHUP received: re-exec daemon

2016:03:03-12:53:50 4844 exim-in[5138]: 2016-03-03 12:53:50 exim 4.82_1-5b7a7c0-XX daemon started: pid=5138, no queue runs, listening for SMTP on port 25 (IPv4) port 587 (IPv4) and for SMTPS on port 465 (IPv4)

2016:03:03-12:54:00 4844 exim-out[31535]: 2016-03-03 12:54:00 Start queue run: pid=31535



This thread was automatically locked due to age.
Parents
  • 0

    stegman

    I can see you're pretty frustrated with this issue, understandably. I'm sure everyone here are contributors to the forums in one way or another...

    I found some info on one of the repeating errors which turn out not to be an error:

    stegman said:
    2016:03:03-12:53:00 4844 exim-out[31395]: 2016-03-03 12:53:00 1abRUb-0007R1-0T == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

    https://www.sophos.com/en-us/support/knowledgebase/120368.aspx

    But I take it that you are obviously not receiving the emails you are expecting? Is this still the case or have you heard back from Support on the matter? 

    Two interesting reads:
    https://forums.cpanel.net/threads/t-remote_smtp-defer-53-retry-time-not-reached-for-any-host.72383/
    http://livebook.in/2013/04/solved-exim-defer-53-retry-time-not-reached-for-any-host/

    This may, if anything, help you or forward it to the support team you are working with... 

    Please do let us know if you find a solution and what it is... [^o)] 

  • 0 in reply to AndrewSalm

    Hi Andrew,

    Thanks for your reply!

    Support has been active on the backend for a couple of days and today suddenly the mails are coming in again!

    The postfix service was not working and Sophos Support restarted the postfix service and everything started working normally.

    I have rebooted the UTM machine myself several times during my own troubleshooting actions, but it seems the manual restart by Sophos Support solved the issue.

    so I want to know how to restart the service myself for future troubleshooting.

  • 0 in reply to stegman

    Unfortunately I am not sure. 

    Sophos runs on a linux platform and depending on what distribution it is using could change the location of the service. Perhaps you can ask support who helped you to provide you this information for future reference. 

    Sorry I can't be of any further assistance here... If you do get it... share it for those that may run into the same problem 

  • 0 in reply to AndrewSalm

    Just heard from support;

    it would be in shell /var/mdw/scripts/postfix restart

    But just to mention restarting the postfix cause's other issue's as well so I would suggest not to use it often .

    Currently it works good after unticking 'Limit Notiofications' (management - notification - global tab)

  • 0 in reply to stegman
    Changing the hostname will stop notifications if the hostname consists of only numbers.
    I changed it back to 4844 and notifications stopped.
    Reboot UTM did not help.
    I restarted the postfix and got an  error about invalid hostname with all numbers.
    I changed it back to all letters and rebooted the UTM (because i was told that restarting the postfix to much could cause other problems)
    and the notifications started working again.
    This to inform that the use of only numbers (perhaps no numbers are allowed at all?) is not a valid hostname configuration.
    p.s. actually i did not rebooted the UTM but turned if off and on again.
    I am not sure a restart will do the same as off - on
    Today i was connected with VPN and rebooted the UTM and i could login again without reconnecting the VPN so i think it has not completely rebooted but only restarted some daemons/services?
Reply
  • 0 in reply to stegman
    Changing the hostname will stop notifications if the hostname consists of only numbers.
    I changed it back to 4844 and notifications stopped.
    Reboot UTM did not help.
    I restarted the postfix and got an  error about invalid hostname with all numbers.
    I changed it back to all letters and rebooted the UTM (because i was told that restarting the postfix to much could cause other problems)
    and the notifications started working again.
    This to inform that the use of only numbers (perhaps no numbers are allowed at all?) is not a valid hostname configuration.
    p.s. actually i did not rebooted the UTM but turned if off and on again.
    I am not sure a restart will do the same as off - on
    Today i was connected with VPN and rebooted the UTM and i could login again without reconnecting the VPN so i think it has not completely rebooted but only restarted some daemons/services?
Children
No Data
Unfiltered HTML