marka11111
join:2000-12-18
Pittsburgh, PA
| 7008ABR Fail to send alert mail
This router suddenly has gotten flaky. This is from the log,
any ideas?
12/26/2007 10:05:08 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:04:53 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:04:37 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:04:22 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:04:06 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:03:33 **TCP Null Scan** 70.20.101.176, 37232->> 8.15.7.117, 25 (from PPPoE Outbound)
12/26/2007 10:03:26 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:03:19 SMTP fail message>250 Ok..
12/26/2007 10:02:53 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:02:53 SMTP fail message>250 Ok..
12/26/2007 10:02:42 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:02:42 SMTP fail message>250 Ok..
12/26/2007 10:02:32 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:02:32 SMTP fail message>250 Ok..
12/26/2007 10:02:21 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:02:21 SMTP fail message>250 Ok..
12/26/2007 10:02:11 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:02:11 SMTP fail message>250 Ok..
12/26/2007 10:02:00 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:02:00 SMTP fail message>250 Ok..
12/26/2007 10:01:50 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:01:50 SMTP fail message>250 Ok..
12/26/2007 10:01:40 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:01:40 SMTP fail message>250 Ok..
12/26/2007 10:01:30 SMTP> Fail to send alert mail. Delay 10 seconds.
12/26/2007 10:01:29 SMTP fail message>250 Ok.. |
|
Duncan
@aol.com
| Hi there, just come across this thread while googling...
I have the exact same issue...blkin router is flaky so checked the logs and get 'SMTP> Fail to send alert mail. Delay 10 seconds.' repeated over and over again. I am running Vista, hope someone can shed some light?
Duncan |
|
bambzled
@verizon.net | reply to marka11111
I've googled the IP 8.15.7.117, 63.251.179.13 and 66.150.2.134 and everybodys machines that want to go there are goofing up. So why does my machine want to ping these
addresses and why should they even be in lmhost? I smell a breach. |
|
inmuck
Idiot In The East
Premium,MVM
join:2003-01-29
Raleigh, NC | reply to marka11111
I smell that too.. and all cases seems to be with Verizon DSL or FIOS in NE USA. |
|
bambzld
@verizon.net
| reply to marka11111
Could this be SMTP from your firewall log? Perhaps it is on but nowhere configured to send it. Not listening to traps.
The other IPs i listed are Windows networking, broadcasting workgroup names to the internet trying to find old dns servers to resolve machines and shares. It's about my laptop that isn't always there so my 98 machine is lonely. Since they don't resolve in DNS anymore Verizon FIOS (and DSL)just redirects to their Google ads page (whatever). Filter outgoing netbios ports to put a lid on that (maybe) but IPv6 from my XP machine and Verizon Westell 6100 wants to talk.
I did IPv6 /uninstall to speed things up because it was banging all over the network. I sure don't need IPv6 on my LAN. |
|
bambzld
@verizon.net
| reply to marka11111
Also, I was seeing too much incoming from Verizon WAN to WAN (the 70.xx.xx.xx) administrative traffic. I found that setting my firewall in the Westell to HI stopped that without hurting my connection. My Linksys AP on the LAN quit locking up too. |
|
