Hi Lucio,
On Mon 05/Oct/2015 17:53:50 +0200 Lucio Crusca wrote:
>
> I'm trying to add DKIM signatures to outgoing messages. I've followed this
> guide [1], but my feeling is that nothing is happening, as far as DKIM is
> concerned.
You should see a DKIM-Signature on outgoing mail, e.g. if you
Hello,
I'm trying to add DKIM signatures to outgoing messages. I've followed this
guide [1], but my feeling is that nothing is happening, as far as DKIM is
concerned.
How do I test my setup? Are there any logs that tell me what zdkimfilter is
doing?
1.
RFC 7489 was published last month. Using zdkimfilter 1.5 it is easy to meet
DMARC minimum implementation requirements --section 8 of the RFC. That section
stresses the ability to send and receive reports, which is the most noteworthy
addition with respect to ADSP. It makes mail servers of
The new version can interoperate better with other filters, as it can
reject/drop based on a header added by another filter, or install with a
different name so that another filter can reject/drop based on DKIM
verification.
See more detail at http://www.tana.it/sw/zdkimfilter/
Still no DMARC
On Fri 26/Jul/2013 22:08:58 +0200 Anders wrote:
By chance I compared the dkim=fail against what SpamAssassin said:
== courier log
Jul 26 21:45:47 e350 courierfilter:
zdkimfilter[12888]:id=00C804FC.51F2D1E6.3235:
verified: dkim=fail
On Mon 29/Jul/2013 09:12:12 +0200 I wrote:
On Fri 26/Jul/2013 22:08:58 +0200 Anders wrote:
By chance I compared the dkim=fail against what SpamAssassin said:
== courier log
Jul 26 21:45:47 e350 courierfilter:
zdkimfilter[12888]:id=00C804FC.51F2D1E6.3235:
So far, since I got zdkimfilter to work properly I have recieved som
dkim=pass (usually from gmail) and some dkim=fails.. All seems ok. By
chance I compared the dkim=fail against what SpamAssassin said:
== courier log
Jul 26 21:45:47 e350 courierfilter:
Hi,
On Wed 24/Jul/2013 00:17:17 +0200 Anders wrote:
So, now comes to testing it all... To summarize, no mails are signed
because I think that zdkimfilter can't find anything suitable to match
domain/selector against. What can be the cause?
I think that's because you set RELAYCLIENT based
Hi,
I'll comment in-line.
I am using zdkimfilter-1.2 , provided by gentoo ebuild/portage. Compiler
is gcc 4.7.3
Thank you very much.
~A
On 2013-07-24 11:13, Alessandro Vesely wrote:
Hi,
On Wed 24/Jul/2013 00:17:17 +0200 Anders wrote:
So, now comes to testing it all... To summarize, no
On Wed 24/Jul/2013 13:39:37 +0200 Anders wrote:
I'll comment in-line.
Yup :-)
I am using zdkimfilter-1.2 , provided by gentoo ebuild/portage. Compiler
is gcc 4.7.3
I haven't been able to find that version --see below.
I think that's because you set RELAYCLIENT based on the IP address,
On 2013-07-24 18:10, Alessandro Vesely wrote:
On Wed 24/Jul/2013 13:39:37 +0200 Anders wrote:
I'll comment in-line.
Yup :-)
I am using zdkimfilter-1.2 , provided by gentoo ebuild/portage. Compiler
is gcc 4.7.3
I haven't been able to find that version --see below.
I think that's because
On Wed 24/Jul/2013 20:51:06 +0200 Anders wrote:
On 2013-07-24 18:10, Alessandro Vesely wrote:
The opendkim-2.2.2 version they used to build zdkimfilter seems to be
lost.
I realise I have a local overlay with zdkimfilter-1.2. I will revert to 1.1.
It won't get things better. Knowing the
Alright, it works now. Here is what I did:
* Install zdkimfilter-1.1 (perhaps not needed, but still)
* fix permissions on /etc/courier/filters/keys to be accessible by
courier user
* add ESMTPAUTH=PLAIN LOGIN to esmptd-msa...
Now it seems to work, both for verifying and signing! yay :)
~A
On
On 2013-07-24 21:25, Alessandro Vesely wrote:
On Wed 24/Jul/2013 20:51:06 +0200 Anders wrote:
On 2013-07-24 18:10, Alessandro Vesely wrote:
The opendkim-2.2.2 version they used to build zdkimfilter seems to be
lost.
I realise I have a local overlay with zdkimfilter-1.2. I will revert to 1.1.
Hi Anders,
On Sun 21/Jul/2013 13:23:16 +0200 Anders wrote:
Can someone contribute with some example configuration files for
zdkimfilter and courier, especially for signing outgoing mail.
something like this zone-file snippet?
beta._domainkey IN TXT ( v=DKIM1; k=rsa;
Thanks!
I reset my configs and followed Jérôme's installation tips from the
previous emails. It seems as something was odd with my bind config.
Apparently, I had to split the _domainkey TXT into several segments, or
bind would't add it.
So, now comes to testing it all... To summarize, no
Le 21/07/2013 13:23, Anders a écrit :
Hi!
Can someone contribute with some example configuration files for
zdkimfilter and courier, especially for signing outgoing mail. I have
tried to follow the information from the zdkimfilter website and the
man/config files but I can't get it to work,
Hi all,
new features of this release of zdkimfilter [Z] are as follows:
*Signing*
-
It is now possible to select the signing domain according to the value
of a configured header in the outgoing message.
*Verifying*
---
Statistics files. This requires OpenDKIM v2.2.0, released a
Hi all,
this to announce the new version, and also to confirm a feature of
global filtering that Sam has described last May.
*zdkimfilter 0.4*
In the new version ADSP failures are treated differently, as
summarized in the table below, where the failure condition is the
result of evaluating
On 29/Apr/10 06:25, Carlos Lopez wrote:
Site is not working :(, check it.
A mediaconverter burned out, for ip 85.18.98.155. Is been replaced
about 3 hours ago.
Carlos.
--- El mié, 4/28/10, Alessandro Veselyves...@tana.it escribió:
http://www.tana.it/sw/zdkimfilter/
I've extended the spf_whitelist option so as to accept
john@example.com in case example.com publishes a discard ADSP
policy and the signature has been broken by the whitelisted sender.
I've also removed the x- from x-dkim-adsp, in
Authentication-Results lines, and slightly modified adsp
Site is not working :(, check it.
Carlos.
--- El mié, 4/28/10, Alessandro Vesely ves...@tana.it escribió:
De: Alessandro Vesely ves...@tana.it
Asunto: [courier-users] zdkimfilter 0.3
A: Courier Users courier-users@lists.sourceforge.net
Fecha: miércoles, 28 de abril de 2010, 04:16 am
I've
In case anyone is using it, I've added an spf_whitelist option for
accepting messages that have From: john@nospam.example.com from
a few domains, while still rejecting the other non-existent From.
My stance is that a domain must get an SPF-MAILFROM pass to be
eligible for spf_whitelist
23 matches
Mail list logo
