On Mon, 2003-07-14 at 04:39, Ken Murchison wrote:
> Nope, I use Sendmail. I don't understand why people have such a hard
> time setting up SASL. If you use either sasldb2 or saslauthd, its
> trivial. If you use MySQL or LDAP (which I've never tried), it gets a
> little more complicated.
Act
On Mon, 14 Jul 2003, Roman Neuhauser wrote:
> better documented, and I got to avoid SASL:
>
>
> http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=sasl+vulnerability&btnG=Google+Search
Of course, the vulnerability you're mentioning here was fixed immediately
after it was annouced.
-
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2003-07-13 09:39:53 -0400:
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2003-07-01 10:25:29 -0400:
Since I've heard bad things about Courier's standards complicance, I
Care to share some details?
Do a google groups search for the keywords "courier
# [EMAIL PROTECTED] / 2003-07-13 09:39:53 -0400:
> Roman Neuhauser wrote:
> ># [EMAIL PROTECTED] / 2003-07-01 10:25:29 -0400:
> >
> >>Since I've heard bad things about Courier's standards complicance, I
> >
> >Care to share some details?
>
> Do a google groups search for the keywords "courier
On Sun, 13 Jul 2003, Roman Neuhauser wrote:
> # [EMAIL PROTECTED] / 2003-07-01 10:25:29 -0400:
> > Since I've heard bad things about Courier's standards complicance, I
>
> Care to share some details?
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=Pine.LNX.4.50.0206050910320.6814-1000
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2003-07-01 10:25:29 -0400:
Since I've heard bad things about Courier's standards complicance, I
Care to share some details?
Do a google groups search for the keywords "courier imap compliance" or
a search for "courier" where the author is "[EM
# [EMAIL PROTECTED] / 2003-07-01 10:25:29 -0400:
> Since I've heard bad things about Courier's standards complicance, I
Care to share some details?
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message.see http://www.eyrie.org./~eagle/faqs/questions.html
On Tue, Jul 01, 2003 at 10:25:29AM -0400, Rob Siemborski wrote:
>
> Since I've heard bad things about Courier's standards complicance, I
> can't advocate its use in any way.
Don't worry, this is for copying *from* Courier *to* Cyrus :-)
> In this case, though, you have to use the plaintext IMAP
> S: * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
> THREAD=REFERENCES SORT
> What mechanism is it using? What is the right thing to do?
The IMAP4 LOGIN command, I'd expect. When there's no AUTH= offered, I'd
say that's the only thing to do, and pray that you're using SSL/TLS.
On Tue, 1 Jul 2003, Patrick Welche wrote:
> When connecting to imap servers with sasl, I thought the plan was to
> parse the capability string and add any AUTH= to the mechlist. This
> was fine for cyrus :) and UW, but pointing my code at Courier, I
> get
>
> S: * CAPABILITY IMAP4rev1 CHILDREN NAM
When connecting to imap servers with sasl, I thought the plan was to
parse the capability string and add any AUTH= to the mechlist. This
was fine for cyrus :) and UW, but pointing my code at Courier, I
get
S: * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES
SORT
.
11 matches
Mail list logo