-
Notifications
You must be signed in to change notification settings - Fork 49
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
Comments
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. |
Actually it reports that the mail was delivered correctly, so I don't know why ovh doesn't forward the mail. |
This is with a newer version or with the 0.11 I use ? |
Your log shows "delivery successful", which should mean that the SMTP server told us that it accepted the mail. |
Did you ever get this working? |
Sorry but we don't use OVH anymore ....
Missatge de Simon Schubert <notifications@github.com> del dia dv., 30 d’ag.
2019 a les 9:11:
… Did you ever get this working?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#54?email_source=notifications&email_token=ACPWWQFPCZZCNMFLWI5MPT3QHDB2ZA5CNFSM4EJVTSXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5QY4XY#issuecomment-526487135>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACPWWQGW6WAJYZINMEUASXDQHDB2ZANCNFSM4EJVTSXA>
.
|
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
Is there any possibility to log the actual message that's being sent? |
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
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. |
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 It's working now, and it's a really nice & simple MTA, thank you very much for the great work! 👍 |
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 ?
The text was updated successfully, but these errors were encountered: