SWA + Search

[savant]

Hi Tantony,

tried using 0.0.0.0 ?

Unless you have security issues with that, in which case you should add the subnet from which your clients are connecting instead (like 192.168.123.0). My mail host is firewalled so I allow all for these services and restrict in iptables instead.

Regards,
Simon.

[MailMan]

Hi Tantony,

Have you tried reindexing?

sxmkindex

Regards,

Ken

[kanderson]

Actually, have a look here:

http://www.scalix.com/wiki/index.php?ti ... buildIndex

Kev.

[MailMan]

sweet

[scalixuser]

[quote="jaime.pinto"]Yes we did. This morning we gave them remote access to our system and eventually they figured out what was wrong. I'll ask them to either post the solution or let me know what they did.[/quote]

Jaime,
We are anxious too to hear what fixed this for you.

[jaime.pinto]

I'll email scalix one more time.
They must have a written record somewhere of what they did to fix.
I usually keep a very close eye on everything that happens or is done to our server, but that one day I missed the boat. Sorry.

[michaelw]

I had also pretty much fun with the swa-search, tried every possible solution i've found here in scalix-forum without success.
I thought i'll never get the search running but this morning i succeeded!

I'm using Fedora 7 with german locale (that's also the reason for my average english )
I tried this

Code: Select all

/etc/init.d/scalix-tomcat stop ; omshut
change system locale to en_US.UTF-8 (/etc/sysconfig/i18n on redhat/fedora)
logout and re-login (to make the locale change active in your shell or it won't work)
/etc/init.d/scalix-tomcat start ; omrc

without success but still believed, the locale causes the error.
Therefore i ran

Code: Select all

locale -a

and got, among other things, this output:
en_US.utf8
Nearly the same i've tried several times in i18n before, but without the dash.
I chanced my /etc/sysconfig/i18n like this:

Code: Select all

LANG="en_US.utf8"
SUPPORTED="en_US.utf8:en_US:en"

and rebooted the server. (I found a recommendation in another forum that changing the locale on fedora only works proper through reboot)

I opend webmail, started the search and got answers. What should a say? It was a unbelievable feeling
HTH

[jaime.pinto]

Florian looked up the scalix internal ticketing system for us, and replied with the solution. It's difficult to believe something apparently so "inoffensive" could cause such a trouble.

Bottom line: we also enabled SquirrelMail on our server, since several users find it better(faster) than scalix webmail. Following the convention of the http://scalixserver/m ,for mobile clients, we use http://scalixserver/s as a shortcut for SquirrelMail. Everything was fine until the day we setup the SSL redirect for SquirrelMail as well, ie, https://scalixserver/s . That seems to be the URL used "internally" for the SIS in scalix, hence the conflict. How could we know?!!!

They did reply to my request previously, but we had a brief email problem that day and didn't get the message.

Here was the solution for our situation:

Hi Jaime,

Your apache config had a redirect for the SIS url. In
/etc/opt/scalix-tomcat/connector/ajp/instance-mail2.conf:

<LocationMatch "^/s/*">
RewriteEngine on
RewriteRule ^(.*) https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
</LocationMatch>

This was commented out, and everything works now.

cheers,

Dug Smith

[scalixuser]

After a lot of frustration we were about to give up when Michaelw posted the solution above, and as a last resort we tried his fix. Good for all non-US Linux/Scalix users to know that this fix works on CentOS 4.5 too. We are using CentOS in the Netherlands. Apparently this bug does not appear when Scalix is installed on a US English version of the operating system.
Could Scalix build in a check in the installer; and/or fix this bug otherwise?

[mrezzonico]

Hi all,

I still have problems with the search functin in SWA (in Outlook is OK).

http://www.company.com/api/user@company ... ch?q=Hello
-> did not works !!

sxsearch --direct=Hello "user@company.com"
-> works

Any help is appreciated. Miche

[eltonmachado]

Hi all,

I still have problems with the search functin in SWA (in Outlook is OK).

http://www.company.com/api/user@company ... ch?q=Hello
-> did not works !!

sxsearch --direct=Hello "user@company.com"
-> works

Any help is appreciated. Miche

Same here!

Did you solved your problem? I'm getting crazy with this :S

[mrezzonico]

Hi Elton,

the problem is not solved.

I have installed 3 times scalix on my computer (same OS, same version, same procedure).
The 2nd time, the search in SWA was ok, but I do not know why.

I will try tomorrow with the new version (11.3).

I will report here.


Regards. Miche

[eltonmachado]

Hi Elton,

the problem is not solved.

I have installed 3 times scalix on my computer (same OS, same version, same procedure).
The 2nd time, the search in SWA was ok, but I do not know why.

I will try tomorrow with the new version (11.3).

I will report here.


Regards. Miche

Hi there,

In mean time i resolved mine with the other sugestions, i had to changed de default language to english again and restart the server, beyond the procedures to fix the indexes and prepare the imap folders.

It all working okay now.

Good luck and thanks by the way

[deyjvu]

I had this issue at a site that had changed their ldap port to other than 389 and had security set on Apache. Most of what is in this case we tried, we didn't get to the changing of the i18N file in /etc/sysconfig so that this pointed to en_GN or en_US but it could be an issue as we point to en_AU which isn't supported.

I found that the platform.properties file had an entry that pointed to the default LDAP=389 and once I changed that and several other things from this case (sorry can't recall all we did as this has been over a two week period) we finally have SIS working. I know we did the "sxmkindex -r 00:00:00" after the server was rebooted (yes the server not the services was rebooted in my case, not that this maybe necessary).

I haven't seen it mentioned anywhere else here but
"curl -v servername/sis" was used in troubleshooting my problem. It showed an incorrect output when I first ran this as compared to the same command run for the swa "curl -v servername/webmail". Might help someone else.... :-)

[Tobias]

I just want to confirm michaelw´s post. Changed locale to en_US.utf8 and restarted my server > search works for e-mail as well!
THANKS!