You are correct. It will only sign emails with a From header with the
domain that you specified if:
a. it comes from a trusted ip
b. it comes via smtp auth
There are other configuration settings that can have some impact on
this signing decision. Your best bet is to enable LogWhy to see why
signing decisions are made the way they are (not real verbose, but it
at least lets you see that it decided not to sign or what made it
decide to sign).
Regards... Todd
On Sun, Dec 26, 2010 at 4:19 PM, Roman Gelfand <rgelfand2_at_gmail.com> wrote:
> Sorry for the false alarm. After looking around the opendkim config
> file, I found that single milter could serve both servers. Using
> Domain tag I made sure that only my domain gets signed and everything
> else fell in place.
>
> If I am wrong, please let me know.
>
> Thanks
>
> On Sun, Dec 26, 2010 at 5:57 PM, Roman Gelfand <rgelfand2_at_gmail.com> wrote:
>> My mta is postfix. My configuraiton is performing key verification
>> for incoming emails. I, also, would like opendkim to sign outgoing
>> emails. I have a separate smtpd for outgoing server which accepts
>> client connections on non standard port. I am not sure how to handle
>> this. My guess is create a new instance of dkim milter service with
>> it's own configuration file and listens on another port. Would this
>> work?
>>
>> If there is better way to do this, please let me know.
>>
>> Thanks in advance
>>
>
>
>
--
Regards... Todd
I seek the truth...it is only persistence in self-delusion and
ignorance that does harm. -- Marcus Aurealius
Received on Mon Dec 27 2010 - 01:02:47 PST