email not delivered

[developer]

Hi @twisted1919

I have used delivery server for elastic email.

I have set “Subscribers at once – 50.” - https://www.screencast.com/t/OwjeL98gL1jL

I have check campaigns delivery logs, email was not sending. - display following error. - https://www.screencast.com/t/gMPZSCJEa1

 

[twisted1919]

@developer - looks like they had a temporary issue ?
I can access https://api.elasticemail.com/ just fine, so it should work now.

 

[developer]

Hi @twisted1919

I can also access https://api.elasticemail.com/

But

My issue is email’s are not delivered till now.

Please check error in campaigns delivery log. - https://www.screencast.com/t/pWcu9x3cz2

I have try send to campaign using command line but it show me error, check below screen shot. - https://www.screencast.com/t/DhfQYSm2oV9H

For this error - “Failed to connect to api.elasticemail.com port 443: Connection refused”

 

[twisted1919]

I can also access https://api.elasticemail.com/

You can. but can you do it from your server?

 

[frm.mwz]

Hi @twisted1919

I can also access https://api.elasticemail.com/

But

My issue is email’s are not delivered till now.

Please check error in campaigns delivery log. - https://www.screencast.com/t/pWcu9x3cz2

I have try send to campaign using command line but it show me error, check below screen shot. - https://www.screencast.com/t/DhfQYSm2oV9H

For this error - “Failed to connect to api.elasticemail.com port 443: Connection refused”

on cli
ping api.elasticemail.com
and in the account check if all is set correctly, perhaps you are over limit or the authentications are not yet set up, etc

 

[twisted1919]

on cli
ping api.elasticemail.com

this only checks if the host is up which isn't always what you are after.

You might be after nmap:

$ nmap api.elasticemail.com
Starting Nmap 7.50 ( https://nmap.org ) at 2017-09-26 12:51 EEST
Nmap scan report for api.elasticemail.com (46.105.88.234)
Host is up (0.019s latency).
Other addresses for api.elasticemail.com (not scanned): 188.165.1.80 94.23.161.19
Not shown: 991 filtered ports
PORT     STATE SERVICE
80/tcp   open  http
110/tcp  open  pop3
143/tcp  open  imap
443/tcp  open  https
465/tcp  open  smtps
587/tcp  open  submission
993/tcp  open  imaps
995/tcp  open  pop3s
2525/tcp open  ms-v-worlds
Nmap done: 1 IP address (1 host up) scanned in 5.84 seconds

 

[frm.mwz]

this only checks if the host is up which isn't always what you are after.

You might be after nmap:

$ nmap api.elasticemail.com
Starting Nmap 7.50 ( https://nmap.org ) at 2017-09-26 12:51 EEST
Nmap scan report for api.elasticemail.com (46.105.88.234)
Host is up (0.019s latency).
Other addresses for api.elasticemail.com (not scanned): 188.165.1.80 94.23.161.19
Not shown: 991 filtered ports
PORT     STATE SERVICE
80/tcp   open  http
110/tcp  open  pop3
143/tcp  open  imap
443/tcp  open  https
465/tcp  open  smtps
587/tcp  open  submission
993/tcp  open  imaps
995/tcp  open  pop3s
2525/tcp open  ms-v-worlds
Nmap done: 1 IP address (1 host up) scanned in 5.84 seconds

Yes, that is much better, especially when checking for the port specific errors. Thx!