Sending mail

[Neonblue]

I'm working on getting mail to be sent out through the web access component (since I don't have the outlook going yet) and when I try to send I get a message:

"Unable to send mail to:

myaddress@testserver.com"

I read through the docs and found the flow chart for messages being sent out and see on page 35 of the install doc that it's working with a directory called /opt/scalix/bin/xport.out . When I go do /opt/scalix/bin and do an ls -al xport.out I see:

-r-sr-sr-t 2 root scalix 65768 Feb 18 19:04 xport.out

Which is not a directory. In fact, when I do an ls on the directory I see many other files with this same mod setting.

Any ideas on why this is?

Thanks

[ScalixSupport]

xport.out is used for Scalix to Scalix server transport, it isn't used for message submission from SWA.

Your unable to send message indicates a problem talking to the SMTP relay so the first thing to check is that /etc/opt/scalix/webmail/partner.xml contains the right information for smtpServer. If you make a change, you will need to restart tomcat to pick up the changes.

If that looks to be OK, check that you are being recognised by the SMTP relay. The file /var/opt/scalix/sys/smtpd.cfg has a couple of lines towards the end which should begin with "RELAY accept". This gives a list of domains which are allowed to mail messages to other domains, i.e. external mail. You should see something like:

Code: Select all

RELAY accept 127.0.0.1
RELAY accept domain.com
RELAY accept .domain.com

If that doesn't look correct, you need to change the domain lines to match the domain that the Scalix server "owns", i.e. whatever domain you specify at the end of your addresses.

Cheers

Dave

[Neonblue]

I checked the /etc/opt/scalix/webmail/partner.xml and found this:

rulesWizardURL="http://mail/Scalix/rw"

I must have entered a hostname wrong somewhere along the way. When I login into the admin I have to use sxadmin@mail.domain.com for the user ID.

Regardless, "mail" does resolve to the correct address.

In smtpd.conf my domains were not listed so I added them in. Is this something I'm going to have to remember to do when I install a scalix server or is it something that should have been automatic?

RELAY accept 127.0.0.1
RELAY accept domain1.com
RELAY accept domain2.us
RELAY accept .domain1.com
RELAY accept .domain2.us
RELAY accept .mail
RELAY Log_Reject ALL

I restarted tomcat and still had the same problem. Anything else I can look at?

[ScalixSupport]

The RPM installation for SWA and for the server will take the output from

Code: Select all

uname -n

and do an nslookup to obtain the official FQDN for the server. If no result is returned, the uname -n output will be used. This is where the "problem" may occur on the initial installation.

Being unable to send mail can be one of several reasons:

a) The smtpServer setting in partner.xml is incorrect
b) The Scalix SMTP relay is not listening on port 25 of the address specified in the smtpServer setting
c) You have the password incorrect[/list]

The last item is highly unlikely because you have already signed on using SWA in order to attempt to send the message.

You can enable some logging by adding the following line to /var/opt/scalix/sys/smtpd.cfg:

Code: Select all

DEBUG_LOG=TRUE

You should stop and restart the SMTP relay

Code: Select all

omoff -d 0 smtpd
omon smtpd

This will create a file in /var/opt/scalix/tmp called smtpd.log. This contains the SMTP conversations that take place in the SMTP relay. Can you do this, attempt to send another message and post the resultant file here ?

Cheers

Dave

[Neonblue]

Ok this is crazy...

I made the debug change and restarted the smtp service. I went to send a message and it worked with no errors. I didn't make any changes since this morning when I made the initial changes you stated. I restarted the server after making those changes and still had the issue.

So the initial change must have fixed it but for some reason it had problems after the intial reboot of the server. I did have to start tomcat manually when it came back up, perhaps it wasn't don't reloading when I tried to send it? I don't know, but it's working.

I verified the uname -n and you are correct. It returned "mail". I guess I'm not sure on what you are referring to? I did have problems with my MS DNS providing the correct DNS entry back to the host during the pre-check. (I'm still having problems with the scalix-default alias - I wish I could go back to bind, that always worked.) During the pre-check it kept erroring out on the DNS entry. After I got that fixed, I was able to get past it. Are you talking about the reverse DNS? Is that what it's looking for? Is there anyway to repair this after installation?

I do have to say, I've installed tons of exchange servers in the past. I'm also well versed on installing applications on Linux. Comparing this to other things I've installed I would have to say that this was pretty darn easy. Although I know there are a lot of "features" and configs that I don't know anything about yet. Is there a better tech manual for the configs and/or troubleshooting? If everything works ok on my side during my test, I'll be selling to many of my clients as a cost effective exchange replacement/solution. I do like the web interface a lot; it's very sharp. (Even better than OWA in my opinion)

Thanks
Scott