5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Error in IMAP com...
FromSent OnAttachments
Dan KuykendallJun 19, 2000 6:37 am 
Anand BuddhdevJun 19, 2000 9:29 am 
Lars HeuerJun 19, 2000 9:47 am 
Dan KuykendallJun 19, 2000 10:06 am 
Sam VarshavchikJun 19, 2000 10:16 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Error in IMAP command recieved by serverActions...
From:Anand Buddhdev (ar@anand.org)
Date:Jun 19, 2000 9:29:33 am
List:net.sourceforge.lists.courier-users

On Mon, Jun 19, 2000 at 06:38:21AM -0700, Dan Kuykendall wrote:

It was rather rude of you to post a huge 360K message to a mailing list. You should have instead provided a web page to the output, so that only those who need to see it can look at it.

On another side note, if you extract the source code from a tarball, and then edit the spec files, you don't need to tar and zip it up again. You can simply do:

rpm -ba /path/to/spec/file, instead of rpm -ta <tarball>

Saves time. man rpm.

I compiled with the workaround and it still happens. Any ideas as to what I can try next?

Double check that you`ve actually installed the recompiled version, and that you have not misspelled the option when configuring.

I recompiled from source and it seems to be working.

I had first tried to compile to RPM, then install from that, but I was foiled at every turn. First I untarred the file, then I edited both the courier-imap.spec and courier-imap.spec configure line(s) to look like this %configure --localstatedir=%{_localstatedir} \ --with-authdaemonvar=%{authdaemondir} \ --enable-workarounds-for-imap-client-bugs

and once like this: %configure --localstatedir=%{_localstatedir} --with-authdaemonvar=%{authdaemondir} --enable-workarounds-for-imap-client-bugs

(the above is one single long line)

Then I created a new tarball and gzipped it. Then ran rpm -ta against it. When I had the --enable-workarounds-for-imap-client-bugs, it would always bomb out, but if I took that out it worked fine. I have attached my session logs so you can see whats happening.

[snip]