michael.w...@microsoft.com said:
> The problem is ... trying to avoid mailbombing the abuse@ address by
> spammers.
Are spammers just stupidly sending to abuse@, deliberately trying to DoS
abuse@, or is the problem spam reporters sending to every abuse@ mailbox they
can find? (or something I
On 2018-11-12 12:58:12 (-0800), Hal Murray wrote:
Hey, senders or receivers or spam filterers. Do you use abuse.net? Do
you register client domains with abuse.net? Do you query it to see
where to send complaints? Do you forward complaints through it?
I think they dropped the forwarding.
I
In article <20181112205812.c7d58406...@ip-64-139-1-69.sjc.megapath.net> you
write:
>
>> Hey, senders or receivers or spam filterers. Do you use abuse.net? Do you
>> register client domains with abuse.net? Do you query it to see where to send
>> complaints? Do you forward complaints through it?
>
The problem is ... trying to avoid mailbombing the abuse@ address by spammers.
Almost needs + addressing for both sender and receiver.
Aloha,
Michael.
--
Michael J Wise
Microsoft Corporation| Spam Analysis
"Your Spam Specimen Has Been Processed."
Got the Junk Mail Reporting
on Mon, Nov 12, 2018 at 11:02:28AM -0500, Al Iverson wrote:
> Hey, senders or receivers or spam filterers. Do you use abuse.net?
Every domain for which I have patterns in Enemieslist has an associated
abuse addy fetched from abuse.net, but frankly I don't do anything with
them - IIRC the "nobody
> Hey, senders or receivers or spam filterers. Do you use abuse.net? Do you
> register client domains with abuse.net? Do you query it to see where to send
> complaints? Do you forward complaints through it?
I think they dropped the forwarding.
I query it occasionally.
For my uses, it has
That is my biggest bug-bear with this .. the people I am having the most
problem with are people I'm in contact with on a regular basis! I switched
email client and suddenly stuff was being quarantined or bitbucketed (the
latter I assume is due to the particularly tenants chosen settings.)
I think the only way is to carefully test it, “In Combat”.
Just remember, if you’re sending to the same recipient all the time, the
machine will notice …
* When you start sending
* If the recipient never replies
* … other things.
So you will need many test recipients, and careful
For anyone interested in this..
I had a bit of an exchange with Michael off-list, we thought he had
mitigated the issue, it seems not.
Reading between the lines of Michael's off-list replies, I went looking at
a certain part of the Mailpile code (I intentionally won't be too precise
here.)
Hey, senders or receivers or spam filterers. Do you use abuse.net?
Do you register client domains with abuse.net?
Do you query it to see where to send complaints?
Do you forward complaints through it?
We at Salesforce Marketing Cloud / ExactTarget register all client
domains with it, but don't
Thanks! I see today that I am now able to submit my two latest ranges
for SNDS access -- I, too, was seeing the "too many RIPE lookups"
issue.
Cheers,
Al Iverson
On Mon, Nov 12, 2018 at 8:17 AM Benoit Panizzon wrote:
>
> Hi List
>
> Finally git positive Feedback from the SNDS Support Team. It
Hi List
Finally git positive Feedback from the SNDS Support Team. It looks
like, after some escalations, they solved the issue of too many requests
to RIPE. (they only had to contact ripe and ask politely for the quota
to be risen I suppose).
I was now able to 'Request Access' to more than just
12 matches
Mail list logo
