Il 07/08/2012 17:13, Eric Shubert ha scritto:
On 08/07/2012 02:19 AM, Alessio Cecchi wrote:
Hi,
I would like to switch from "autoresponder" to "qmail-autoresponder"
http://untroubled.org/qmail-autoresponder/ for store user's config in
mysql instead of .qmail and vacation/.
With qmail-autoresponder-mysql you can simply add in .qmail-default
| /usr/local/bin/qmail-autoresponder-mysql -- "$EXT" "$USER"
and manage autoresponder message only via MySQL.
Is qmailadmin geared to manage the autoresponder message via MySQL?
Users can presently manage their own message via qmailadmin.
No, qmailadmin is unable to manage this type of autoresponder. But I'm
creating a simple shell script for manage autoresponder (mysql and .qmail).
But I have a doubt, my .qmail-default now is:
# cat .qmail-default
| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
| /usr/local/bin/qmail-autoresponder-mysql -- "$EXT" "$USER"
This change may cause problems?
I do know of a qmailadmin bug which creates duplicate delivery lines
when you change the name field of an account. That has to do with the
account/.qmail file though.
yes, I know this bug, and isn't the only one.
In any case, qmailadmin updates of the .qmail-default file for bounce
processing will likely conflict. Also, command(s) in vpopmail/bin that
create/update these files could be a problem.
We rebuild always qmailadmin with "--disable-catchall". I don't love
catchall.
Do you remember some vpopmail commands that modifies .qmail-default
file? So I can test it.
Two questions come to mind about this. Why do you want this data in
mysql, and how do you intend to manage it? Some of the features of
qmail-autoresponder do look nice, but the present autoresponder comes
from inter7, and is thus fairly tightly integrated with vpopmail and
qmailadmin.
Good questions :-) My idea (in the long term) is to switch from
qmailadmin to another control panel and create a complete set of (web)
API for manage the main actions on domains and mailboxes
(create/delete/modify). Have autoresponder configuration in DB and don't
need to edit .qmail files every time is (or could be) a necessary step.
Initially I made some changes to vpopmaild and vqadmin but the job was
too complex for me so I decided to start writing a new control panel.
The new control panel will continue to use the good vpopmail commands.
When some commands are missing, for example manage autoresponder and
forward, I will create some shell scripts.
When they are ready I can share these changes.
Vpopmail does have some config options for storing data in mysql that's
presently in flat files. You might look into these config settings if
you haven't yet. We might at some point change QMT to use the database
for some of this data. I simply haven't gotten to the point of reviewing
this. We do plan to change a couple vpopmail configuration settings in
the fairly near future though, so if you'd like to come up with a
recommendation, that'd be great. Please be sure to identify benefits in
your recommendation.
I believe that storing various settings in the database is best than in
flat files, especially in case of future migration.
--
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
on LinkedIn -> http://www.linkedin.com/in/alessice
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
@ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
