Re: [Indimail-support] dkim-status header
Brought to you by:
mbhangui
From: Fabian A. S. <fsa...@ga...> - 2017-03-21 16:45:07
|
On March 21, 2017 12:42:54 PM EDT, Manvendra Bhangui <mbh...@gm...> wrote: >On 21 March 2017 at 22:03, Fabian A. Santiago ><fsa...@ga...> wrote: >> On March 21, 2017 12:30:23 PM EDT, Manvendra Bhangui ><mbh...@gm...> wrote: >>>On 21 March 2017 at 21:45, Manvendra Bhangui <mbh...@gm...> >>>wrote: > >>>It is the same executable qmail-dkim which is used for both >>>verification and signing. >>>However there is no point in doing both together, even though it will >>>work. You should >>>either set verification or set signing. Hence it is not a good idea >to >>>use the same SMTP >>>server/port for serving incoming as well as outgoing emails. >>> >>>Here is a good documentation from Roberto for qmail-dkim (which I >>>submitted for netqmail). >>>You may find lot of information here >>>http://notes.sagredo.eu/comment/768#comment-768 >> >> For my purposes it shouldn't be an issue. Not very high volume plus >only have one box for everything. Unless you mean different smtpd >instances to handle each? >> >> I could look into that just for exploratory purposes if you can point >me to a guide for such setup. >> > >If DKIMSIGN is set, qmail-dkim will do signing only >If both are set, qmail-dkim will do signing > >Don't set DKIMSIGN in the smtpd.25 variables >Set it in qmail-send.25 variables, so that only emails that go to >qmail-local or qmail-remote >will get signed >For incoming emails what will happen is that DKIMVERIFY will happen at >smtp. >if you have the following line in /var/indimail/control/filterargs >control file >*:remote:/var/indimail/bin/dk-filter >Then only emails that go to qmail-remote will get signed > >In that case you need not set two smtpd instance on the same machine Excellent. That makes sense. Thanks. -- Thanks. Fabian S. |