unable to connect Error#22 after migrating to SMTP.com relay

SAW

Member
MBM is unable to connect and send out through SMTP.com (the relay service we use to send our bulk email.)

This is what I get:
Looking for...
Error#22


I have already been though SMTP.com help desk and they do not know why it won't work. They think everything is set up correctly. We dribble checked settings, user & pass. They are now sending me back to MBM.

The backstory is http://www.SMTP.com bought out UnifiedEmail, and all customers have been moved over to SMTP.com.

UnifiedEmail worked perfectly for 4 years. The only difference in setup was supposed to be the new “Mail Server Name.” User and pass all stayed the same.

I have tried on both MBM 8.6 and 8.5.5.
Mac 10.11.6

My shiny new smtp.com dedicated mail server is:
knsawart.smtp.com

I have tried to change ports
:25
:80
:2525
:25025
:2082

Authentication:
ESMTP

I have tried all 3:
Login
Plain
MD5 Challenge-Response


Here is the delivery log:

Code:
[01] 3/28 16:25:22     ~ Opening connection for delivery...
[01] 3/28 16:25:22     ~ Connecting to knsawart.smtp.com Port:25
[01] 3/28 16:25:29     ~ The server knsawart.smtp.com doesn't respond. Trying on port #587
[01] 3/28 16:25:36     ~ The server knsawart.smtp.com doesn't respond. Trying on port #2525
[01] 3/28 16:25:36     ~ The server knsawart.smtp.com doesn't respond. Trying on port #26
[01] 3/28 16:25:38     ~ The server knsawart.smtp.com doesn't respond. Trying on port #2526
[01] 3/28 16:25:42     ~ The server knsawart.smtp.com doesn't respond. Trying on port #3535
[01] 3/28 16:25:42     ~ Socket #1 failed to establish a connection with knsawart.smtp.com
[00] 3/28 16:25:42     ~ [-??]
[00] 3/28 16:25:42     ~ Closing all streams
[00] 3/28 16:25:42     ~ Creating report...
[00] 3/28 16:25:42     ~ Finishing...
[00] 3/28 16:25:42     ~ Finished.

Terminal says this:

telnet knsawart.smtp.com 25, says
Trying 198.105.254.130...

telnet knsawart.smtp.com 80, says
Trying 198.105.254.130...
Connected to knsawart.smtp.com.
Escape character is '^]'.


I have also followed these instruction PDFs:

https://www.smtp.com/assets/Max-Bulk-Mailer.pdf

https://ncp-gm.smtp.com/bundles/smtpcore/tutorials/mass_mailing_software/Max_Bulk_Mailer.pdf


Please advise. Than you!!
 

SAW

Member
Re: unable to connect Error#22 after migrating to SMTP.com r

yes, we tried :80
knsawart.smtp.com:80

actually, tried that about 10 times!
I so thought that would work.

I filled out a MaxProg support ticket email that has my:
• server
• user
• pass
just so you have all the credentials and can troubleshoot first hand.

I am so surprised / frustrated it does not work.

eager for your follow up.
thanks, Stan!
 

stanbusk

Administrator
Staff member
Re: unable to connect Error#22 after migrating to SMTP.com r

When settings don't work it is usually because they are wrong. Maybe you need to activate TLSv1? Have you tried? Note that I tried your settings with Telnet and I only get a host error. Telnet says that 'knsawart.smtp.com' doesn't exist. :shock:

--
Follow maxprog.com on Facebook | Google+ | Linkedin | Twitter | YouTube
and keep up-to-date with the latest Max Programming updates!
 

SAW

Member
Re: unable to connect Error#22 after migrating to SMTP.com r

Okay, I tried TLSv1
via POP
via APOP

And neither one worked. :(
Ugh.

Should I try tech help again with SMPT.com ?

Should I tell them that:
MaxProg tried your settings with Telnet and got a host error.
Telnet says that 'knsawart.smtp.com' doesn't exist. :shock:
?

Stan, do you suspect user/pass problem ?
Or a handshake with 'knsawart.smtp.com' problem ?
Or some thing else ? :?

- - -

How was your trip?
They say a good sign of a vacation is when you are ready to be back home...
and answer all my tech help questions! ;-)
Please hang in there with me Stan, I really appreciate it!

My IT guy and I are rebuilding from the ground up with:
clean dedicated server 1 hosting MLM
clean dedicated server 2 hosting linked images
server 3 being a clean email server
and using SMTP.com to be the relay service (RIP UnifiedEmail.net)

That is a ton of work just to make our e-newsletters successfully land in inboxes.
Fingers crossed.
 
Top