Our OTRS 3 server is hosted on an Amazon EC2 Micro EBS Instance with an assigned Elastic IP.<div>The monthly cost for the instance is less than $18 and handles our ticket volume very well.</div><div><br><div>Our regular email is serviced by Google Apps for Business (premium edition) where the addresses are</div>
<div><a href="mailto:emailaddy@ourdomain.com">emailaddy@ourdomain.com</a></div><div><br><div>We use a Google Apps free edition domain for service accounts including the main OTRS mailbox which is </div><div><br></div><div>
<a href="mailto:helpdesk@ourdomain.net">helpdesk@ourdomain.net</a></div><div><br></div><div>This is the primary address which OTRS uses, polling the mailbox every two minutes using the OTRS fetch mail cronjob</div><div><br>
</div><div>Google Apps allows up to 30 alias email addresses per individual.  We have aliases set up that correspond to queue names, e.g.</div><div><a href="mailto:desktops@ourdomain.net">desktops@ourdomain.net</a> &gt;&gt; desktops queue</div>
<div><a href="mailto:servers@ourdomain.net">servers@ourdomain.net</a> &gt;&gt; servers queue</div><div><a href="mailto:malware@ourdomain.net">malware@ourdomain.net</a> &gt;&gt; malware queue</div><div><br></div><div>Even though all the messages go to the same <a href="mailto:helpdesk@ourdomain.net">helpdesk@ourdomain.net</a> mailbox OTRS can see the to: field of each message and routes the messages accordingly.  I should think that this same method would work for technician emails as well, even though we&#39;re not using that method.  In this way each of your technicians could have a proper email box in the primary company domain for regular internal correspondence, and a helpdesk email address in the service domain to give to customers to keep those emails on the helpdesk.</div>
</div><div><br></div><div>Rob</div></div><div><br></div>