> Yes, I understand, and everything works. Message and subject is saved, and
> sent to Sender (provided there is a .vacation.db). If the .db-file is not
> present, the Sender gets a bounce message from postfix:
>
> Command died with status 1: "/usr/bin/vacation <user>"
>
> and a message in mail.log about missing .vacation.db
>
> But the plugin works.
>
> I am not much of a programmer, but I will try to find some time to dig
> into it.
>
> Thanks so far, will keep you posted.
Hi all,
I had this problem as well. I installed the vacation_local, jumped through the
hoops to get it working, and was able to get the plugin working. However, the
actual sending of the vacation message was getting the "Command died with status
1" error.
I knew that the problem had to do with the missing .vacation.db file because I
encountered and fixed this before but that was not with a webmail interface and
plugin so this was some new territory for me.
I am running:
-- SquirrelMail version 1.4.5
-- SquirrelMail vacation_local plugin version 2.0
-- Postfix 2.1.1
I could not find the alpha or beta file of vacation_local floating around so I
had to configure what I had.
Because the interface runs as the apache server user such as "wwwrun" it does
not have the permission to write to the users home directory. So to resolve
this I set up a sudoers file to allow "wwwrun" to run the vacation
initialization as the user setting the vacation message. So I had to give
permission to "wwwrun" for all of the users who need to write the messages. I
only have around 23 users who need to be set up with this so this configuration
is not a big deal for me. There could be a better way of doing such as giving
permissions to a group ID. I didn't explore anything like that.
Using visudo here is the sudoers file I set up:
Runas_Alias POPMAIL = {list of users using the vacation utility}
.
.
wwwrun ALL=(POPMAIL) NOPASSWD: /usr/bin/vacation
This last statement tells the system that the user "wwwrun" can run the command
"/usr/bin/vacation" as any of the users in "POPMAIL" without entering an
password for that user.
The next thing I did was get the vacation_local to initialize the database after
a user entered in a vacation message. To do this I edited the following:
vacation_local/config.php:
I added the following statements:
$sudo_binary = '/usr/bin/sudo -u';
$vacation_initialize = '/usr/bin/vacation -I';
vacation_local/vac_init.php:
I added the following statement:
// upload
//
upload_data($forward_file_contents, $forward_file);
ADDED ----> exec($sudo_binary . ' ' . $username . ' ' . $vacation_initialize);
The config.php file changes are just variable set ups. The change to
vac_init.php tells the system that after the updated/new vacation message is
uploaded to the user's home directory it will run a vacation initialization as
the user who just did the message.
I have tested this several times and it works. So, if anyone is having this
same problem and they don't have the next version that is supposed to
incorporate the initialization you can try out these changes I did and see how
it works for you.
Thanks all.
Trevor Cullingsworth
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
--
squirrelmail-users mailing list
Posting Guidelines:
http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines
List Address: squirrelmail-users@lists.sourceforge.net
List Archives:
http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
