I believe Tim draegan from DMARCian would probably have all of them covered
in between his clients and so will Agari and Returnpath. They might be
willing to share.
On Jun 8, 2017 21:24, "Laura Atkins" wrote:
Thank you to everyone who responded!
On Jun 8, 2017, at 10:33 AM, John Levine wrote:
Hi,
I am trying to report a phishing incident (someone spoofing docusign with a
cousin domain docusgn.com, malicious link also hosted on godaddy) and your
web interface fails to accept the report. please contact me off-list.
Regards,
Gil Bahat,
DevOps/Postmaster,
Magisto Ltd.
___
One of my clients experiences a mutual drop from proofpoint (both sending
to proofpoint and receiving from proofpoint to gapps). Please contact me
off-list.
Regards,
Gil Bahat
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin
Unless you have physical presence in korea, KISA will not admit you. Even
if you do, there are apparently legal ramifications to sending spam in
korea which must be accounted for.
If that doesn't deter you, you can do the following:
1. Create the most encompassing yet still valid SPF record for y
I had good luck by subscribing to naver and opening a ticket. You may need
to pass a Korean captcha, which you can do by redrawing characters in any
draw-based input method
On Jan 30, 2017 5:57 PM, "Zack Aab" wrote:
> Hi all,
>
> I'm working with a very high volume sender who sends to Korea and
I would email TWNIC and ask them whether they are aware what is the right
abuse contact for HINET. it's pretty obvious that a NIC cannot conduct
investigations in registered networks, but it is likely that they do have a
valid contact.
You're right that it's silly to advertise a pointless IRT recor
Hi,
Do providers document which engine(s) they're using to flag suspicious
attachments?
I am having a case where a client is forwarding attachments which are
deemed dangerous by the destination (in this particular case it's gmail but
it might as well be any other), but no engine on virustotal flag
of
crap" about any blacklist -- and you could even be correct some of the time
-- but somebody does use it somewhere, so it exists and one has to deal
with it sometimes.
Cheers,
Al
--
Al Iverson
www.aliverson.com
(312)725-0130 <(312)%20725-0130>
On Fri, Dec 9, 2016 at 10:44 AM
+1 unreasonable for an indiscriminate block on all of Amazon SES. Why would
anyone want to use such a BL is beyond me given that there are many, much
better alternatives.
On Dec 9, 2016 5:30 PM, "Vladimir Dubrovin via mailop"
wrote:
25.11.2016 22:50, Al Iverson пишет:
Hi Otto,
Long time no tal
ed by it.
6. Deriving from 4+5, the practice attests to lazyness or apathy to false
positives by the operator deploying it.
Gil
On Wed, Jun 15, 2016 at 12:36 PM, Michelle Sullivan
wrote:
> Gil Bahat via mailop wrote:
>
>> public PBL registry. Do you see any big recipients
>> (gmail/ho
email ground rules and some of the heat senders receive will
fall back at them, then we'll see some progress around that.
Gil
On Wed, Jun 15, 2016 at 10:30 AM, Noel Butler
wrote:
> On 15/06/2016 16:59, Gil Bahat via mailop wrote:
>
> I beg to differ. Spamhaus offers the PBL in rsyn
on't, and their performance requirements are much more stringent than
yours. That could be a good indication you're cutting corners and having
someone else pay the price for it.
Gil
On Wed, Jun 15, 2016 at 9:48 AM, Noel Butler wrote:
> On 15/06/2016 16:09, Gil Bahat via mailop wro
Prudency aside, this is one of the things wrong in the email world. I don't
get it why recipients do something which is patently lax (having a naive
regex) when a more appropriate solutions exist (spamhaus PBL) with a 'screw
the sender, it's their problem, they'll bear the wrath of their users' -
o
I wouldn't recommend this approach. If your email carries high business
value, even a relatively small ISP could justify the time investment needed
to resolve the situation. when we had issues with spamcannibal BL and the
operator was unyielding, I went the time to research which of the providers
u
FWIW I understood that the policy of large recipients is to already
'demand' and 'assume' that the URLs in List-Unsubscribe behave as 1-clicks
and that mailto: links can also be triggered from backend systems. That was
the requirement that I passed to our R&D. I'd be happy if anyone from a
large re
It's called bounceio 'domain monetization' and it's not new at all. They
will send bounces specifically back to the sender address and not the
return path address. Like any spam operation, it's UCE. Unlike any other
spam operation, not enough people mark them as spam, so their email still
gets acce
We've been GL'ed by yahoo for over a year now and I pretty much gave up all
hope of ever getting it fixed, despite the fact that we send time-sensitive
emails. We get a mix of the postmaster-21 notice and another notice with a
vague/generic text.
Gil
On Apr 27, 2016 1:23 AM, "Renaud Allard via mai
17 matches
Mail list logo
