[rt-users] email address per queue

[Norton, Ian]

Hi Chris,

When you're creating your queue, you specify the addresses that you want
it to send mail as.  This doesn't automatically transfer to your MTA for
receipt of mail.  We use a small script to generate our alias file from
the RT database which I have attached - it saves having to remember to
generate the alias lines in addition to creating the queue :)

Perhaps others will also find this script useful.

We use exim as our MTA, which allows multiple alias files.  I couldn't
say if you'll need to munge the auto generated data into a single alias
file if that's all your MTA supports.

Regards, Ian.
--
Ian Norton
Mail & Systems Support
Lancaster University, UK

-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of
Covington, Chris
Sent: 28 April 2005 23:03
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] email address per queue

> Chris, RT doesn't directly have anything to say about 
> how you get e-mail into it.  Basically you configure 
> your mail system to direct mail to the 'rt-mailgate' 
> program with the appropriate arguments to direct the
> message

OK, 

Since it doesn't seem like you can have multiple values for:

Set($CorrespondAddress , '');
Set($CommentAddress , '');
Set($RTAddressRegexp , '');

Is it possible to have different aliases for each queue, or will this
screw up RT's loop detection as in RT_SiteConfig.pm?


---
Chris Covington
IT
Plus One Health Management
75 Maiden Lane Suite 801
NY, NY 10038
646-312-6269
http://www.plusoneactive.com
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rt-aliases
Type: application/octet-stream
Size: 869 bytes
Desc: rt-aliases
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20050429/88c354ce/attachment.obj>