MyMTS problems

  • 1
  • Problem
  • Updated 2 years ago
  • Acknowledged
  • (Edited)
Trying to send email to MyMTS customers from my own email server. I have seen this myself and I have another user report the same thing. It fails to any MyMTS address. I can send to Hotmail addresses no problem.
Failed address: XXXX@mymts.net

--- Session Transcript --- Sat 2015-12-12 08:11:07: Parsing message <xxxxxxxxxxxxxxxxxx\pd35000062916.msg> Sat 2015-12-12 08:11:07: * From: XXXX@draega.net Sat 2015-12-12 08:11:07: * To: XXXX@mymts.net Sat 2015-12-12 08:11:07: * Subject: XXXX Sat 2015-12-12 08:11:07: * Size (bytes): 2485 Sat 2015-12-12 08:11:07: * Message-ID: <59E0211A-55F5-4D35-A0FF-41D5EAECA3D4@draega.net> Sat 2015-12-12 08:11:07: Attempting SMTP connection to [mymts.net] Sat 2015-12-12 08:11:07: Resolving MX records for [mymts.net] (DNS Server: 64.59.176.13)... Sat 2015-12-12 08:11:07: * P=010 S=000 D=mymts.net TTL=(43) MX=[mx.mymts.net] Sat 2015-12-12 08:11:07: Attempting SMTP connection to [mx.mymts.net:25] Sat 2015-12-12 08:11:07: Resolving A record for [mx.mymts.net] (DNS Server: 64.59.176.13)... Sat 2015-12-12 08:11:07: * D=mx.mymts.net TTL=(43) A=[69.168.103.61] Sat 2015-12-12 08:11:07: Attempting SMTP connection to [69.168.103.61:25] Sat 2015-12-12 08:11:07: Waiting for socket connection... Sat 2015-12-12 08:11:07: * Connection established (184.71.79.226:55472 -> 69.168.103.61:25) Sat 2015-12-12 08:11:07: Waiting for protocol to start... Sat 2015-12-12 08:11:08: <-- 220 2.0.0 mx.mymts.net ESMTP ecelerity 3.6.6.45965 r(Core:3.6.6.0) Sat, 12 Dec 2015 09:11:04 -0500 Sat 2015-12-12 08:11:08: --> EHLO draega.net Sat 2015-12-12 08:11:08: <-- 250-mx.mymts.net says EHLO to 184.71.79.226:55472 Sat 2015-12-12 08:11:08: <-- 250-PIPELINING Sat 2015-12-12 08:11:08: <-- 250-8BITMIME Sat 2015-12-12 08:11:08: <-- 250-STARTTLS Sat 2015-12-12 08:11:08: <-- 250-ENHANCEDSTATUSCODES Sat 2015-12-12 08:11:08: <-- 250 XDUMPCONTEXT Sat 2015-12-12 08:11:08: --> STARTTLS Sat 2015-12-12 08:11:08: <-- 220 2.0.0 continue Sat 2015-12-12 08:11:08: SSL negotiation successful (TLS 1.0, 2048 bit key exchange, 256 bit encryption) Sat 2015-12-12 08:11:08: --> EHLO draega.net Sat 2015-12-12 08:11:08: <-- 250-mx.mymts.net says EHLO to 184.71.79.226:55472 Sat 2015-12-12 08:11:08: <-- 250-XDUMPCONTEXT Sat 2015-12-12 08:11:08: <-- 250-ENHANCEDSTATUSCODES Sat 2015-12-12 08:11:08: <-- 250-8BITMIME Sat 2015-12-12 08:11:08: <-- 250 PIPELINING Sat 2015-12-12 08:11:08: --> MAIL From:<XXXX@draega.net> Sat 2015-12-12 08:11:08: <-- 250 2.0.0 MAIL FROM accepted Sat 2015-12-12 08:11:08: --> RCPT To:<XXXX@mymts.net> Sat 2015-12-12 08:11:08: <-- 250 2.1.5 Accepted for you Sat 2015-12-12 08:11:08: --> DATA Sat 2015-12-12 08:11:08: <-- 354 3.0.0 continue. finished with "\r\n.\r\n" Sat 2015-12-12 08:11:08: Sending <xxxxxxxxxxxxxxxxxx\pd35000062916.msg> to [69.168.103.61] Sat 2015-12-12 08:11:08: Transfer Complete Sat 2015-12-12 08:11:09: <-- 554 5.7.1 [P4] Message blocked due to spam content in the message. Sat 2015-12-12 08:11:09: --> QUIT --- End Transcript ---

My server is not blacklisted on any list that I can find.

Thx.

Sean
Photo of Sean Odell

Sean Odell

  • 70 Points

Posted 2 years ago

  • 1
Photo of Jeremy

Jeremy, Official Rep

  • 18,704 Points 10k badge 2x thumb
Official Response
Hey Sean,
We have been doing a lot of work on the spam filters with the @mymts.net email and it's possible you may be getting caught in the mix of these changes.  I would suggest giving our tech support crew a call and a ticket can be escalated to look into your sending address specifically.  They will need things such as the address you're sending from, a couple examples of addresses that you sent to as well as a copy of the email sent with headers.
They can be reached by phone 24/7 at 204-225-5687 or you can chat in during business hours via the mts.ca/support site.
(Edited)