Displaying 20 results from an estimated 6000 matches similar to: "Forcing TLS for SMTP?"
2019 Dec 04
2
Forcing TLS for SMTP?
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
2019 Dec 04
0
Forcing TLS for SMTP?
See bottom post below.
On Wednesday, December 4, 2019 2:24:51 PM PST Phil Perry wrote:
> On 04/12/2019 22:03, Lists wrote:
> > 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
2019 Dec 04
2
Forcing TLS for SMTP?
On 04/12/2019 22:03, Lists wrote:
> 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
2017 Aug 24
3
dmarc report faild ?
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
2013 Sep 05
2
Vacation message and DMARC validation
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
2024 Jul 20
2
openssh-unix-dev DMARC-related settings (was Re: scattered thoughts on connection sharing)
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
2019 Sep 17
0
OT: DMARC / DKIM Failure Reports
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
2023 Jan 17
1
submission_host auth
> 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
2019 Feb 11
3
[fdo] PSA: Mailman changes, From addresses no longer accurate
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
2019 Feb 11
3
[fdo] PSA: Mailman changes, From addresses no longer accurate
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
2017 Aug 24
3
dmarc report faild ?
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
2018 Nov 21
0
analysing of dmarc report
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
2019 Sep 17
2
OT: DMARC / DKIM Failure Reports
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
2020 Oct 08
0
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
2015 Apr 05
0
Some subscribers posts to the list ending up in Gmail spam
On 04/04/2015 09:59 AM, Andrew Holway wrote:
> Did we work out the technical reason why some users that post to the list
> are getting dumped into gmail spam?
>
> Ta,
>
> Andrew
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
It is most probably due to the various issues
2015 Jan 04
0
DMARC test
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:
> http://www.zytor.com/mailman/listinfo/syslinux
As some users may already be aware, my test
2015 Jan 04
4
DMARC test
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:
2015 Jan 17
0
DMARC test (request)
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
2018 Jun 17
0
Passwords in plain text
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 enforces dmarc,(gmail does) and you
>>> get mail from a list that doesn't
2018 Jun 18
0
Passwords in plain text
On 06/17/2018 11:13 AM, Alice Wonder via CentOS wrote:
> 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