Skip to content
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

Smarthost problem #54

Closed
xagaba opened this issue Dec 27, 2017 · 9 comments
Closed

Smarthost problem #54

xagaba opened this issue Dec 27, 2017 · 9 comments

Comments

@xagaba
Copy link

xagaba commented Dec 27, 2017

I see previous issues about this, but I'm a little lost here...
I'm using dma 0.11 from debian stretch and using this config :

SMARTHOST ssl0.ovh.net
PORT 587
AUTHPATH /etc/dma/auth.conf
SECURETRANSFER
STARTTLS

I get this in mail.log

dma[]: trying delivery
dma[]: using smarthost (ssl0.ovh.net:587)
dma[]: trying remote delivery to ssl0.ovh.net [213.186.33.20] pref 0
dma[]: SSL initialization successful
dma[]: using SMTP authentication for user postmaster@domain
dma[]: smarthost authentication: AUTH cram-md5 not available: 535 5.7.8 Error: authentication failed: Invalid authentication mechanism
dma[]: delivery successful

But the email it's not received...
Using the same smarthost config in postfix, works fine

Any advice how I can debug this ?

@corecode
Copy link
Owner

Thanks for the report. It seems that we should either parse the AUTH report and only try mechanisms that are listed, or we should ignore the error reply while we still have available mechanisms.

@corecode
Copy link
Owner

Actually it reports that the mail was delivered correctly, so I don't know why ovh doesn't forward the mail.

@xagaba
Copy link
Author

xagaba commented Jan 12, 2018

This is with a newer version or with the 0.11 I use ?
I try to forward the problem to OVH

@corecode
Copy link
Owner

Your log shows "delivery successful", which should mean that the SMTP server told us that it accepted the mail.

@corecode
Copy link
Owner

Did you ever get this working?

@xagaba
Copy link
Author

xagaba commented Aug 30, 2019 via email

@moqmar
Copy link

moqmar commented Nov 20, 2019

I'm having the same problem with postmarkapp.com. My config is pretty much the same (except for the host, and an additional line with the MAILNAME). Log output follows:

new mail from user=root uid=8 envelope_from=<root@momar.xyz>
mail to=<test@blackhole.postmarkapp.com> queued as a00eb.558181882230
trying delivery
using smarthost (smtp.postmarkapp.com:587)
trying remote delivery to smtp.postmarkapp.com [63.35.51.189] pref 0
SSL initialization successful
using SMTP authentication for user 00000000-0000-0000-0000-000000000000
delivery successful

Is there any possibility to log the actual message that's being sent?

@corecode
Copy link
Owner

I just implemented debug logging, but it turns out that postmarkapp will accept mails, even if it will later reject them because of account limits. You can see delivery errors in the "Activity" tab.

My first two trials didn't work because of

  • The 'From' address you supplied (...) is not a Sender Signature on your account.
  • While your account is pending approval, all recipient addresses must share the same domain as the 'From' address.

After fixing both problems, a mail sent by dma through postmarkapp got delivered successfully.

Postmarkapp's mail server behavior is quenstionable: if a mail server accepts a mail, it must deliver it, or bounce a message when it cannot deliver. Postmarkapp does neither, it just logs an error in the web interface.

In summary, dma successfully delivers to postmarkapp, and with correct sender and recipient, postmarkapp will successfully process and deliver the mail.

@moqmar
Copy link

moqmar commented Nov 25, 2019

Oh wow... I verified my domain, looked into the Activity tab, even created a Webhook, and it would just stay empty. The issue: I tested this with echo "From: ...\r\nTo: ...\r\nSubject: ...\r\n\r\n..." | dma ..., but I was supposed to use echo -e ..., as it was taking the backslashes literally otherwise - awesome that Postmark doesn't even bounce mails which are just plain wrong. :/

It's working now, and it's a really nice & simple MTA, thank you very much for the great work! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants