Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://infosec.exchange/users/wdormann/statuses/114263980151741657">Will Dormann (wdormann@infosec.exchange)'s status on Wednesday, 02-Apr-2025 03:02:08 JST</a><a href="https://infosec.exchange/@wdormann" title="wdormann@infosec.exchange"><img src="https://gnusocial.jp/avatar/232810-48-20240116185707.webp" width="48" height="48" alt="Will Dormann" style="position: absolute; left: 0; top: 0;">Will Dormann</a><div><a href="https://infosec.place/objects/40b7a1b7-4ad3-4c4c-ac7c-386fe5b79e09" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/161036" title="cr0w@infosec.exchange">cR0w :cascadia:</a></li></ul></div></section><article><p><a href="https://infosec.place/users/buherator" rel="nofollow">@buherator</a> <a href="https://infosec.exchange/@cR0w">@cR0w</a> <br>Yeah, even with a number of different ZIP passwords, I found that Gmail's SMTP server still found the evil inside if I didn't use PGP encryption at the higher layer.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4828178#notice-9456065">In conversation</a><time datetime="2025-04-02T03:02:08+09:00" title="Wednesday, 02-Apr-2025 03:02:08 JST">about 8 days ago</time> <span>from <span><a href="https://infosec.exchange/@wdormann/114263980151741657" rel="external" title="Sent from infosec.exchange via ActivityPub">infosec.exchange</a></span></span><a href="https://infosec.exchange/@wdormann/114263980151741657">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/4399375">Send Message Error
Send Message Error
Sending of the message failed.An error occurred while sending mail. The mail server
responded: This message was blocked because its
content presents a potential
security issue. To review our message content and
attachment content
guidelines, go to
https://support.google.com/mail/?p=BlockedMessage
d75a77b69052e-474691a1ff3sm10899261cf.7 - gsmtp.
Please check the message and try again.OK</a></label><br><a href="https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/263/976/042/780/469/original/87d57216a4fab70e.png" rel="external">https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/263/976/042/780/469/original/87d57216a4fab70e.png</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Will Dormann (wdormann@infosec.exchange)'s status on Wednesday, 02-Apr-2025 03:02:08 JSTWill Dormann
in reply to
- buherator
- cR0w :cascadia:
@buherator @cR0w
Yeah, even with a number of different ZIP passwords, I found that Gmail's SMTP server still found the evil inside if I didn't use PGP encryption at the higher layer.
In conversation8 days ago from infosec.exchangepermalink
Attachments
1. Send Message Error Send Message Error Sending of the message failed. An error occurred while sending mail. The mail server responded: This message was blocked because its content presents a potential security issue. To review our message content and attachment content guidelines, go to https://support.google.com/mail/?p=BlockedMessage d75a77b69052e-474691a1ff3sm10899261cf.7 - gsmtp. Please check the message and try again. OK
  https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/263/976/042/780/469/original/87d57216a4fab70e.png

Public

Embed Notice

HTML Code

Corresponding Notice