Mailing List Archive

[Bug 339] Put callout response into a variable
http://www.exim.org/bugzilla/show_bug.cgi?id=339





------- Additional Comments From iane@sussex.ac.uk 2006-10-17 12:12 -------
It would also be nice if any rfc2034 extended error codes were stored in a separate variable.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 339] Put callout response into a variable [ In reply to ]
http://www.exim.org/bugzilla/show_bug.cgi?id=339





------- Additional Comments From marc@perkel.com 2006-10-17 15:57 -------
I'd like to have it too. Sometimes the text of the callout is important. For
example, I might be rejected because I'm blacklisted somewhere and want to know
that. I also want to pass the final string back as part of the error code.

In may case I do front end spam filtering for other domains. When someone
connects to me I do a recipient callout to verify the recipient. But if my spam
filtering servers get accidently listed on some blacklist (which happens) then
my customers start bouncing mail from me and it looks like my forward recipient
verificatrion fails and I end up sending back an invalid user error. If I had
the string I could test for the word "blacklisted" and spool the email unlit I
fixed the problem.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##