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
Catching a BadReply somewhere but not sure why #118
Comments
I've been able to pinpoint this further down. When you instantiate a BadReply with some data, the data attribute is empty when the exception is raised. I'm going to post some code which will replicate this. |
An example to reproduce it is when a server sends a SMTP response without a status code. This is an example caught in a PowerMTA server: And this is what is reported by slimta: "4.3.0 Bad SMTP reply from server." I'll post 2 minimalist pieces of code to reproduce it, a rely and an edge:
and
The problem is this: |
I'm catching a
SmtpTransientRelayError as e
, but ine.reply.message
i've got the following text:4.3.0 Bad SMTP reply from server.
. I want to find out what's happening, but i can't find out when this is raised, because BadReply is always initialized with some other message. There doesn't seem to be a message here, and i can't find it once the exception is raised.I'm on slitma3.
The text was updated successfully, but these errors were encountered: