https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6910
--- Comment #3 from Kevin A. McGrail <[email protected]> --- (In reply to comment #2) > > Since EDNS is disabled by default, it sounds to me like a sane buffer would > > be 4096. Is the buffer configurable? > > Currently EDNS is disabled by default for compatibility with previous > versions (i.e. a 512 bytes buffer is implied). > > Setting buffer size to 4096 by default would be my choice too, > it should work well (and would mostly avoid a need for a TCP fallback) > with a local recursive DNS server, which is used by most if not all > serious installations. > > For some SOHO sites using their ISP's DNS server (or some public DNS server), > this may break their DNS resolving and would require them to explicitly > turn off the option in their SpamAssassin configuration - so this may > require a compatibility note in release notes. On the other hand, such > sites even now probably suffer from breakage in their DNSBL lookups, > without realizing they have a problem or just not caring about it. > I agree that a local caching nameserver is the best setup for any installation. Having that setup will support EDNS without the same concerns. So to me it seems like 3.4.0 is a good time to turn on EDNS by default... > Btw, setting a buffer size to anything larger than 512 bytes implies > the EDNS option in a DNS packet. Or in other words: the EDNS option > in a DNS query its the (only) mechanism by which a client can indicate > it is capable of receiving UDP replies larger than the traditional > 512 bytes limit. Good point. -- You are receiving this mail because: You are the assignee for the bug.
