Scalix 9.2.1 Evaluation error in Network Check

[andrecruz]

Hello,

I have Fedora Core 3 clean installation and when trying to install 9.2.1 Eval it gives an error in network check, it says :
1. Netwiork Check Fail : Hosts file in not configured with fully qualified domain name (FQDN)
2. Network Check Fail : Invalid FQDN ' scalix.ibertelco.intranet'

My hosts file :
127.0.0.1 localhost.localdomain localhost
192.168.1.8 scalix.ibertelco.intranet scalix
192.168.1.8 scalix-default-mail

My network eth0 :
DEVICE=eth0
BOOTPROTO=static
BROADCAST=192.168.1.255
IPADDR=192.168.1.8
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
TYPE=Ethernet

When doing the nslookup from server :
[root@scalix ~]# nslookup scalix
Server: 192.168.1.2
Address: 192.168.1.2#53

Name: scalix.ibertelco.intranet
Address: 192.168.1.8

[root@scalix ~]# nslookup 192.168.1.8
Server: 192.168.1.2
Address: 192.168.1.2#53

8.1.168.192.in-addr.arpa name = scalix.ibertelco.intranet.

[root@scalix ~]# nslookup scalix-default-mail
Server: 192.168.1.2
Address: 192.168.1.2#53

scalix-default-mail.ibertelco.intranet canonical name = scalix.ibertelco.intranet.
Name: scalix.ibertelco.intranet
Address: 192.168.1.8

Any help would be apreciated...

Best Regards,

Andre Cruz

[andrecruz]

Hello again,

I just found what is wrong... ibertelco.intranet as the FQDN, created a new zone named teste.com and maintain everything as it was and now it works fine.

I don't understand that if this is an evaluation version and it suppose to be tested in non production enviroments why it don't accept domains that aren't related with internet. If i have already a domain set-up that works it should accept it now matter what i put in as the FQDN.

[ScalixSupport]

The Scalix evaluation edition is the same code as the fully-licensed version except that you are only able to add a limited number of users and are restricted by the license terms to a limited usage period.

The installer does not have any features that need to be restricted and so we use the same installer for both versions. So, it will perform the same checks for both versions.

Scalix expects there to be a fully-functional DNS service available. It doesn't need to be pointed to the internet but the server needs to be able to resolve its own name correctly. A mis-configured DNS service will cause problems with sendmail in the long run so it's always best to have these things sorted out before installation.

Cheers

Dave

[Ripper007]

Is it required to set up the DNS entry before installing scalix?

I've the problem that I downloaded the evaluation of scalix and now I want to test it in our company network. All runs fine, installation, tomcat, java, access, web-client

I can send emails between the internal users without problems. but when i try to send an email to another recipient (external) then I got I message from MAIL-SYSTEM with the error "Domain of sender address XXX does not exist". Where is my mistake?

I want scalix to send all external eMails to an mail-relay in our internal network. What is to do for me?

greetings from germany

[jch]

I get the "domain of sender adress does not exist" message from my ISP when I try to send mail home from my workstation. Is the returned message coming from outside or is it being generated by an internal server? Depending on where the message is being rejected will make a difference to what you need to do to fix it. Anyway, there are a few things you can try:

The first one, and the one easiest to say but possibly hardest to arrrange is to make the name of your server visible to the outside world. Our external facing machine here in the UK has an MX record referring to the UK gateway and that satisfies everyone that we talk to.

The second option, and this might or might not work, is to configure a smarthost for the sendmail running on your Scalix server machine. If you do this by editing sendmail.mc and then "recompiling" the sendmail.cf, you'll need to run "omsendin" to re-apply the scalix changes to the sendmail.cf. Of course, if you edit sendmail.cf directly you don't need to worry about that. There's a fair chance that this will work since the originating server for mail going to the outside world will be one that announces itself with a name that ISPs will believe. Of course, the server you're relaying through might not like you using it as a relay, but as it's going to be internal you can fix that!

The third option, which you might need to use in conjunction with the second one, is to use domain masquerading so that your mail appears to come from a server that can send mail outside. The downside of this, of course, is that replies to the message will go to the server mentioned in the address, not the originating server (but that's what masquerading means).

In a real environment rather than a test environment, you should go for the first option. Of course, you may not need to do that if you're going to run scalix on a host that's already registered in the DNS.

jch

[Ripper007]

Here in our case it works a little bit different. the scalix server should not send the mails to our ISP. There is another server, which receives all emails from our main-mail-server (SLOX) and sends them after working with rules (MailFirewall) to the ISP.

Now I have to say scalix to send the messages to this internal server!!! But where can I do this???

The SYSTEM-MAIL "domain of sender adress does not exist" comes from the scalix-server. I looked at the mail-headers.

I thought it's easy to work with scalix after the installation but it doesn't work and I don't know why ... :-(((

[jch]

Are your users configured with an Internet address whose domain exists? I forget where it is at the moment, but you can also turn off domain name checking in sendmail.

jch

[Ripper007]

The domain exists! It is in yast in the field "domain search" and "name search" ... its difficult to understand for me ... I want to test it with real mails but it doesn't work ... ARGH :-)

[jch]

OK. So try

Code: Select all

host -a <domain>

and see what the DNS server says. Of course, <domain> should be the domain associated with the user who is trying to send the message. Also try just sending a message using mutt or mail (or even telnet to the SMTP port) and see what happens.

We might be able to spot something if you post a rejection notice. If the rejection notice is too sensitive to post in a public forum e-mail it to me, although it would be better to have more eyes just mine.

jch

[Ripper007]

Trying "domain.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61292
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;domain.com. IN ANY

;; ANSWER SECTION:
domain.com. 10800 IN SOA B31S000201.domain.com. mail.domain.com. 2005048357 10800 3600 604800 3600
domain.com. 10800 IN NS B31S000201.domain.com.

;; AUTHORITY SECTION:
domain.com. 10800 IN NS B31S000201.domain.com.

;; ADDITIONAL SECTION:
B31S000201.domain.com. 1296000 IN A 10.31.201.201

Received 120 bytes from 10.31.201.202#53 in 9 ms


I replaced our real-name wirth "domain" ... B31S000201 is the nameserver!

[jch]

Why is your domain so secret? :-) Oh well, rather than checking out the DNS myself and being able to give you a positive answer, try

Code: Select all

host domain.com
host -t mx domain.com

If you do this with scalix.com you'll get

Code: Select all

$ host scalix.com
scalix.com has address 66.33.223.131
$ host -t mx scalix.com
scalix.com mail is handled by 15 gw2.scalix.com.
scalix.com mail is handled by 25 gw3.scalix.com.
scalix.com mail is handled by 5 gw1.scalix.com.

The reason for this is that the command you tried (and I suggested) tends to only show what information is cached in the local name server. In the case of scalix.com, I saw an A record and some NS records; after I'd checked for the MX record explicitly I also saw the MX records in the "any" query. Sorry about that, I'd forgotten.

Anyway, so far it looks as though domain.com has an SOA (which is good, it means it's a domain!) but it has neither an A nor MX records -- that means it doesn't really exist as something that can originate mail messages.