Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Tue Aug 24, 2010 22:43 Post subject:
I just tried the straight forward approach and used my ISP SMTP server. Nothing received in ether the sender box as in an error or the receivers box. Nothing in the log.
Dark Shadow, when you try just this (adapt it for yourself), do you get any response at all? When it's working, you should see several lines of SMTP conversation. At one location where it's working, that's what I see. In the one where it's not, I get no response at all. Yet, the procedure at the KB article below works fine.
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Tue Aug 24, 2010 22:56 Post subject:
rseiler wrote:
Dark Shadow, when you try just this (adapt it for yourself), do you get any response at all? When it's working, you should see several lines of SMTP conversation. At one location where it's working, that's what I see. In the one where it's not, I get no response at all. Yet, the procedure at the KB article below works fine.
I am not running a smtp server my isp is, therefor the KB article is of no consequence.
However it looks like it's working on the router side, there's just a setting in the code, I need to get right.
EDIT: Explanation of flags
-S = smtp server address
-f = from email address
-u = username for the smtp account
-p = password for smtp account
-s = email subject
-d = senders domain
-F = "From" name (as opposed to address)
And I figure that the email at the end of the script is the destination email addy but has no flags. _________________ Peacock Thread-FAQ -- dd-wrt Wiki
1) -d seems undocumented and unnecessary [Update: it may be undocumented, but it is necessary]. The only place I've seen it meaning 'domain' is in the link in the top post.
2) sendmail either always works or always doesn't for no apparent reason. It likes Comcast in some places but not others. It also isn't on speaking terms with Exchange 2003's virtual SMTP server, which internally anyway, is ready and waiting for all comers on port 25--except for sendmail. When it doesn't work, there's no output from sendmail whatsoever. When it does work, it's chatty.
3) There doesn't seem to be a way to send on alternate ports, at least via a switch.
4) If you want to send to multiple recipients, separate them by spaces.
Last edited by rseiler on Wed Aug 25, 2010 4:33; edited 1 time in total
I meant the previous example (only changing the port) as exclusive to comcast.net as it does not require SSL encryption. It might help rseiler.
With busybox sendmail, the SSL method is discussed here. However, that requires openssl. You might be better off with ssmtp or another MTA if you go as far as installing additional software.
EDIT: I am starting to think this would be possible if you have a mail server on another machine (that forwards mail to gmail via SMTP) with which you can create a SSH tunnel to from DD-WRT.
You're right, of course, if you leave out the -d you get "invalid domain name." This has been a long day, and when I was testing before I had thought I excluded it. Apparently not. Puzzling that something important seems not to exist though.
At the location I really wanted to get reporting working, I did, by using the DSL provider's SMTP instead of the one in the office (which is Exchange's SMTP, which sendmail dislikes as much as Comcast). It works great.
The port and credentials didn't help with Comcast, and that stands to reason since I'm not getting anything back from sendmail at any time with Comcast. Even if 25 was blocked, which I've proved it isn't, you'd still get back some indication that something at all has happened. So it's some larger puzzle, perhaps something with this version of DD-WRT, though sendmail is part of Busybox, and I don't think that's been updated in ages (on DD-WRT, at least).
Comcast (both on ports 25 and 587) works if you use 76.96.30.117 instead of smtp.comcast.net. Exchange's SMTP works if you use the server's LAN IP. Some sort of selective DNS issue on the router, apparently.
For anyone else still having problems (no options besides SSL-required SMTP), I would recommend setting up a local-only mail server (if you have linux server box available).
Just make sure to either not expose any ports outside your LAN or keep the restrictions on relaying to only allowed hosts so that you don't inadvertently become a SPAM relay.
Joined: 07 Jun 2006 Posts: 1476 Location: New York, USA
Posted: Wed Aug 25, 2010 14:04 Post subject:
tc23emp wrote:
For anyone else still having problems (no options besides SSL-required SMTP), I would recommend setting up a local-only mail server (if you have linux server box available).
Just make sure to either not expose any ports outside your LAN or keep the restrictions on relaying to only allowed hosts so that you don't inadvertently become a SPAM relay.
Seems like a much simpler method for this type of report - and much more detailed reports (by IP, protocol, etc) would be to use a Netflow tool such as ManageEngine and simply schedule reports....
