On 17 May 2022, at 21:59, Dave Crocker via mailop wrote:
> I keep enjoying that it has the style of satire, but is so well done is it
> /extremely/ useful for legitimate use.
I wonder if this one
( ) Public reluctance to accept weird new forms of money
should be complemented with a crypto vers
Dave Crocker via mailop wrote on 2022-05-17 18:01:
..., the bigger problem, IMO, are the folk who operate in a criminal
style, ignoring rules.
my view has always been that the people who don't know what the rules
are, and the people who know what the rules are but see them broadly
ignored, cr
Hmm, take a look at the MX record published for AOL.COM
AOL is owned by Verizon Media, which also owns Yahoo.
On 5/17/2022 5:58 PM, sam via mailop wrote:
Hello,
I am trying to track down a contact for aol.com as we have a couple
users who are emailing into aol.com but there mail is landing i
On 5/17/2022 5:01 PM, Justin Scott via mailop wrote:
I seem to recall a list of "reasons your anti-spam proposal won't work"
http://craphound.com/spamsolutions.txt
Some of us send it pretty automatically to whatever the next proposal is.
Cory just told me that he got it from somewhere
Justin Scott via mailop wrote on 2022-05-17 17:01:
Ah, the Good Old Days(tm). I seem to recall a list of "reasons your
anti-spam proposal won't work" someone would post every time someone
came up with a new way to fight spam that included things like "It
requires spammers to change their beh
On 5/17/2022 4:40 PM, Anne Mitchell via mailop wrote:
"why we can't do that", culminating in "the Commission concludes that, under
present conditions, a National Do Not Email Registry in any form would not have any beneficial
impact on the spam problem. It is clear, based on spammers’ abiliti
So are we making our own list? This happening? I just use this right
now: https://www.stopforumspam.com/downloads
On 2022-05-17 18:40, Anne Mitchell via mailop wrote:
For those who didn't know, you may find this infuria...interesting.
Did you know that CAN-SPAM mandated that the FTC look at cre
Ah, the Good Old Days(tm). I seem to recall a list of "reasons your
anti-spam proposal won't work" someone would post every time someone came
up with a new way to fight spam that included things like "It requires
spammers to change their behavior" and "it involves a central authority or
agency to
For those who didn't know, you may find this infuria...interesting. Did you
know that CAN-SPAM mandated that the FTC look at creating a Do Not Email list
and report their findings within 6 months of CAN-SPAM being enacted? That
report was created and delivered, and it is 60 pages of "why we can
Heho,
> They're just reporting what they recieve. It shouldn't be a big surprise
> that spamware makes up addresses, some of which happen to be in your domains.
Nah, i mean 'i receive spam with a from of $large_entity and reject due to
DMARC failing', hence my systen tries to send a report to w
On Tue, 17 May 2022, Tobias Fiebig wrote:
However, judging from the state of DMARC reporting by the bounces
hitting my report-from (_large_ orgs having non existent mailboxes in
there etc.), I'd argue that the only thing that prevents ruf/rua that
are stale for a decade is the age of RFC7489.
Hello,
I am trying to track down a contact for aol.com as we have a couple users who
are emailing into aol.com but there mail is landing in spam
I confirmed that SPF and DKIM are enabled and dmarc is enabled as well on the
domain
___
mailop mailing lis
Heho,
> If they did, they would age them for at least a year before turning them into
> traps, by which time the DMARC records would be long gone.
I generally agree with your argument, that this is a really unlikely scenario.
Also, because the spam-trap domain would naturally lack the
._report._
It appears that Tobias Fiebig via mailop said:
>Heho,
>I recently described how this could actually be used by a malicious third
>party to cause a sender to be blocklisted by major mail operators (see thread
>titled
>"DMARC/TLSRPT to non-existing accounts/reflection and sender reputation" from
Heho,
I recently described how this could actually be used by a malicious third party
to cause a sender to be blocklisted by major mail operators (see thread titled
"DMARC/TLSRPT to non-existing accounts/reflection and sender reputation" from
the end of April). However, in your case it does not
A similar issue (not with spamhaus) crept up recently and I had to do a
lot of log diving to find the culprit. Just for kicks and in case you
get nothing else of value in reply, any chance that taking the two time
frames and comparing them to see what recipients matched is of any
value? I guess
Hopefully somebody from spamhaus is reading.
The 2nd day in a row, our main mailplattform IP address is listed and
outlook.com blocks all emails.
Spamhaus only gives a timestamp +/- 5 minutes.
There are A LOT OF EMAILS passing our plattform in 10 Minutes.
Yesterday I found a suspect. One custom
17 matches
Mail list logo
