On Fri, Sep 3 '21 at 10.02 NZST, Mark Fletcher via mailop
wrote:
> On Thu, Sep 2, 2021 at 2:31 PM Ken Johnson via mailop
> wrote:
>
> >
> > The kind of answer I was expecting was along the lines of "Obviously your
> > data has been mis-interpreted as XYZZY encoding. You can read about XYZZY
On Thu, Sep 2, 2021 at 2:31 PM Ken Johnson via mailop
wrote:
>
> The kind of answer I was expecting was along the lines of "Obviously your
> data has been mis-interpreted as XYZZY encoding. You can read about XYZZY
> encoding here ." (I did not say so, not
> wanting to launch preconceptions.)
Yes, it is clear that something changed recently with Microsoft's JMRP
(Junk Mail Reporting Program, aka the ISP Feedback Loop) reporting for
their OLC (Hotmail, Outlook.com, etc.) domains.
Complaints are way up for our clients, as well. It's not just you --
other ESPs are seeing as well.
Right
Interesting.
We're seeing oddities with M365 with customers with connectors for our
IPs getting S77719. I'm still gathering information about to open a
ticket but this is just started today.
Regards,
KAM
On 9/2/2021 5:42 PM, yitzi--- via mailop wrote:
We've been seeing much higher
We've been seeing much higher levels of spam markings and SNDS was crazy the
past couple days, more so than normal. So yes, I'd say we're also experience
some unusual activity surrounding Microsoft reporting.
One of my colleagues mentioned back in mid-July that she suspected there could
be
Thank you everyone for the interest shown so far. I appreciate the suggestions
about Packet Capture (sure, Wireshark can use a certificate for decryption),
DKIM (interesting, but overcome by events -- see below), etc.
The kind of answer I was expecting was along the lines of "Obviously your
On Thu, 2 Sep 2021, Ken Johnson via mailop wrote:
I recently needed to send a software key to a remote colleague who needed to
reinstall some commercial software after re-installing Windows. However,
after the key failed to authorize, an investigation determined that the key
was corrupt in the
Response in line
> Could you clarify "associated sending domains"?
>
The domain namespace associated with the disposable addresses. If the
platform is offering *@example.com example.com would be the namespace of
interest.
> The primary use of disposable email websites TTBOMK is for receiving
Response inline:
When you say 'disposable' I am assuming you mean alice12...@gmail.com,
> so I think you better mean 'freemail' addresses that are used for
> spamming, correct?
>
'disposable' in this case is a pairing of intent and infrastructure. Many
of these services are providing
On Thu 02/Sep/2021 19:58:10 +0200 Ken Johnson via mailop wrote:
The first line of the key is:
PXP70-KK4tQ6fJQYAI32PugLL4GK9pJOZT4ocM9J0ICAoharwSAYhplSMpFm+n+b2xJ65hNI043
which becomes:
PXP70-KK4tQ6fJQYAI32PugLL4GK9pJOZT4ocM9J0ICAoharwSAYhplSMpFm+n+b2xJ65hNI
Maybe the remote SMTP is failing to properly wrap from 75 characters down to 72?
Maybe line wrapping is interfering with base64 decode (if base64 was applied)?
It would be helpful to know the remote SMTP software+version and a copy of your
email headers, showing what kind of encoding &
On Thu, 2 Sep 2021 at 19:35, Ken Johnson via mailop
wrote:
> I recently needed to send a software key to a remote colleague who needed
> to
> reinstall some commercial software after re-installing Windows. However,
> after the key failed to authorize, an investigation determined that the key
>
What software is in-use for the mail server, any AV products that might be
intercepting it, and the mail clients?
Have you tried tossing a packet capture on the mail server to see what is
received from your client? Or what the recipient receives when he pulls
mail from his box?
-A
On Thu, Sep
I recently needed to send a software key to a remote colleague who needed to
reinstall some commercial software after re-installing Windows. However,
after the key failed to authorize, an investigation determined that the key
was corrupt in the email he received from me. The first line of the
On 9/2/21 08:09, IP Abuse Research via mailop wrote:
To provide an even assessment, the problem isn't limited to Gmail
addresses. Is anyone tracking disposable email websites and associated
sending domains or is this just seen as noise in the larger scope? Is
anyone interested in trying to
Dnia 2.09.2021 o godz. 11:09:39 IP Abuse Research via mailop pisze:
> Having observed a large number of disposable gmail address sites out there
> with supporting APIs, abused accounts are likely a component. Websites like
> https://www(.)gmailnator(.)com/ and supporting APIs (
>
Having observed a large number of disposable gmail address sites out there
with supporting APIs, abused accounts are likely a component. Websites like
https://www(.)gmailnator(.)com/ and supporting APIs (
https://rapidapi(.)com/johndevz/api/gmailnator
) that facilitate abuse of Google services yet
17 matches
Mail list logo
