Topic: extra e-smith in domain names ???

[Jeff]

This information is from the "review configuration" menu in the e-smith-manager, why do I have an "e-smith" before all of my .domain.com addresses, they were not there in previous versions and I can't seem to rid my system of them.

Web and proxy servers www.e-smith.domain.com:3128
FTP server ftp.e-smith.domain.com
SMTP, POP, and IMAP mail servers mail.e-smith.domain.com


Jeff

[Eddy Van Hoeserlande]

You can rid of it, if you change the perl scripts! And yes, I don't like the 'e-smith.' thing in it also

Maybe we should start a vote on it ...

[Joseph Morrison]

Hello all!

Keep in mind that this is compatible behavior with e-smith 3.1 - if your ISP publishes your correct domain information you can forget about the "e-smith" prefix.

We simply offer the "www.e-smith.domain.com" names as additional names that you can use immediately before your ISP publishes the real ones.

Still, we are listening to your feedback . We are considering the idea of returning to the behavior of the early 4.0 betas, if there is enough demand.

Best regards,
- Joe Morrison, CEO

[sonnius]

Id vote for the e-smith thingy to get outJoseph Morrison wrote:

> Hello all!
>
> Keep in mind that this is compatible behavior with e-smith 3.1
> - if your ISP publishes your correct domain information you can
> forget about the "e-smith" prefix.
>
> We simply offer the "www.e-smith.domain.com" names as
> additional names that you can use immediately before your ISP
> publishes the real ones.
>
> Still, we are listening to your feedback . We are considering
> the idea of returning to the behavior of the early 4.0 betas,
> if there is enough demand.
>
> Best regards, - Joe Morrison, CEO
>

[Charlie Brady]

sonnius wrote:

> Id vote for the e-smith thingy to get out

Before you do that, it would be a good idea if you knew why it is in there. Prior to that change, the e-smith server identified itself to machines on the local net as www.domainname.xxx, ftp.domainname.xxx, mail.domainname.xxx and a few other names, and accepted mail for user@domainname.xxx. This caused problems for the considerable number of sites whose public web site www.domainname.xxx was hosted by a web hosting company, e.g. by their ISP. Everyone in the world could access their public web site - except people on their own LAN. See:

http://www2.e-smith.net/bboard/read.php3?num=1&id=2780&loc=0&thread=2780

for an example of someone in this category.

Similar problems could occur for ftp.domainname.xxx etc.

The e-smith.domainname.xxx suffix for hosts on the LAN was chosen to be distinct from any Internet site.

It seems to me that it is an aesthetic problem (you folks don't like the look of it) rather than a practical problem (something doesn't work). Please correct me if I'm wrong (and provide details of what doesn't work, so that we can fix it).

If you don't like the look of those long domain names, you can
drop the suffix altogether, and use just the hostnames - use http://www/e-smith-manager/ to access the manager interface, configure "mail" as the server in your mail program, etc.

Regards

Charlie

[Luke Drumm]

Hi,

Might I suggest a small comprimise?

Would it be possible to have the offending domain name portion (ie '.e-smith') configurable?

I'm not all that strong on the inner workings of the mail setup and related programs but I'm suspecting it would be easier to impliment this as a one time installation option rather than as a web 'any time' type of config.

That way the business users could specify something vaugely more memorable for their staff (eg. "...staff.domain.xxx") and the geeks & gurus could satisfy their customisation needs (eg. "...matrix.domain.xxx").

Luke.

[Jeff]

I would simply not like to have it there at all, how can I remove it from the scripts, the previous scenerios do not apply to me and I don't think it should be removed from the distribution, but I would like to remove it from my copy.

Thanks,
Jeff

[Adik Gede]

I don't think that is so much a matter of aesthics as an issue of being cumbersome.  Why not just www.mydomain.lan ftp.mydomain.local mail.mydomain.office smtp.mydomain.school

or as Luke suggests make it configurable so the administrator can choose a name that is relevent to the people who will be using the server.

[Orville Carter]

Charlie,
   Here is a sample from my server after installation and config of e-smith 4.0 final.
I did not have this problem with e-smith 4.07b.

As you are aware the "legaldomain.com" represents a real internet domain on my server. I cannot read any email from the server. How can I remove the e-smith
from these names??? We had to put the old P233 server with e-smith 4.07b back in
service to handle our mail. All other services appear to be working, ie. Proxy & web server works. I have email on this server and I cannot access it. I need a fast work-around.

Server names
DNS server xxx.xxx.xxx.xxx
Web and proxy servers www.e-smith.legaldomain.com:3128
FTP server ftp.e-smith.legaldomain.com
SMTP, POP, and IMAP mail servers mail.e-smith.legaldomain.com

Domain information
Primary domain legaldomain.com
Virtual domains No virtual domains defined
Primary web site http://www.legaldomain.com
e-smith manager http://www.e-smith.legaldomain.com/e-smith-manager
e-smith individual password changer http://www.e-smith.legaldomain.com/e-smith-password

[Orville Carter]

Orville Carter wrote:

> Charlie, Here is a sample from my server after installation and
> config of e-smith 4.0 final. I did not have this problem with
> e-smith 4.07b.
>
> As you are aware the "legaldomain.com" represents a
> real internet domain on my server. I cannot read any email from
> the server. How can I remove the e-smith from these names??? We
> had to put the old P233 server with e-smith 4.07b back in
> service to handle our mail. All other services appear to be
> working, ie. Proxy & web server works. I have email on this
> server and I cannot access it. I need a fast work-around.
>
> Server names DNS server xxx.xxx.xxx.xxx Web and proxy servers
> www.e-smith.legaldomain.com:3128 FTP server
> ftp.e-smith.legaldomain.com SMTP, POP, and IMAP mail servers
> mail.e-smith.legaldomain.com
>
> Domain information Primary domain legaldomain.com Virtual
> domains No virtual domains defined Primary web site
> http://www.legaldomain.com e-smith manager
> http://www.e-smith.legaldomain.com/e-smith-manager e-smith i....


From the e-smith 4.07b server (this configuration works perfectly!)
Server names
DNS server xxx.xxx.xxx.xxx
Web and proxy servers www.legaldomain.com
FTP server ftp.legaldomain.com
SMTP, POP, and IMAP mail servers mail.legaldomain.com

Domain information
Primary domain legaldomain.com
Virtual domains No virtual domains defined
Primary web site http://www.legaldomain.com
e-smith manager http://www.legaldomain.com/e-smith-manager
e-smith individual password changer http://www.legaldomain.com/e-smith-password

[Charlie Brady]

Orville Carter wrote:

> Charlie, Here is a sample from my server after installation
> and config of e-smith 4.0 final. I did not have this problem
> with e-smith 4.07b.
>
> As you are aware the "legaldomain.com" represents a
> real internet domain on my server. I cannot read any email
> from the server. How can I remove the e-smith from these
> names???

You do not need to remove the e-smith from those names. You *do* need to add the e-smith to the names that you have set up in your client machines, for example in their mail program setup. The only exception to this is that if you set up your client machines to use just "mail", then they will continue to work.

Let me explain this in a new way to see if it helps clear things up for you.

The machines on your LAN are not accessible from the Internet - therefore there is no valid relationship between fully qualified domain names and IP addresses for the machines on your LAN. The names that you use on your LAN are therefore arbitrary - you can make them whatever you like. However, you do not want any of the FQD names that you use on your LAN to clash with valid internet domain names - because otherwise you will not be able to reach those machines from your LAN.

That is why the machines on your LAN are named *.e-smith.legaldomain.com - because we know that those names are extremely unlikely to clash with real machines on the Internet.

Because the names are arbitrary, the only thing that matters is that all machines on your LAN agree. That is why if your server calls itself mail.e-smith.legaldomain.com, then your client machines on the LAN must use that name when accessing the server.

Regards

Charlie

[Orville Carter]

YES! That works just right! What was I thinking! Thanks Charlie.

While trying to solve the "mail.e-smith.legaldomain.com" I deleted a user email account on e-smith server gateway. I would like to recreate the same user name, but e-smith would not allow it. [Error: account "username" is an existing user-deleted account.]

Hey, Tell me something I dont know, already!  (Hah! You gotta love computers. ha! ha!) but how can I re-create this account?? The user receives email on this account. HELP!

[Charlie Brady]

Orville Carter wrote:

> YES! That works just right! What was I thinking! Thanks Charlie.

My pleasure. And better for both of us that you continuing to use 4.0b7.

> While trying to solve the
> "mail.e-smith.legaldomain.com" I deleted a user email
> account on e-smith server gateway. I would like to recreate the
> same user name, but e-smith would not allow it. [Error: account
> "username" is an existing user-deleted account.]

That indicates a problem when you deleted that user - it left a line in
/home/e-smith/accounts which looks like:

username=user-deleted|First|John|Last|Citizen|....

Remove that line from that file and you can then re-add that user.

Or you could take a short cut and change "user-deleted" to "user", then do:

/sbin/e-smith/signal-event user-create username

Charlie

[Ronald Tanis]

I also have the same problem, my ISP doesn't accept mail from my domain mail.e-smith.rmtanis.tmfweb.nl  how can i change it so that their stands mail.rmtanis.tmfweb.nl

with Regards,

Ronald Tanis