Re: [OpenIndiana-discuss] Long User Names for Email Advice
Happy to help! So yes, it sounds like your problem is getting sendmail to deliver to the virtual user mailboxes. Would you consider using exim or postfix instead of sendmail? They're both infinitely easier to use, more secure, and more common these days than sendmail. If not, sendmail can be made to do it properly too, it's just not as simple as the other SMTP servers! Mat On 12 Dec 2012, at 17:03, dormitionsk...@hotmail.com dormitionsk...@hotmail.com wrote: REALLY??? I didn't know this. Thank you very much. This sounds like a much safer and better way to go than risking having problems from operating system level limitations. God bless you. On Dec 12, 2012, at 3:00 AM, Matt Clark wrote: I would highly recommend dovecot as an IMAP server. It's fast, secure, easy to configure, very well maintained and also very flexible about virtual user management. See http://wiki2.dovecot.org/VirtualUsers On 12 Dec 2012, at 03:04, dormitionsk...@hotmail.com dormitionsk...@hotmail.com wrote: Yikes! I think this is a little beyond my abilities. I'm a lot more of a programmer than a system admin. I think a more reasonable approach for me would be that if I run into problems with the long user names using uw-imap, to just use Cyrus-Imap instead. It doesn't require system user accounts. I didn't like it as well as uw-imap when I tried it for a while on Linux several years ago. It's a lot harder to administer and it's not nearly as mobile as uw-imap. By mobile, I mean that with uw-imap, it's a lot easier to move people's mail from one server to another, and to restore inadvertently deleted mailbox folders, etc. I appreciate the suggestion, though. I really do. I'm an Orthodox Christian priest-monk, and for what it's worth, I pray for all of you OI developers. I greatly appreciate all of the hard work you are putting into making OI a viable and freely available Solaris-based operating system. And I know my God has most certainly helped me on several occasions to get our OI server I've been working on these past few weeks to get it to the point where it's almost ready to put online. I don't think that with as much help as He's given me with this, that he'll abandon the OI Project, or you all, from His care. Thank you again. Peter, hieromonk On Dec 10, 2012, at 8:35 PM, Jim Klimov wrote: On 2012-12-11 01:54, dormitionsk...@hotmail.com wrote: Peter, Thank you very much for your feedback. I really appreciate it. Are there any particular tests that you think I should run, just to make sure that I'm not likely to run into corrupted emails three or four months down the road, well after I've implemented OI? I figured I'd test it with sending, replying to, etc. emails of various different scenarios, just to be on the safe side. But if you think I should test anything in particular, I'd appreciate your thoughts. Is an alternate solution possible for you: use an LDAP catalog with email data for users (as well as POSIX data for UNIX accounts)? This way you can have short uid values and arbitrarily long mail, mailEquivalentAddress or mailAlternateAddress properties. One of these may be u...@domain.com to avoid ambiguity, but is not required to be. There are a number of tutorials about making the Solaris operating environment a client of LDAP (Sun DSEE, OpenDJ, OpenLDAP, etc.); however, the mail subsystem will require its own integration for mail routing to the mailbox server (mailHost), alias address processing, etc. It is well documented for Sendmail in the internet, I am not sure about uw-imap. Don't think it should have problems... Also note that you'd want to avoid a deadlock (rather, a needless startup delay) by making an operating environment (global or local zone) which hosts the LDAP service a UNIX-client of this service. If you must do that, make the LDAP server start up before the SMF service ldap/client. I'd just put different tasks in local zones, LDAP server into one, mail into another, global zone as hypervisor with no end-users (except admins) and no LDAP client. HTH, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Long User Names for Email Advice
Sorry list, accidentally sent private message here. Please ignore On 15 Dec 2012, at 15:35, Matt Clark m...@mattclark.net wrote: Happy to help! So yes, it sounds like your problem is getting sendmail to deliver to the virtual user mailboxes. Would you consider using exim or postfix instead of sendmail? They're both infinitely easier to use, more secure, and more common these days than sendmail. If not, sendmail can be made to do it properly too, it's just not as simple as the other SMTP servers! Mat On 12 Dec 2012, at 17:03, dormitionsk...@hotmail.com dormitionsk...@hotmail.com wrote: ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Long User Names for Email Advice
I would highly recommend dovecot as an IMAP server. It's fast, secure, easy to configure, very well maintained and also very flexible about virtual user management. See http://wiki2.dovecot.org/VirtualUsers On 12 Dec 2012, at 03:04, dormitionsk...@hotmail.com dormitionsk...@hotmail.com wrote: Yikes! I think this is a little beyond my abilities. I'm a lot more of a programmer than a system admin. I think a more reasonable approach for me would be that if I run into problems with the long user names using uw-imap, to just use Cyrus-Imap instead. It doesn't require system user accounts. I didn't like it as well as uw-imap when I tried it for a while on Linux several years ago. It's a lot harder to administer and it's not nearly as mobile as uw-imap. By mobile, I mean that with uw-imap, it's a lot easier to move people's mail from one server to another, and to restore inadvertently deleted mailbox folders, etc. I appreciate the suggestion, though. I really do. I'm an Orthodox Christian priest-monk, and for what it's worth, I pray for all of you OI developers. I greatly appreciate all of the hard work you are putting into making OI a viable and freely available Solaris-based operating system. And I know my God has most certainly helped me on several occasions to get our OI server I've been working on these past few weeks to get it to the point where it's almost ready to put online. I don't think that with as much help as He's given me with this, that he'll abandon the OI Project, or you all, from His care. Thank you again. Peter, hieromonk On Dec 10, 2012, at 8:35 PM, Jim Klimov wrote: On 2012-12-11 01:54, dormitionsk...@hotmail.com wrote: Peter, Thank you very much for your feedback. I really appreciate it. Are there any particular tests that you think I should run, just to make sure that I'm not likely to run into corrupted emails three or four months down the road, well after I've implemented OI? I figured I'd test it with sending, replying to, etc. emails of various different scenarios, just to be on the safe side. But if you think I should test anything in particular, I'd appreciate your thoughts. Is an alternate solution possible for you: use an LDAP catalog with email data for users (as well as POSIX data for UNIX accounts)? This way you can have short uid values and arbitrarily long mail, mailEquivalentAddress or mailAlternateAddress properties. One of these may be u...@domain.com to avoid ambiguity, but is not required to be. There are a number of tutorials about making the Solaris operating environment a client of LDAP (Sun DSEE, OpenDJ, OpenLDAP, etc.); however, the mail subsystem will require its own integration for mail routing to the mailbox server (mailHost), alias address processing, etc. It is well documented for Sendmail in the internet, I am not sure about uw-imap. Don't think it should have problems... Also note that you'd want to avoid a deadlock (rather, a needless startup delay) by making an operating environment (global or local zone) which hosts the LDAP service a UNIX-client of this service. If you must do that, make the LDAP server start up before the SMF service ldap/client. I'd just put different tasks in local zones, LDAP server into one, mail into another, global zone as hypervisor with no end-users (except admins) and no LDAP client. HTH, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Long User Names for Email Advice
REALLY??? I didn't know this. Thank you very much. This sounds like a much safer and better way to go than risking having problems from operating system level limitations. God bless you. On Dec 12, 2012, at 3:00 AM, Matt Clark wrote: I would highly recommend dovecot as an IMAP server. It's fast, secure, easy to configure, very well maintained and also very flexible about virtual user management. See http://wiki2.dovecot.org/VirtualUsers On 12 Dec 2012, at 03:04, dormitionsk...@hotmail.com dormitionsk...@hotmail.com wrote: Yikes! I think this is a little beyond my abilities. I'm a lot more of a programmer than a system admin. I think a more reasonable approach for me would be that if I run into problems with the long user names using uw-imap, to just use Cyrus-Imap instead. It doesn't require system user accounts. I didn't like it as well as uw-imap when I tried it for a while on Linux several years ago. It's a lot harder to administer and it's not nearly as mobile as uw-imap. By mobile, I mean that with uw-imap, it's a lot easier to move people's mail from one server to another, and to restore inadvertently deleted mailbox folders, etc. I appreciate the suggestion, though. I really do. I'm an Orthodox Christian priest-monk, and for what it's worth, I pray for all of you OI developers. I greatly appreciate all of the hard work you are putting into making OI a viable and freely available Solaris-based operating system. And I know my God has most certainly helped me on several occasions to get our OI server I've been working on these past few weeks to get it to the point where it's almost ready to put online. I don't think that with as much help as He's given me with this, that he'll abandon the OI Project, or you all, from His care. Thank you again. Peter, hieromonk On Dec 10, 2012, at 8:35 PM, Jim Klimov wrote: On 2012-12-11 01:54, dormitionsk...@hotmail.com wrote: Peter, Thank you very much for your feedback. I really appreciate it. Are there any particular tests that you think I should run, just to make sure that I'm not likely to run into corrupted emails three or four months down the road, well after I've implemented OI? I figured I'd test it with sending, replying to, etc. emails of various different scenarios, just to be on the safe side. But if you think I should test anything in particular, I'd appreciate your thoughts. Is an alternate solution possible for you: use an LDAP catalog with email data for users (as well as POSIX data for UNIX accounts)? This way you can have short uid values and arbitrarily long mail, mailEquivalentAddress or mailAlternateAddress properties. One of these may be u...@domain.com to avoid ambiguity, but is not required to be. There are a number of tutorials about making the Solaris operating environment a client of LDAP (Sun DSEE, OpenDJ, OpenLDAP, etc.); however, the mail subsystem will require its own integration for mail routing to the mailbox server (mailHost), alias address processing, etc. It is well documented for Sendmail in the internet, I am not sure about uw-imap. Don't think it should have problems... Also note that you'd want to avoid a deadlock (rather, a needless startup delay) by making an operating environment (global or local zone) which hosts the LDAP service a UNIX-client of this service. If you must do that, make the LDAP server start up before the SMF service ldap/client. I'd just put different tasks in local zones, LDAP server into one, mail into another, global zone as hypervisor with no end-users (except admins) and no LDAP client. HTH, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Long User Names for Email Advice
On 2012-12-11 01:54, dormitionsk...@hotmail.com wrote: Peter, Thank you very much for your feedback. I really appreciate it. Are there any particular tests that you think I should run, just to make sure that I'm not likely to run into corrupted emails three or four months down the road, well after I've implemented OI? I figured I'd test it with sending, replying to, etc. emails of various different scenarios, just to be on the safe side. But if you think I should test anything in particular, I'd appreciate your thoughts. Is an alternate solution possible for you: use an LDAP catalog with email data for users (as well as POSIX data for UNIX accounts)? This way you can have short uid values and arbitrarily long mail, mailEquivalentAddress or mailAlternateAddress properties. One of these may be u...@domain.com to avoid ambiguity, but is not required to be. There are a number of tutorials about making the Solaris operating environment a client of LDAP (Sun DSEE, OpenDJ, OpenLDAP, etc.); however, the mail subsystem will require its own integration for mail routing to the mailbox server (mailHost), alias address processing, etc. It is well documented for Sendmail in the internet, I am not sure about uw-imap. Don't think it should have problems... Also note that you'd want to avoid a deadlock (rather, a needless startup delay) by making an operating environment (global or local zone) which hosts the LDAP service a UNIX-client of this service. If you must do that, make the LDAP server start up before the SMF service ldap/client. I'd just put different tasks in local zones, LDAP server into one, mail into another, global zone as hypervisor with no end-users (except admins) and no LDAP client. HTH, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Long User Names for Email Advice
Yikes! I think this is a little beyond my abilities. I'm a lot more of a programmer than a system admin. I think a more reasonable approach for me would be that if I run into problems with the long user names using uw-imap, to just use Cyrus-Imap instead. It doesn't require system user accounts. I didn't like it as well as uw-imap when I tried it for a while on Linux several years ago. It's a lot harder to administer and it's not nearly as mobile as uw-imap. By mobile, I mean that with uw-imap, it's a lot easier to move people's mail from one server to another, and to restore inadvertently deleted mailbox folders, etc. I appreciate the suggestion, though. I really do. I'm an Orthodox Christian priest-monk, and for what it's worth, I pray for all of you OI developers. I greatly appreciate all of the hard work you are putting into making OI a viable and freely available Solaris-based operating system. And I know my God has most certainly helped me on several occasions to get our OI server I've been working on these past few weeks to get it to the point where it's almost ready to put online. I don't think that with as much help as He's given me with this, that he'll abandon the OI Project, or you all, from His care. Thank you again. Peter, hieromonk On Dec 10, 2012, at 8:35 PM, Jim Klimov wrote: On 2012-12-11 01:54, dormitionsk...@hotmail.com wrote: Peter, Thank you very much for your feedback. I really appreciate it. Are there any particular tests that you think I should run, just to make sure that I'm not likely to run into corrupted emails three or four months down the road, well after I've implemented OI? I figured I'd test it with sending, replying to, etc. emails of various different scenarios, just to be on the safe side. But if you think I should test anything in particular, I'd appreciate your thoughts. Is an alternate solution possible for you: use an LDAP catalog with email data for users (as well as POSIX data for UNIX accounts)? This way you can have short uid values and arbitrarily long mail, mailEquivalentAddress or mailAlternateAddress properties. One of these may be u...@domain.com to avoid ambiguity, but is not required to be. There are a number of tutorials about making the Solaris operating environment a client of LDAP (Sun DSEE, OpenDJ, OpenLDAP, etc.); however, the mail subsystem will require its own integration for mail routing to the mailbox server (mailHost), alias address processing, etc. It is well documented for Sendmail in the internet, I am not sure about uw-imap. Don't think it should have problems... Also note that you'd want to avoid a deadlock (rather, a needless startup delay) by making an operating environment (global or local zone) which hosts the LDAP service a UNIX-client of this service. If you must do that, make the LDAP server start up before the SMF service ldap/client. I'd just put different tasks in local zones, LDAP server into one, mail into another, global zone as hypervisor with no end-users (except admins) and no LDAP client. HTH, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Long User Names for Email Advice
On Fri, Nov 30, 2012 at 5:59 PM, Nicholas Metsovon nmets...@yahoo.com wrote: I've been building an OpenIndiana server to replace our existing Linux web server. I've always - since the 70's - wanted to run a real Unix server. I have the server almost built, and everything so far is working great. Glory be to our holy God! However last night, when I was configuring the email, I went to add another user using the GUI tool, since I'm not that familiar with all of the Solaris command line tools, in order to test the email further. It was then that I discovered that it would only let me add a user with no more than eight characters. In searching the net, I found a post where it said that if I added the user via the command line, it would complain about it being more than eight characters, but would go ahead and add it anyway. I'm using uw-imap. I know that if I was to use Cyrus imap, which doesn't require a system user account for email recipients, none of this would matter; but I don't like Cyrus imap. And I like uw-imap a lot. The users that have names longer than eight characters would only ever log into the system to check their mail via either SquirrelMail, or the mail client on their workstations. It's not like they'd ever actually log into the system itself. So, my big question is, am I likely to run into problems if I use the command line tool to add user names longer than eight characters? Does anyone out there have any experience with this? I've used usernames with well over 8 characters for years, without any serious issues. At least with usernames up to 12-14 characters You'll run into lots of cosmetic problems (columns in ls and ps output won't line up prettily, that sort of thing). More serious is occasional truncation (including utilities like ps truncating usernames as input). One of the more annoying aspects of this is the fact that different tools start to exhibit problems at different lengths. However, given your use case, most of these issues are just irrelevant. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Long User Names for Email Advice
Peter, Thank you very much for your feedback. I really appreciate it. Are there any particular tests that you think I should run, just to make sure that I'm not likely to run into corrupted emails three or four months down the road, well after I've implemented OI? I figured I'd test it with sending, replying to, etc. emails of various different scenarios, just to be on the safe side. But if you think I should test anything in particular, I'd appreciate your thoughts. Thank you again. Peter, hieromonk Dormition Skete Monastery Website: http://www.DormitionSkete.org Convent Website: http://www.HolyApostlesConvent.org On Dec 10, 2012, at 1:53 PM, Peter Tribble wrote: On Fri, Nov 30, 2012 at 5:59 PM, Nicholas Metsovon nmets...@yahoo.com wrote: I've been building an OpenIndiana server to replace our existing Linux web server. I've always - since the 70's - wanted to run a real Unix server. I have the server almost built, and everything so far is working great. Glory be to our holy God! However last night, when I was configuring the email, I went to add another user using the GUI tool, since I'm not that familiar with all of the Solaris command line tools, in order to test the email further. It was then that I discovered that it would only let me add a user with no more than eight characters. In searching the net, I found a post where it said that if I added the user via the command line, it would complain about it being more than eight characters, but would go ahead and add it anyway. I'm using uw-imap. I know that if I was to use Cyrus imap, which doesn't require a system user account for email recipients, none of this would matter; but I don't like Cyrus imap. And I like uw-imap a lot. The users that have names longer than eight characters would only ever log into the system to check their mail via either SquirrelMail, or the mail client on their workstations. It's not like they'd ever actually log into the system itself. So, my big question is, am I likely to run into problems if I use the command line tool to add user names longer than eight characters? Does anyone out there have any experience with this? I've used usernames with well over 8 characters for years, without any serious issues. At least with usernames up to 12-14 characters You'll run into lots of cosmetic problems (columns in ls and ps output won't line up prettily, that sort of thing). More serious is occasional truncation (including utilities like ps truncating usernames as input). One of the more annoying aspects of this is the fact that different tools start to exhibit problems at different lengths. However, given your use case, most of these issues are just irrelevant. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
