similar to: Request to list owner

Hi, I have finally managed to implement the Sieve "foreverypart" and "mime" extensions (RFC 5703). These are now included in the main Mercurial repository and will be included in the next release. I will be fixing a few minor details in the coming week; e.g., interaction with "include" and "editheader" extensions needs more work. Still, in the mean time,

I see, If i need anything else i'll post, Thanks, > -----Original Message----- > From: Larry Rosenman [mailto:larryrtx at gmail.com] > Sent: segunda-feira, 13 de Outubro de 2014 21:05 > To: Jorge Bastos > Subject: Re: Compile dovecot with sieve/managesieve support > > Pigeonhole does ManageSieve as well...... > > On 10/13/14, Jorge Bastos <mysql.jorge at

Did we work out the technical reason why some users that post to the list are getting dumped into gmail spam? Ta, Andrew

I'm petty sure I messed up attributions, so am deleting them. >> I believe this is a DMARC issue. Yahoo, among other places, has set >> their dmarc records to p=reject: >> So, if your mail hosting provider enforces dmarc,(gmail does) and you >> get mail from a list that doesn't rewrite the headers, and people >> from places like yahoo post to the list,

On 06/17/2018 09:11 AM, Alice Wonder via CentOS wrote: > On 06/17/2018 08:52 AM, Michael Hennebry via CentOS wrote: >> I'm petty sure I messed up attributions, so am deleting them. >> >>>> I believe this is a DMARC issue. Yahoo, among other places, has set >>>> their dmarc records to p=reject: >> >>>> So, if your mail hosting provider

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

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 Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: > On Sun, Jan 4, 2015 at 9:27 AM, gene.cumm at yahoo.com <gene.cumm at yahoo.com> wrote: > > Test from Yahoo via Android > > > > --Gene > > _______________________________________________ > > Syslinux mailing list > > Submissions to Syslinux at zytor.com > > Unsubscribe or set options at:

Guys, Whats the best mailbox format: - dbox - mbox - maildir - ?!? Pros and cons? > -----Original Message----- > From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Jorge > Bastos > Sent: segunda-feira, 13 de Outubro de 2014 21:35 > To: dovecot at dovecot.org > Subject: RE: Compile dovecot with sieve/managesieve support > > I see, > > If i need

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 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

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

Hi all, There's a good chance that the people who most need to see this won't see it, but here goes anyway. Google is currently dropping a _lot_ of the mail we attempt to deliver to lists.fd.o subscribers. The immediate cause is sending on mail from domains with SPF/DKIM/DMARC policies which explicitly specify that lists.fd.o cannot relay mail on their behalf. Every time we do that, not

On Sun, Jan 04, 2015 at 07:37:44PM +0100, Geert Stappers wrote: > On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: <snip/> > > As far as I can tell, GMail does process the SPF/DKIM/DMARC properties > > but ignores Yahoo!'s DMARC policy to reject on failure. > > The Syslinux ML should now be ready for DMARC p=reject > > We shall see how

Test from Yahoo via Android --Gene

> On 29. Sep 2018, at 23:58, John R. Dennison <jrd at gerdesas.com> wrote: > > Save yourself the effort, time, headaches and eventual bloody tears of impotent > rage and just go with Google or some other provider. Running a mail > server properly is one of the more difficult tasks and quite often not > worth the time and trouble, especially if one is asking about it on a

> 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

I recently wrote to the list. The distributed message had the following headers: > Date: Fri, 16 Feb 2024 19:22:59 +0100 (CET) > From: Roger Price via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > Reply-To: Roger Price <roger at rogerprice.org> > To: nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org> > Subject: ... Note that the Reply-To

Jorge Bastos via dovecot skrev den 2019-11-13 22:00: > How can i have the same with dovecot SASL? > Thanks in advanced, https://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL Hi benny, Thanks, That's exactly what i have in postfix: smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes plus: smtpd_sasl_local_domain = fastmail but the user that i have