hi
On Thu, 25 Jan 2007, Chad Leigh -- Shire.Net LLC wrote:
Now it looks like this
A
B
D
E
F
G
but if I click, say E, it has F's contents, F has Gs contents, and no
mail has D's contents that I can see. But the list in the mail
client list view is correct.
So, courier is apparently opening the wrong file or it's getting incorrect
data from the disk cache when it's trying to read the next message file.
If you 'cat' those files on your server at the same time when you open
messages in your mail client, do you get the correct content (from cat) ?
And the nfs server has the ZFS option turned on to NOT update the
last accessed date for when the file is accessed for reading.
It shouldn't matter, I don't update access times on the filer either.
If you've built courier with FAM, try disabling this first just in
case.
I did not explicitly turn this on so I assume it is built witthout FAM.
If you've built it from ports, I think it's enabled by default and it's not
even FAM, but a FAM's replacement.
I would try disabling it and if it doesn't help, try using a different nfs
server to make sure it's not some solaris thing messing stuff up...
Do you have any special settings on the NetApps side or on the client
nfs side?
Nope, some optimizations, which are mostly relevant to my particular setup,
but default settings also work just fine.
8 messages in net.sourceforge.lists.courier-usersRe: [courier-users] courier-imap -- s...
