On 10/15/21 17:40, Grant Taylor via mailop wrote:
On 10/15/21 5:37 PM, Dave Crocker via mailop wrote:
Yes, but... That's the point that is intuitively reasonable which
doesn't make real sense to me, after thinking about it.
What doesn't make real sense to you? The relation of reputation and
It appears that Dan Mahoney via mailop said:
>I will say, as a data-point, that dayjob has had one customer that required us
>to use a CA for our SMTP server that’s on a whitelist-approved by a
>certain automaker industry consortium. To the point where when they decided
>they couldn’t
On 10/15/2021 5:40 PM, Grant Taylor via mailop wrote:
The motivation for spreading service IPs across different /24 prefixes
is so that if
The issue here is not the generic one of using multiple IPs. It is
about using them to separate IMAP from SMTP. That's an entirely
different matter.
Anyone from Google here?
I'm seeing a bug where messages sent to same Gmail account (same from and to
@gmail.com address) are accepted by smtp.gmail.com but are never delivered,
dropped instead.
This happens if:
- Messages are sent using a mail app using IMAP / SMTP
- Mail app uses OAUTH2 for
On 10/15/2021 6:44 PM, Grant Taylor via mailop wrote:
I can see a hypothetical scenario where a client is running a firewall
that is filtering connections based on IP reputation. So if an SMTP
server is erroneously listed, said firewall might block the IP, thereby
blocking the client's
I will say, as a data-point, that dayjob has had one customer that required us
to use a CA for our SMTP server that’s on a whitelist-approved by a certain
automaker industry consortium. To the point where when they decided they
couldn’t communicate with a secure SSL cert (even though SSL was
I've had customers repeatedly approach me about a similar issue and I
ended up writing this in mass response:
https://mxroute.com/docs/im-forwarding-or-retrieving-email-to-at-gmail-and-when-i-send-a-test-email-from-the-same-address-that-will-ultimately-be-receiving-it-it-doesnt-work/
I could
On 10/15/21 11:54 PM, Michael via mailop wrote:
Remember, each lookup against Let's Encrypt shares information,
that can be resold.
What is different for a CA that a certificate is purchased from?
--
Grant. . . .
unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
On Thu 14/Oct/2021 21:35:02 +0200 Alexey Shpakovsky via mailop wrote:
Worth noting that OpenDKIM's latest stable release was in 2015, and latest
beta in 2018. The app seems to be in somewhat active development on
Github, but to see it you must switch from default "master" branch to more
active
On Fri, 15 Oct 2021, Michael wrote:
I prefer to think that the company I pay $$ to for a cert, makes enough
they don't have to sell our data. Remember, each lookup against Let's
Encrypt shares information, that can be resold.
Sorry, but that is simply wrong. It's not how SSL works.
The
Making no apology whatsoever about top posting from my phone's mail client:
STOP with the niggles. Please, just stop.
"I'm getting 1 unsolicited calendar invites from $provider every
minute" seems to me a legitimate operational problem and one worth raising
here, and/or directly with
On Fri, 2021-10-15 at 18:07 -0500, Mike Jovanovic via mailop wrote:
> Gmail can send email to spam if it arrives in a language that is
> different from the recipient's default language setting.
Do you have evidence to substantiate your claim?
I have plenty of beef with Big Tech, but it is not
On Tue, 2021-10-05 at 18:15 -0700, Brandon Long via mailop wrote:
> larger providers are their own special targets.
Thank you for sharing with us the perspective of a Big service
provider, and how you deal with annoyances on that exa-scale.
> We also see spammers try to use Gmail to spam other
13 matches
Mail list logo
