On Mon, July 27, 2009 23:40, Stefan Förster wrote:
> I guess that's working as intended. A more specific match (here: the
> value of a mail's "From:" header) leading to a first-party signature
> takes precedence over a more general match (here: the rfc2822 message
> sender), which would result in
On Mon, July 27, 2009 23:40, Stefan Förster wrote:
> I guess that's working as intended. A more specific match (here: the
> value of a mail's "From:" header)
not so well for maillist domains, but for general use its okay as i see it
> leading to a first-party signature
> takes precedence over a
* Benny Pedersen wrote:
> On Mon, July 27, 2009 18:53, Benny Pedersen wrote:
>> signing based on From: not envelope_sender seems to be my problem,
>> tryed to test 2.6.4 witch also does this :(
>
> it signs with correct domain if from: is not a dkim signed domain
> from my testing, is it my amavi
On Mon, July 27, 2009 18:53, Benny Pedersen wrote:
> signing based on From: not envelope_sender seems to be my problem, tryed to
> test 2.6.4 witch also does this :(
it signs with correct domain if from: is not a dkim signed domain from my
testing, is it my amavisd.conf error or is it supposed
On Mon, July 27, 2009 16:56, Benny Pedersen wrote:
> i noticed today that mails sent to my maillist at lists.junc.info is signed
> with junc.org dkim key
> can some help me sort it out how i should debug this
> amavisd testkeys
> says all dkim keys pass
signing based on From: not envelope_sender
i noticed today that mails sent to my maillist at lists.junc.info is signed
with junc.org dkim key
can some help me sort it out how i should debug this
amavisd testkeys
says all dkim keys pass
--
xpoint
--
