On Thu, Jul 18, 2019 at 12:08 PM Steven Champeon via mailop <
mailop@mailop.org> wrote:
> on Thu, Jul 18, 2019 at 06:27:37PM +, Michael Wise via mailop wrote:
> > The doctrine seems to be that they're sufficiently on the ball that
> > they can handle all abuse issues internally, and thus,
On Thu, Jul 18, 2019 at 3:11 AM Benoit Panizzon via mailop <
mailop@mailop.org> wrote:
> Hi List
>
> Operating the SWINOG Blacklist and Spamtraps, I notice quite some spam
> originating from Google IPv6 Ranges (yes, trying to catching up
> whitelisting them, which is not easy with their constant
On Sat, 20 Jul 2019 08:31:11 +1000, Angelo Giuffrida via mailop
wrote:
>Sorry it's been a rough day (death of a friend and member of our team) and
>I might have been a bit snipey. I have a load of frustrations with
>Microsoft's handling of spam, and assumed that somebody with seniority at
Sorry it's been a rough day (death of a friend and member of our team) and
I might have been a bit snipey. I have a load of frustrations with
Microsoft's handling of spam, and assumed that somebody with seniority at
Microsoft might have had a hand in developing those policies.
On Sat., 20 Jul.
> On Jul 19, 2019, at 12:30 AM, Angelo Giuffrida via mailop
> wrote:
>
> I find it rich that Michael is in here throwing stones... can't exactly throw
> stones when you live in a glass house there big Mikey!
I find it rich that you would disparage Michael like this, especially when, to
the
On 7/19/2019 10:06 AM, Al Iverson via mailop wrote:
Please don't insult big Mikey, he does a lot of good for the community
and is a good person. He is not personally responsible for everything
you don't like about MSFT.
YES! Michael Wise is part of the solution, doing MUCH good, he shouldn't
Please don't insult big Mikey, he does a lot of good for the community and
is a good person. He is not personally responsible for everything you don't
like about MSFT.
Regards,
Al Iverson
On Fri, Jul 19, 2019 at 1:37 AM Angelo Giuffrida via mailop <
mailop@mailop.org> wrote:
> I find it rich
I find it rich that Michael is in here throwing stones... can't exactly
throw stones when you live in a glass house there big Mikey!
Cheers, Angelo.
On Fri, Jul 19, 2019 at 3:38 PM Jesper Sörtoft via mailop
wrote:
> On 2019-07-18 21:06, Steven Champeon via mailop wrote:
>
> >
On 2019-07-18 21:06, Steven Champeon via mailop wrote:
Bwahahahahahahahahahahaha.
Yeah, whatever. I've had rulesets that block webmail-injected 419/AFF
scams for over a decade and Google is among the few who I still get them
from because I can't tell if the IP is in West Africa thanks to this
on Thu, Jul 18, 2019 at 06:27:37PM +, Michael Wise via mailop wrote:
> The doctrine seems to be that they're sufficiently on the ball that
> they can handle all abuse issues internally, and thus, they hide that
> information, since it could be used to, for instance, launch a DDOS
> attach
lop@mailop.org
Subject: Re: [mailop] How to identify source of email sent via Google?
On 7/18/19 4:08 AM, Benoit Panizzon via mailop wrote:
> Hi List
Hi,
> Unfortunately with emails sent over Gmail, there are no more IP source
> before the Google IP Address, so I started wondering i
On 7/18/19 4:08 AM, Benoit Panizzon via mailop wrote:
Hi List
Hi,
Unfortunately with emails sent over Gmail, there are no more IP source
before the Google IP Address, so I started wondering if there is any
other way to find an unique source in the Gmail Headers:
I will be quite surprised
Hi List
Operating the SWINOG Blacklist and Spamtraps, I notice quite some spam
originating from Google IPv6 Ranges (yes, trying to catching up
whitelisting them, which is not easy with their constant morphing).
Usually the Received: Line parser skips a line indicating a whitelisted
souce IP.
13 matches
Mail list logo
