On Thu, Mar 09, 2023 at 01:21:02PM -0500, postfix--- via Postfix-users
wrote:
> > I am still seeing DKIM fails and two DKIM-Signatures.
> > Is this correct? Haven´t seen this with other mails but I cannot rule out a
> > config issue on my side. Is someone else observing that?
>
> Yes there
Unfortunately, due to company policy, I can only work with RPM packages from
either the default repo or EPEL and nothing else. I know several other
companies that have the same rule. Its not something that I can change, so I
work with what I have.
On Fri, 10 Mar 2023 11:14:14 -0500 PGNet
On Fri, 2023-03-10 at 17:35 +0200, mailmary--- via Postfix-users wrote:
>
> Looking at the opendkim/opendmarc right now, they appear dead over the past 2
> years or so, which is sad really.
>
It's not sad at all. It's a testament to the stability of the project.
Sure, both projects could use
Thanks. As of a few minutes ago there's a dkimpy 1.1.1, although there aren't
any changes that will affect you one way or the other if you're using it for
dkimpy-milter.
thx,
Name: dkimpy
Version: 1.1.1
Name: dkimpy-milter
Version: 1.2.3
the 'hardest' part
On 3/10/23 11:13, Curtis Maurand via Postfix-users wrote:
On 3/7/23 15:36, Bernardo Reino via Postfix-users wrote:
rspamd does DKIM, SPF, DMARC and ARC (and lots more), and doesn't
segfault (so far ;-)
I've been running rspamd for nearly a year and I've been very happy with
it. It's a huge
On 3/8/23 15:30, Scott Techlist via Postfix-users wrote:
On Tue, 7 Mar 2023, John Stoffel via Postfix-users wrote:
So what's the option for a more upto date version of DKIM milter for debian?
rspamd does DKIM, SPF, DMARC and ARC (and lots more), and doesn't segfault (so
far ;-)
I'm STILL
The problem with dkimpy/dkimpy-milter, is that they don't exist in enterprise
distros (Alma, Rocky, Oracle) via EPEL.
FWIW, it's a trivial install with python/pip, and plays nicely in a venv.
works a charm here.
rpm spec's also straightforward.
here's one for Fedora,
On 3/7/23 15:36, Bernardo Reino via Postfix-users wrote:
On Tue, 7 Mar 2023, John Stoffel via Postfix-users wrote:
So what's the option for a more upto date version of DKIM milter for
debian?
rspamd does DKIM, SPF, DMARC and ARC (and lots more), and doesn't
segfault (so far ;-)
I've
The problem with dkimpy/dkimpy-milter, is that they don't exist in enterprise
distros (Alma, Rocky, Oracle) via EPEL.
The popularity of opendkim/opendmarc is due to their packages being available
via EPEL.
Looking at the opendkim/opendmarc right now, they appear dead over the past 2
years
* Scott Kitterman via Postfix-users :
That would be great. I started dkimpy-milter for two reasons: I wanted to
experiment with the new DKIM crypto types that lead to RFC 8463 and there
didn't seem to be much activity with opendkim maintenance (this is, of course,
ironic given how well I did
On Wednesday, March 8, 2023 1:52:47 AM EST Patrick Ben Koetter via Postfix-
users wrote:
> * Scott Kitterman via Postfix-users :
>
> ...
>
>
> > For Debian, if someone can find/test patches, I can get them into Debian's
> > package. I assume other distributors are similar. Feel free to update
I am still seeing DKIM fails and two DKIM-Signatures.
Is this correct? Haven´t seen this with other mails but I cannot rule out a
config issue on my side. Is someone else observing that?
Yes there will be two DKIM signatures due to the configuration of the mailing
list.
The first DKIM
We'll generate a new 2024 Bit key pair and place the new key in DNS. When we
do that we'll also see to fix the h=sha256 problem. This will take place
within the next 12 hours. Mailman will be restarted in the end and the service
will be unavailable for about 30 seconds. No list mail will be lost.
We'll generate a new 2024 Bit key pair and place the new key in DNS. When we
do that we'll also see to fix the h=sha256 problem. This will take place
within the next 12 hours. Mailman will be restarted in the end and the service
will be unavailable for about 30 seconds. No list mail will be lost.
Michael wrote in
<0d3709b8-72ae-4e54-a8a5-5a82f3b09...@hemathor.de>:
|On Thursday, 9 March 2023 15:29:01 CET, Wietse Venema via Postfix-users
|wrote:
|> Let me help remind you that your email address has been out there
|> for a while. Here are some samples from the postfix-users list:
|
|i
On 3/8/23 17:44, Phil Stracchino via Postfix-users wrote:
OK, this is very useful information that's not obvious from the
documentation. I have taken a leap of faith and made the tiny handful
of Postfix configuration changes necessary to let Rspamd handle all of
DKIM, DMARC, SPF instead of
hey,
On Thursday, 9 March 2023 15:29:01 CET, Wietse Venema via Postfix-users
wrote:
Let me help remind you that your email address has been out there
for a while. Here are some samples from the postfix-users list:
i am totally aware of that. and to be clear: my email address being public
Michael via Postfix-users:
> wietse,
>
> On Monday, 6 March 2023 17:08:49 CET, Wietse Venema wrote:
> > This week, the Postfix mailing lists will be migrated from Majordomo at
> > Cloud9.net to Mailman at Sys4.de.
> > [...]
>
> what a coincidence!
Let me help remind you that your email address
Michael via Postfix-users skrev den 2023-03-09 11:57:
On Monday, 6 March 2023 17:08:49 CET, Wietse Venema wrote:
This week, the Postfix mailing lists will be migrated from Majordomo
at
Cloud9.net to Mailman at Sys4.de.
[...]
what a coincidence!
wietse,
On Monday, 6 March 2023 17:08:49 CET, Wietse Venema wrote:
This week, the Postfix mailing lists will be migrated from Majordomo at
Cloud9.net to Mailman at Sys4.de.
[...]
what a coincidence!
since 'Monday, 6 March 2023 00:02:20 CET' i see multiple attempts to login
to this email
On 3/8/23 16:02, Bernardo Reino via Postfix-users wrote:
Here some quick notes from my configuration (related to SPF/DKIM/DMARC checking,
i.e. when receiving e-mails):
SPF and DKIM are enabled by default, and at least I didn't need to have any
local config (which would go in
> "Phil" == Phil Stracchino via Postfix-users
> writes:
> On 3/7/23 15:36, Bernardo Reino via Postfix-users wrote:
>> On Tue, 7 Mar 2023, John Stoffel via Postfix-users wrote:
>>
>>> So what's the option for a more upto date version of DKIM milter for debian?
>>
>> rspamd does DKIM,
On Wed, 8 Mar 2023, Phil Stracchino via Postfix-users wrote:
On 3/7/23 15:36, Bernardo Reino via Postfix-users wrote:
On Tue, 7 Mar 2023, John Stoffel via Postfix-users wrote:
So what's the option for a more upto date version of DKIM milter for
debian?
rspamd does DKIM, SPF, DMARC and
If there’ a pull request to get it into the current “develop” branch of
opendmarc, I have the privs to merge it.
-Dan
> On Mar 8, 2023, at 11:14 AM, Peter Ajamian via Postfix-users
> wrote:
>
> On 9/03/23 08:11, Peter wrote:
>> On 8/03/23 15:46, Scott Kitterman via Postfix-users wrote:
>>>
>> On Tue, 7 Mar 2023, John Stoffel via Postfix-users wrote:
>>
>>> So what's the option for a more upto date version of DKIM milter for debian?
>>
>> rspamd does DKIM, SPF, DMARC and ARC (and lots more), and doesn't segfault
>> (so
>> far ;-)
>
>
>I'm STILL trying to figure out rspamd's
On 3/7/23 15:36, Bernardo Reino via Postfix-users wrote:
On Tue, 7 Mar 2023, John Stoffel via Postfix-users wrote:
So what's the option for a more upto date version of DKIM milter for debian?
rspamd does DKIM, SPF, DMARC and ARC (and lots more), and doesn't segfault (so
far ;-)
I'm STILL
On 8/03/23 10:40, postfix--- via Postfix-users wrote:
I am using RHEL8 and after checking for updates I was able to update
opendmarc to 1.4.2 (from 1.4.1) however it still has the error, only
with mail from this list.
In the mean time as suggested, I added "list.sys4.de" to the ignorelist
to
On 9/03/23 08:11, Peter wrote:
On 8/03/23 15:46, Scott Kitterman via Postfix-users wrote:
For Debian, if someone can find/test patches, I can get them into
Debian's package. I assume other distributors are similar. Feel free
to update the Debian bug with information. It's unfortunate we
On 8/03/23 15:46, Scott Kitterman via Postfix-users wrote:
For Debian, if someone can find/test patches, I can get them into Debian's
package. I assume other distributors are similar. Feel free to update the
Debian bug with information. It's unfortunate we don't have a better
maintained
On 8/03/23 10:54, postfix--- via Postfix-users wrote:
No solution so far, I think there are 2-3 open bug reports on
github, but since the project is very dead, nobody has bothered to
fix the problem.
So what's the option for a more upto date version of DKIM milter for
debian?
And what would
We'll generate a new 2024 Bit key pair and place the new key in DNS. When we
do that we'll also see to fix the h=sha256 problem. This will take place
within the next 12 hours. Mailman will be restarted in the end and the service
will be unavailable for about 30 seconds. No list mail will be lost.
* Viktor Dukhovni via Postfix-users :
> On Wed, Mar 08, 2023 at 07:42:56AM +0100, Patrick Ben Koetter via
> Postfix-users wrote:
>
> > - The key material is 4096 Bit and it was brought to my attention there's a
> > bug / missing functionality (?) in opendmarc which results in the program
> >
On Wed, Mar 08, 2023 at 07:42:56AM +0100, Patrick Ben Koetter via Postfix-users
wrote:
> - The key material is 4096 Bit and it was brought to my attention there's a
> bug / missing functionality (?) in opendmarc which results in the program
> being unable to handle keys at sizes larger than
* Scott Kitterman via Postfix-users :
...
> For Debian, if someone can find/test patches, I can get them into Debian's
> package. I assume other distributors are similar. Feel free to update the
> Debian bug with information. It's unfortunate we don't have a better
> maintained solution.
* postfix--- via Postfix-users :
> > > > OpenDMARC is segfaulting. That's what 'signal 11' means. Postfix fails
> > > > to get an answer to its end-of-body milter call because of the segfault
> > > > closing the other end of that socket. That failure results in Postfix
> > > > sending a 4xx to
On March 7, 2023 11:37:53 PM UTC, Phil Stracchino via Postfix-users
wrote:
>On 3/7/23 15:28, John Stoffel via Postfix-users wrote:
>>> "mailmary---" == mailmary--- via Postfix-users
>>> writes:
>>
>>> Unfortunately I've seen this crash as well, its actually quite
>>> frequent in my
On 3/7/23 15:28, John Stoffel via Postfix-users wrote:
"mailmary---" == mailmary--- via Postfix-users
writes:
Unfortunately I've seen this crash as well, its actually quite
frequent in my case and I'm using a newer version of OpenDMARC than
you:
# opendmarc -V
opendmarc: OpenDMARC Filter
No solution so far, I think there are 2-3 open bug reports on
github, but since the project is very dead, nobody has bothered to
fix the problem.
So what's the option for a more upto date version of DKIM milter for debian?
And what would be a dmarc replacement or solution for RHEL systems?
Steffen Nurpmeso wrote in
<20230307214046.ajvsx%stef...@sdaoden.eu>:
|The nice thing about this new list server is that it plays very
The ugly that it uses this terrible "Who via LIST "
stuff even if the sender does not (granted: yet) uses DKIM.
--steffen
|
|Der Kragenbaer,The
The nice thing about this new list server is that it plays very
well with gray listing (without causing the immediate "retry
storms" that sometimes can be seen, especially with German service
providers which do nothing but themselve perform address
verification, and are unfortunately used very
OpenDMARC is segfaulting. That's what 'signal 11' means. Postfix fails to get
an answer to its end-of-body milter call because of the segfault closing the
other end of that socket. That failure results in Postfix sending a 4xx to the
client.
First step is to verify your installation of
OpenDMARC is segfaulting. That's what 'signal 11' means.
On Mar 7, 2023, at 11:37 AM, postfix--- via Postfix-users
As far as i know everything is up to date.
[root]# opendmarc -V
opendmarc: OpenDMARC Filter v1.4.1
SMFI_VERSION 0x101
libmilter version 1.0.1
Active
On Tue, 7 Mar 2023, John Stoffel via Postfix-users wrote:
So what's the option for a more upto date version of DKIM milter for debian?
rspamd does DKIM, SPF, DMARC and ARC (and lots more), and doesn't segfault (so
far ;-)
Good luck.
___
No solution so far, I think there are 2-3 open bug reports on
github, but since the project is very dead, nobody has bothered to
fix the problem.
So what's the option for a more upto date version of DKIM milter for debian?
fwiw, for inbound DKIM, DMARC, ARC, etc, this
> "mailmary---" == mailmary--- via Postfix-users
> writes:
> Unfortunately I've seen this crash as well, its actually quite
> frequent in my case and I'm using a newer version of OpenDMARC than
> you:
> # opendmarc -V
> opendmarc: OpenDMARC Filter v1.4.2
> SMFI_VERSION 0x101
Unfortunately I've seen this crash as well, its actually quite frequent in my
case and I'm using a newer version of OpenDMARC than you:
# opendmarc -V
opendmarc: OpenDMARC Filter v1.4.2
SMFI_VERSION 0x101
libmilter version 1.0.1
Active code options:
> On Mar 7, 2023, at 11:37 AM, postfix--- via Postfix-users
> wrote:
>
>> OpenDMARC is segfaulting. That's what 'signal 11' means. Postfix fails to
>> get an answer to its end-of-body milter call because of the segfault closing
>> the other end of that socket. That failure results in Postfix
OpenDMARC is segfaulting. That's what 'signal 11' means. Postfix fails to get
an answer to its end-of-body milter call because of the segfault closing the
other end of that socket. That failure results in Postfix sending a 4xx to the
client.
First step is to verify your installation of
On 2023-03-07 at 13:27:41 UTC-0500 (Tue, 07 Mar 2023 13:27:41 -0500)
postfix--- via Postfix-users
is rumored to have said:
Reviewing logs I notice many soft bounces from the new list. Some
emails from the new list have been accepted and I don't understand
what the differences are. I have not
On 08/03/2023 01.09, Patrick Ben Koetter wrote:
* Phil Stracchino :
On 3/6/23 11:08, Wietse Venema wrote:
This week, the Postfix mailing lists will be migrated from Majordomo at
Cloud9.net to Mailman at Sys4.de. Thanks to Cloud9.net for hosting the
Postfix lists for 24 years, and thanks to
On 3/7/2023 12:27 PM, postfix--- via Postfix-users wrote:
Reviewing logs I notice many soft bounces from the new list. Some
emails from the new list have been accepted and I don't understand
what the differences are. I have not seen these types of errors
before and don't understand what is
=list.sys4.de[188.68.34.52]
Mar 7 13:18:57 host postfix/cleanup[1153970]: 4PWNxY2dFlz4l3gy:
message-id=<60a0790cfdbbe3f5c72786e4f6519...@ptld.com>
Mar 7 13:18:57 host postfix/cleanup[1153970]: 4PWNxY2dFlz4l3gy: info: header Subject: [P-U] Re:
Postfix lists are migrating to a new list serve
What date does this take effect and we start receiving list mail from the new
server host?
7th March 2023 (today), 12:35 UTC (approx 5 hours ago).
Oh, silly me. I thought they said a footer would be added when it happened.
Guess I read that wrong.
Looks like no issues and i didn't have to
Hi,
On 7 Mar 2023, at 18:21, postfix--- via Postfix-users wrote:
> What date does this take effect and we start receiving list mail from the new
> server host?
7th March 2023 (today), 12:35 UTC (approx 5 hours ago).
Greetings
Carsten
___
What date does this take effect and we start receiving list mail from the new
server host?
So we can keep an eye out to make sure no issues on our side, whitelisting if
needed.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe
* Harald Koch via Postfix-users :
> On Tue, Mar 7, 2023, at 12:02, Benny Pedersen via Postfix-users wrote:
> >
> > why is arc invalid ?
>
> My email provider is adding a little more detail:
>
> Authentication-Results: pb-mx20.pobox.com;
> arc=invalid
> (as.1.list.sys4.de=invalid
On Tue, Mar 7, 2023, at 12:02, Benny Pedersen via Postfix-users wrote:
>
> why is arc invalid ?
My email provider is adding a little more detail:
Authentication-Results: pb-mx20.pobox.com;
arc=invalid
(as.1.list.sys4.de=invalid (public key: does not support hash algorithm
'sha256'),
ption, unmoderated,
posting by members only."
So filtering on List-Id contents didn't work.
RobertC
From: Benny Pedersen via Postfix-users
Sent: Tuesday, March 7, 2023 11:02
To: postfix-users@postfix.org
Subject: [P-U] Re: Postfix lists are migrating to a new l
Patrick Ben Koetter via Postfix-users skrev den 2023-03-07 17:16:
I'll let Jörg at sys4 take a look at this.
+1
X-Spam-Status: No, score=-1.8 required=5.0
tests=ARC_INVALID,ARC_SIGNED,AWL,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_MISSING,
Gerald Galster via Postfix-users:
> The tab "Archiving" under "List Settings" offers "Archive policy":
> "Public archives", "Private archives", "Do not archive this list".
These settings are mutually exclusive, i.e. the setting "Private
archives" turns OFF "Do not archive this list".
The correct
Out of sheer curiosity ... Mailman 2 or 3?
>>>
>>> Mailman 3 with ARC support enabled. Additionally all listmail will be DKIM
>>> signed.
>>
>> Do you plan to enable a public archive at
>> https://list.sys4.de/hyperkitty/list/postfix-us...@de.postfix.org/
>> as an alternative to
; arc=fail
smtp.remote-ip=188.68.34.52
Received: from list.sys4.de (list.sys4.de [188.68.34.52]) by
fantomas.fantomas.sk (Postfix) with ESMTPS id 2ACE6A012C for
; Tue, 7 Mar 2023 17:17:35 +0100 (CET)
Subject: [P-U] Re: Postfix lists are migrating to a new list server
--
Matus UHLAR - fantomas, uh...@f
* Wietse Venema via Postfix-users :
> Gerald Galster via Postfix-users:
> >
> > >> Out of sheer curiosity ... Mailman 2 or 3?
> > >
> > > Mailman 3 with ARC support enabled. Additionally all listmail will be DKIM
> > > signed.
> >
> > Do you plan to enable a public archive at
> >
Gerald Galster via Postfix-users:
>
> >> Out of sheer curiosity ... Mailman 2 or 3?
> >
> > Mailman 3 with ARC support enabled. Additionally all listmail will be DKIM
> > signed.
>
> Do you plan to enable a public archive at
> https://list.sys4.de/hyperkitty/list/postfix-us...@de.postfix.org/
>> Out of sheer curiosity ... Mailman 2 or 3?
>
> Mailman 3 with ARC support enabled. Additionally all listmail will be DKIM
> signed.
Do you plan to enable a public archive at
https://list.sys4.de/hyperkitty/list/postfix-us...@de.postfix.org/
as an alternative to marc.info,
65 matches
Mail list logo