Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: david@lang.hm
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Dave needs to get better at pushing out patches
Date: Thu, 8 Dec 2011 04:18:13 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1112080412100.2347@asgard.lang.hm> (raw)
In-Reply-To: <CAA93jw7HEqj+6DCU-p7hytLyDDpTg9+p8nA1M7GAmerwebyAqQ@mail.gmail.com>

On Thu, 8 Dec 2011, Dave Taht wrote:

>> as a holdout pine user I understand your frustration :-)
>>
>> have you considered doing something like setting up openvpn to connect to
>> the bufferbloat.net server and then configuring the mail server to trust
>> mail arriving form the VPN clients?
>>
>> I know this is horrible overkill for such a trivial job, but it avoids all
>> the problems of doing authentication for the SMTP connection (and the fact
>> that many locations block outbound connections from dhcp addresses to port
>> 25)
>
> Both 25 and VPNs are blocked at lincs. 567 works. Neither certs nor
> sasl from postfix worked. So far I've figured out

openvpn works over any port you want.

now, as a security person I am going to point out that you should not 
break the security of a company network by establishing a VPN that 
bypasses the security controls.

but if it's just a careless network config (they allow anyone to connect 
to it, but then block specific ports outbound), I feel no guilt over 
establishing connections over oddball ports :-)

I just took an openvpn class, and one of the upcoming features is the 
ability for openvpn to work over ping, so I'll bet that you can make it 
work (odds are really good that it will work over port 443 from just about 
anywhere, and anyone who has security setup well enough that you can't do 
it over 443 is probably a place where youreally shouldn't be doing it 
anywhay :-)

> That the last 'update' from ubuntu wiped out my certs on my main
> email box.
>
> That dovecot sieve sucks compared to procmail
>
> that they've created a new abstraction for mail handling
> for doing sasl that doesn't want to work
>
> and I forget what else.
>
> I mean, mail used to 'just work'. Even with bang
> paths it would mostly just work. Nowadays you have
> to be a rocket scientist to run your own server,
> and damn it, I LIKE running my own mail server.
>
> Or at least, I used to.

It's not quite that bad, but yes, the spammers have required significant 
changes.

If the problem is doing this from one particular network (and one that you 
trust to be sane, like your office), why not just configure the mail 
server to allow unauthenticated mail from that IP (or IP range)?

David Lang

  reply	other threads:[~2011-12-08 12:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 10:16 Dave Taht
2011-12-08 11:55 ` david
2011-12-08 12:06   ` Dave Taht
2011-12-08 12:18     ` david [this message]
2011-12-08 12:39       ` Dave Taht
2011-12-08 12:54         ` david

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=alpine.DEB.2.02.1112080412100.2347@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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