1) So, if I'm not going to put user spools in AFS space, for the reasons already discussed, are there any problem with putting them in NFS space? Does courier's locking mechanism work well enough that NFS's (terrible) locking mechanism wont be an issue? Are there any other issues I should consider if I want to have M machines doing mail delivery and M machines doing POP/IMAP sessions (where the machines may or may not overlap in each of the 3 duties), all into the same account and file space? or would that type of dynamicly balanced clustering not suit courier? would it be better to just go with static failovers if I'm going to adopt courier?
2) Has anyone set up a means of using SpamAssassin and Sophos SAVI with Courier? I currently use them via MailScanner and sendmail. It would be particularly nice if the setup could allow me to have the headers look like the same headers I'm using under Mailscanner (so that my users don't have to re-write their procmail, eudora, netscape, and mail sorting/filtering rules). 3) When converting an existing IMAP setup (UW-IMAP) with mbox folders to Courier's maildirs, do you need the unix envelope "From " to be preserved? Or can you dump it? Otherwise, what things need to be done when splitting up the mbox file into a maildir folder? is a tool for this included? 4) Similar question to #3, but with MMDF folders. While I've got mbox folders on my home mail server, the campus POP server, which I will also probably convert in the near future, uses MMDF format, and thus doesn't have the unix "From " envelope. It would be a more complex task to have to create an envelope "From " header for each message in each folder. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
