similar to: Mailman option "Set Reply-To header to list" unavailable

Am 09.02.19 um 19:56 schrieb Aki Tuomi via dovecot: > I'll review the settings when we manage to upgrade to mailman3 Hello Aki, before updating to mailman3 consider an simpler update to latest mailman2. you're using 2.1.15, current mailman2 is 2.1.29 Your missing an /significant amount/ of DMARC fixes! and: more off-topic: while my messages *to* the dovecot list are sent using

On 10/02/2019 07:38, Ralph Seichter via dovecot wrote: > * Juri Haberland via dovecot: > >> Blindly enabling DMARC checks without thinking about the consequences >> for themselves should not be the problem of other well behaving >> participants. > > Can you judge if DMARC is enabled "blindly"? No, I thought not. Also, > the issue was not on the

On 09/02/2019 10:44, Aki Tuomi via dovecot wrote: > For some reason mailman failed to "munge from" for senders with dmarc policy ;( > > It's now configured to always munge to avoid this again. I'd say, let Mailman throw all people off the list that have enabled DMARC checking without using exceptions for the lists they are on. It's a known fact that DMARC does not

Hello Together Please i have new following Error, from DMARC Report, if i check my domain on example mxtoolbox i dont see any problems. Any from you know this Eror report, what i need to do to fix this issue? C:\folder>nslookup 94.237.32.243 Server: dns204.data.ch Address: 211.232.23.124 Name: wursti.dovecot.fi Address: 94.237.32.243

Just reading up on DMARC, toying with setting it up to auth against incoming emails. (but not configure my domain to use dmarc, or at least not yet) ran into an article about opendmarc, which is available on epel. but when I took a look at the opendmarc website and the git pages it doesn't appear to have been updated in several years. while I see that it is still available from epel, I

On 10/02/2019 12:49, Benny Pedersen via dovecot wrote: > fixing mailman will be the fail, solve it by letting opendkim and opendmarc not reject detected maillist will be solution, A general broad mailing list whitelist will be problematic, do work it needs to look for specific list type hidden headers, spammers and nasties will incorporate those headers into their trash that impersonates

Hi all I have dovecot-lda set up to run as vmail:vmail, with some sieve scripts in /var/lib/dovecot/sieve. The sieve scripts fail to be found with the following (detailed and very helpful) error message: Oct 14 16:13:33 gatekeeper dovecot[8109]: lda(minfrin at example.com)<8109><ZJ9nMo0Hh1+tHwAAKdTwig>: Error: sieve: file storage: Failed to stat sieve storage path:

On 2/10/19 3:46 PM, Michael A. Peters via dovecot wrote: > On 2/10/19 3:42 PM, Noel Butler via dovecot wrote: >> On 10/02/2019 12:49, Benny Pedersen via dovecot wrote: >> >>> >>> fixing mailman will be the fail, solve it by letting opendkim and >>> opendmarc not reject detected maillist will be solution, >> >> >> A general broad mailing

I just got this On 9 Feb 2019, at 00:00, dovecot-request at dovecot.org wrote: > Your membership in the mailing list dovecot has been disabled due to > excessive bounces The last bounce received from you was dated > 02-Feb-2019. You will not get any more messages from this list until > you re-enable your membership. You will receive 1 more reminders like > this before your

Am 30.05.2018 um 18:08 schrieb SATOH Fumiyasu: > Hi! > > On Thu, 31 May 2018 00:44:58 +0900, > A. Schulze wrote: >> When running multiple instances of dovecot on the same host (or running multiple docker container), >> it is hard to distinguish logs from different processes: the syslog entries are all prefixed with the same identifier "dovecot" >> It is

> On 29/05/2020 20:12 Ralph Seichter <abbot at monksofcool.net> wrote: > > > * David Mehler: > > > I'd ideally like to back up all the mails in the maildir location, > > copy that over, load in my configuration files, and bring the system > > back up. > > I don't think this qualifies as "ideal" for migration. My recommendation

Hi guys, when I send e-mails to CentOS mailing list <centos at centos.org>, I received DMARC / DKIM failure reports. Is it possible to solve this problem and if so how? This is the first report: This is an email abuse report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:25 +0200. The message below did not meet the sending domain's DMARC policy. For

In the same vein, I am receiving forensic DMARC reports from mx01.nausch.org. Whenever I send a message to the mailing list or when my server sends a DMARC report, I'm getting a DMARC Forensic report. It's odd, because the actual report tells me both DKIM and SPF (in the the of a DMARC report) pass... Here is what I am getting : This is an authentication failure report for an email

On Tue, 18 Jun 2019 at 01:35, Ralph Seichter via dovecot < dovecot at dovecot.org> wrote: > * Odhiambo Washington via dovecot: > > > Is it possible? How do I do it for ALL mailboxes? > > This has been asked (and answered) recently; see the Dovecot Wiki. > > -Ralph > Could you kindly point me to the exact article in the wiki, please? -- Best regards, Odhiambo

so... I've got some mailman lists running on centos 6. apparently c6 has mailman 2.1.12, which is far too old to have the dmarc patches (introduced in 2.1.16 and updated in 2.1.??, so of course, I'm having ongoing issues with yahoo/sbc/att/aol/etc subscribers and bouncing messages ending up causing 30%+ of my subscribers not to be able to get mail. These are mostly non-technical

* mj: > Our autoreply message reads: "Your email has not been read nor > forwarded", which is also the case, forcing the sender to take action. No, it does not. An auto-reply message, even if it is actually read by the sender, can be ignored without penalty. An MTA rejection puts the ball into the sender's court because the message has never been accepted by the

Hi all, We have hit another step change in aggressive anti-spam techniques from major mail providers. Over the past few days, we saw a huge spike in the number of mails we were failing to deliver to GMail and outlook.com in particular. It looks like it is now no longer acceptable for us to break DMARC/DKIM/SPF. These are DNS-based extensions to SMTP, which allow domains to publish policies as to

Hi all, We have hit another step change in aggressive anti-spam techniques from major mail providers. Over the past few days, we saw a huge spike in the number of mails we were failing to deliver to GMail and outlook.com in particular. It looks like it is now no longer acceptable for us to break DMARC/DKIM/SPF. These are DNS-based extensions to SMTP, which allow domains to publish policies as to

Hi Ralph! Thanks for your reply! On 4/20/20 12:19 PM, Ralph Seichter wrote: > I suggest you don't use Sieve for this, but simply configure Postfix > to reject messages to @old.domain.com with the desired message. MTA > rejections signal clearly that the message has not been delivered, and > you can also include an URL pointing to a web page with more detailed > information.

Noel Butler via dovecot skrev den 2019-02-10 01:51: > ... and surely he does not expect those with a million plus users sit > here and whitelist the million plus mailing lists that exist around > the world, heh, like thats going to happen :) fixing mailman will be the fail, solve it by letting opendkim and opendmarc not reject detected maillist will be solution, even if openarc comes