Brandon Long via mailop writes:
> And even if you do block at smtp time, in forwarding situations you're
> just making someone else generate the backscatter... [...]
>
> And of course, those bounces going to a mailing list just cause havoc
> for some list providers, either greatly increasing
Anyone from HSBC HK here?
We're seeing issues from HSBC HK to Singapore (test either MX for
ofs.edu.sg). All connections from hsbc.com.hk abort after connect.
Nov 22 10:40:21 smtp6 sendmail[22604]: NOQUEUE: connect from psmtp5.hsbc.com.hk
[203.112.90.15]
Thanks!
Patrick
Hello,
Is anyone from Optimum here? Haven't had much luck reaching anyone regarding
delivery issues.
Please reach out offline.
Thanks,
Brian Kowalewicz
Hostopia.com
___
mailop mailing list
mailop@mailop.org
We have considered running dmarc checks on outbound to know if a message
will likely be rejected. We also considered it for the custom from setting
for Gmail before we decided that dmarc settings could change after setup.
It would make sense for an esp to check the sending configs for a customer
Hello guys,
We have the same issue since a couple of weeks on several IPs,
185.41.28.0/24 eg.
Messages are deferring due to too many concurrent connections and/or too
many sessions are opened. But, overall, we don't open more than 5 parallel
connections as recommended in Cox postmaster page:
There was nothing particularly useful or novel contained in the responses.
But as an ESP, we had no way of monitoring or tracking our senders' DMARC
reports. Heck, we had quite a few senders who had quarantine or reject
policies with no RUA or RUF addresses specified which is clearly there
problem
On Thu, Nov 21, 2019, Carl Byington via mailop wrote:
> My servers have Let's Encrypt certs for sendmail, and receive a fair bit
> of mail from mimecast.
Just to clarify: If I understand it correctly, there are configuration
options how to handle STARTTLS which mimecast customers can modify,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2019-11-21 at 17:09 +0100, Claus Assmann via mailop wrote:
> I wasted several hours to set up one host to get a Let's Encrypt cert,
> configured my server to use that for connections from mimecast, and
> ... still get the same error.
My
For an ESP, did the DMARC rejects contains information not available
elsewhere, or "just" put several relevant pieces of information in one place ?
On Thu, 21 Nov 2019, Luke via mailop wrote:
DMARC rejects had great utility in my time working at an ESP. They would
have little or no utility
On Thu, Nov 21, 2019, Steven Champeon via mailop wrote:
> We recently ran into this as well, via a longtime list member whose
> company decided to switch to mimecast. I just grudgingly disabled TLS
> altogether until I can investigate what ridiculous hoops I need to jump
Well, that doesn't work
on Wed, Nov 20, 2019 at 10:15:20AM +0100, Claus Assmann via mailop wrote:
> seemingly because it does not like my (self-signed) cert.
We recently ran into this as well, via a longtime list member whose
company decided to switch to mimecast. I just grudgingly disabled TLS
altogether until I can
DMARC rejects had great utility in my time working at an ESP. They would
have little or no utility for forwarded messages. It would be interesting
to see the spread of DMARC rejects for forwarded versus non forwarded
messages. Although it wouldn't change the fact that the responses are
indeed
to quote MJW:
"And, of course, "Reject" only works if you are checking SPF/DKIM/DMARC at the
edge, before sending the final 250 ok.
"Afterwards, it's just another source of backscatter.”
and to quote MDR:
"If you administer a system that accepts orders of magnitude fewer than 150,000
On 21/11/2019 13:10, Luke via mailop wrote:
One of the features of email is that it you can send responses back
about the status or handling of a message. Here's one such response
from a gmail server:
/550 5.7.1 Unauthenticated email from domain.tld is not accepted due
to domain's
One of the features of email is that it you can send responses back about
the status or handling of a message. Here's one such response from a gmail
server:
*550 5.7.1 Unauthenticated email from domain.tld is not accepted due to
domain's DMARC policy. Please contact administrator of
On Wed, 20 Nov 2019, Matt Vernhout via mailop wrote:
If a sender asked you to reject that mail with their policy do them
a favour and send a bounce that says something like âyour DMARC said
to bounce failed messages, if this is wrong fix your authentication
and try againâ
One of the
16 matches
Mail list logo
