Hi, From: "Jason R. Mastaler" <[EMAIL PROTECTED]> Subject: Re: tmda-ofmipd: patch for imap[s] and pop3 remote auth Date: Wed, 04 Sep 2002 18:24:06 -0600
> [EMAIL PROTECTED] writes: ... > > Exactly [1]. So IIUC the following should be theoretically > > possible: > > > > 0) tmda-ofmipd is used in personal mode w/ ~user/.tmda/tofmipd > > > > 1) Client uses CRAM-MD5 to interface w/ tmda-ofmipd > > > > 2) tmda-ofmipd uses APOP to interface w/ pop server > > If you already using ~user/.tmda/tofmipd to authenticate, why would > you then need to reauthenticate against an APOP server? Good point! Silly me (-; Thanks for straighten me out. > > I got the impression from the 0.62 release info that for certain > > things Python 2.2 is required. > > Python 2.0 and 2.1 is still supported for the vast majority of TMDA. > Certain features require 2.2 however (e.g, SMTP over SSL), but those > are optional features. If you don't need to use them, you don't need > to upgrade. > > Although unless you have a specific reason not to, you might as well > upgrade to 2.2.1. It contains lots of bugfixes and performance > improvements relative to earlier releases. The rfc2822 header parsing > is also much better. I'd go for it as soon as there are Debian packages for stable (-; > > Is it the case that Python 2.2 is now required for tmda-ofmipd > > itself? > > This has been the case ever since tmda-ofmipd was introduced. See > ``Requirements'' under http://tmda.net/tmda-ofmipd.html. The reason > for this is because os.setgroups() was only introduced in 2.2 -- this > is an essential feature when tmda-ofmipd is started as root. IIRC it wasn't necessary when tmda-ofmipd was first in cvs -- all the testing I did and reported on took place w/ a lesser Python version (I'm pretty sure because that machine still has the lesser Python on it). FWIW, I don't have any use for the global mode of operation of tmda-ofmipd -- I've been planning all along to have my users use "personal mode". > > [2] Sadly, not many mail clients have support for setting up a > > tunnel w/ ssh before sending/receiving mail. > > Why is this necessary? As root, you can setup a global ssh port forward > that every user can use. Users can do the same from the command line. > Mail client support is not necessary. See the ssh example I posted > earlier. David's stunnel example also applies. I've been using manual ssh port-forwarding for as far back as I've been using ssh (which is to say quite a few years) -- but, I understand that some people find it more convenient to have their mail client perform the operation (cf. Mew mail reader has support). _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
