[kwlug-disc] Testing a mail port
Bob Jonkman
bjonkman at sobac.com
Wed Mar 9 18:36:45 EST 2016
B.S. wrote:
> You should not, and should not have to, use smtp.bellnet.ca. This
> means a Bell server is e-mail relaying all e-mail, for all providers
> (stemming from within their network).
Shouldn't have to, but Bell (and Rogers) does impose that restriction.
Even if they allow port 587 (Message Submission Protocol), Bell and
Rogers customers can't run mail servers which require port 25 (SMTP) to
do server-to-server communication. And, as Joe discovered, SysAdmins
can't perform troubleshooting from Bell and Rogers networks either.
--Bob.
Bob Jonkman <bjonkman at sobac.com> Phone: +1-519-635-9413
SOBAC Microcomputer Services http://sobac.com/sobac/
Software --- Office & Business Automation --- Consulting
GnuPG Fngrprnt:04F7 742B 8F54 C40A E115 26C2 B912 89B0 D2CC E5EA
On 2016-03-09 03:49 PM, B.S. wrote:
> The telnets mentioned as working do not work for me (I'm on Bell,
> too.)
>
> From the other messages, clearly the server is up and working. It may
> be slightly broken / misconfigured in some senses, but clearly, for
> example, your telnet tests should work.
>
> Couple things, make sure you're running from as close to the router
> as you can for testing. And take a peek at the router config for
> something unexpected.
>
> Elsewise, this is indeed Bell doing you in - you should be able to
> cross-check / confirm by going to any other e-mail provider. i.e. If
> 25 and 587 are blocked, feels like they will be blocked across the
> board. Yet my e-mail has been working fine. Perhaps this is across
> the board on 25 and not 587. e.g.
>
> # nc smtp.googlemail.com 587 220 smtp.googlemail.com ESMTP
> j18sm141810ioj.40 - gsmtp
>
>
>
> You should not, and should not have to, use smtp.bellnet.ca. This
> means a Bell server is e-mail relaying all e-mail, for all providers
> (stemming from within their network).
>
> Which is to say, their fingers are in and aware of all outgoing
> e-mail. Perhaps not what you intended. (Although I get people needing
> to get on with their day in the mean time.)
>
>
>
> This is my traceroute. Perhaps others can run too, especially where
> telnet mail.ufn.com 25 works, and spot if there is a backbone routing
> divergence only impacting Bell.
>
> $ traceroute mail.ufn.com traceroute to mail.ufn.com (54.235.159.86),
> 30 hops max, 60 byte packets 3 * 10.178.206.42 (10.178.206.42)
> 15.812 ms 15.837 ms 4 10.178.206.43 (10.178.206.43) 15.949 ms
> 16.355 ms 18.744 ms 5 tcore4-kitchener06_Bundle-ether4.net.bell.ca
> (64.230.113.70) 35.229 ms 35.454 ms 33.409 ms 6
> tcore3-toronto21_hun1-1-0-0.net.bell.ca (64.230.50.188) 34.318 ms
> 35.692 ms tcore4-toronto63_pos0-14-0-0.net.bell.ca (64.230.49.34)
> 36.321 ms 7 tcore4-chicagocp_hundredgige0-5-0-0.net.bell.ca
> (64.230.79.155) 33.176 ms
> tcore3-chicagocp_hundredgige0-8-0-0.net.bell.ca (64.230.79.161)
> 28.286 ms 28.489 ms 8 bx7-chicagodt_bundle-ether5.net.bell.ca
> (64.230.79.171) 30.632 ms 30.434 ms
> bx7-chicagodt_bundle-ether4.net.bell.ca (64.230.79.169) 25.927 ms 9
> amazon_bx7-chicagodt (184.150.181.125) 27.828 ms 28.245 ms 28.352
> ms 10 52.95.62.70 (52.95.62.70) 36.052 ms 52.95.62.118
> (52.95.62.118) 51.321 ms 52.95.62.38 (52.95.62.38) 34.331 ms 11
> 52.95.62.141 (52.95.62.141) 29.368 ms 52.95.62.143 (52.95.62.143)
> 31.537 ms 52.95.62.61 (52.95.62.61) 30.651 ms 12 54.239.41.21
> (54.239.41.21) 45.284 ms 45.451 ms 54.239.42.37 (54.239.42.37)
> 48.768 ms 13 54.240.228.246 (54.240.228.246) 49.346 ms
> 54.240.228.236 (54.240.228.236) 48.909 ms 54.240.228.234
> (54.240.228.234) 49.557 ms 14 54.240.229.191 (54.240.229.191)
> 42.336 ms 54.240.229.185 (54.240.229.185) 42.306 ms 54.240.229.191
> (54.240.229.191) 42.602 ms 15 54.240.228.177 (54.240.228.177)
> 43.444 ms 54.240.228.171 (54.240.228.171) 42.550 ms 54.240.228.181
> (54.240.228.181) 42.063 ms 16 * * * 17 * * * 18 54.239.110.239
> (54.239.110.239) 66.452 ms 54.239.110.241 (54.239.110.241) 56.168
> ms 54.239.110.251 (54.239.110.251) 41.452 ms 19 54.239.109.141
> (54.239.109.141) 41.589 ms 54.239.109.107 (54.239.109.107) 42.875
> ms 54.239.110.55 (54.239.110.55) 42.820 ms 20 72.21.222.139
> (72.21.222.139) 45.224 ms 44.879 ms 42.706 ms 21 * * * 22 * * *
> 23 * * * 24 216.182.224.51 (216.182.224.51) 42.763 ms
> 216.182.224.67 (216.182.224.67) 47.154 ms 216.182.224.57
> (216.182.224.57) 42.917 ms 25 * * * 26 * * * 27 * * *
>
>
> ping is non-responsive.
>> ________________________________ From: Joe Wennechuk
>> <youcanreachmehere at hotmail.com> To: "kwlug-disc at kwlug.org"
>> <kwlug-disc at kwlug.org> Sent: Wednesday, March 9, 2016 2:19 PM
>> Subject: Re: [kwlug-disc] Testing a mail port
>>
>>
>>
>> Okay All fied.. I had to use smtp.bellnet.ca to send. Thanks for
>> all of the help.
>>
>> Joseph Wennechuk Phone: (226) 600-6119
>> https://www.linkedin.com/pub/joseph-wennechuk/4/b59/382
>>
>>
>>
>>
>>> Date: Wed, 9 Mar 2016 13:57:07 -0500 From: kb at 2bits.com To:
>>> kwlug-disc at kwlug.org Subject: Re: [kwlug-disc] Testing a mail
>>> port
>>>
>>> On Wed, Mar 9, 2016 at 1:49 PM, Joe Wennechuk
>>> <youcanreachmehere at hotmail.com> wrote:
>>>> actually this is what I was looking for... dig.. The domain is
>>>> kwflowers.com but I get nothing interesting back when I do a
>>>> dig mx kwflowers.com
>>>
>>> dig mx kwflowers.com says:
>>>
>>> ;; ANSWER SECTION: kwflowers.com. 86400 IN MX 10
>>> mail.ufn.com.
>>>
>>>> Now I am not sure. When I use mxtoolbox to check kwflowers.com
>>>> I get mail.ufn.com.
>>>
>>> That confirms what dig shows.
>>>
>>> So, mail is supposed to be handled by mail.ufn.com
>>>
>>> Maybe this is what they want, maybe not. If not, then that
>>> explains why email is not being handled for that domain.
>
>
> _______________________________________________ kwlug-disc mailing
> list kwlug-disc at kwlug.org
> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20160309/5e02aa2c/attachment.sig>
More information about the kwlug-disc
mailing list