Jesse Guardiani <[EMAIL PROTECTED]> writes: > I got tripped up at first because (I think) the -f and -b options > are new.
Always read the UPGRADE file before upgrading TMDA. This change is documented there. > --- tmda-ofmipd Tue Jan 21 00:36:24 2003 > +++ /usr/local/tmda/bin/tmda-ofmipd Tue Jan 21 13:34:13 2003 > @@ -552,7 +552,8 @@ > self.__auth_username = None > self.__auth_password = None > self.__auth_sasl = None > - self.__sasl_types = ['login', 'cram-md5', 'plain'] > +# self.__sasl_types = ['login', 'cram-md5', 'plain'] > + self.__sasl_types = ['login', 'plain'] > self.__auth_cram_md5_ticket = '<%s.%s@%s>' % (random.randrange(10000), > int(time.time()), FQDN) > self.__server = server > --------------------------------------------------- > > I had to make this change because even though CRAM-MD5 doesn't work > for IMAP auth, and I'm using IMAP auth, tmda-ofmipd is still > publishing CRAM-MD5 capability to incoming clients. Of course this won't work because it disables CRAM-MD5 globally. We should only not advertise CRAM-MD5 when -A or -R is specified, right? _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
