From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Dave Täht" <dave@taht.net>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] in the post-cisa world
Date: Mon, 15 Feb 2016 22:13:14 +0100 [thread overview]
Message-ID: <877fi5he39.fsf@toke.dk> (raw)
In-Reply-To: <56C22402.3080506@taht.net> ("Dave =?utf-8?Q?T=C3=A4ht=22's?= message of "Mon, 15 Feb 2016 11:16:18 -0800")
Dave Täht <dave@taht.net> writes:
> Even then, though, barrier #2 - the prospect of being a drive-by spam
> target - bothers me, so having a box in the cloud that can
> "turnaround" and rate limit stuff from port 25 there to my vpn here
> seemed ideal... except that good anti-spam requires that there be a
> reverse lookup on the origin ip and spf record that you lose that way,
> before you can get as far as starttls.
Use the cloud server as a NAT box, forwarding through the VPN? If you do
this in both directions (i.e. outgoing traffic will seem to come from
the cloud IP), you can get the reverse lookup while still having the
actual TLS connection terminate in the house? That was my plan... Will
get around to implementing it one of these days...
-Toke
prev parent reply other threads:[~2016-02-15 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 19:16 Dave Täht
2016-02-15 21:13 ` Toke Høiland-Jørgensen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fi5he39.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox