You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2009/10/15 19:18:27 UTC
[Bug 6221] DnsResolver.pm attempts to bind ports at random
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6221
Mark Martinec <Ma...@ijs.si> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Undefined |3.3.0
--- Comment #1 from Mark Martinec <Ma...@ijs.si> 2009-10-15 10:18:26 UTC ---
> Created an attachment (id=4551)
--> (https://issues.apache.org/SpamAssassin/attachment.cgi?id=4551) [details]
> Patch to always use port 0 instead of trying ports at random
>
> DnsResolver.pm attempts to bind UDP ports at random. This causes numerous
> errors if listening on specific ports is restricted to specific
> applications/users.
>
> The correct way to acquire a UDP socket to listen for responses is to bind to
> port 0 instead. The OS will automatically allocate an appropriate free port
> from the range defined for local allocation (net.ipv4.ip_local_port_range on
> Linux).
While I agree in general, I think there was some underlying reason for the
current hack, but I can't find a reference now. Possibly something to do
with mismatching DNS replies with queries. Moving to 3.3.0 target.
Related to Bug 5264.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.