I think you have a typo in the following code:

[root@host etc]# host -ttxt mail._domainkey.domain.tls
mail._domainkey.domain.tld descriptive text “k=rsa\; t=s\; p=MFwwDQYJ……0JMCAwEAAQ==”

Shouldn’t it be:

[root@host etc]# host -ttxt mail._domainkey.domain.tld

A working signature does not automatically mean that emails won’t be marked as spam. It just provides a way for them to reliably track your domain’s reputation.

I had a lot of perl dependency errors during install on CentOS 5.4. I used CPAN ay first and still couldn’t quiet the errors. Next I tried searching for RPMs online and eliminated some. Finally, I installed DAG and used YUM to install latest versions of MAIL::DKIM and dependencies without errors. Next, I installed dkimproxy 1.2 with success. I followed the configure instructions exactly, setup the init/d script and config files, made the mods to EXIM, and was ready to go. or so I thought. When starting with service dmproxy start I get green lights, but when I check a few seconds later with service dmproxy status I see that both the in and out processes have stopped. Nothing at all in the system logs, so I have nothing to go on.

Any ideas? Is there a switch for debug or verbose logging?

Thanks!

Your suggestions worked perfectly. I changed the SMTP port from 25 to 587 in Squirrelmail configuration and that worked. Thank you for you time and you made a great job by posting this tutorial.

Thank you
Manish

I didn’t think about that correctly. The master.cf file I mentioned above doesn’t sign mail coming in on port 25 (since all inbound mail comes in on that port).

Ideally, you would configure squirrelmail to send to port 587 which should get signed. Alternatively, you could change the ’smtp’ section of master.cf to look like this:

smtp  inet  n     -       n       -       -       smtpd
    -o content_filter=dksign:[127.0.0.1]:10027

That will send all incoming messages through dkimproxy and try to sign them, which obviously adds some un-necessary overhead.

Thank you for the prompt response, well yes that line is already there in my master.cf file. Squireelmail is using Port 25 for making SMTP connection and maillog gives status as

dkimproxy.in[27581]: DKIM verify – none;

as the mail is send through squirrelmail, also it has dovecot installed with IMAP and POP

So is there something I am missing.

Thank you
Manish

Did you add this line to your master.cf file:

pickup    fifo  n       -       n       60      1       pickup
    -o content_filter=dksign:[127.0.0.1]:10027

That is the service used when programs use the command-line sendmail program to submit messages, which is likely what your CLI scripts and squirrelmail use.

Thanks,
Brandon

I followed your tutorial and everything works fine, but when the mail is send through squirrelmail then mail is not signed through DKIMProxy and when the mail is send from the server itself using cli like mail or sendmail command then mail is signed with DKIMProxy. Is there any configuration which I am missing in configuring dkimproxy. I get that message form maillog is

dkimproxy.in[27581]: DKIM verify – none;

What could be wrong.

Thank you
Manish