From: Murray T. <mtr...@ce...> - 2005-10-28 08:05:00
|
Hi Jamie, I noticed that the module allows me to give two different users the same alias. This isn't the behaviour desired in my case. Is there any way of stopping this by checking if the alias already exists? I suppose that would involve an LDAP search for the requested new alias of all users under that domain and accepting it if it didn't already exist. Regards Murray |
From: Craig W. <cra...@az...> - 2005-10-28 13:50:24
|
On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > Hi Jamie, > > I noticed that the module allows me to give two different users the same > alias. This isn't the behaviour desired in my case. Is there any way > of stopping this by checking if the alias already exists? I suppose > that would involve an LDAP search for the requested new alias of all > users under that domain and accepting it if it didn't already exist. ---- Alias? email alias? attribute? dn? Clarify please Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Murray T. <mtr...@ce...> - 2005-10-29 08:29:08
|
Hi Craig, I am talking about e-mail aliases which are entered in the Mail Aliases field. That stores the entry in the user's alias LDAP attribute. Murray > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > Hi Jamie, > > > > I noticed that the module allows me to give two different users the same > > alias. This isn't the behaviour desired in my case. Is there any way > > of stopping this by checking if the alias already exists? I suppose > > that would involve an LDAP search for the requested new alias of all > > users under that domain and accepting it if it didn't already exist. > ---- > Alias? email alias? attribute? dn? > > Clarify please > > Craig > |
From: Craig W. <cra...@az...> - 2005-10-29 15:47:03
|
On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > Hi Craig, > > I am talking about e-mail aliases which are entered in the Mail Aliases > field. That stores the entry in the user's alias LDAP attribute. > > Murray > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > Hi Jamie, > > > > > > I noticed that the module allows me to give two different users the same > > > alias. This isn't the behaviour desired in my case. Is there any way > > > of stopping this by checking if the alias already exists? I suppose > > > that would involve an LDAP search for the requested new alias of all > > > users under that domain and accepting it if it didn't already exist. > > ---- > > Alias? email alias? attribute? dn? > > > > Clarify please ----- In that event - an attribute of an entry, openldap wouldn't catch that and I wouldn't know about other ldap programs. That would be an interesting escalation of the power of the LDAP Users and Groups module. Considering that some of the attributes are necessarily duplicated within the DSA and some are necessarily unique, an option to check for uniqueness would have to be very configurable. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Jamie C. <jca...@we...> - 2005-10-29 19:19:05
|
On Sat, 2005-10-29 at 08:46, Craig White wrote: > On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > > Hi Craig, > > > > I am talking about e-mail aliases which are entered in the Mail Aliases > > field. That stores the entry in the user's alias LDAP attribute. > > > > Murray > > > > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > > Hi Jamie, > > > > > > > > I noticed that the module allows me to give two different users the same > > > > alias. This isn't the behaviour desired in my case. Is there any way > > > > of stopping this by checking if the alias already exists? I suppose > > > > that would involve an LDAP search for the requested new alias of all > > > > users under that domain and accepting it if it didn't already exist. > > > ---- > > > Alias? email alias? attribute? dn? > > > > > > Clarify please > ----- > In that event - an attribute of an entry, openldap wouldn't catch that > and I wouldn't know about other ldap programs. That would be an > interesting escalation of the power of the LDAP Users and Groups module. > Considering that some of the attributes are necessarily duplicated > within the DSA and some are necessarily unique, an option to check for > uniqueness would have to be very configurable. That is quite a good idea for a feature actually .. in the next release, I will add a Module Config option to specify custom fields that are not allowed to contain duplicates with other users. Also, the mail alias field will automatically have this enforced .. - Jamie |
From: Craig W. <cra...@az...> - 2005-10-30 03:17:26
|
On Sat, 2005-10-29 at 12:18 -0700, Jamie Cameron wrote: > On Sat, 2005-10-29 at 08:46, Craig White wrote: > > On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > > > Hi Craig, > > > > > > I am talking about e-mail aliases which are entered in the Mail Aliases > > > field. That stores the entry in the user's alias LDAP attribute. > > > > > > Murray > > > > > > > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > > > Hi Jamie, > > > > > > > > > > I noticed that the module allows me to give two different users the same > > > > > alias. This isn't the behaviour desired in my case. Is there any way > > > > > of stopping this by checking if the alias already exists? I suppose > > > > > that would involve an LDAP search for the requested new alias of all > > > > > users under that domain and accepting it if it didn't already exist. > > > > ---- > > > > Alias? email alias? attribute? dn? > > > > > > > > Clarify please > > ----- > > In that event - an attribute of an entry, openldap wouldn't catch that > > and I wouldn't know about other ldap programs. That would be an > > interesting escalation of the power of the LDAP Users and Groups module. > > Considering that some of the attributes are necessarily duplicated > > within the DSA and some are necessarily unique, an option to check for > > uniqueness would have to be very configurable. > > That is quite a good idea for a feature actually .. in the next release, > I will add a Module Config option to specify custom fields that are not > allowed to contain duplicates with other users. Also, the mail alias > field will automatically have this enforced .. ---- I'm all for it. Just curious - by default, Webmin doesn't include rfc822Mailbox or mail as a standard attributes and I've always added it for the base mailboxes. There is no standard for a mail alias unless you are talking about the objectclass nisMailAlias which is not an attribute so I'm not entirely sure where you are headed when you say the 'mail alias will be automatically enforced' but I'm interested. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Craig W. <cra...@az...> - 2005-11-08 03:45:16
|
On Sat, 2005-10-29 at 12:18 -0700, Jamie Cameron wrote: > On Sat, 2005-10-29 at 08:46, Craig White wrote: > > On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > > > Hi Craig, > > > > > > I am talking about e-mail aliases which are entered in the Mail Aliases > > > field. That stores the entry in the user's alias LDAP attribute. > > > > > > Murray > > > > > > > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > > > Hi Jamie, > > > > > > > > > > I noticed that the module allows me to give two different users the same > > > > > alias. This isn't the behaviour desired in my case. Is there any way > > > > > of stopping this by checking if the alias already exists? I suppose > > > > > that would involve an LDAP search for the requested new alias of all > > > > > users under that domain and accepting it if it didn't already exist. > > > > ---- > > > > Alias? email alias? attribute? dn? > > > > > > > > Clarify please > > ----- > > In that event - an attribute of an entry, openldap wouldn't catch that > > and I wouldn't know about other ldap programs. That would be an > > interesting escalation of the power of the LDAP Users and Groups module. > > Considering that some of the attributes are necessarily duplicated > > within the DSA and some are necessarily unique, an option to check for > > uniqueness would have to be very configurable. > > That is quite a good idea for a feature actually .. in the next release, > I will add a Module Config option to specify custom fields that are not > allowed to contain duplicates with other users. Also, the mail alias > field will automatically have this enforced .. ---- has this made it into the current development version that I could ***test*** ? ;-) Just asking, no pressure. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Murray T. <mtr...@ce...> - 2005-10-30 06:22:22
|
On Sun, 2005-10-30 at 03:18, Jamie Cameron wrote: > On Sat, 2005-10-29 at 08:46, Craig White wrote: > > On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > > > Hi Craig, > > > > > > I am talking about e-mail aliases which are entered in the Mail Aliases > > > field. That stores the entry in the user's alias LDAP attribute. > > > > > > Murray > > > > > > > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > > > Hi Jamie, > > > > > > > > > > I noticed that the module allows me to give two different users the same > > > > > alias. This isn't the behaviour desired in my case. Is there any way > > > > > of stopping this by checking if the alias already exists? I suppose > > > > > that would involve an LDAP search for the requested new alias of all > > > > > users under that domain and accepting it if it didn't already exist. > > > > ---- > > > > Alias? email alias? attribute? dn? > > > > > > > > Clarify please > > ----- > > In that event - an attribute of an entry, openldap wouldn't catch that > > and I wouldn't know about other ldap programs. That would be an > > interesting escalation of the power of the LDAP Users and Groups module. > > Considering that some of the attributes are necessarily duplicated > > within the DSA and some are necessarily unique, an option to check for > > uniqueness would have to be very configurable. > > That is quite a good idea for a feature actually .. in the next release, > I will add a Module Config option to specify custom fields that are not > allowed to contain duplicates with other users. Also, the mail alias > field will automatically have this enforced .. I'm wondering if the mail alias being unique should be optional on it's intended use. In my setup I have postfix configured to use an ldap-aliases file to search my LDAP directory for recipients. The search looks for matching mail and alias attributes and returns the matching users uid names which correspond with their Cyrus mailbox names so the mail can be delivered. I just tried adding the same alias e-mail address attribute to two users and an e-mail to the alias is delivered to both of them. This is probably what should happen in this case and is often pretty useful - ie. basic mailing list functionality. Maybe we need separate Personal Mail Aliases and Group Mail Alias entry fields - the former enforcing uniqueness and the latter not. The group alias would normally only be used when we specifically have a need to direct e-mail to a group of users via a common address. Murray |
From: Jamie C. <jca...@we...> - 2005-10-30 19:12:44
|
On Sat, 2005-10-29 at 23:28, Murray Trainer wrote: > On Sun, 2005-10-30 at 03:18, Jamie Cameron wrote: > > On Sat, 2005-10-29 at 08:46, Craig White wrote: > > > On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > > > > Hi Craig, > > > > > > > > I am talking about e-mail aliases which are entered in the Mail Aliases > > > > field. That stores the entry in the user's alias LDAP attribute. > > > > > > > > Murray > > > > > > > > > > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > > > > Hi Jamie, > > > > > > > > > > > > I noticed that the module allows me to give two different users the same > > > > > > alias. This isn't the behaviour desired in my case. Is there any way > > > > > > of stopping this by checking if the alias already exists? I suppose > > > > > > that would involve an LDAP search for the requested new alias of all > > > > > > users under that domain and accepting it if it didn't already exist. > > > > > ---- > > > > > Alias? email alias? attribute? dn? > > > > > > > > > > Clarify please > > > ----- > > > In that event - an attribute of an entry, openldap wouldn't catch that > > > and I wouldn't know about other ldap programs. That would be an > > > interesting escalation of the power of the LDAP Users and Groups module. > > > Considering that some of the attributes are necessarily duplicated > > > within the DSA and some are necessarily unique, an option to check for > > > uniqueness would have to be very configurable. > > > > That is quite a good idea for a feature actually .. in the next release, > > I will add a Module Config option to specify custom fields that are not > > allowed to contain duplicates with other users. Also, the mail alias > > field will automatically have this enforced .. > > I'm wondering if the mail alias being unique should be optional on it's > intended use. In my setup I have postfix configured to use an > ldap-aliases file to search my LDAP directory for recipients. The > search looks for matching mail and alias attributes and returns the > matching users uid names which correspond with their Cyrus mailbox names > so the mail can be delivered. I just tried adding the same alias e-mail > address attribute to two users and an e-mail to the alias is delivered > to both of them. This is probably what should happen in this case and > is often pretty useful - ie. basic mailing list functionality. Maybe we > need separate Personal Mail Aliases and Group Mail Alias entry fields - > the former enforcing uniqueness and the latter not. The group alias > would normally only be used when we specifically have a need to direct > e-mail to a group of users via a common address. Fair enough .. I will make duplicate checking for the alias manual. - Jamie |
From: Murray T. <mtr...@ce...> - 2005-10-31 05:13:58
|
On Mon, 2005-10-31 at 04:12, Jamie Cameron wrote: > On Sat, 2005-10-29 at 23:28, Murray Trainer wrote: > > On Sun, 2005-10-30 at 03:18, Jamie Cameron wrote: > > > On Sat, 2005-10-29 at 08:46, Craig White wrote: > > > > On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > > > > > Hi Craig, > > > > > > > > > > I am talking about e-mail aliases which are entered in the Mail Aliases > > > > > field. That stores the entry in the user's alias LDAP attribute. > > > > > > > > > > Murray > > > > > > > > > > > > > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > > > > > Hi Jamie, > > > > > > > > > > > > > > I noticed that the module allows me to give two different users the same > > > > > > > alias. This isn't the behaviour desired in my case. Is there any way > > > > > > > of stopping this by checking if the alias already exists? I suppose > > > > > > > that would involve an LDAP search for the requested new alias of all > > > > > > > users under that domain and accepting it if it didn't already exist. > > > > > > ---- > > > > > > Alias? email alias? attribute? dn? > > > > > > > > > > > > Clarify please > > > > ----- > > > > In that event - an attribute of an entry, openldap wouldn't catch that > > > > and I wouldn't know about other ldap programs. That would be an > > > > interesting escalation of the power of the LDAP Users and Groups module. > > > > Considering that some of the attributes are necessarily duplicated > > > > within the DSA and some are necessarily unique, an option to check for > > > > uniqueness would have to be very configurable. > > > > > > That is quite a good idea for a feature actually .. in the next release, > > > I will add a Module Config option to specify custom fields that are not > > > allowed to contain duplicates with other users. Also, the mail alias > > > field will automatically have this enforced .. > > > > I'm wondering if the mail alias being unique should be optional on it's > > intended use. In my setup I have postfix configured to use an > > ldap-aliases file to search my LDAP directory for recipients. The > > search looks for matching mail and alias attributes and returns the > > matching users uid names which correspond with their Cyrus mailbox names > > so the mail can be delivered. I just tried adding the same alias e-mail > > address attribute to two users and an e-mail to the alias is delivered > > to both of them. This is probably what should happen in this case and > > is often pretty useful - ie. basic mailing list functionality. Maybe we > > need separate Personal Mail Aliases and Group Mail Alias entry fields - > > the former enforcing uniqueness and the latter not. The group alias > > would normally only be used when we specifically have a need to direct > > e-mail to a group of users via a common address. > > Fair enough .. I will make duplicate checking for the alias manual. > > - Jamie How about keeping the existing mail aliases field and just adding a tickbox to allow/disallow duplicates (default ticked or unticked configurable in the module's config page). Murray |
From: Jamie C. <jca...@we...> - 2005-10-31 05:18:17
|
On Sun, 2005-10-30 at 21:19, Murray Trainer wrote: > On Mon, 2005-10-31 at 04:12, Jamie Cameron wrote: > > On Sat, 2005-10-29 at 23:28, Murray Trainer wrote: > > > On Sun, 2005-10-30 at 03:18, Jamie Cameron wrote: > > > > On Sat, 2005-10-29 at 08:46, Craig White wrote: > > > > > On Sat, 2005-10-29 at 16:34 +0800, Murray Trainer wrote: > > > > > > Hi Craig, > > > > > > > > > > > > I am talking about e-mail aliases which are entered in the Mail Aliases > > > > > > field. That stores the entry in the user's alias LDAP attribute. > > > > > > > > > > > > Murray > > > > > > > > > > > > > > > > > > > On Fri, 2005-10-28 at 16:10 +0800, Murray Trainer wrote: > > > > > > > > Hi Jamie, > > > > > > > > > > > > > > > > I noticed that the module allows me to give two different users the same > > > > > > > > alias. This isn't the behaviour desired in my case. Is there any way > > > > > > > > of stopping this by checking if the alias already exists? I suppose > > > > > > > > that would involve an LDAP search for the requested new alias of all > > > > > > > > users under that domain and accepting it if it didn't already exist. > > > > > > > ---- > > > > > > > Alias? email alias? attribute? dn? > > > > > > > > > > > > > > Clarify please > > > > > ----- > > > > > In that event - an attribute of an entry, openldap wouldn't catch that > > > > > and I wouldn't know about other ldap programs. That would be an > > > > > interesting escalation of the power of the LDAP Users and Groups module. > > > > > Considering that some of the attributes are necessarily duplicated > > > > > within the DSA and some are necessarily unique, an option to check for > > > > > uniqueness would have to be very configurable. > > > > > > > > That is quite a good idea for a feature actually .. in the next release, > > > > I will add a Module Config option to specify custom fields that are not > > > > allowed to contain duplicates with other users. Also, the mail alias > > > > field will automatically have this enforced .. > > > > > > I'm wondering if the mail alias being unique should be optional on it's > > > intended use. In my setup I have postfix configured to use an > > > ldap-aliases file to search my LDAP directory for recipients. The > > > search looks for matching mail and alias attributes and returns the > > > matching users uid names which correspond with their Cyrus mailbox names > > > so the mail can be delivered. I just tried adding the same alias e-mail > > > address attribute to two users and an e-mail to the alias is delivered > > > to both of them. This is probably what should happen in this case and > > > is often pretty useful - ie. basic mailing list functionality. Maybe we > > > need separate Personal Mail Aliases and Group Mail Alias entry fields - > > > the former enforcing uniqueness and the latter not. The group alias > > > would normally only be used when we specifically have a need to direct > > > e-mail to a group of users via a common address. > > > > Fair enough .. I will make duplicate checking for the alias manual. > > > > - Jamie > > How about keeping the existing mail aliases field and just adding a > tickbox to allow/disallow duplicates (default ticked or unticked > configurable in the module's config page). That is exactly what I did :-) - Jamie |
From: Craig W. <cra...@az...> - 2005-10-31 08:23:08
|
On Sun, 2005-10-30 at 21:17 -0800, Jamie Cameron wrote: > > > > How about keeping the existing mail aliases field and just adding a > > tickbox to allow/disallow duplicates (default ticked or unticked > > configurable in the module's config page). > > That is exactly what I did :-) > ---- I get it now - you're talking about the alias field in the cyrus configuration at the bottom of the configuration which I could never make work in RHEL 3.x I was able to get Net::LDAP installed on RHEL 4 (required MIME::Base64 and MD5 perl modules) and it appears to be working except I get an error... Failed to connect to IMAP server localhost. Maybe your module configuration is incorrect. but it seems straightforward enough, server is localhost, username is cyrus and cyrus' password - which I can do from command line all day long... # imtest -u cyrus localhost S: * OK srv1.azapple.com Cyrus IMAP4 v2.2.12-Invoca-RPM-2.2.12-9 server ready C: C01 CAPABILITY S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE STARTTLS LISTEXT LIST-SUBSCRIBED X-NETSCAPE S: C01 OK Completed Please enter your password: C: L01 LOGIN root {6} S: + go ahead C: <omitted> S: L01 OK User logged in Authenticated. Security strength factor: 0 . logout * BYE LOGOUT received . OK Completed Connection closed. So what am I doing wrong? Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Murray T. <mtr...@ce...> - 2005-10-31 08:38:17
|
On Mon, 2005-10-31 at 16:22, Craig White wrote: > On Sun, 2005-10-30 at 21:17 -0800, Jamie Cameron wrote: > > > > > > > How about keeping the existing mail aliases field and just adding a > > > tickbox to allow/disallow duplicates (default ticked or unticked > > > configurable in the module's config page). > > > > That is exactly what I did :-) > > > ---- > I get it now - you're talking about the alias field in the cyrus > configuration at the bottom of the configuration which I could never > make work in RHEL 3.x > > I was able to get Net::LDAP installed on RHEL 4 (required MIME::Base64 > and MD5 perl modules) and it appears to be working except I get an > error... > Failed to connect to IMAP server localhost. Maybe your module > configuration is incorrect. > > but it seems straightforward enough, server is localhost, username is > cyrus and cyrus' password - which I can do from command line all day > long... > > # imtest -u cyrus localhost > S: * OK srv1.azapple.com Cyrus IMAP4 v2.2.12-Invoca-RPM-2.2.12-9 server > ready > C: C01 CAPABILITY > S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS > NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND > BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE > STARTTLS LISTEXT LIST-SUBSCRIBED X-NETSCAPE > S: C01 OK Completed > Please enter your password: > C: L01 LOGIN root {6} > S: + go ahead > C: <omitted> > S: L01 OK User logged in > Authenticated. > Security strength factor: 0 > . logout > * BYE LOGOUT received > . OK Completed > Connection closed. > > So what am I doing wrong? > > Craig > Hi Craig, I never figured out imtest. Try a telnet to localhost on the imap port and do ". login userid password" for cyrus and then a test ldap user (might need an existing Cyrus mailbox). If they work then the Cyrus side of things is OK and it must be a problem in the LDAP Users module config. Murray |
From: Craig W. <cra...@az...> - 2005-10-31 15:48:27
|
On Mon, 2005-10-31 at 16:44 +0800, Murray Trainer wrote: > On Mon, 2005-10-31 at 16:22, Craig White wrote: > > On Sun, 2005-10-30 at 21:17 -0800, Jamie Cameron wrote: > > > > > > > > > > How about keeping the existing mail aliases field and just adding a > > > > tickbox to allow/disallow duplicates (default ticked or unticked > > > > configurable in the module's config page). > > > > > > That is exactly what I did :-) > > > > > ---- > > I get it now - you're talking about the alias field in the cyrus > > configuration at the bottom of the configuration which I could never > > make work in RHEL 3.x > > > > I was able to get Net::LDAP installed on RHEL 4 (required MIME::Base64 > > and MD5 perl modules) and it appears to be working except I get an > > error... > > Failed to connect to IMAP server localhost. Maybe your module > > configuration is incorrect. > > > > but it seems straightforward enough, server is localhost, username is > > cyrus and cyrus' password - which I can do from command line all day > > long... > > > > # imtest -u cyrus localhost > > S: * OK srv1.azapple.com Cyrus IMAP4 v2.2.12-Invoca-RPM-2.2.12-9 server > > ready > > C: C01 CAPABILITY > > S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS > > NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND > > BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE > > STARTTLS LISTEXT LIST-SUBSCRIBED X-NETSCAPE > > S: C01 OK Completed > > Please enter your password: > > C: L01 LOGIN root {6} > > S: + go ahead > > C: <omitted> > > S: L01 OK User logged in > > Authenticated. > > Security strength factor: 0 > > . logout > > * BYE LOGOUT received > > . OK Completed > > Connection closed. > > > > So what am I doing wrong? > > > > Craig > > > Hi Craig, > > I never figured out imtest. Try a telnet to localhost on the imap port > and do ". login userid password" for cyrus and then a test ldap user > (might need an existing Cyrus mailbox). If they work then the Cyrus > side of things is OK and it must be a problem in the LDAP Users module > config. ---- # telnet localhost 143 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK srv1.azapple.com Cyrus IMAP4 v2.2.12-Invoca-RPM-2.2.12-9 server ready . login cyrus XXXXXXXX . OK User logged in . logout * BYE LOGOUT received . OK Completed Connection closed by foreign host. imtest/telnet to 143 all the same. I can login as cyrus without a problem. But if in configuration, I set host=localhost, username=cyrus, password=XXXXXXX error message as reported above. This isn't rocket science but it isn't working. Thanks Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Craig W. <cra...@az...> - 2005-10-31 17:49:12
|
On Mon, 2005-10-31 at 08:48 -0700, Craig White wrote: > On Mon, 2005-10-31 at 16:44 +0800, Murray Trainer wrote: > > On Mon, 2005-10-31 at 16:22, Craig White wrote: > > > On Sun, 2005-10-30 at 21:17 -0800, Jamie Cameron wrote: > > > > > > > > > > > > > How about keeping the existing mail aliases field and just adding a > > > > > tickbox to allow/disallow duplicates (default ticked or unticked > > > > > configurable in the module's config page). > > > > > > > > That is exactly what I did :-) > > > > > > > ---- > > > I get it now - you're talking about the alias field in the cyrus > > > configuration at the bottom of the configuration which I could never > > > make work in RHEL 3.x > > > > > > I was able to get Net::LDAP installed on RHEL 4 (required MIME::Base64 > > > and MD5 perl modules) and it appears to be working except I get an > > > error... > > > Failed to connect to IMAP server localhost. Maybe your module > > > configuration is incorrect. > > > > > > but it seems straightforward enough, server is localhost, username is > > > cyrus and cyrus' password - which I can do from command line all day > > > long... > > > > > > # imtest -u cyrus localhost > > > S: * OK srv1.azapple.com Cyrus IMAP4 v2.2.12-Invoca-RPM-2.2.12-9 server > > > ready > > > C: C01 CAPABILITY > > > S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS > > > NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND > > > BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE > > > STARTTLS LISTEXT LIST-SUBSCRIBED X-NETSCAPE > > > S: C01 OK Completed > > > Please enter your password: > > > C: L01 LOGIN root {6} > > > S: + go ahead > > > C: <omitted> > > > S: L01 OK User logged in > > > Authenticated. > > > Security strength factor: 0 > > > . logout > > > * BYE LOGOUT received > > > . OK Completed > > > Connection closed. > > > > > > So what am I doing wrong? > > > > > > Craig > > > > > Hi Craig, > > > > I never figured out imtest. Try a telnet to localhost on the imap port > > and do ". login userid password" for cyrus and then a test ldap user > > (might need an existing Cyrus mailbox). If they work then the Cyrus > > side of things is OK and it must be a problem in the LDAP Users module > > config. > ---- > # telnet localhost 143 > Trying 127.0.0.1... > Connected to localhost.localdomain (127.0.0.1). > Escape character is '^]'. > * OK srv1.azapple.com Cyrus IMAP4 v2.2.12-Invoca-RPM-2.2.12-9 server > ready > . login cyrus XXXXXXXX > . OK User logged in > . logout > * BYE LOGOUT received > . OK Completed > Connection closed by foreign host. > > imtest/telnet to 143 all the same. I can login as cyrus without a > problem. But if in configuration, I set host=localhost, username=cyrus, > password=XXXXXXX error message as reported above. This isn't rocket > science but it isn't working. > ---- going through my logs, it shows that cyrus has indeed logged in successfully so it appears to be an issue with Net::LDAP (NetxAP) and RHEL distributions though I can get it installed on RHEL 4 where I couldn't get that far on RHEL 3 Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Jamie C. <jca...@we...> - 2005-10-31 18:09:43
|
On Mon, 2005-10-31 at 09:48, Craig White wrote: > On Mon, 2005-10-31 at 08:48 -0700, Craig White wrote: > > On Mon, 2005-10-31 at 16:44 +0800, Murray Trainer wrote: > > > On Mon, 2005-10-31 at 16:22, Craig White wrote: > > > > On Sun, 2005-10-30 at 21:17 -0800, Jamie Cameron wrote: > > > > > > > > > > > > > > > > How about keeping the existing mail aliases field and just adding a > > > > > > tickbox to allow/disallow duplicates (default ticked or unticked > > > > > > configurable in the module's config page). > > > > > > > > > > That is exactly what I did :-) > > > > > > > > > ---- > > > > I get it now - you're talking about the alias field in the cyrus > > > > configuration at the bottom of the configuration which I could never > > > > make work in RHEL 3.x > > > > > > > > I was able to get Net::LDAP installed on RHEL 4 (required MIME::Base64 > > > > and MD5 perl modules) and it appears to be working except I get an > > > > error... > > > > Failed to connect to IMAP server localhost. Maybe your module > > > > configuration is incorrect. > > > > > > > > but it seems straightforward enough, server is localhost, username is > > > > cyrus and cyrus' password - which I can do from command line all day > > > > long... > > > > > > > > # imtest -u cyrus localhost > > > > S: * OK srv1.azapple.com Cyrus IMAP4 v2.2.12-Invoca-RPM-2.2.12-9 server > > > > ready > > > > C: C01 CAPABILITY > > > > S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS > > > > NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND > > > > BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE > > > > STARTTLS LISTEXT LIST-SUBSCRIBED X-NETSCAPE > > > > S: C01 OK Completed > > > > Please enter your password: > > > > C: L01 LOGIN root {6} > > > > S: + go ahead > > > > C: <omitted> > > > > S: L01 OK User logged in > > > > Authenticated. > > > > Security strength factor: 0 > > > > . logout > > > > * BYE LOGOUT received > > > > . OK Completed > > > > Connection closed. > > > > > > > > So what am I doing wrong? > > > > > > > > Craig > > > > > > > Hi Craig, > > > > > > I never figured out imtest. Try a telnet to localhost on the imap port > > > and do ". login userid password" for cyrus and then a test ldap user > > > (might need an existing Cyrus mailbox). If they work then the Cyrus > > > side of things is OK and it must be a problem in the LDAP Users module > > > config. > > ---- > > # telnet localhost 143 > > Trying 127.0.0.1... > > Connected to localhost.localdomain (127.0.0.1). > > Escape character is '^]'. > > * OK srv1.azapple.com Cyrus IMAP4 v2.2.12-Invoca-RPM-2.2.12-9 server > > ready > > . login cyrus XXXXXXXX > > . OK User logged in > > . logout > > * BYE LOGOUT received > > . OK Completed > > Connection closed by foreign host. > > > > imtest/telnet to 143 all the same. I can login as cyrus without a > > problem. But if in configuration, I set host=localhost, username=cyrus, > > password=XXXXXXX error message as reported above. This isn't rocket > > science but it isn't working. > > > ---- > going through my logs, it shows that cyrus has indeed logged in > successfully so it appears to be an issue with Net::LDAP (NetxAP) and > RHEL distributions though I can get it installed on RHEL 4 where I > couldn't get that far on RHEL 3 Some people have reported problems with Net::LDAP and Cyrus before .. try doing a search on the mailing list. Unfortunately I don't use Cyrus myself, so I can't help much .. - Jamie |
From: Craig W. <cra...@az...> - 2005-10-31 20:06:39
|
On Mon, 2005-10-31 at 10:09 -0800, Jamie Cameron wrote: > > ---- > > going through my logs, it shows that cyrus has indeed logged in > > successfully so it appears to be an issue with Net::LDAP (NetxAP) and > > RHEL distributions though I can get it installed on RHEL 4 where I > > couldn't get that far on RHEL 3 > > Some people have reported problems with Net::LDAP and Cyrus before .. > try doing a search on the mailing list. Unfortunately I don't use Cyrus > myself, so I can't help much .. ---- in the last 2 years or so - it's primarily been me ;-) I had forgotten that I got a new server at home and set it up with CentOS 4 which I was able to load Net::LDAP where I wasn't able to do that with RHEL 3. We need to get you to see the light of cyrus ;-) I suppose I can debug, I have other fish to fry for the time being. Thanks Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |