* Recently verisign added a wildcard A record to the .COM and .NET TLD * zones making all .com and .net domains appear to be registered * This causes many problems such as breaking important anti-spam checks * which verify source domains exist. Wietse have released a patch for Postfix dealing with this.
There were reports on the Postfix/TLS list that the tls patch breaks with the verisign patch. I'll try to look into this.
Not sure if this is corrects, but the patch was updated anyhow due to some problems. Cannot recall if it was tls or not. Great if this could be fixed as it's a very needed featurer...
Sorry, didn't mean to change the url -- it is set back. Anywho, so far things seem happy with this patch. I tested: USE=ssl -ipv6 -postgres USE=ssl ipv6 postgres USE=-ssl ipv6 postgres Committing a new version of the 2.0.16 ebuild (-r1).
The '/var/spool/postfix/maildrop' dir seam to have get lost in the r1 release.
Hmm.. I don't see that on my end, can you verify? Mine shows up correctly: # grep maildrop /var/db/pkg/`portageq best_version / postfix`/CONTENTS dir /var/spool/postfix/maildrop Also, nothing has changed between the -r0 and -r1 ebuilds that would affect this. As a side issue, is this patch still needed since verisign turned off site-finder (or whatever they called it).
Well I don't remember now, must have fixed it somehow... :-) I don't think it's needed anymore, havn't check with the postfix list though what the status is.
I believe this is all fixed with the latest commits.
