| Bug#: 199100 | Product: Gentoo Linux | Version: unspecified | Platform: All |
| OS/Version: Linux | Status: RESOLVED | Severity: normal | Priority: P2 |
| Resolution: FIXED | Assigned To: dragonheart@gentoo.org | Reported By: rtpsld@ntsel.com | |
| Component: Applications | |||
| URL: | |||
| Summary: mail-filter/dkim-milter-2.3.2 - emerge --config creates non-working TXT record | |||
| Keywords: | |||
| Status Whiteboard: | |||
| Opened: 2007-11-13 22:27 0000 | |||
| Description: | Opened: 2007-11-13 22:27 0000 |
emerge --config mail-filter/dkim-milter produces a TXT record which includes g=\; I'm new to DKIM, but as far as I can tell that prevents this key from working at all. Changing the TXT record to have g=* seems to be working, and from what I can gather the g= entry may not be necessary at all. Reproducible: Didn't try Steps to Reproduce: 1.emerge --config mail-filter/dkim-milter 2.accept default selector name of mydomain.com 3.select 1024 bit key Actual Results: mydomain.com._domainkey IN TXT "g=\; k=rsa\; ... Expected Results: mydomain.com._domainkey IN TXT "g=*\; k=rsa\; ...
You're right. Fixed in cvs (w/o revision bump) by replacing g= with v=DKIM1.
Good, I was hoping I wasn't making a fool of myself ;) Otherwise an excellent set of instructions for initial setup - thanks for making this a relatively painless implementation.