From: Jeroen de B. <in...@sp...> - 2008-02-12 16:17:46
|
Hello, I have a strange problem with the proon plugin for Squirrelmail. After installing, everything seemed to work fine (I haven't gotten to the point where it should actually do something yet...), but when I add a new account on the server and enter Squirrelmail using that account, I cannot enter the preferences anymore. I should enter automatically in the Personal Information page (caused by the askuserinfo plugin for a new account), but I enter in the Options overview page and clicking on any of the options there does nothing. By the way, I did not try the proon options link, just the normal options (Personal Information, Display Preferences, etc.). Is there some kind of incompatibility between these plugins? Thanks for any help, Jeroen -- Jeroen de Bruin Special Stamp Collections / Thom Cofre Filatelia 46520 Puerto de Sagunto Valencia, Spain tel: +34 6516 77344 skype: jeroen_de_bruin |
From: Jeroen de B. <je...@je...> - 2008-02-15 17:08:17
|
Hello, I have a problem using the proon plugin for Squirrelmail (see below) and to solve my problem I would like to use the plugin in a different way: I would like to setup proon to run as a cron job on a Linux server so that I can get rid of old messages for all users (also the users who don't use Squirrelmail if I could get it to work there...). Is that possible and is there documentation available on the subject? Thanks a lot, Jeroen de Bruin Hello, I have a strange problem with the proon plugin for Squirrelmail. After installing, everything seemed to work fine (I haven't gotten to the point where it should actually do something yet...), but when I add a new account on the server and enter Squirrelmail using that account, I cannot enter the preferences anymore. I should enter automatically in the Personal Information page (caused by the askuserinfo plugin for a new account), but I enter in the Options overview page and clicking on any of the options there does nothing. By the way, I did not try the proon options link, just the normal options (Personal Information, Display Preferences, etc.). Is there some kind of incompatibility between these plugins? Thanks for any help, Jeroen -- Jeroen de Bruin Jeronimo Design Puerto de Sagunto, Valencia Spain tel: +34 6516 77344 web: http://www.jeronimodesign.com |
From: WJCarpenter <bil...@ca...> - 2008-02-17 18:35:15
|
> I would like to setup proon to run as a cron job on a Linux server so > that I can get rid of old messages for all users (also the users who > don't use Squirrelmail if I could get it to work there...). > IMHO, as the author of proon, I think what you describe is exactly the right approach. The proper place for pruning and a lot of other message management things is on the back end, which is to say operating on the mail store itself, either by talking to the IMAP server or by working on the filesystem. Operating as part of the UI has a lot of disadvantages. For example, as you say, users who don't use SM don't get pruning. (There are some disadvantages of doing it outside of the UI layer. Users are more likely to be surprised that messages have been deleted. Some email clients will cache information about messages in folders which will be out of sync if you delete or move messages via another path [that only adds a small element of confusion and isn't too serious].) I have no idea how difficult it would be to directly run SM/proon as some kind of cron job. I suspect it would be a lot of trouble. If you are a programmer (or can get one interested :-), a better technical approach might be to forget SM and proon entirely and just reimplement the proon logic on top of some generic tool or language that knows how to speak to an IMAP server. Although there are special cases to consider for IMAP servers (which the SM code generally handles pretty well), talking directly to the IMAP servers will abstract things away from the details of the underlying mail store. You'd have to work out some scheme to let your script to logins as ordinary users (dovecot IMAP server has this feature built-in ... I don't know about others). A very large part of the proon code is concerned with building and displaying the forms and proon results report. A comparatively small part is concerned with the logic of computing which messages should be pruned and actually doing that. For a non-UI tool, you could skip most of that and just use the proon core logic to re-implement it in perl or php or python or C++ or whatever language you have which can speak IMAP. > Is that possible and is there documentation available on the subject? > There is no additional documentation about proon other than the source and the help on the form. If you go down a path of re-implementing the proon logic in a command line tool, I'd be happy to answer what questions I can. (I would probably be useless for answering questions about running SM/proon via cron.) |
From: Paul L. <pa...@sq...> - 2008-02-25 21:20:23
|
On Sun, Feb 17, 2008 at 10:37 AM, WJCarpenter <bil...@ca...> wrote: > > > I would like to setup proon to run as a cron job on a Linux server so > > that I can get rid of old messages for all users (also the users who > > don't use Squirrelmail if I could get it to work there...). > > > > IMHO, as the author of proon, I think what you describe is exactly the > right approach. The proper place for pruning and a lot of other message > management things is on the back end, which is to say operating on the > mail store itself, either by talking to the IMAP server or by working on > the filesystem. Operating as part of the UI has a lot of > disadvantages. For example, as you say, users who don't use SM don't > get pruning. Agreed. Note that some IMAP servers already support periodic cleanup of certain mail folders. You might check your IMAP configuration before going further. > (There are some disadvantages of doing it outside of the > UI layer. Users are more likely to be surprised that messages have been > deleted. Some email clients will cache information about messages in > folders which will be out of sync if you delete or move messages via > another path [that only adds a small element of confusion and isn't too > serious].) > > I have no idea how difficult it would be to directly run SM/proon as > some kind of cron job. I suspect it would be a lot of trouble. You'd have to have login information stored on the server (passwords) for all users if you tried to run SM *as is* in a cron. Bad idea(tm). You could hack it up, but... > If you > are a programmer (or can get one interested :-), a better technical > approach might be to forget SM and proon entirely and just reimplement > the proon logic on top of some generic tool or language that knows how > to speak to an IMAP server. Yep. There was already a plugin released that did this in certain environments (I think it bypassed the IMAP server and instead worked directly on maildirs (mailboxes?), which isn't the best idea IMO). It is no longer developed, but if needed, I can dig up the last version, which probably still works. > Although there are special cases to > consider for IMAP servers (which the SM code generally handles pretty > well), talking directly to the IMAP servers will abstract things away > from the details of the underlying mail store. You'd have to work out > some scheme to let your script to logins as ordinary users (dovecot IMAP > server has this feature built-in ... I don't know about others). > > > A very large part of the proon code is concerned with building and > displaying the forms and proon results report. A comparatively small > part is concerned with the logic of computing which messages should be > pruned and actually doing that. For a non-UI tool, you could skip most > of that and just use the proon core logic to re-implement it in perl or > php or python or C++ or whatever language you have which can speak IMAP. > > > > > Is that possible and is there documentation available on the subject? > > > > There is no additional documentation about proon other than the source > and the help on the form. If you go down a path of re-implementing the > proon logic in a command line tool, I'd be happy to answer what > questions I can. (I would probably be useless for answering questions > about running SM/proon via cron.) |
From: WJCarpenter <bil...@ca...> - 2008-02-12 18:42:20
|
> Is there some kind of incompatibility between these plugins? > Are you running the latest versions of proon and askuerinfo? What version of SM are you running? |
From: Paul L. <pa...@sq...> - 2008-02-12 19:34:42
|
On Feb 12, 2008 8:16 AM, Jeroen de Bruin <in...@sp...> wrote: > Hello, > > I have a strange problem with the proon plugin for Squirrelmail. > > After installing, everything seemed to work fine (I haven't gotten to > the point where it should actually do something yet...), but when I add > a new account on the server and enter Squirrelmail using that account, I > cannot enter the preferences anymore. I should enter automatically in > the Personal Information page (caused by the askuserinfo plugin for a > new account), but I enter in the Options overview page and clicking on > any of the options there does nothing. By the way, I did not try the > proon options link, just the normal options (Personal Information, > Display Preferences, etc.). Show what those links are (the ones that "do nothing"). Show your web server errors, if any (please see the posting guidelines if you do not know how to find them). > Is there some kind of incompatibility between these plugins? > > Thanks for any help, > Jeroen > > -- |