Re: vacation with .forward
Michael Bunk <[email protected]>
| Newsgroups | gmane.comp.isp.ispman.devel |
|---|---|
| Organization | Computer Leipzig |
| Message-ID | <[email protected]> |
Hi, thanks for so much feedback. I understand that it makes most sense to put vacation/autoreply functionality into a web based mail client. That webmail client would have to store the autoreply information somewhere, but under the user's uid, not the webserver's. I found the vacation plugin for IMP that uploads autoreply information to an ftp server. But we don't want to give ftp access to all our mail users. Setting up a second ftp server that is available internally only - and this way for the webmail client - would be an option. But to be correct, ftp uploads would have to go to the user's filehost. That information is available in LDAP only. There is no webmail app plugin, that can do this for us. For avelsieve/websieve/smartvieve, I would need a server talking the MANAGESIEVE protocol, kind of limited ftp. But using courier-imapd, there is no timsieved. For gnarwl, http://www.oss.billiton.de/software.shtml , that manages auto-reply via LDAP, the autoreply settings would have to get into LDAP first. So ideal for me, having no MANGESIEVE daemon, would be a webmail app plugin that gets the correct internal ftp server to upload to and download current .forward settings from... it sounds not practical. I will go on like i had planned, but these changes I will do for myself. Maybe next time I use cyrus instead :) Mit freundlichen Grüßen, Michael Bunk www.computer-leipzig.de ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id040&op=click