Peter Maydell wrote:
>
> ...only of course I forgot to include the patch...
>
Hi Peter
After I used the patch, I hit another different problem.
[EMAIL PROTECTED]:~$ send -sasl -watch -verbose
Use "/home/zhangweiwu//Mail/drafts/2"? y
-- Posting for All Recipients --
post: problem initializing
Sorry for the late reply; been swamped. Hopefully can catch up now.
> >> I happen to have some spare time, which I could use to work out
> >> whether there are bugs in the bug tracking system which ought to
> >> be fixed, fix them, etc, if these are likely to get into a release...
> >
> >I think t
Peter Maydell wrote:
> (Also I'd like to audit that code to check
>that the string really is always NUL-terminated.)
I'm glad I did that, because smhear() appears to have had in it for a decade
completely broken accounting of the space left in the reply buffer in the
case where there's a continuat
>This seems to work, modulo that audit:
>[...]
Looks fine to me.
>>The second ... yeah, that patch should be applied.
>
>Do you want to commit it or shall I?
You will no doubt be able to get to it before I will, so please, go ahead.
--Ken
___
Nmh-wo
Ken Hornstein wrote:
>(I just saw your patch ... sasl_decode64() can return SASL_CONTINUE?
>Huh, I guess it can. But it looks like technically you need to handle
>that on the client in some special way, but I don't see what you're
>supposed to do. If this solves the problem, then I guess everythi
>Ken Hornstein wrote:
>>I wrote the nmh SASL code, and while my time is limited I would like to
>>continue to make sure that it works.
>
>I don't suppose you have time to look at
>https://savannah.nongnu.org/bugs/?9864
>https://savannah.nongnu.org/patch/?5230
>
>? These SASL-related suggested patch
Josh Bressers <[EMAIL PROTECTED]> writes:
>The easiest way to get nmh running on RHEL4 is going to be this:
>
>Download this:
>http://download.fedora.redhat.com/pub/fedora/linux/development/source/SRPMS/nmh-1.2-20070116cvs.4.fc9.src.rpm
>(it's the Fedora 9 nmh source rpm)
>
>Run:
>rpmbuild --rebui
Ken Hornstein wrote:
>I wrote the nmh SASL code, and while my time is limited I would like to
>continue to make sure that it works.
I don't suppose you have time to look at
https://savannah.nongnu.org/bugs/?9864
https://savannah.nongnu.org/patch/?5230
? These SASL-related suggested patches have b
Peter Maydell wrote:
>Peter Maydell wrote:
>>Anyway, for SASL, I wonder if this is the same problem as mentioned
>>here for mutt:
>>
>>http://osdir.com/ml/security.cyrus.sasl/2006-09/msg00010.html
>
>I set up a spare machine with an SMTP server with SASL enabled so
>I could test this, and reproduce
Peter Maydell wrote:
>Anyway, for SASL, I wonder if this is the same problem as mentioned
>here for mutt:
>
>http://osdir.com/ml/security.cyrus.sasl/2006-09/msg00010.html
I set up a spare machine with an SMTP server with SASL enabled so
I could test this, and reproduced the problem. In fact it tur
>[EMAIL PROTECTED]:/usr/local/nmh$ send -verbose -watch -sasl
>Use "/home/zhangweiwu//Mail/drafts/2"? y
> -- Posting for All Recipients --
>post: problem initializing server; [BHST] SASL base64 decode failed: another
>step is needed in authentication
>send: message not delivered to anyone
You mig
Zhang Weiwu wrote:
>My sasl is cyrus-sasl 2.1.22-r2
>When sending emails, I got the following:
>
>[EMAIL PROTECTED]:/usr/local/nmh$ send -verbose -watch -sasl
>Use "/home/zhangweiwu//Mail/drafts/2"? y
> -- Posting for All Recipients --
>post: problem initializing server; [BHST] SASL base64 decode f
Dear all
I am a new nmh user. I configured mts: smtp and configured SMTP server
hostname. I compiled nmh 1.2 myself with sasl support. My sasl is
cyrus-sasl 2.1.22-r2. OS is Gentoo Linux.
When sending emails, I got the following:
[EMAIL PROTECTED]:/usr/local/nmh$ send -verbose -watch -sasl
Use "
13 matches
Mail list logo