[rt-users] Configuring fetchmail to poll emails to respective queues.

[Aaron C. de Bruyn]

I'm not 100% sure, but I think your 'Reply Address' and 'Comment Address'
need to be different.

To get mail into the "IT Support" queue, you will need to modify
fetchmailrc to call rt-mailgate --queue "IT Support" and it should
hopefully work.

-A

On Tue, Jun 2, 2015 at 9:12 AM, Rohit Gupta <rohit.gupta at syncoms.co.uk>
wrote:

>  Dear All,
>
> I have configured new queue with ‘IT Support’ and configured want that any
> emails coming to ithelpdesk at syncoms.co.uk should be fetched into this new
> queue. The snapshot of the new queue:
>
>
>
>  So far, everything is running fine and emails are been received in the
> ‘general’ queue. Now what do I need to do in order to configure rt such
> that any emails coming to ithelpdesk at syncoms.co.uk comes in IT Support
> queue. As per few blogs they are saying to add in /etc/aliases . can you
> please suggest as what do I need to do – if I have to enter into the
> /etc/aliases then how my configuration will look like?
>
>  At the moment, /etc/aliases is:
>
>   And /etc/fetchmailrc:
>
>
>
> Also, I have tried changing the –queue general to –queue ‘it support’ but
> it didn’t work. Infact this time the requestor is receiving a mailer demon
> error message.
>
> Please suggest. Thanks
>
>
>
>
>
> Kind Regards,
>
>
>
> *Rohit Gupta*
>
> IT Infrastructure Manager
>
> Synchronized Communications Ltd
>
> [image: New-RGB-logo-invoice]
>
>
>
> Unit 5, Stonefield Way,
>
> South Ruislip Middlesex
>
> London  UK– HA4 0JS
>
>
>
> DDI: +44(0)208 185 6163
>
> Fax: +44(0)208 845 3657
>
> Email: rohit.gupta at syncoms.co.uk
>
> Web: www.syncoms.co.uk
>
> *P* *please don't print this e-mail unless you really need to*
>
> *Confidentiality Notice <http://www.syncoms.co.uk/Legal.html> | Legal
> <http://www.syncoms.co.uk/Legal.html> | Disclaimer
> <http://www.syncoms.co.uk/Disclaimer.html>*
>
>
>
> [image: image005][image: Kite-Mark-Blue-2010]
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20150602/4cbe73d4/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 49188 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20150602/4cbe73d4/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 21146 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20150602/4cbe73d4/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 1831 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20150602/4cbe73d4/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 6426 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20150602/4cbe73d4/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 3043 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20150602/4cbe73d4/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 11981 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20150602/4cbe73d4/attachment-0002.png>