On 1/18/06, Dale <[EMAIL PROTECTED]> wrote: > On Wednesday 18 January 2006 08:22, Richard Fish wrote: > > traceroute -n mail.exceedtech.net > > Usually traceroute does not work. They block it somewhere and I get a but > ****** stuff. Anyway, this one worked, for once.
Tell them to cut that sh*t out. Traceroute is far too useful of a debugging tool to be blocked by your ISP. Ok, so they don't want ICMP flooding...there are better ways of recognizing and defending against this... > [EMAIL PROTECTED] / # traceroute -n mail.exceedtech.net > traceroute to mail.exceedtech.net (65.116.46.23), 30 hops max, 40 byte packets > 1 63.152.9.43 121.969 ms 120.002 ms 123.893 ms > 2 63.152.43.189 123.963 ms 119.943 ms 119.958 ms > 3 63.152.126.13 156.027 ms 159.922 ms 155.967 ms > 4 205.171.31.9 155.920 ms 156.014 ms 159.886 ms > 5 205.171.8.146 175.994 ms 179.910 ms 176.014 ms > 6 205.171.21.62 179.964 ms 175.912 ms 179.924 ms This is crazy...this is all on QWest's network. Was this from your home, or from your brother's house? Because it looks like you are still connecting through someone else's network! Maybe your first question to ask is whether exceedtech has their own access numbers, or whether they lease them from other companies. That is the only reason I can think of you would have a level-3 address in the morning, and a qwest address in the evening! > That help any? That's a lot of hops for me to be connected to their server > huh? The number of hops doesn't bother me...but the fact that you don't start out on an exceed.net address does. Here is what I get on Cox: carcharias rjf # traceroute smtp.west.cox.net traceroute to smtp.west.cox.net (68.6.19.4), 30 hops max, 38 byte packets 1 192.168.2.1 (192.168.2.1) 1.151 ms 1.092 ms 1.087 ms 2 10.117.128.1 (10.117.128.1) 9.290 ms 8.108 ms 11.160 ms 3 ip68-2-6-93.ph.ph.cox.net (68.2.6.93) 33.443 ms 9.608 ms 15.850 ms 4 68.2.13.94 (68.2.13.94) 15.123 ms 10.373 ms 16.376 ms 5 68.2.13.9 (68.2.13.9) 8.174 ms 20.969 ms 15.987 ms 6 68.2.13.5 (68.2.13.5) 12.353 ms 11.337 ms 16.227 ms 7 * 68.2.13.1 (68.2.13.1) 12.494 ms 10.503 ms 8 68.2.14.65 (68.2.14.65) 43.162 ms 11.696 ms 14.463 ms 9 chndbbrc01-pos0103.rd.ph.cox.net (68.1.0.240) 9.944 ms 11.977 ms chndbbrc01-pos0101.rd.ph.cox.net (68.1.0.164) 17.020 ms 10 fed1bbrc02-pos0102.rd.sd.cox.net (68.1.0.167) 20.230 ms 19.743 ms 20.047 ms 11 fed1dsrj02-so000.rd.sd.cox.net (68.1.0.207) 20.614 ms 18.560 ms 20.005 ms 12 68.6.8.198 (68.6.8.198) 29.634 ms 18.571 ms 19.673 ms 13 172.18.176.1 (172.18.176.1) 25.442 ms 17.996 ms 20.621 ms 14 172.18.176.1 (172.18.176.1) 24.843 ms 18.762 ms 18.625 ms 15 172.18.176.1 (172.18.176.1) 21.634 ms 17.584 ms 21.471 ms 16 172.18.176.1 (172.18.176.1) 23.933 ms 17.406 ms 19.978 ms 17 172.18.176.1 (172.18.176.1) 21.458 ms 21.400 ms 18.633 ms 18 172.18.176.1 (172.18.176.1) 27.909 ms 19.177 ms 21.069 ms .... Ok, ignore the crazy routing loop at the end. The point is that after my firewall/gateway (192.168.2.1), and the modem (10.117.128.1), I am on cox's network. > I see what you are saying though. It would be like if I cnnected with the > modem to my brother's Bell South account and tried to send exceedtech email. > Bell South may not want to handle what is exceedtech's data, basically. Close...it would be more accurate to say that exceedtech doesn't want bellsouth customers spoofing addresses and using exceedtech's mail server. > Maybe I can explain this to them in the morning. Maybe they will fix this > thing already. I'm going nuts here. Well, I think I can at least explain why KMail works and Mozilla fails. From the traces you sent me, kmail performs the following exchange: ~/Desktop > grep SMTP ethereal-kmail Response: 220 mirus.exceedtech.net ESMTP Sendmail 8.12.8/8.12.8; Wed, 18 Jan 2006 Command: EHLO 0-1pool99-184.nas1.columbus1.ms.us.da.qwest.net Response: 250-mirus.exceedtech.net Hello 0-1pool99-184.nas1.columbus1.ms.us.da.qwest.net [65.136.99.184], pleased to meet you Command: MAIL FROM:<[EMAIL PROTECTED]> SIZE=363 Response: 250 2.1.0 <[EMAIL PROTECTED]>... Sender ok Message Body Response: 250 2.0.0 k0J39ewT002685 Message accepted for delivery Command: QUIT Response: 221 2.0.0 mirus.exceedtech.net closing connection While mozilla does: Response: 220 mirus.exceedtech.net ESMTP Sendmail 8.12.8/8.12.8; Wed, 18 Jan 2006 00:39:11 -0600\r\n Command: EHLO [4.253.131.84] Response: 250-mirus.exceedtech.net Hello dialup-4.253.131.84.Dial1.Houston1.Level3.net [4.253.131.84], pleased to meet you Command: MAIL FROM:<[EMAIL PROTECTED]> SIZE=382 Response: 250 2.1.0 <[EMAIL PROTECTED]>... Sender ok Command: RCPT TO:<[EMAIL PROTECTED]> Response: 550 5.7.1 <[EMAIL PROTECTED]>... Relaying denied Notice that mozilla actuall tells the mail server who you are sending mail to, while kmail does not, and it is that command that actually triggers the "Relaying denied". I'm not sure what you can do about this...it isn't wrong to send the RCPT TO command, so it doesn't seem to be a bug in mozilla. Possibly if you give this information (and maybe the ethereal traces) to exceedtech, they may be able to modify their mail server's configuration to compensate. Or you could try thunderbird... -Richard -- gentoo-user@gentoo.org mailing list
