software:requesttracker:autoqueue
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| software:requesttracker:autoqueue [2024/08/29 19:38] – rodolico | software:requesttracker:autoqueue [2024/08/30 01:29] (current) – rodolico | ||
|---|---|---|---|
| Line 38: | Line 38: | ||
| return 1; | return 1; | ||
| </ | </ | ||
| + | |||
| + | ===== Placing mail to different addresses in different queues ===== | ||
| + | |||
| + | This is easy to do in RT, if you are using aliases to route them. For example, if you have // | ||
| + | <code bash> | ||
| + | support: " | ||
| + | support-comment: | ||
| + | </ | ||
| + | which will redirect the incoming mail to Request Tracker' | ||
| + | |||
| + | In order to add new clients, you can create different aliases for each to correspond with; in this case, client1 and client2, which would go into the queue' | ||
| + | <code bash> | ||
| + | support: " | ||
| + | support-comment: | ||
| + | client1: " | ||
| + | client1-comment: | ||
| + | client2: " | ||
| + | client2-comment: | ||
| + | </ | ||
| + | |||
| + | Now, mail sent to client1@example.com would be forwarded to client1@rt.example.com, | ||
software/requesttracker/autoqueue.1724978283.txt.gz · Last modified: 2024/08/29 19:38 by rodolico
