> Anecdotal, but last time I delved deep into this, apparently the
> majority of spam was sent via IPv6
i don't see this
a quick db query gives me:
v6 pct
-- --
0 89.45
1 10.55
it would probably be even more v4 as presently persisten
On 2019-12-18 18:57:09 (+0800), Ken O'Driscoll via mailop wrote:
On Mon, 2019-12-16 at 17:45 -0800, Brandon Long via mailop wrote:
If you wanted something, you'd probably want a proxy, something that
speaks enough IMAP to do LOGIN/AUTHENTICATE, then re-login to Gmail
with OAUTHBEARER, and then
Anecdotal, but last time I delved deep into this, apparently the majority of
spam was sent via IPv6
December 19, 2019 12:16 PM, "Brian via mailop" wrote:
> On Wed, 2019-12-18 at 13:44 -0800, Mark Milhollan via mailop wrote:
>
>> IPv6 is normally preferred so if you have published an for t
On Wed, 2019-12-18 at 13:44 -0800, Mark Milhollan via mailop wrote:
> IPv6 is normally preferred so if you have published an for the
> highest priority MX then IPv6 would be tried first, and since you
> accept
> the messages you no longer see much IPv4 from them. As to why they
> don't li
On Wednesday 2019-12-18 12:18, Brian wrote:
For what I can see
on my logs, Gmail seem to prefer v6 when delivering emails to my
server, but for some reason when my server uses v6 to deliver emails
their milters mark them as spam (except of course when I send test
emails to my 15 years old person
Probably lack of authentication. Did you set up an SPF record? Did
that SPF record include your V6 addresses?
Honestly, so much of email service is on ipv4 that I just disabled my
server's ipv6 interface. Prior to that I would have similar issues,
intermittently. It turns out the intermittent natu
I never had any significant deliverability issues with my personal low
volume email server before, which I have been running for several years
following pretty much all the well-known recommendations and standards.
Two months ago I decided to take some time to setup IPv6 using a new
/64 I got from
On 12/18/19 09:58, Daniele Nicolodi via mailop wrote:
Hello,
in the last few days I am receiving a constant stream of spam from
isaxl.com via bluehornet.com (apparently also known as mapp.com).
[snip]
Does it make sense to report this to someone, and if so how, or should I
simply siphon all
Hi Daniele,
I handle compliance for Mapp.
We will look into this, sorry for the unwanted mail.
If you can forward the message to ab...@mapp.com with the headers I can make
sure your address is removed in the meantime while we look further into this.
Regards,
Tom
Tom Ellengold
Sr Compliance &
Hello,
in the last few days I am receiving a constant stream of spam from
isaxl.com via bluehornet.com (apparently also known as mapp.com).
Because of the distinctive content of those spammy messages (for
examples some with commercial offers from a major mobile phone operator
in Italy, which I fi
Hello,
Does anyone have a good point of contact for netease? I've had no luck
emailing postmaster@
Thank you,
Dani Martens
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
On Mon, 2019-12-16 at 17:45 -0800, Brandon Long via mailop wrote:
> If you wanted something, you'd probably want a proxy, something that
> speaks enough IMAP to do LOGIN/AUTHENTICATE, then re-login to
> Gmail with OAUTHBEARER, and then just be a pass through. We do something
> similar for the reve
Dnia 18.12.2019 o godz. 10:18:33 Ken O'Driscoll via mailop pisze:
>
> I've used Evolution (which talks GOA) for years with multiple G Suite
> accounts and it works like a treat. And that's in a work capacity, not as a
> home user/hobbyist so I'm unforgiving of problems.
Nice to hear that. Until n
On Mon, 2019-12-16 at 22:30 +0100, Jaroslaw Rafa via mailop wrote:
> Do any Windows/Linux/MacOS email clients currently support OAuth "out of
> the box"?
> If not, that's basically cutting nearly everybody using regular IMAP
> email clients off of G Suite...
For Linux, the Gnome Online Accounts su
14 matches
Mail list logo
