Re: OpenDMARC 1.4.1 Released

On 2021-04-30 23:07, Xavier Belanger wrote: https://github.com/trusteddomainproject/OpenDMARC/archive/refs/heads/master.zip always latest tags ? cleanup would be nice there

Re: OpenDMARC 1.4.1 Released

On 2021-04-30 22:08, John Levine wrote: It appears that Benny Pedersen said: On 2021-04-30 18:34, John Levine wrote: We've just released OpenDMARC 1.4.1 over at https://github.com/trusteddomainproject/OpenDMARC Care to try again? sure follow the above url, first step at left press mast

Re: Postfix stable release 3.6.0

> On Apr 30, 2021, at 2:38 PM, Demi Marie Obenour wrote: > > Is it possible for mail to be lost and/or mishandled as a result, or > will the mess resolve itself when Postfix is restarted? No mail will be lost, some could be delayed. -- Viktor.

Re: OpenDMARC 1.4.1 Released

> On Apr 30, 2021, at 2:58 PM, John R. Levine wrote: > >> Fair warning, we’re likely to relese a 1.4.1.1 shortly to cover a minor >> gaffe that happened when we merged our “develop” branch back to “master”. >> >> We are also trying to clear up the fact that sourceforge is stuck on an >> olde

Re: OpenDMARC 1.4.1 Released

Fair warning, we’re likely to relese a 1.4.1.1 shortly to cover a minor gaffe that happened when we merged our “develop” branch back to “master”. We are also trying to clear up the fact that sourceforge is stuck on an older version, and trusteddomain.org claims 1.3.x

Re: Postfix stable release 3.6.0

Demi Marie Obenour: > Is it possible for mail to be lost and/or mishandled as a result, or > will the mess resolve itself when Postfix is restarted? > > Demi Oh ye of little faith. Wietse

Re: OpenDMARC 1.4.1 Released

Fair warning, we’re likely to relese a 1.4.1.1 shortly to cover a minor gaffe that happened when we merged our “develop” branch back to “master”. We are also trying to clear up the fact that sourceforge is stuck on an older version, and trusteddomain.org claims 1.3.x

Re: OpenDMARC 1.4.1 Released

Hi, John Levine wrote: > I cloned the github repo which contains no zip files, so no I don't know that. Cloning the repository will indeed not create a zip file, you must use the GitHub web interface to get access to it. Click on the green 'code' button on the right, then on the "Download ZIP"

Re: OpenDMARC 1.4.1 Released

It appears that Benny Pedersen said: >On 2021-04-30 18:34, John Levine wrote: > >>> We've just released OpenDMARC 1.4.1 over at >>> https://github.com/trusteddomainproject/OpenDMARC >> >> Thanks. Is there a downloadable tarball available? Sourceforge only >> has 1.3.2 > >the zip file is on git

Re: Postfix stable release 3.6.0

On 4/30/21 8:44 AM, Wietse Venema wrote: > @lbutlr: >> On 29 Apr 2021, at 17:05, Wietse Venema wrote: >>>This release requires "postfix stop" before updating, or before >>>backing out to an earlier release, because some internal protocols >>>have changed. Otherwise, long-running daemon

Re: Postfix stable release 3.6.0

> On 30 Apr 2021, at 18:15, Rob McGee wrote: > > Perhaps you are confused because of your distributor's abstraction of > postfix(1) commands? There is no "postfix restart" command. There is > [among others] reload, start, and stop. You need to do whatever > translates to "postfix stop" and t

Re: OpenDMARC 1.4.1 Released

On 2021-04-30 18:34, John Levine wrote: We've just released OpenDMARC 1.4.1 over at https://github.com/trusteddomainproject/OpenDMARC Thanks. Is there a downloadable tarball available? Sourceforge only has 1.3.2 the zip file is on github hopefully you did know that :) but postfix/sendma

Re: OpenDMARC 1.4.1 Released

It appears that Dan Mahoney (Gushi) said: >Hey there, > >A cross post because there's enough dmarc discussion to be relevant. > >We've just released OpenDMARC 1.4.1 over at >https://github.com/trusteddomainproject/OpenDMARC Thanks. Is there a downloadable tarball available? Sourceforge only has

Re: Postfix stable release 3.6.0

Wietse Venema: > Peter: > > On 30/04/21 11:05 am, Wietse Venema wrote: > > > Postfix stable release 3.6.0 is available. This ends the support > > > for legacy release Postfix 3.2. > > > > > > To keep the old postscreen logging set "respectful_logging = > > > no" in main.cf before setting

Re: Postfix stable release 3.6.0

On 1/05/21 4:08 am, Wietse Venema wrote: Did you mean: postfix/postscreen[22642]: Using backwards-compatible default setting respectful_logging=no for client [address]:port Yes, that. I see what is the problem. This message is logged for actions in postscreen.c, but it is missi

Re: Postfix stable release 3.6.0

Peter: > On 30/04/21 11:05 am, Wietse Venema wrote: > > Postfix stable release 3.6.0 is available. This ends the support > > for legacy release Postfix 3.2. > > > > To keep the old postscreen logging set "respectful_logging = > > no" in main.cf before setting "compatibility_level = 3.6".

Re: Postfix stable release 3.6.0

On 30/04/21 11:05 am, Wietse Venema wrote: Postfix stable release 3.6.0 is available. This ends the support for legacy release Postfix 3.2. To keep the old postscreen logging set "respectful_logging = no" in main.cf before setting "compatibility_level = 3.6". In any case, the old

Re: Postfix stable release 3.6.0

On 2021-04-30 02:18, @lbutlr wrote: On 29 Apr 2021, at 17:05, Wietse Venema wrote: This release requires "postfix stop" before updating, or before backing out to an earlier release, because some internal protocols have changed. Otherwise, long-running daemons (pickup, qmgr, verify,

Re: Postfix shows unknown instead of resolved hostname

> From the times I was using sendmail, I remember that in case when > forward/reverse DNS didn't match, sendmail logged something like > unknown (reverse.dns.hostname) [ip.ad.dr.ess] Log? relay=hedefserver.com [2.56.152.122] (may be forged) Or are you talking about the Received: header? Received

Re: Postfix stable release 3.6.0

@lbutlr: > On 29 Apr 2021, at 17:05, Wietse Venema wrote: > >This release requires "postfix stop" before updating, or before > >backing out to an earlier release, because some internal protocols > >have changed. Otherwise, long-running daemons (pickup, qmgr, > >verify, tlsproxy, po

Re: Postfix stable release 3.6.0

On 29 Apr 2021, at 17:05, Wietse Venema wrote: >This release requires "postfix stop" before updating, or before >backing out to an earlier release, because some internal protocols >have changed. Otherwise, long-running daemons (pickup, qmgr, >verify, tlsproxy, postscreen) may fail