Julie S. Lin wrote:
while I understand this is prolly some obscure little thing, i'm hoping
that someone has seen it and can help out.
esp since I'm a newbie to courier.
i've two cases of weird behavior. i've upgrade the mailserver to redhat
4, courier 0.52, and courier-authlib-0.58....pls recent
versions of all the rest (pcre, pam, etc). I did use the
--enable-workarounds-for-imap option after making sure make clean
had no other errors then did make install ((perhaps this is not
correct? hence my post here today)
I don't recommend updating beyond the RHEL packages of pcre, pam, etc if
that's what you did. I'm happily running Courier on a RHEL4 box built
against the RHEL4 packages.
in both cases when I run the account on a win2k / outlook express (or
even outlook 2002) test box the user account works fine...
however, the users would like to be able to use their preferred reader,
just outlook 2002 on their own desktops
Urge your users to use a more standards compliant (and open source!)
client like Mozilla Thunderbird. I do however understand you may be
dealing with the Corporate line of "MS is the way, the truth..."
the first case, is a xp box with outlook 2002. the user (C) is able to
send messages, but does not see any messages
come in. in fact a second account on the same machine (test) is able to
receive messages from (C) just fine. when I switch
(C) to outlook express on the user desktop, it works fine.....AND....the
second case has identical symptons, expect it's
win2k / outlook 2003.
I have a hunch that your issue lies with Courier's use of fam (actually
gamin on RHEL4). Outlook 2002 will use IDLE / enhanced IDLE while OE
will not. I recommend removing the gamin-devel package from RHEL,
untarring the courier-0.52 tarball and commenting out the Requires:
Fam-devel line, then rebuilding the Courier RPM. See if that solves the
problem. Tony Earnshaw has also suggested that RedHat's fam/gamin
packages are severly broken and building your own fam from source gets
rid of many problems.
anyone have any ideas what's the deal with this? or seen this kinda
behavior? i'm hoping to avoid talking to microsoft
Don't waste your valuable sysadmin time talking to MS, in the end
they'll just give you a "maybe you should try Exchange..." crap line
anyway. As Sam has said in the past though, MS is not really interested
in supporting IMAP, it wants you to use Exchange protocol to it's
Exchange server... thus MS' IMAP code is crap.
Jay
--
Jay Lee
Network / Systems Administrator
Information Technology Dept.
Philadelphia Biblical University
--
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
