On 3/22/23 01:35, Hans-Martin Mosner via mailop wrote:
I tried to report a phishing spam to Sendgrid, and look what I got:
- The following addresses had permanent fatal errors -
(reason: 552-5.7.0 This message was blocked because its content presents a
potential)
-
Eh.
Sendgrid isn't a mailbox provider. Holding them to that standard of things
isn't the right way of looking at it.
For an Email Service Provider (like Sendgrid), the headers likely do have
the information to find the outgoing job where the actual messages were
built and there will be
Thats why the systems should be able to fish out based on for example
Message-ID, and for additional security, AES-256 encrypt the message with the
SHA256 hash of the message ID.Of course only abuse department should have
access to these tools.Thus you dont need to rummage through people's
On 2023-03-22 at 05:01:53 UTC-0400 (Wed, 22 Mar 2023 10:01:53 +0100)
Sebastian Nielsen via mailop
is rumored to have said:
A good idea when you get this type of response, just include the full
headersand not the actual body of message.A competent abuse department
should be able to fish out a
On Wed, 22 Mar 2023 10:01:53 +0100, Sebastian Nielsen via mailop
wrote:
>A good idea when you get this type of response, just include the full
>headersand not the actual body of message.A competent abuse department should
>be able to fish out a verbatim copy of the message being reported in
Dnia 22.03.2023 o godz. 10:01:53 Sebastian Nielsen via mailop pisze:
> A good idea when you get this type of response, just include the full
> headersand not the actual body of message.A competent abuse department
> should be able to fish out a verbatim copy of the message being reported
> in
A good idea when you get this type of response, just include the full
headersand not the actual body of message.A competent abuse department should
be able to fish out a verbatim copy of the message being reported in their
logging systems using the headers alone.
Originalmeddelande
I tried to report a phishing spam to Sendgrid, and look what I got:
- The following addresses had permanent fatal errors -
(reason: 552-5.7.0 This message was blocked because its content presents a
potential)
- Transcript of session follows -
... while talking to
