similar to: Dmarc

On Wed, 8 Mar 2017, Mark Weaver wrote: > Hello all, > > I've been googling my brains out since yesterday looking for up-to-date > information on this matter, and have found information that is anywhere from > 15 to 5 years old. I'd really like some information that much more up to date > on the subject. Specifically configuring Sendmail SMTP authentication (_no >

----- Forwarded message from Louis Kowolowski <louisk@bend.com> ----- Date: Thu, 28 Aug 2003 11:37:42 -0700 From: Louis Kowolowski <louisk@bend.com> To: freebsd-security@freebsd.org Subject: snort, postgres, bridge User-Agent: Mutt/1.5.4i I've been prowling through the FreeBSD and Snort list archives in search of information on setting up snort on a FreeBSD bridge(4) that logs

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 05/04/2019 08:57, David B?rgin via dovecot wrote: > Andr?, are you quite sure you have it working? > > In this thread someone from Open-Xchange stated that no, Dovecot doesn?t > have SMTPUTF8 support implemented, and the same response was given by > another Dovecot developer last September (it ?is being considered? was > the answer then, see >

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, It seems that there is an issue with the submission service when the SMTP server advertises chunking (I use Exim v4.91). I tried this with Dovecot v2.3.3 and current master and could reproduce it with both versions. My setup is that dovecot submission proxies to Exim on port 10025. The first mail gets through without any issues, but the second email will not get send. I had this issue at

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

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

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

On 2019-04-05 08:57, David B?rgin via dovecot wrote: > Andr?, are you quite sure you have it working? > > In this thread someone from Open-Xchange stated that no, Dovecot > doesn?t > have SMTPUTF8 support implemented, and the same response was given by > another Dovecot developer last September (it ?is being considered? was > the answer then, see >

/var/log/maillog showed this Oct 19 13:25:41 ns1 postfix/smtpd[1298]: 7599A2C19C6: client=unknown[127.0.0.1] Oct 19 13:25:41 ns1 postfix/cleanup[1085]: 7599A2C19C6: message-id=<edc55a9b-eb49-3945-dc60-0e1d51a78e97 at nbmlaw.co.uk> Oct 19 13:25:41 ns1 postfix/qmgr[1059]: 7599A2C19C6: from=<matthew.broadhead at nbmlaw.co.uk>, size=3190, nrcpt=1 (queue active) Oct 19 13:25:41 ns1

Op 10/20/2016 om 7:38 PM schreef Matthew Broadhead: > do i need to provide more information? > It still doesn't make sense to me. I do notice that the version you're using is ancient (dated 26-09-2013), which may well the problem. Do have the ability to upgrade? Regards, Stephan. > On 19/10/2016 14:49, Matthew Broadhead wrote: >> /var/log/maillog showed this >>

are there any instructions or tests i can make to check the sieve configuration? or does the magic all happen internally and there are no settings to change? On 21/10/2016 10:22, Matthew Broadhead wrote: > the server is using CentOS 7 and that is the package that comes > through yum. everything is up to date. i am hesitant to install a > new package manually as that could cause

it seemed like a simple configuration issue. i was hoping someone could point me in the right direction. seems i was wrong. i may as well unsubscribe this list as there is not much help here On 02/11/2016 18:29, Matthew Broadhead wrote: > is there something more i need to be doing my end? > > On 25/10/2016 09:11, Matthew Broadhead wrote: >> are there any instructions or tests

On 2/9/19 10:48 AM, Juri Haberland via dovecot wrote: > 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

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

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 list whitelist will be problematic, do work it > needs to look for specific list type

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 09 February 2019 at 20:48 Juri Haberland via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div>

do i need to provide more information? On 19/10/2016 14:49, Matthew Broadhead wrote: > /var/log/maillog showed this > Oct 19 13:25:41 ns1 postfix/smtpd[1298]: 7599A2C19C6: > client=unknown[127.0.0.1] > Oct 19 13:25:41 ns1 postfix/cleanup[1085]: 7599A2C19C6: > message-id=<edc55a9b-eb49-3945-dc60-0e1d51a78e97 at nbmlaw.co.uk> > Oct 19 13:25:41 ns1 postfix/qmgr[1059]: