Re: Passwd for file DB Vpopmail

"Ismal Hisham Darus" <[email protected]>
Newsgroups gmane.comp.horde.sork
Message-ID <432E8802.27266.511DCE@localhost>
Sorry It's a bit mess with my previous message. Let me 
rephrase it again.

Hi Gary,

Just wondering if you manage to have the same success for 
vacation mudule authenticate via vpopmail ?


Thanks.


On 19 Sep 2005 at 9:37, Ismal Hisham Darus wrote:

> Dear all,
> 
> Since I am running a mail server using vpopmail with file DB, 
> I implemented 
> this vpopmail_expect script to integrate with vpopmail. The 
> following 
> implementation should work with mysql version of vpopmail, 
> too.
> 
> Hi Gary,
> 
> Just wondering if you manage to have the same success for 
> vacation mudule authenticate via vpopmail ?
> 
> Thanks
> 
> Installation instruction:
> 
> 1 - chmod u+s /home/vpopmail/bin/vchangepw
> chmod g+s /home/vpopmail/bin/vchangepw
> 
> 2 - modify horde/passwd/main.php line 39:
> $userid = Auth::getAuth(); // instead of $userid = 
> Auth::getBareAuth();
> 
> 3 - copy the vpopmail_expect script to horde/passwd/scripts
> 
> 4 - modify the backends.php to use expect script pointing to 
> horde/passwd/scripts/vpopmail_expect
> 
> I wish it can help others who would like to integrate this 
> useful module 
> with file DB vpopmail.
> 
> Gary
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: vpopmail_expect
> Type: application/octet-stream
> Size: 1751 bytes
> Desc: not available
> Url : 
> http://lists.horde.org/archives/sork/attachments/20050914/9eb6
> f3aa/vpopmail_expect.obj
> 
> -- 
> Sork mailing list - Join the hunt: http://horde.org/bounties/#sork
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: [email protected]



-- 
Sork mailing list - Join the hunt: http://horde.org/bounties/#sork
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.