I noticed that maybe I should have changed _all_ the entry of type:

$conf['server']['params']['default']['XXXXXX']

to:

$conf['server']['params']['example.com']['XXXXXX']



After doing this I don't get the warning anymore.



Also, I noticed that whatever ['default'] or ['example.com'] I use it 
works fine now. I was sure it didn't work before (but maybe I only 
forgot to relogin in horde after changing configuration? I was, 
however, pretty sure I did a relogin).



The bug could then be closed. I'll reopen if I'll have other problem.

I guess you are using the FTP VFS driver? Try editing 
horde/lib/VFS/ftp.php and remove the @ characters in front of the 
ftp_put() call in the write() method. Then see if you get some more 
useful PHP warnings.

Done. When trying to submit my vacation message I get this:



Error  Failure in modifying vacation notice: Unable to write VFS file 
".vacation.pag".

Try manually editing your conf.php and changing the realm name from 
"default" to

the value of your realm.  So if you realm was "example.com" you could 
try changing



$conf['server']['params']['default']['dbtype'] = 'hash3';



to



$conf['server']['params']['example.com']['dbtype'] = 'hash3';



If that works, then it is a realm issue.  You'd then have to look at 
the conf.xml stuff to

see if it is supporting realms correctly or not, and if so how to use 
them with it...

For now, try manually editing the file to see if it works or not.

Yes, I have a realm defined in

imp/config/servers.php

within $servers['imap'] = array( ....
It's not very clear to me what should I do.

Do you have a realm defined?  If so, you need to define it with the 
realm name. If not,

then it should work as shown (using "default" for the realm).

This is what I have in my conf.php:

$conf['server']['params']['default']['dbtype'] = 'hash3';

but it alwys take empty.empty.bin .



Could you reproduce the problem?

I'm sorry, but I'm not entirely sure we're talking about the same 
question - in the config file, is the setting correct? In other words, 
is the dbtype right in the configuration file, but not being honored? 
Or is it not even getting into the configuration file correctly?

It was always empty, whatever dbtype I selected.

So you had set the dbtype parameter to 'hash3', but it was defaulting 
to 'empty'?

I work around it with this hack:

empty.empty.bin -> empty.hash3.bin



empty.empty.bin is now a simbolic link to empty.hash3.bin (the db I 
wanted to use).

When using vacation, whatever type of database driver I use (empty, 
hash, hash3 ...) the .vacation.db file is created empty.

The .forward file is created fine.