Scott Neal wrote:
> On 1 Feb 2007 at 17:07, Trapper wrote:
> 
>> I tried the conf/defaults.generic.inc hack. It does create the special
>> folder names in the folder list. However, it does not create the
>> folders for me. I still have to depend on the user to do this through
>> their Options interface.
>>
>> As far as other folders goes, I have Mercury Mail Transport's IMAP
>> server it it has no facility to create folder files when a new user is
>> created on the mail server.
> 
> 
> For this purpose I have what I call my 'IMAP_skeleton' folder.  With 
> a dummy user logged in with Ilohamail (or any IMAP client), create 
> the 'Trash' and 'Sent' folders (see below about INBOX).  The result 
> is the following list of files, which I copy to the new user's 
> mailbox directory:
> 
> FOL006CA.PMI
> FOL006CA.PMM
> FOL00EE6.PMI
> FOL00EE6.PMM
> HIERARCH.PM
> IMAPSUB.PM
> STATE.PMJ
> 
> The *.PMI and *.PMM file pairs are the Trash and Sent mail folders, 
> the last five (hex) digits in the filename will differ for you as 
> they are automagically generated by Mercury/32.  The rest of the 
> files are other components of Mercury/32's IMAP system and are all 
> text files which you can examine with your favorite text editor.
> 
> 
>> I note that RoundCube does physically create Sent, Trash and Draft
>> folders by default. I'll sift through the code and see if I can figure
>> out how they accomplish it. Perhaps it will offer an idea.
>>
>> Sadly, the IMAP server is in the Windows NT 4.0 environment. I doubt I
>> will have much success in preventing folder deletions through the OS's
>> permissions and still maintain write permissions on the folder. :) I
> 
> 
> My opinion...tell them this is standard operating procedure, if they 
> don't like it, take it up with the boss.  Rules are a necessary part 
> of organizational operation...enough said.
> 
> As far as the NT4 box goes, no need to be sad about it.  If it's 
> rock solid, uhh...rock on!  If not, replace it.  My only other point 
> of concern might be that if IIS4 is running behind Ilohamail, you 
> need to pay attention to making it safe.
> 
> 
>> note that the INBOX cannot be deleted in IlohaMail though so there
>> must be some secret somewhere.
> 
> The 'secret' is the INBOX is a pseudo folder.  Each message 
> delivered to a user is written to the mailbox directory as an 
> individual *.CNM file.  Mercury/32 then presents them as the 
> contents of the IMAP client's INBOX.
> 
> It doesn't make sense for any IMAP client to delete the INBOX 
> anyway.  Throw IMAP out of the picture...how many mail clients let 
> the user delete the local INBOX/New Mail folder?
> 
> 
>> Thanks for your input. I will continue working on this and post any
>> success resolves I may come up with.
>>

Hi Scott. Good to hear from you. Thanks for all the information.

I could swear that I tried the 'IMAP_skeleton' trick you mentioned but 
it failed. I maybe flubbed it up and will try again. Obviously it works 
for you so it should for me.

My NT4 box has been dependable for years. No problems here and 
absolutely no reason to change to anything else. We'll just execute 
anyone that starts deleting folders. :-)

As for IIS4, nope, not here. We have Apache 2 running and haven't 
experienced any unsafe happenings yet.

Thanks Again,
   Trapper

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Ilohamail-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ilohamail-users

Reply via email to