similar to: Mail server troubles

On Thu, 8 Oct 2020 at 17:50, Nicolas Kovacs <info at microlinux.fr> wrote: > Hi, > > This is probably a bit OT, but here goes. > > I've been running our local school's mail server since 2013, with mail > addresses for school staff and some teachers. The server is running CentOS > 7 > with Postfix and Dovecot, and it's a nice no-bullshit configuration with

On 9/10/20 11:08 am, Stephen John Smoogen wrote: > On Thu, 8 Oct 2020 at 17:50, Nicolas Kovacs <info at microlinux.fr> wrote: > >> Hi, >> >> This is probably a bit OT, but here goes. >> >> I've been running our local school's mail server since 2013, with mail >> addresses for school staff and some teachers. The server is running CentOS

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

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:

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

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

Test from Yahoo via Android --Gene

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,

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

> 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

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

> 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

[sorry off-topic, ignore if uninterested in dmarc/dkim/mail filters] On 2024/07/17 22:14, mark.yagnatinsky at barclays.com wrote: > I don't know enough about DMARC to make any sense of what you just said... actually wait, maybe I get it. > You're saying that email sent that I send to the list will land in your inbox with my address in the From header. > But the recipient mail

Dear Admin, It seems that mails from our iit.ac.in domain are being marked as spam. It would be nice if something could be done about this. Best Regards Ramakrishna On Tue, Mar 24, 2015 at 1:12 AM, Aditya Kamath < adityakamath+llvmdev at gmail.com> wrote: > Hi all, > > (I received many emails that my posts were marked spam, so I am re-sending > this from another email address

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

Thanks for the reply, postfix + dovecot sasl configured and working properly. My question is about "adding dovecot authentication when sending emails via submission_host". 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 User foo at example.com has the following

I have a goal of securing email. Updated the company mail server and DNS (CentOS 7 + Postfix, otherwise pretty stock) with support for SPF, DKIM, and DMARC. So far, all good, and everything "just works". Our mail server has supported SMTP / TLS for a long time, but recently I've been considering requring TLS all the time. Is there anybody here who's done this? Has it