Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 199100
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Daniel Black <dragonheart@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Steve Moerk <rtpsld@ntsel.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 199100 depends on: Show dependency tree
Bug 199100 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

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\; ...

------- Comment #1 From Alin Năstac 2007-11-14 04:48:05 0000 ------- 
You're right. Fixed in cvs (w/o revision bump) by replacing g= with v=DKIM1.

------- Comment #2 From Steve Moerk 2007-11-14 16:01:11 0000 ------- 
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.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug