NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Email alert does not work @ RAIDiator 4.2.21
I've attempted to configure email alert to a couple of recipients, but I can't get it to work using the built-in, nor the gmail mail engine. The /var/log/exim/mainlog lists this after attempting to...
This evening I put a wire tap between my NAS and the router/firewall.
1) When using the internal mail engine, I can see (presumably) exim querying and resolving the recipients mail exchanger IPs, but no SMTP traffic is observed. The mail is kept under /var/spool/exim and according to logs it seems like exim is on regular basis (I believe I saw a cronjob entry for exim) trying to deliver the mail, but to no avail.
The exim log file becomes filled with messages similar to the ones I reported yesterday.
T=remote_smtp defer (113): No route to host
Frontview returns with a success message... :(
2) When using gmail I believe sendmail is used and now I can see some outgoing SMTP (after address resolving).
Regardless if I use default (with TLS) or custom (with/without TLS enabled) settings, TLS handshake takes place after the initial unencrypted SMTP handshake (EHLO -> At your service -> QUIT). I can't tell what takes place in the TLS part that follows, but a moderate number of encrypted bytes are sent back and forth (just as if a message is forwarded).
Connection made to 173.194.71.109 (one of the two IPv4 address behind smtp.gmail.com)
220 mx.google.com ESMTP somehash
EHLO localhost
250-mx.google.com at your service, [my.external.ip.address]
250-SIZE 35882577
250-8BITMIME
250-STARTTLS
250 ENHANCEDSTATUSCODES
QUIT
221 2.0.0 closing connection somehash
Connection is closed and then reestablished with 173.194.71.108 (the other IPv4 address behind smtp.gmail.com)
220 mx.google.com ESMTP somehash
EHLO localhost
250-mx.google.com at your service, [my.external.ip.address]
250-SIZE 35882577
250-8BITMIME
250-STARTTLS
250 ENHANCEDSTATUSCODES
STARTTLS
220 2.0.0 Ready to start TLS
A few TLS encrypted telegrams are now exchanged before the connection is closed.
Then a new connection is established (again) with 173.194.71.109 (the IP used in the first connection)
After some more TLS encrypted telegrams the connection is dropped.
Now Frontview returns with an error message "Failed to contact SMTP server."
What can be wrong?
Why is exim not able to route itself out of my box (ping can...)?
Why does the sendmail/TLS session fail even when gmail seem to "talk"?
/f
1) When using the internal mail engine, I can see (presumably) exim querying and resolving the recipients mail exchanger IPs, but no SMTP traffic is observed. The mail is kept under /var/spool/exim and according to logs it seems like exim is on regular basis (I believe I saw a cronjob entry for exim) trying to deliver the mail, but to no avail.
The exim log file becomes filled with messages similar to the ones I reported yesterday.
T=remote_smtp defer (113): No route to host
Frontview returns with a success message... :(
2) When using gmail I believe sendmail is used and now I can see some outgoing SMTP (after address resolving).
Regardless if I use default (with TLS) or custom (with/without TLS enabled) settings, TLS handshake takes place after the initial unencrypted SMTP handshake (EHLO -> At your service -> QUIT). I can't tell what takes place in the TLS part that follows, but a moderate number of encrypted bytes are sent back and forth (just as if a message is forwarded).
Connection made to 173.194.71.109 (one of the two IPv4 address behind smtp.gmail.com)
220 mx.google.com ESMTP somehash
EHLO localhost
250-mx.google.com at your service, [my.external.ip.address]
250-SIZE 35882577
250-8BITMIME
250-STARTTLS
250 ENHANCEDSTATUSCODES
QUIT
221 2.0.0 closing connection somehash
Connection is closed and then reestablished with 173.194.71.108 (the other IPv4 address behind smtp.gmail.com)
220 mx.google.com ESMTP somehash
EHLO localhost
250-mx.google.com at your service, [my.external.ip.address]
250-SIZE 35882577
250-8BITMIME
250-STARTTLS
250 ENHANCEDSTATUSCODES
STARTTLS
220 2.0.0 Ready to start TLS
A few TLS encrypted telegrams are now exchanged before the connection is closed.
Then a new connection is established (again) with 173.194.71.109 (the IP used in the first connection)
After some more TLS encrypted telegrams the connection is dropped.
Now Frontview returns with an error message "Failed to contact SMTP server."
What can be wrong?
Why is exim not able to route itself out of my box (ping can...)?
Why does the sendmail/TLS session fail even when gmail seem to "talk"?
/f
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
