A
ajack
Guest
In this day and age, we'd be foolish to run a consumer web business without signing our mail with DomainKeys, given how many people have Yahoo accounts (more than Hotmail and Yahoo in my experience).
So I have been looking around for guides on how to patch the Plesk version of Qmail to support DomainKeys.
There are a few good documents out there, but I still have a missing link.
First, to patch qmail and stay in good terms with Plesk, we have some good guidlines here:
http://forum.swsoft.com/showthread.php?s=&threadid=34664
http://kb.swsoft.com/article_22_1161_en.html
And that is working fine.
Then to patch qmail for DomainKeys, we have the reference here:
http://jeremy.kister.net/howto/dk.html
The problem is that this document assumes you have a qmail setup similar to an installation following the guidelines at http://www.lifewithqmail.org
Unfortunately, that is not the case for a Plesk install, in particular:
- there is no /etc/tcp.smptp
- there is a conflict between qmail-1.03-dk-0.54.patch and one of the Plesk 8 patches (on Makefile)
By looking at the code, I can eventually figure out a way to resolve the patch conflict. By the lack of tcp.smtp is a bigger problem because this file is where you tell qmail to use qmail-dk to process the queue and sign outgoing mail. So it means that there is a another *different* process in Plesk's version of Qmail to define how the queue will be processed.
I don't know what it is, does anybody know?
Searching around this forum, I also found this good post:
http://forum.swsoft.com/showthread.php?t=26721
The poster here gives guidelines on how to implement DomainKeys when qmail-scanner is installed, which addresses the problem above since qmail-scanner-queue.pl *is* where the queue is process and the DK signing can be initiated.
Although it's easy and painless to install qmail-scanner, the patch suggested in the post (which is 2+ years old) no longer works and everybody has the same error messages (including me). The error suggested mismatched brackets but I cannot figure out why it occurs or how to correct it.
The most suprising to me is that there are most likely 1000's of sites running off Plesk, so I am sure that many admins out there have faced this problem, and I can't imagine that no one has found a solution yet.
I spent a good amount of time researching today... I am almost there
... can anybody help me with the last mile?
Thanks in advance
Ajack
So I have been looking around for guides on how to patch the Plesk version of Qmail to support DomainKeys.
There are a few good documents out there, but I still have a missing link.
First, to patch qmail and stay in good terms with Plesk, we have some good guidlines here:
http://forum.swsoft.com/showthread.php?s=&threadid=34664
http://kb.swsoft.com/article_22_1161_en.html
And that is working fine.
Then to patch qmail for DomainKeys, we have the reference here:
http://jeremy.kister.net/howto/dk.html
The problem is that this document assumes you have a qmail setup similar to an installation following the guidelines at http://www.lifewithqmail.org
Unfortunately, that is not the case for a Plesk install, in particular:
- there is no /etc/tcp.smptp
- there is a conflict between qmail-1.03-dk-0.54.patch and one of the Plesk 8 patches (on Makefile)
By looking at the code, I can eventually figure out a way to resolve the patch conflict. By the lack of tcp.smtp is a bigger problem because this file is where you tell qmail to use qmail-dk to process the queue and sign outgoing mail. So it means that there is a another *different* process in Plesk's version of Qmail to define how the queue will be processed.
I don't know what it is, does anybody know?
Searching around this forum, I also found this good post:
http://forum.swsoft.com/showthread.php?t=26721
The poster here gives guidelines on how to implement DomainKeys when qmail-scanner is installed, which addresses the problem above since qmail-scanner-queue.pl *is* where the queue is process and the DK signing can be initiated.
Although it's easy and painless to install qmail-scanner, the patch suggested in the post (which is 2+ years old) no longer works and everybody has the same error messages (including me). The error suggested mismatched brackets but I cannot figure out why it occurs or how to correct it.
The most suprising to me is that there are most likely 1000's of sites running off Plesk, so I am sure that many admins out there have faced this problem, and I can't imagine that no one has found a solution yet.
I spent a good amount of time researching today... I am almost there
Thanks in advance
Ajack