It also heavily depends on the ASN.
It is the most ridiculous filter mechanism I ever came across. We had a
whole ASN blocked and waited for weeks until it was removed from their
list. No information which system triggered it. We never found a reason
nor were we given a reason by MS.
If they d
Being "properly configured" these days entails needing many things
that you didn't say. Forward-Reverse-DNS, SPF, DKIM, DMARC just for
starters. And then more in other places.
Impossible to know and so impossible to say. It's a private 3rd party
reputation scoring system in use.
Hello,
On Mon, 2021-02-08 at 14:09 +0100, Ale via mailop wrote:
> > Being "properly configured" these days entails needing many things
> > that you didn't say. Forward-Reverse-DNS, SPF, DKIM, DMARC just for
> > starters. And then more in other places.
>
> > Impossible to know and so impossible to say.
On 2021-02-08 7:37 a.m., Alan Hodgson via mailop wrote:
Unfortunately getting mail accepted at MS or Google from a new VPS seems
to be nearly impossible. I would love to be proved wrong, though, by
those more knowledgeable.
Probably depends on the network reputation where the VPS is located.
B
Didn't take Google spammers long to figure out using + addressing to try
and get by spam filters.. or personal block lists..
Return-Path:
From: "Bitcoin Trader"
Judging by volume, I am sure that there are no sane rate limiters in
place..
I would think that any use of a + address, usually
Hi Ale,
On 08/02/2021 14.09, Ale via mailop wrote:
I will see what happens until June, when my domain expires. If the
problem will persist, I'm gonna contact them and eventually change
domain and IP.
According to
https://whatismyipaddress.com/ip/78.14.94.161
You are on ADSL, probably with
It's a testing server at ... Hetzner. So, yeah, good luck.
Unfortunately getting mail accepted at MS or Google from a new VPS
seems to be nearly impossible. I would love to be proved wrong,
though, by those more knowledgeable.
I'm not expert on these kind of things. I've a direct friend who man
I'm going to go wide (and unpopular) on this one and say that this is
just another reason address plussing is crappy.
Even the desired use case is very easily exploited.
Bad guys can just strip the +tag and then you lose your visibility
into where they got the address from.
I guess if it's all you
+1 to Al. (no pun intended for the '+'.)
Only this weekend I was trying to help an old colleague with a migration from
Gsuite to M365. The #1 complaint... was some of his minions were seemingly
crippled by the lack of this function.. and I was thinking err aliases?
Aliases?
At least I am n
On 8 Feb 2021, at 17:03, Richard Bewley via mailop wrote:
+1 to Al. (no pun intended for the '+'.)
Only this weekend I was trying to help an old colleague with a
migration from Gsuite to M365. The #1 complaint... was some of his
minions were seemingly crippled by the lack of this function.. a
On 2021-02-08 15:03, Richard Bewley via mailop wrote:
Only this weekend I was trying to help an old colleague with a migration from
Gsuite to M365. The #1 complaint... was some of his minions were seemingly
crippled by the lack of this function.. and I was thinking err aliases?
Aliases?
On 2021-02-08 16:14, Bill Cole via mailop wrote:
On 8 Feb 2021, at 17:03, Richard Bewley via mailop wrote:
The critical feature in '+' tagging (and equivalents using other
characters or patterns) is the ability to create aliases on-the-fly in a
namespace that the user controls such that the m
On 8 Feb 2021, at 21:20, Dave Warren via mailop wrote:
On 2021-02-08 16:14, Bill Cole via mailop wrote:
[...]
The "de-tagging" tactic that Al noted has existed, although I don't
see much evidence of it in recent years. I think it may be that
enough people who use tagged addresses give tagged
13 matches
Mail list logo
