Koozali.org: home of the SME Server

DNS Problem or something set up wrong???

d_gerst

DNS Problem or something set up wrong???
« on: June 24, 2005, 08:36:00 PM »
Hello!

I've setup a SME 6.5 RC1 server and i've got following problems:

1. If you send an request (ftp.domain.xx, www.domain.xx or mail.domain.xx) the host won't answer with www.domain.xx, ftp.domain.xx, mail.domain.xx. The machine is answering with it's hostname.domain.xx.

At the moment I handle this proplem on this way, set hostname to mail.domain.xx, so that I've not to confirm securemail transaction (IMAPS/POP3S/SSMTP) every time I receive mail from the server (hostname is not identic to the name of the machine in the ssl certificate). For www.domain.xx I used a separate ssl certificate that is correctly set in httpd.conf.
Is there a handier solution available?

2. FTP over SSL,I recompilied ProFTP with mod_tls and install it. After the installation the system is crasching down. What do I have to attend? Is there a rpm available for horde gollem or an other webftp tool with ssl?

3. Did someone know a way to fix following problem? Two email adresses info@domain.xx and info@domain1.xx and they should delivered to diffrent accounts. I've seen on dungog.net there's a rpm is aviable but it is not for free. Could I modify the mailrules.default of qmail to fix this problem?

Best regards,
Daniel Gerst

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: DNS Problem or something set up wrong???
« Reply #1 on: June 24, 2005, 11:19:08 PM »
Quote from: "d_gerst"

1. If you send an request (ftp.domain.xx, www.domain.xx or mail.domain.xx) the host won't answer with www.domain.xx, ftp.domain.xx, mail.domain.xx. The machine is answering with it's hostname.domain.xx.


What exactly does "send a request" mean?

Quote

2. FTP over SSL,I recompilied ProFTP with mod_tls and install it. After the installation the system is crasching down. What do I have to attend? Is there a rpm available for horde gollem or an other webftp tool with ssl?


Just use winscp (which connects via SSH).

Quote

3. Did someone know a way to fix following problem? Two email adresses info@domain.xx and info@domain1.xx and they should delivered to diffrent accounts.


This has been mentioned here many times.

d_gerst

DNS Problem or something set up wrong???
« Reply #2 on: June 25, 2005, 06:45:08 AM »
Hello CharlieBrady!

To send a request means:

telnet mail.domain.xx 25/465
reply -> hostname.domain.xx and not mail.domain.xx

telnet ftp.domain.xx
reply -> hostname.domain.xx and not ftp.domain.xx

I know the way to use winscp, but if I give a user ssh access, he could use also putty to access the server. But I don't want to give user ssh access.

Best reards,
Daniel Gerst

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
DNS Problem or something set up wrong???
« Reply #3 on: June 25, 2005, 07:08:05 AM »
Quote from: "d_gerst"

To send a request means:

telnet mail.domain.xx 25/465
reply -> hostname.domain.xx and not mail.domain.xx

telnet ftp.domain.xx
reply -> hostname.domain.xx and not ftp.domain.xx


You don't "send a request" when you do "telnet mail.domain.xx 25" - you connect to the SMTP port using telnet. The SMTP server then answers, and sends a banner which looks like:

220 hostname.domain.x mailfront ESMTP

The SMTP server doesn't know which address you typed to telnet (www.domain.xx, or ftp.domain.xx or 1.2.3.4) so it cannot include the address you typed in its banner. All it can report is a single address, and the SME server is configured to greet with the hostname and domain name you configured the server with.

So what I think you are asking for is impossible.

Why do you think it matters?

d_gerst

DNS Problem or something set up wrong???
« Reply #4 on: June 25, 2005, 07:34:06 AM »
Hello CharlieBradly!

Cause if you use SSL to receive your mails and you use mail.domain.xx, the name you requst is no the same as the system named in the ssl certificate.

I've got three other problems:

1. If you change the httpd.conf, after a reboot it will be automatic set to old values.

2. SME denied all e-mail for example daniel@otherdomain.xx which is not hosted on sme. I could not send an email to this account from sme server until I change mailrules.default to p*:daniel@*:Sorry, invalid recipient domain

3. I have made no changes to ProFTP, but the service could not start. If I change servertyp to standalone (default inetd) everything works fine until to next reboot. After reboot the cahnges are setting to default values (inetd).

Any suggestion?

I find a way to fix the virtual domain email problem, but it don't work with sme 6.5 RC1. Here is the link or did I something wrong?

http://mirror.contribs.org/smeserver/contribs/rmitchell/smeserver/howto/virtual%20domain%20email%20aliases%20HOWTO%20for%20sme%20server.htm

best regards,
Daniel Gerst

d_gerst

DNS Problem or something set up wrong???
« Reply #5 on: June 25, 2005, 07:43:42 AM »
Hello CharlieBradly!

The second problem depends on mailblocking from dungog.

Best regards,
Daniel Gerst

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
DNS Problem or something set up wrong???
« Reply #6 on: June 26, 2005, 05:47:18 PM »
Quote from: "d_gerst"
Hello CharlieBradly!


That is not my name.

Quote

Cause if you use SSL to receive your mails and you use mail.domain.xx, the name you requst is no the same as the system named in the ssl certificate.


But that has nothing to do with what you describe using telnet.

You have an easy solution - use the name in the ssl certificate as the mail host name in your mail client configuration.

Quote

3. I have made no changes to ProFTP, but the service could not start.


Don't try to start/restart a service. ProFtp config changes take effect immediately, because proftp runs from an inetd like service.

If you stop fighting the system, and read here about using custom templates, and using "signal-event post-upgrade ; signal-event reboot", or "signal-event remoteaccess-upgrade" etc, then your experience with SME server will be less frustrating for you.