Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 2 > Installation/Configuration

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #11  
Old 16th September 2007, 20:42
vaio1 vaio1 is offline
Senior Member
 
Join Date: Jul 2007
Location: Italy
Posts: 664
Thanks: 77
Thanked 12 Times in 7 Posts
Default

The problem has been the sql insert query into ISP Config.
The record was corrupted. The userid was "web19_" without name.

Thanks
Reply With Quote
Sponsored Links
  #12  
Old 17th September 2007, 19:19
chancer chancer is offline
Member
 
Join Date: Sep 2007
Posts: 88
Thanks: 6
Thanked 1 Time in 1 Post
Default

Is the prefix web#_ required for each username? I read in the docs this could be changed - I deleted it for three reasons:

1. In transferring all the sites onto the new system, I wanted to keep life as easy as possible for my clients by making as few changes as possible

2. I wanted to keep it all as easy as possible for myself by having as few new things to explain as possible

3. I can't see any reason for such a device, and none was given in the documentation. It's not a distinguishing feature - I spell real names properly, usernames are all lower case and passwords must contain at least one digit, one non-alphanumeric character, one upper case and one lower case letter in a statutory 9-character password.

However, I am having all sorts of niggling, seemingly random, problems with email services so if this is at least a partial cure, I'm interested.
Reply With Quote
  #13  
Old 18th September 2007, 08:28
till till is online now
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,456
Thanks: 813
Thanked 5,223 Times in 4,093 Posts
Default

Quote:
Is the prefix web#_ required for each username?
No, but recommended. Email users must be unique for the whole server, so if you do not add a prefix, you have to make your own naming conventions. Additionally if you run postfix and use config files in sendmail style, the system will accept email for system usernames directly, so if you create a user "info", this suer will get email sent to info@anydomain.com on your server, if info@anydomain.com is not a regular mailbox created under this domain.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #14  
Old 18th September 2007, 11:07
chancer chancer is offline
Member
 
Join Date: Sep 2007
Posts: 88
Thanks: 6
Thanked 1 Time in 1 Post
Default

Thanks, till. Just so I (and anyone else reading here) get this absolutely right, is it the users who should have a prefix? Users can have whatever aliases they like. So if some users have been using aliases like info@ and accounts@ they may continue doing so?

So if I change to this convention now, I take it this will affect existing users, too?
Reply With Quote
  #15  
Old 18th September 2007, 11:15
chancer chancer is offline
Member
 
Join Date: Sep 2007
Posts: 88
Thanks: 6
Thanked 1 Time in 1 Post
Default

Thanks, till. Just so I (and anyone else reading here) get this absolutely right, is it the users who should have a prefix? Users can have whatever aliases they like. So if some users have been using aliases like info@ and accounts@ they may continue doing so?

So if I change to this convention now, I take it this will affect existing users, too?
Reply With Quote
  #16  
Old 18th September 2007, 11:18
till till is online now
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,456
Thanks: 813
Thanked 5,223 Times in 4,093 Posts
Default

Quote:
Originally Posted by chancer
Thanks, till. Just so I (and anyone else reading here) get this absolutely right, is it the users who should have a prefix? Users can have whatever aliases they like. So if some users have been using aliases like info@ and accounts@ they may continue doing so?
yes. The username can be totally different to the part before the @ of the email address. Thats why we use the prefixes.

Quote:
So if I change to this convention now, I take it this will affect existing users, too?
Existing users will not be affected.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
The Following User Says Thank You to till For This Useful Post:
chancer (18th September 2007)
  #17  
Old 19th September 2007, 00:20
chancer chancer is offline
Member
 
Join Date: Sep 2007
Posts: 88
Thanks: 6
Thanked 1 Time in 1 Post
Default

Taking this logic a step further, could the home directory names (i.e. web1, web2 and so forth) in /var/www/ be customised, too? I'm thinking of ISP1, ISP2 where we could substitute something of our own choosing for ISP?

Perhaps this is OT and I should be posting it as a new thread under Feature Requests or Develepors' Forum. But it does strike me that we can keep on challenging the Maine Monolith (great news from the EU courts on that score ) if we improve our marketing skills.

If we can have user home directory names matching user prefixes, and both matching our branding efforts, it affords us some marketing consistency. Prefixing/naming with web# specifically, and I now appreciate several very good reasons for such a convention, is bland.
Reply With Quote
  #18  
Old 19th September 2007, 08:29
till till is online now
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,456
Thanks: 813
Thanked 5,223 Times in 4,093 Posts
Default

Quote:
Taking this logic a step further, could the home directory names (i.e. web1, web2 and so forth) in /var/www/ be customised, too?
No. Because the home directories are just the "technical" directory names that are not used by the users on the shell. For the use on the shell, ISPConfig creates symlinks like /var/www/www.domain.com/
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #19  
Old 19th September 2007, 15:38
catdude catdude is offline
Senior Member
 
Join Date: Jun 2007
Posts: 178
Thanks: 1
Thanked 12 Times in 11 Posts
 
Default

Quote:
Originally Posted by chancer
Taking this logic a step further, could the home directory names (i.e. web1, web2 and so forth) in /var/www/ be customised, too? I'm thinking of ISP1, ISP2 where we could substitute something of our own choosing for ISP?

Perhaps this is OT and I should be posting it as a new thread under Feature Requests or Develepors' Forum. But it does strike me that we can keep on challenging the Maine Monolith (great news from the EU courts on that score ) if we improve our marketing skills.

If we can have user home directory names matching user prefixes, and both matching our branding efforts, it affords us some marketing consistency. Prefixing/naming with web# specifically, and I now appreciate several very good reasons for such a convention, is bland.
As it stands currently, your choices for User Prefix are [WEBID], [DOMAIN], [HOST], and [HOSTDOMAIN]. You might watn to take a look at http://www.howtoforge.com/forums/arc...hp/t-1064.html

I've posted a message on the "Suggestions" board that in a future release a field be added at the domain level, for storing a custom prefix. I'm currently using [DOMAIN] as my prefix, but the flavor of Linux I'm running limits user names to 32 characters, so long domain names make for some pertty short user names.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Freebsd 6.1 support misterm Installation/Configuration 10 9th April 2009 09:29
email forwarding locally consumes all resources rdells General 20 1st May 2006 19:43
UebiMiau webmail adding @localhostname to email address except first address. Kamran Shah Installation/Configuration 5 11th October 2005 17:01


All times are GMT +2. The time now is 18:30.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.