Re: courier-imap authentication and vpopmail 4.9.5
courier-imap uses the same code base. You should be able to copy the preauthvchkpw.c (or whatever it's called) into courier-imap/authlib and compile. I'm working on a new preauthvchkpw.c file. It will support the gid flags in vpopmail. It will also open up the smtp relay, a la vpopmail roaming users, for imap user logins. Once it's all set I'll send it off to MrSam so he can include it in the next releases. Cheers Ken Jones Matt Simerson wrote: Follow up: I was partially in error when I stated that sqwebmail failed to authenticate against vpopmail users whose domains were in users home directory other than vpopmails. It does in fact work if you read the vpopmail web page and catch the new link to the patched preauthvchkpw.c. Works just peachy with sqwebmail 1.0 and domains within or out of vpopmails home dir. Now if only I had the patch to make courier-imap do that... BTW: I have written up the procedure I have used to build a mail toaster based around qmail, vpopmail, sqwebmail, courier-imap, and all the trimmings. It does everything I can think of having a mail server do except smtp-auth which I'll get around to implementing here someday. It's at http://matt.simerson.net/computing/qmail.toaster.shtml. Comments and suggestions are welcome. When I get some more time on my hands I'll so some really cool stuff like write up scripts that feed the log files through the processors and graph how many messages the servers are handling, cpu load, and network activity in something pretty like MRTG. Matt -Original Message- From: Matt Simerson [mailto:[EMAIL PROTECTED]] Sent: Sunday, October 15, 2000 5:44 PM To: Vpopmail (E-mail) Subject: RE: quota question on 4.9.5 I've installed the new vpopmail 4.9.5 and created a couple users under system users other than vpopmail and they work just fine for mail delivery and pop but neither sqwebmail nor courier-imap will authenticate users whose UID/GID is not vpopmail/vchkpw. Courier-imap has it's own authentication module for authenticating a vpopmail user. I had courier-imap 1.0 installed and it failed with an error message that indicated an authentication failure. Just for grins I decided to see if it was fixed in courier-imap 1.1 and installed it. It works just fine for domains installed user the vpopmail UID/GID but still won't authenticate for domains within another home dirctory. The error message returned is: Your account is temporarily unavailable (+t bit set on home directory). Configuration: Account: admin.mail.safeserver.com (1) Server: admin.mail.safeserver.com User name: [EMAIL PROTECTED] Protocol: IMAP Port: 993 Secure(SSL): 1 Code: 800cccdd It yields the same error message when connecting to either the IMAP or IMAP SSL ports. The same problem plagues sqwebmail at this time too. It won't authenticate users whose domains are not located within the ~vpopmail dir. I tried installing the newer 1.0.0.20001007 version but without success (so far, I'm still playing with it). Have I just missed something completely obvious or is this a valid limitation at this time? Matt -Original Message- From: listy-dyskusyjne Krzysztof Dabrowski [mailto:[EMAIL PROTECTED]] Sent: Sunday, October 15, 2000 2:42 PM To: [EMAIL PROTECTED] Subject: Re: quota question on 4.9.5 I don't mind doing some coding, but there seems to be more missing. I'll need to dig through the code some more. It would be nice if we can have the postmaster get an unlimited quota so they can be informed that their domain is over quota and that they should get the quota increased or have their people start cleaning up their mail. The postmaster may need to get mail on each bounce (not the message, but that a message from so-and-so bounced), and possibly which ID's are using up the space so it can be cleaned properly. Before putting some code together, we may want to put together a real design first and try to think it through. The domain per unix ID is good, but we may want to put the postmaster in a different place so they can still get notifications. What are your thoughts? What else did I miss? (I'm sure I've missed alot). My vargid patch (get it from my page, announced on the list separately) will let you choose any gid/uid for any domain. We can then use a GID per domain scheme. Postmaster can be given another uid (a special one) so it wont have the quota. I do not know 2 things at this point: a) how group user quotas mix together b) is it reasonable to have one quota-less account and give it to user... they will use this account to transfer big emials for sure and this is what we want to stop , using quotas. Kris
Re: courier-imap authentication and vpopmail 4.9.5
on 10/17/00 6:44 PM, Ken Jones at [EMAIL PROTECTED] wrote: I'm working on a new preauthvchkpw.c file. It will support the gid flags in vpopmail. It will also open up the smtp relay, a la vpopmail roaming users, for imap user logins. Once it's all set I'll send it off to MrSam so he can include it in the next releases. This is good news.. I have a few IMAP users that currently have to setup bogus POP accounts just to get in the open.smtp relay file.. this is a better solution. Thanks, Bill Shupp
RE: courier-imap authentication and vpopmail 4.9.5
Follow up: I was partially in error when I stated that sqwebmail failed to authenticate against vpopmail users whose domains were in users home directory other than vpopmails. It does in fact work if you read the vpopmail web page and catch the new link to the patched preauthvchkpw.c. Works just peachy with sqwebmail 1.0 and domains within or out of vpopmails home dir. Now if only I had the patch to make courier-imap do that... BTW: I have written up the procedure I have used to build a mail toaster based around qmail, vpopmail, sqwebmail, courier-imap, and all the trimmings. It does everything I can think of having a mail server do except smtp-auth which I'll get around to implementing here someday. It's at http://matt.simerson.net/computing/qmail.toaster.shtml. Comments and suggestions are welcome. When I get some more time on my hands I'll so some really cool stuff like write up scripts that feed the log files through the processors and graph how many messages the servers are handling, cpu load, and network activity in something pretty like MRTG. Matt -Original Message- From: Matt Simerson [mailto:[EMAIL PROTECTED]] Sent: Sunday, October 15, 2000 5:44 PM To: Vpopmail (E-mail) Subject: RE: quota question on 4.9.5 I've installed the new vpopmail 4.9.5 and created a couple users under system users other than vpopmail and they work just fine for mail delivery and pop but neither sqwebmail nor courier-imap will authenticate users whose UID/GID is not vpopmail/vchkpw. Courier-imap has it's own authentication module for authenticating a vpopmail user. I had courier-imap 1.0 installed and it failed with an error message that indicated an authentication failure. Just for grins I decided to see if it was fixed in courier-imap 1.1 and installed it. It works just fine for domains installed user the vpopmail UID/GID but still won't authenticate for domains within another home dirctory. The error message returned is: Your account is temporarily unavailable (+t bit set on home directory). Configuration: Account: admin.mail.safeserver.com (1) Server: admin.mail.safeserver.com User name: [EMAIL PROTECTED] Protocol: IMAP Port: 993 Secure(SSL): 1 Code: 800cccdd It yields the same error message when connecting to either the IMAP or IMAP SSL ports. The same problem plagues sqwebmail at this time too. It won't authenticate users whose domains are not located within the ~vpopmail dir. I tried installing the newer 1.0.0.20001007 version but without success (so far, I'm still playing with it). Have I just missed something completely obvious or is this a valid limitation at this time? Matt -Original Message- From: listy-dyskusyjne Krzysztof Dabrowski [mailto:[EMAIL PROTECTED]] Sent: Sunday, October 15, 2000 2:42 PM To: [EMAIL PROTECTED] Subject: Re: quota question on 4.9.5 I don't mind doing some coding, but there seems to be more missing. I'll need to dig through the code some more. It would be nice if we can have the postmaster get an unlimited quota so they can be informed that their domain is over quota and that they should get the quota increased or have their people start cleaning up their mail. The postmaster may need to get mail on each bounce (not the message, but that a message from so-and-so bounced), and possibly which ID's are using up the space so it can be cleaned properly. Before putting some code together, we may want to put together a real design first and try to think it through. The domain per unix ID is good, but we may want to put the postmaster in a different place so they can still get notifications. What are your thoughts? What else did I miss? (I'm sure I've missed alot). My vargid patch (get it from my page, announced on the list separately) will let you choose any gid/uid for any domain. We can then use a GID per domain scheme. Postmaster can be given another uid (a special one) so it wont have the quota. I do not know 2 things at this point: a) how group user quotas mix together b) is it reasonable to have one quota-less account and give it to user... they will use this account to transfer big emials for sure and this is what we want to stop , using quotas. Kris
