Hi,
I’m wondering if RT is able to handle multiple (sub)domains for receive
email?
For instance, we have support per department that we would like to see
into seperate ‘queues’:
support@dep-a.company.com should go to queue ‘dep-a support’
support@dep-b.company.com should go to queue ‘dep-b support’
support@company.com should go to ‘generic support’
sales@dep-a.company.com should go to queue ‘dep-a sales’
sales@dep-b.company.com should go to queue ‘dep-b sales’
sales@company.com should go to ‘generic sales’
I see options to ‘stripe’ subdomains etc, but I really can’t see how RT
can be configured to handle the situation mentioned above?
Thanks,
=20
I’m wondering if RT is able to handle multiple (sub)domains for receive
email?
=20
For instance, we have support per department that we would like to see
into seperate ‘queues’:
=20
support@dep-a.company.com should go to queue ‘dep-a support’
support@dep-b.company.com should go to queue ‘dep-b support’
support@company.com should go to ‘generic support’
=20
sales@dep-a.company.com should go to queue ‘dep-a sales’
sales@dep-b.company.com should go to queue ‘dep-b sales’
sales@company.com should go to ‘generic sales’
=20
=20
I see options to ‘stripe’ subdomains etc, but I really can’t see how RT
can be configured to handle the situation mentioned above?
This is just a mail issue, not RT.
Suppose RT is running on a machine that recieves mail @rt.company.com
One option is to set your mail relay so that:
support@dep-a.company.com forwards to support-dep-a@rt.company.com
…
Then it would be easy for rt to check each address and insert
into the proper queue.
bobg