Request Tracker

[les]

Hi,

shortly i will be installing Scalix on the same server which runs Request Tracker, a help desk software package, driven by email.

Request Tracker integrates with sendmail using aliases to pipe mail into and out of its internal queues.

The alias generally looks like this in the sendmail aliases file...

help: "|/opt/rt3/bin/rt-mailgate --queue help --action correspond --url http://1.2.3.4/"

I know aliases are groups in scalix and was wondering whether the above alias might work, or if there was something special required to make it work? has anyone had scalix co-exist with Request Tracker?

TIA,

[Valerion]

I've done a test setup about this last week. In general, Scalix and sendmail aliases do interoperate fine, so all Scalix mail will get delivered to Scalix first, then all other mail gets handed down to sendmail to handle. So in this case your RT will get all its own mail, and will handle it itself.

Just don't give a sendmail alias and a Scalix mailbox the same address, then only Scalix will get it.

[les]

Cheers,

sounds easy enough!

[jonny]

Hmm, I am facing a similar challange myself (and started learning Request Tracker today as well - oh joy!)

I understand that you want to pipe mail out of sendmail and into Request Tracker - but what if you are running Request Tracker on a seperate box?

Is it possible to get Scalix to push the RT Mail (support@ourdomain.net) over to a different sendmail server (rt.outdomain.net) which will then in turn process it?

Failing that I guess I can use the POP box method - but it's not as nice :)

Thanks
jonny.

[les]

Hmm, I am facing a similar challange myself (and started learning Request Tracker today as well - oh joy!)

I understand that you want to pipe mail out of sendmail and into Request Tracker - but what if you are running Request Tracker on a seperate box?

Is it possible to get Scalix to push the RT Mail (support@ourdomain.net) over to a different sendmail server (rt.outdomain.net) which will then in turn process it?

Failing that I guess I can use the POP box method - but it's not as nice :)

Thanks
jonny.

I haven't even got to implementing yet, now i'm waiting for version 11 of scalix.

however it should be as simple as an alias in scalix for support@ourdomain.net to go to support@rt.outdomain.net.

then setup your sendmail aliases on the rt.outdomain.net box.

[jonny]

Hey Les,

Well, learning on the fly as I am - I think I got it working both ways (Sendmail integration and pulling from a Pop3 box). Fore those who may need it in the future:

Sendmail
This is the preffered approach but not always an option:

* Edit the /etc/aliases file on your Scalix Server, add the following line:
* support: "|/path/to/rt-mailgate --queue general --action correspond --url http://your.rt.server/"
* Save your changes and issue a 'newalises' from the CLI to rebuild
* Restart sendmail for good measure

Pop3
This is very simple to set up requiring only fetchmail on the RT Server.

* Install fetchmail and perl-Crypt-SSLeay (if you're going to use HTTPS) on the RT Server
* Create a new 'support' user in the SAC - he only needs to be a standard user
* Create a fetchmail config file on the RT Server (ie: /opt/rt3/etc/fetchmail.cfg). something like this:


Code: Select all

poll your.scalix.server  proto pop3:
username support    password ******    mda "/opt/rt3/bin/rt-mailgate --url http://your.rt.server --queue General --action correspond"


* You can now add the fetchmail pull to a Cron job (fetchmail -r /path/to/fetchmail.cfg)

Good luck!