-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't connect with SMTP #293
Comments
When I add additional credentials how do I use then? |
@willpower232 We have sent test messages successfully but not though SMTP |
You can try using After you have created a credential, a link appears saying |
I have followed the instructions on the help guide you've directed me to.
Haven't been able to connect with SMTP yet. Server operational.
What could I be doing wrong? Can you walk me through an example? Thank you
for helping me to understand the credentials, once we get the default SMTP
settings working we can use your advice to use different credentials.
Thank you, Mark
On Aug 5, 2017 8:41 AM, "Will Power" <notifications@github.com> wrote:
You can try using postal status and netstat -lnp to see if you have an SMTP
process for postal.
After you have created a credential, a link appears saying Read more about
sending outgoing e-mails which tells you how to use the credential.
Additional credentials are essentially different passwords for the same
username.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#293 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AMMA56PeH3oYl-1qsmujEuc5VL6Vys0Dks5sVGMJgaJpZM4Os2uq>
.
|
Can you send the output of |
It might be worth verifying that the SMTP port is reachable. Can you try using telnet from your computer to try to connect to your server? P.S. screenshots are better than textual messages |
Thanks for that, have you had a go with telnet yet?
|
Yes able to connect and AUTH LOGIN with base64 encoded username and
password.
However SMTP doesn't allow me to connect from third party platform, so when
attempting to authenticate from my delivery platform I still cannot
authenticate...
…On Sep 17, 2017 5:32 AM, "Will Power" ***@***.***> wrote:
Thanks for that, have you had a go with telnet yet?
Can you try using telnet from your computer to try to connect to your
server? telnet postal.yourserver.com 25
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#293 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AMMA58gEIyh7KHt_SWVPyRu_st3CUQw8ks5sjOdGgaJpZM4Os2uq>
.
|
Telnet suggests SMTP is working, and connection is authenticated with the credentials encoded in base64, however to note .. ... .... the SMTP connection between third party delivery platforms is still showing me errors. So when attempting to connect SMTP I am not authenticating from other platforms. Should the Username and Password be encoded in base64 on the third party delivery platform? Should I be connecting with STARTTLS, or other methods? What is preventing the SMTP from connecting to third party delivery platforms?(seeing as Telnet method is working..) I am only able to deliver any messages with clicking through messages/send test at postal.mydomain.com/org/v/servers/postal/messages/new |
@willpower232 @adamcooke netstat -lnp |
As far as I am aware, you don't need to base64 encode things. We had some issues with port 25 on AWS so used |
I was able to start the SMTP server, and still not able to authenticate with my email platform. CLIENT: telnet postal.mydomain.com 25 @willpower232 @adamcooke Note that "postal status" response does not list port #'s for active processes, if this is any indication of misconfiguration please let me know what to do. I am just not able to authenticate with third party delivery platforms using SMTP method as of yet. I have credentials, and verified telnet ability, but the delivery and authentication from other platforms is just giving me troubles. Hoping this can help root@postal:/opt/postal/config# postal status || web || worker || cron || smtp || requeuer root@postal:/opt/postal/config# netstat -lnp (omitted my IP from below, replaced with 127.0.0.1 for this post) |
127.0.0.1 == my ip :/opt/postal/config# postal test-app-smtp test@verifiedpostaldomain.com SMTP Host: 127.0.0.1 |
Postal status wouldn't be intended to show the ports since netstat does a much better job. In the smtp section of 'From/Sender name is not valid' implies that your domain may not be verified for the credential used so you should also check that. |
That's how I have it setup.
And the domain is verified.
It's the same used in the telnet posted earlier.
…On Oct 4, 2017 4:43 AM, "Will Power" ***@***.***> wrote:
Postal status wouldn't be intended to show the ports since netstat does a
much better job.
In the smtp section of postal.yml try putting the domain name for the
host instead of any IP address.
'From/Sender name is not valid' implies that your domain may not be
verified for the credential used so you should also check that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#293 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AMMA57uF8K5wZnDa9KSXg9hilpBgOmFsks5so0U-gaJpZM4Os2uq>
.
|
Also can't send with API but testing works |
Make sure you are using a credential that comes from the same area as the domain name you are trying to send with. |
Same issue it works with telnet command line but it doesn't work using another third party app such as spree mail setting https://github.com/spree-contrib/spree_mail_settings. |
@Reklen please open a new issue with more details of your error message |
I'm trying to connect with SMTP and I'm not able to use the provided details in the configuration. Please advise, how have you been able to successfully send via SMTP? What's the process?
I've tried the following;
u/user
passKey
postal.mydomain.com
25 or 2525
The text was updated successfully, but these errors were encountered: