use 127.0.0.0/8 range for signers, and for wan only do verifying,
this only need opendkim-verify.conf and opendkim-signer.conf with is
binded in master.cf as services where it fit
For some reason second postfix refused to route mail out to wan ip
(loops back to myself) when i binded it only to
On 2014-02-04 07:53, Solk Maaker wrote:
Only downside is that this setup needs two ip addresses.
use 127.0.0.0/8 range for signers, and for wan only do verifying, this
only need opendkim-verify.conf and opendkim-signer.conf with is binded
in master.cf as services where it fit
You can do both on one machine using multiple postfix instances, one
for incoming mail and another for outgoing mail, each running on its
own IP. But since you already have multiple postfix instances on two
machines it seems silly to complicate a working setup for little
gain, unless you're tryin
On 2/3/2014 5:31 AM, Solk Maaker wrote:
>> From DKIM's perspective it really makes no sense to validate a
>> signature generated by yourself.
>> ( How often do you check your own identity card to prove that you
>> are you? )
>
> Yes, that is true, there is no point to verify my own signature, but
From DKIM's perspective it really makes no sense to validate a
signature generated by yourself.
( How often do you check your own identity card to prove that you are
you? )
Yes, that is true, there is no point to verify my own signature, but in
case of virtual domains, if domain1 does not belo
Solk Maaker:
If user sends mail from domain1 (virtual domain) to domain2 (virtual
domain) in same machine, mail is signed but signature is not
verified - not OK.
From DKIM's perspective it really makes no sense to validate a
signature generated by yourself.
( How often do you check you
Hi
Problem description:
If user sends mail out (to Internet) from domain1 (virtual domain),
mail is signed and in receiver side mail is verified - everything is OK.
If mail comes in (from Internet) to domain1 (virtual domain) wiht DKIM
signature, signature is verified - everything is OK.
If use
