https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8213
Sidney Markowitz <sidney@sidney.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sidney@sidney.com
--- Comment #1 from Sidney Markowitz <sidney@sidney.com> ---
I gather from bug 6910 and what I have gleaned from looking over the code, that
SpamAssassin does not retry truncated UDP replies by sending a TCP query. If
Mail::SPF correctly handles TCP fallback for truncated UDP replies, that would
explain why the SPF plugin is able to work with domains that have huge TXT
records even though the SpamAssassin's DNS processing logs those warnings.
Looking back at the history of this, I think what happened is that Net::DNS did
not reliably do what we needed and we implemented our own bgsend and bgread for
asynchronous handling of DNS queries for RBLs. Our version did not implement
TCP fallback from truncated UDP queries when that was added to Net::DNS. When I
read over the comment history in bug 4620 I can see that it would not be easy
to change much of this: I don't remember any of that stuff, and I wrote a good
number of those comments and code almost 20 years ago!
If someone can come up with a patch to use bgsend and bgread from
Net::DNS::Resolver instead of our own version, and demonstrate that everything
still works, that could be a solution.
However, I would like to see that there really is a problem other than warnings
in logs. Given that SPF processing is done by Mail::SPF which doesn't have a
problem with TCP fallback, I want to see an example of a mail message that
SpamAssassin fails on because of truncated UDP replies.
--
You are receiving this mail because:
You are the assignee for the bug.
Sidney Markowitz <sidney@sidney.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sidney@sidney.com
--- Comment #1 from Sidney Markowitz <sidney@sidney.com> ---
I gather from bug 6910 and what I have gleaned from looking over the code, that
SpamAssassin does not retry truncated UDP replies by sending a TCP query. If
Mail::SPF correctly handles TCP fallback for truncated UDP replies, that would
explain why the SPF plugin is able to work with domains that have huge TXT
records even though the SpamAssassin's DNS processing logs those warnings.
Looking back at the history of this, I think what happened is that Net::DNS did
not reliably do what we needed and we implemented our own bgsend and bgread for
asynchronous handling of DNS queries for RBLs. Our version did not implement
TCP fallback from truncated UDP queries when that was added to Net::DNS. When I
read over the comment history in bug 4620 I can see that it would not be easy
to change much of this: I don't remember any of that stuff, and I wrote a good
number of those comments and code almost 20 years ago!
If someone can come up with a patch to use bgsend and bgread from
Net::DNS::Resolver instead of our own version, and demonstrate that everything
still works, that could be a solution.
However, I would like to see that there really is a problem other than warnings
in logs. Given that SPF processing is done by Mail::SPF which doesn't have a
problem with TCP fallback, I want to see an example of a mail message that
SpamAssassin fails on because of truncated UDP replies.
--
You are receiving this mail because:
You are the assignee for the bug.