Thanks for your answere!

Yes, it's a global daemon.

At this time I will test it with a file per user. If a user has no config file,

the daemon has to do nothing.

Thanks :)

Hello,

I've another  questions... I plan for my daemon to create a possibility to make settings per mailbox.

Could it make problems if I store a file in a mailbox like "mercury\mail\{mailboxname}\daemon.conf"?

Or should I better create a general file in the root of the mercury dir "mercury\mydaemon.conf" where

all setting, for each mailbox, will be stored?

Thanks.

As long as the filename won't be the same as anything that can be used by Mercury you can put it in the mailbox directories. It could be that it would be more efficient to just have a single configuration file for all users, though (at least with a global daemon if you have a lot of access but not a very large number of users).

/Rolf