https://github.com/QMailToaster/qmail
Each QMT package is in it's own repo on github.
The .spec file for each package contains all the 'rules' need to build
the rpms.
You should find somewhere in the .spec where it renames qmail-queue to
qmail-queue.orig and creates the symlink to qmail-dk. I think we should
still create the symlink, but simply point it back to the .orig file.
That will disable DomainKeys by default, and allow someone to easily
enable it if they choose to.
Thanks Helmut!
--
-Eric 'shubes'
On 11/21/2014 12:44 PM, Helmut Fritz wrote:
Eric,
Glad to help if I can. I am not a developer or even a packaging person.
Where would I find the qmail.spec file?
Helmut
-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: Thursday, November 20, 2014 11:22 AM
To: [email protected]
Subject: [qmailtoaster] Re: qmail-dk and DKIM status
On 11/18/2014 03:40 PM, Helmut Fritz wrote:
I ran into an issue with the dreaded and familiar "Transaction failed
554 qmail-dk: Cannot sign message due to invalid message syntax.
(#5.3.0)".
I checked and sure enough my system was using qmail-dk. I had 'fixed'
that years ago, but I have recently updated my toaster (with the clamav
release). So if I do a complete rebuild it seems to put this back to
default?
I thought DKIM was going to be disabled in the toaster until working?
did it slip back in somehow?
Also, what is the status of this? are we just going to say goodbye to
DKIM? Is it really needed? My guess is no since most of us are
probably doing without it? or did I miss something somewhere?
Thx!
Helmut
I'd have to look at the qmail.spec file to know for sure what the
default is. I know I left the program in the package just in case
someone was using it successfully.
DKIM would be nice to have, but it's not necessary. DKIM is preferred
these days, and the wiki has instructions for setting that up, although
I haven't done so myself.
I'm sorry if a reinstall broke your setup. If you'd care to modify the
spec so that the default doesn't use it, feel free to do so and issue a
pull request for the change. I'll be happy to have you do that.
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
