> On May 21, 2022, at 8:03 AM, Viktor Dukhovni <postfix-us...@dukhovni.org> > wrote: > > On Sat, May 21, 2022 at 12:09:37AM -0700, Jeremy Hansen wrote: > >> What I experience when the port forward is enabled is suddenly >> “things” out there are attempting to just email random addresses at >> the AWS instance hostname. > > You don't have to accept such mail, or if you, you don't have to forward > it to the internal system behind the SSH port forward. And if > nevertheless you do, you can arrange to not forward it back from the > internal MTA. > >> http://skidrowstudios.com/mta/cmx01-logs.txt > > Post all relevant data in the body of your message, I am not inclined to > chase them down by switching to a web browser.
I tried. The mail list rejected my messages since it was too many characters. > > Loop breaking is simply a matter of knowing which system is responsible > for final delivery of a given message recipient. This is actually what I expected to happen but since the Ciphermail host (This is just postfix with some filters to gpg encrypt all incoming mail if a key is available for the destination user. https://gitlab.com/ciphermail/ciphermail-community). > > Don't forward mail that for which the input MTA is expected to be the > final destination. That sounds logical. I’m not sure why it’s even forwarding the mail since that user or domain is not defined to accept that mail. > > -- > Viktor. -jeremy
signature.asc
Description: Message signed with OpenPGP
