For a rogue test message?
However, a quick search through the mail log shows that indeed, there
are messages coming from random Amazon AWS hosts that are... "interesting"
I smirk a bit when I see this in our mail logs:
Sep 2 10:36:06 mta postfix/smtpd[1091]: warning: non-SMTP command from
ec2-184-72-79-140.compute-1.amazonaws.com[184.72.79.140]: GET / HTTP/1.1
As for blocking, we rely quite a bit on available spam-hauses, such as
zen.spamhaus.org, and they do catch the occasional individual Amazon
AWS machine (seen in our logs), so it seems that they do get reports
on misbehaving machinery.
Apart from hightened emotions (I understand them, believe you me), are
there tangible reasons for applying the kind of arbitrary
sledge-hammer that you propose?
I would rather not, unless I really must.
Cheers,
Richard
On Mon, 31 Aug 2020 16:28:53 +0200,
Marc Roos wrote:
>
>
> Why don't you block the whole compute cloud of amazon?
> ec2-3-21-30-127.us-east-2.compute.amazonaws.com
>
>
> -----Original Message-----
>
> To: openssl-users@openssl.org
> Subject: Testing
>
>
>
> --
> -----BEGIN EMAIL SIGNATURE-----
>
> The Gospel for all Targeted Individuals (TIs):
>
> [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S.
> Embassy Workers
>
> Link:
> https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html
>
> ************************************************************************
> ********************
>
> Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic
> Qualifications as at 14 Feb 2019 and refugee seeking attempts at the
> United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug
> 2019) and Australia (25 Dec 2019 to 9 Jan 2020):
>
> [1] https://tdtemcerts.wordpress.com/
>
> [2] https://tdtemcerts.blogspot.sg/
>
> [3] https://www.scribd.com/user/270125049/Teo-En-Ming
>
> -----END EMAIL SIGNATURE-----
>
>
--
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
