similar to: Dovecot list breaks DKIM.

On 2019-09-17 09:06, Miroslav Geisselreiter wrote: > 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? > That is why DMARC took 10 years of heated discussions, before it was actually implemented - in first place by big boys who will never

Thanks for the pointer! That didn't work though, but what worked was: [Service] ReadWriteDirectories=/home/dovecot What would be the preferred directory for storing all virtual mail without modification to system files? Thanks! Reio On 01.02.2018 21:57, Aki Tuomi wrote: > /etc/systemd/system/dovecot.service.d/writable-home.conf > > [Service] > ProtectHome=false > > >

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

Hello Aki and everyone, "Increase memory, your cache takes more memory than you have anticipated." What setting do I need to update in dovecot? I hope your not talking about the vps it has 4GB of ram. Thanks. Dave. On 4/12/18, Reio Remma <reio at mrstuudio.ee> wrote: > Hey, > > maybe it's like Aki said, you need more memory. :) Other than that I > can't

Hello! I noticed these in the logs since upgrading from 2.3.6. to 2.3.7: Jul 13 11:52:10 turin dovecot: doveadm: Error: dsync-remote(reio at mrstuudio.ee)</1ekE7qbKV2gYwAAsNnMGQ>: Error: Exporting mailbox INBOX failed: Mailbox attribute vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox attributes not enabled Jul 13 11:52:11 turin dovecot: doveadm: Error:

Greetings! I'm having a bit of trouble trying out Dovecot 2.3 on CentOS 7. Dovecot 2.2.33 works fine on the same system (same config as well, minus the SSL changes) but after upgrading to 2.3 I'm getting the following errors: Feb? 1 21:30:18 localhost dovecot: imap(reio at bwo.mrstuudio.ee)<3566><FoOsnStkXt4KAAgC>: Debug: INBOX.Templates: Mailbox opened because: STATUS

/etc/systemd/system/dovecot.service.d/writable-home.conf [Service]ProtectHome=false maybe this helps? ---Aki TuomiDovecot oy -------- Original message --------From: Reio Remma <reio at mrstuudio.ee> Date: 01/02/2018 21:44 (GMT+02:00) To: dovecot at dovecot.org Subject: Dovecot 2.3 on CentOS 7. Greetings! I'm having a bit of trouble trying out Dovecot 2.3 on CentOS 7. Dovecot 2.2.33

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

Hello, Thanks for the info and workaround! I found and have the same problems after read your mail :-(. Am Samstag, 13. Juli 2019, 11:13:23 CEST schrieb Reio Remma via dovecot: > Hello! > > I noticed these in the logs since upgrading from 2.3.6. to 2.3.7: > > Jul 13 11:52:10 turin dovecot: doveadm: Error: > dsync-remote(reio at mrstuudio.ee)</1ekE7qbKV2gYwAAsNnMGQ>:

Greetings, I have found an issue in the interaction between sieve vacation messages and the SPF, DKIM and DMARC email validation systems. For example, let's say we have a message coming from a at a.com to b at b.com at a server imap.mydomain.com. The account b at b.com has a vacation rule in sieve, and that generates an autoresponse to a at a.com. Our problem begins with the definition

> On 27/04/2020 12:35 Reio Remma <reio at mrstuudio.ee> wrote: > > > On 27.04.2020 12:15, Reio Remma wrote: > > Hello! > > > > Over the weekend I converted our Dovecot server from Maildir quota to > > MySQL backed quota and then provisioned a fresh replica server and > > seeded it via Dovecot replication. > > > > This morning most

On Thu, Jul 18, 2024 at 5:14?AM Stuart Henderson <stu at spacehopper.org> wrote: > The mail admins can choose what is covered by the DKIM signature. > In the case of barclays.com there are various headers (which I think > make it through the mailing list untouched) but also the body, which > does not; a footer with the list URL is added. The real issue here is that the Mailman

> On 16/07/2019 18:40 Stuart Henderson via dovecot <dovecot at dovecot.org> wrote: > > > On 2019-07-13, Reio Remma via dovecot <dovecot at dovecot.org> wrote: > > Hello! > > > > I noticed these in the logs since upgrading from 2.3.6. to 2.3.7: > > > > Jul 13 11:52:10 turin dovecot: doveadm: Error: > > dsync-remote(reio at

I was wondering about that myself, but then I couldn't find any info on quota = in the wiki. Please update: https://wiki2.dovecot.org/Quota :) Thanks, Reio On 17/09/2018 08:57, Aki Tuomi wrote: > You did everything except actually enable quota... =) > > Try adding this to your configuration > > quota = count:User quota > quota_vsizes = yes > > inside the

> Let's say we have dovecot + sieve plugin container. > Dovecot configured to use remote SMTP submission host to send messages: > submission_host = postfix.example.com:587 I reviewed my config to see how i did it. I think you are right and SASL isn't used here. I have dovecot and postfix on the same machine and in dovecot i set submission_host = localhost:25 Then in my

You should read it more carefully.? See the 'Configuration' section. Aki On 17.09.2018 09:31, Reio Remma wrote: > I was wondering about that myself, but then I couldn't find any info > on quota = in the wiki. > > Please update: > > https://wiki2.dovecot.org/Quota > > :) > > Thanks, > Reio > > On 17/09/2018 08:57, Aki Tuomi wrote: >> You

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

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

I have a problem with understanding dmarc reports and some features. I attach two reports. First one come from google.com, second one from tumieszkamy.pl. On my server is dns zone of domain kamir-transport.pl but whole mail service is deployed on Google - in dns zone MX points to Google and there are all mailboxes, aliases etc. Last time I have configured dkim and dmarc policies and I got two