whatever8
-Mike-
Premium
join:2003-10-01
Canada
clubs:
| reply to Doci
Re: E-mail taking a dump?
said by Doci  :Could somebody give this guy a run through the cluefield? Current email issues have nothing to do with MSN. Nexxia MXs(SMTPs) are taking a dump, just like bbuchanan reiterated. I'm not sure why you feel the need to be rude in your comments. Nevertheless, we are both correct. Yes, the nexxia servers have taken a dump. And yes, there ARE msn email issues on the go. BOTH are causing numerous headaches at this time.
--
i\am/canadian |
|
Doci
Toothless Fairy
join:2003-02-01 | reply to whatever8
Could somebody give this guy a run through the cluefield?
Current email issues have nothing to do with MSN. Nexxia MXs(SMTPs) are taking a dump, just like bbuchanan reiterated.
--
My freedom is a debt to Hitler. |
|
whatever8
-Mike-
Premium
join:2003-10-01
Canada
clubs:
| reply to Doci
said by Doci :Are you that naive? So, if the front line ones' are dead, why does it matter that MSN ones are too? Again, there are two issues at hand here affecting email. I'm not sure what it has to do with naivete.
--
i\am/canadian |
|
Doci
Toothless Fairy
join:2003-02-01
 ·Bell Sympatico
| reply to whatever8
said by whatever8 :Actually, there are issues currently on both platform servers. There is no blame-shifting undergo. Are you that naive? Go read what we've said so for, email is accepted by Nexxia SMTPs, then it is forwarded to MSN ones. So, if the front line ones' are dead, why does it matter that MSN ones are too?
--
My freedom is a debt to Hitler. |
|
whatever8
-Mike-
Premium
join:2003-10-01
Canada
clubs:
| reply to Doci
said by Doci :There's your problem right there. Their SMTP answering for their domain are royally fucked and they're shifting the blame over to MSN. How convenient of them. Actually, there are issues currently on both platform servers.
There is no blame-shifting undergo.
--
i\am/canadian |
|
noneoneinparticular
@simianscience.com
| reply to Doci
They are hosed (at least from the application layer) from inside and outside their network.
> telnet toip1.bellnexxia.net smtp
Trying 209.226.175.84...
telnet: Unable to connect to remote host: Connection refused
> telnet toip2.bellnexxia.net smtp
Trying 209.226.175.85...
telnet: Unable to connect to remote host: Connection refused
> telnet toip3.bellnexxia.net smtp
Trying 209.226.175.86...
telnet: Unable to connect to remote host: Connection refused
> telnet toip4.bellnexxia.net smtp
Trying 209.226.175.87...
Connected to toip4.bellnexxia.net.
Escape character is '^]'.
421 #4.4.5 Too many connections to this host.
Connection closed by foreign host.
> telnet toip5.bellnexxia.net smtp
Trying 209.226.175.88...
telnet: Unable to connect to remote host: Connection timed out
> telnet toip6.bellnexxia.net smtp
Trying 209.226.175.174...
telnet: Unable to connect to remote host: Connection refused
> telnet toip7.bellnexxia.net smtp
Trying 209.226.175.175...
telnet: Unable to connect to remote host: Connection refused
>
> traceroute to 209.226.175.175 (209.226.175.175), 30 hops max, 40 byte packets
1 cn-rte2-artsnet.uwaterloo.ca (129.97.42.1) 1.275 ms 1.210 ms 1.223 ms
2 cn-rtext.uwaterloo.ca (129.97.10.3) 0.698 ms 0.336 ms 0.353 ms
3 f0-16.na02.b011027-0.yyz01.atlas.cogentco.com (38.112.15.77) 4.724 ms 5.050 ms 5.090 ms
4 g2-0-2.core01.yyz01.atlas.cogentco.com (38.112.35.21) 6.014 ms 5.511 ms 5.342 ms
5 p13-0.core02.ord01.atlas.cogentco.com (66.28.4.213) 18.685 ms 18.991 ms 19.059 ms
6 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 20.827 ms 173.352 ms 128.984 ms
7 bellnexxia.ord01.atlas.cogentco.com (154.54.11.30) 19.956 ms 19.736 ms 18.924 ms
8 core2-chicago23-pos0-3.in.bellnexxia.net (206.108.103.126) 116.094 ms 211.254 ms 230.663 ms
9 core3-toronto63-pos6-3.in.bellnexxia.net (206.108.103.113) 29.851 ms 29.928 ms 29.540 ms
10 core2-torontodc-pos3-0.in.bellnexxia.net (206.108.98.250) 30.036 ms 30.406 ms 30.020 ms
11 dis4-torontodc-Vlan82.in.bellnexxia.net (206.108.104.30) 30.770 ms 29.968 ms 29.807 ms
12 * * *
% traceroute 209.226.175.175
traceroute to 209.226.175.175 (209.226.175.175), 64 hops max, 40 byte packets
1 HSE-Montreal-ppp109023.qc.sympatico.ca (64.230.199.2) 9.572 ms 6.918 ms 7.807 ms
2 dis47-toronto63-Vlan150.in.bellnexxia.net (64.230.232.177) 5.845 ms 5.538 ms 5.604 ms
3 HSE-Sherbrooke-ppp98328.qc.sympatico.ca (64.230.220.229) 5.612 ms 5.727 ms 5.855 ms
4 core3-toronto63-pos0-0.in.bellnexxia.net (64.230.242.109) 6.587 ms 5.593 ms 6.321 ms
5 core2-torontodc-pos3-0.in.bellnexxia.net (206.108.98.250) 5.838 ms 6.035 ms 6.073 ms
6 dis4-torontodc-Vlan82.in.bellnexxia.net (206.108.104.30) 6.452 ms 6.073 ms 6.334 ms
7 * * *
8 * * *
9 * * * |
|
Doci
Toothless Fairy
join:2003-02-01 | reply to secotton
There's your problem right there. Their SMTP answering for their domain are royally fucked and they're shifting the blame over to MSN. How convenient of them.
--
My freedom is a debt to Hitler. |
|
secotton
join:2005-03-30
North York, ON
1 edit | reply to Doci
said by Doci :said by f1ipmode :nope wrong again.;) What do you think are those MX record entry servers? They're SMTP. Just so you don't know, MX=Mail Exchange. Somebody outside of sympatico networks, could you try telnetting into one of those on port 25? From outside Sympatico network:
toip5 - works fine.
toip8 / 4 - it just sits at Trying IP_ADDRESS
rest of them - they just say 'Connection refused' |
|
Doci
Toothless Fairy
join:2003-02-01 | reply to f1ipmode
Read this; »computer.howstuffworks.com/email5.htm
--
My freedom is a debt to Hitler. |
|
Doci
Toothless Fairy
join:2003-02-01
·Bell Sympatico
1 edit | reply to f1ipmode
said by f1ipmode :nope wrong again.;) What do you think are those MX record entry servers? They're SMTP. Just so you don't know, MX=Mail Exchange.
Somebody outside of sympatico networks, could you try telnetting into one of those on port 25?
--
My freedom is a debt to Hitler. |
|
f1ipmode
join:2004-04-05
Scarborough, ON | reply to secotton
nope wrong again.;) |
|
secotton
join:2005-03-30
North York, ON
| reply to f1ipmode
I thought what I've learned with email and sendmail stuff, is that when an email is sent, it goes to your local SMTP server. From there, if it's a local domain, it gets passed the the POP3 server, and if it's a remote address, it hands it to the remote SMTP server. This is when the SMTP server passes it to the POP3 mail server again.
sending email client --> SMTP --> SMTP --> POP3 --> recv. email client
Maybe I'm wrong on this one - but in some way - the SMTP server does handle both incoming and outgoing emails. It could be that it's a different server, and in this case - it too seems to be having difficulties with processing email at the moment. |
|
f1ipmode
join:2004-04-05
Scarborough, ON | reply to secotton
No SMTP doesn't take care of incoming email. |
|
secotton
join:2005-03-30
North York, ON
| reply to mr weather
I've moved now to gmail for the SMTP of choice. And yes - gmail does use port 465 for SSL smtp.
Also - doesn't the SMTP server take care of both the incoming / outgoing emails? I think it is just that it sends the incoming emails into the little holding place for us to actually recieve the emails. I'm pretty sure this is how it works - so that would explain why emails don't go out and come in properly. |
|
