Re: Multiple incoming email boxes
--_000_c960ab75ab514fa8b67e4f3e116e7022CY1PR0201MB0747namprd02_ Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=utf-8 VGF1ZiwNCg0KSSBhbHNvIHdvbmRlciBpZiB5b3Ugc2VwYXJhdGUgdGhlIHJlcXVlc3RzICYgYnVs ayBtYWlsIGludG8gMiBtYWlsYm94ZXMsIGlmIHlvdSBjYW4gY29udHJvbCB0aGUgb3JkZXIgb2Yg d2hpY2ggaXMgcG9sbGVkIGZpcnN0IHNvIHRoYXQgb24gZWFjaCBwb2xsaW5nIGludGVydmFsIHRo ZSByZXF1ZXN0IGJveCAgd291bGQgYmUgcG9sbGVkIGZpcnN0LiAgRG9u4oCZdCBrbm93IHdoYXQg Y29udHJvbHMgcG9sbGluZyBvcmRlciDigJMgbmFtZSwgY3JlYXRlIGRhdGUgb2YgbWFpbGJveCBj b25maWd1cmF0aW9uIHJlY29yZCwgb3Igd2hhdC4gIEJ1dCBtYXliZSB0aGF0IHdvdWxkIHNhdmUg eW91IG1haW50YWluaW5nIG1vcmUgdGhhbiAxIGVtYWlsIGVuZ2luZS4NCg0KRGF2aWQNCg0KRGF2 aWQgRHVybGluZw0KVW5pdmVyc2l0eSBvZiBHZW9yZ2lhDQoNCkZyb206IEFjdGlvbiBSZXF1ZXN0 IFN5c3RlbSBkaXNjdXNzaW9uIGxpc3QoQVJTTGlzdCkgW21haWx0bzphcnNsaXN0QEFSU0xJU1Qu T1JHXSBPbiBCZWhhbGYgT2YgUmFuZGVlcCBBdHdhbA0KU2VudDogVGh1cnNkYXksIEp1bmUgMTks IDIwMTQgOToyOSBQTQ0KVG86IGFyc2xpc3RAQVJTTElTVC5PUkcNClN1YmplY3Q6IFJlOiBNdWx0 aXBsZSBpbmNvbWluZyBlbWFpbCBib3hlcw0KDQoqKg0KSGkgVGF1ZiwNCg0KSSBoYWQgZmFjZWQg YSBzaW1pbGFyIHByb2JsZW0gaW4gdGhlIHBhc3QuICBVcHdhcmRzIG9mIDMwIG1haWxib3hlcyBh Y3Jvc3MgZGlmZmVyZW50IGRlcGFydG1lbnRzLiAgV2UgZGlkIGhhdmUganVzdCBvbmUgZW1haWwg ZW5naW5lIGNvbmZpZ3VyZWQgZm9yIGFsbCBvZiB0aGVtLCBidXQgcmFuIGludG8gbGFyZ2UgbGF0 ZW5jeSBzaW5jZSBpdCB3b3VsZCBnbyB0aHJvdWdoIHRoZW0gYWxsIHNlcmlhbGx5LCBtZWFuaW5n IHRoYXQgbWFpbGJveGVzIHdpdGggMSBvciAyIHVucmVhZCBtZXNzYWdlcyBjb3VsZCB0YWtlIGEg cmVhbGx5IGxvbmcgdGltZSB0byBhcnJpdmUgc2luY2UgdGhlIGVtYWlsIGVuZ2luZSBnb2VzIHRo cm91Z2ggZWFjaCBvbmUgc2VyaWFsbHksIGFuZCB0aGVyZSB3b3VsZCBiZSBzb21lIGhpZ2ggdm9s dW1lICdidWxrJyB0eXBlIGVtYWlsIGJveGVzOyBwcmV0dHkgbXVjaCB3aGF0IHlvdSBhcmUgZGVz Y3JpYmluZy4NCg0KSGVyZSBhcmUgYSBidW5jaCBvZiBwZXJmb3JtYW5jZSB0aXBzIHRvIHNwZWVk IHVwIGVtYWlsIHByb2Nlc3NpbmcgaW4gZ2VuZXJhbC4gIFRoaXMgbWF5IGhlbHAgc2lnbmlmaWNh bnRseSB3aXRoIHlvdXIgaXNzdWUuDQoNCmh0dHBzOi8vY29tbXVuaXRpZXMuYm1jLmNvbS9kb2Nz L0RPQy0xODUxNA0KDQpIb3dldmVyLCBpZiBpdCBpcyBzdGlsbCBub3QgZ29vZCBlbm91Z2ggZm9y IHlvdXIgY3VzdG9tZXJzLCBhbmQgeW91IHdhbnQgdG8gZ2V0IHRoZSBiZXN0IHBvc3NpYmxlIHRo cm91Z2hwdXQsIChpLmUuIHByb2Nlc3MgaW4gcGFyYWxsZWwpIHllcyB5b3UgY2FuIGluc3RhbGwg bXVsdGlwbGUgZW1haWwgZW5naW5lcyBvbiBhIHNpbmdsZSBzZXJ2ZXIgaW4gc2VwZXJhdGUgZGly ZWN0b3JpZXMgb3IgaW5zdGFsbCBtdWx0aXBsZSBvbiBhIHNlcGVyYXRlIHNlcnZlciBvciBldmVu IGEgc2V0IG9mIHNlcnZlcnMuICBZb3Ugd2FudCB0byBkZXRlcm1pbmUgaG93IHRvIGRvdGhpcyBi YXNlZCBvbiBhdmFpbGFibGUgbWVtb3J5IGFuZCBjcHUgZm9yIGVhY2ggc2VydmVyLCBidXQgaW4g eW91ciBjYXNlIHdpdGgganVzdCB0d28gaW5jb21pbmcgZW1haWwgaW5ib3hlcywgdHdvIGVtYWls IGVuZ2luZSBpbnN0YW5jZXMgb24gdGhlIHNhbWUgbWFjaGluZSBzaG91bGQgYmUgZmluZS4gIEkg d291bGQgYXZvaWQgcHV0dGluZyBlbWFpbCBlbmdpbmUgYXMgYSBzZXJ2aWNlIGluIGEgc2VydmVy IGdyb3VwIGlmIHlvdSBkbyB0aGlzLCBhbmQgYWxzbyByZWNvbW1lbmQga2VlcGluZyBlbWFpbCBz dGFydHVwIHNlcGVyYXRlIGZyb20gYXJzeXN0ZW0gc3RhcnR1cC4NCg0KQWZ0ZXIgaW5zdGFsbGlu ZywgYW5kIGJlZm9yZSBzdGFydGluZyBpdCwgeW91IG5lZWQgdG8gZWRpdCB0aGUgZW1haWxkYWVt b24ucHJvcGVydGllcyBmb3IgZWFjaCBpbnN0YW5jZSB0byB0ZWxsIGl0IHdoaWNoIG1haWxib3hl cyBpdCBpcyByZXNwb25zaWJsZSBmb3IuICBJIHRoaW5rIHRoZSBpbnN0YWxsZXIgd2lsbCBhc2sg eW91IGZvciB5b3VyIHRhcmdldCBhcnNlcnZlciBuYW1lIGR1cmluZyBpbnN0YWxsLCBidXQgdGhl IGVtYWlsZGFlbW9uLnByb3BlcnRpZXMgYWxzbyBob2xkcyB0aGlzIGluZm9ybWF0aW9uLg0KDQpj b20ucmVtZWR5LmFyc3lzLmVtYWlsZGFlbW9uLk1haWxib3hlcz0NCklmIHlvdSBydW4gbXVsdGlw bGUgZW1haWwgZW5naW5lcyBmb3IgYSBzaW5nbGUgc2VydmVyLCB0aGlzIHNldHRpbmcNCnNwZWNp ZmllcyB3aGljaCBtYWlsYm94ZXMgdGhpcyBlbWFpbCBlbmdpbmUgc2hvdWxkIHByb2Nlc3MuIFRo ZQ0KdmFsdWUgc2hvdWxkIGNvbnRhaW4gY29tbWEtc2VwYXJhdGVkIG1haWxib3ggbmFtZXMuIElm IHRoZQ0KdmFsdWUgaXMgZW1wdHksIHRoZSBlbWFpbCBlbmdpbmUgcHJvY2Vzc2VzIGFsbCBvZiB0 aGUgbWFpbGJveGVzDQpjb25maWd1cmVkIGZvciB0aGUgc2VydmVyLiBJZiB0aGUgdmFsdWUgaXMg bm90IGVtcHR5LCB0aGUgZW1haWwNCmVuZ2luZSBwcm9jZXNzZXMgdGhlIHNwZWNpZmllZCBtYWls Ym94ZXMgb25seS4NCg0KSFRIDQoNClRoYW5rcw0KDQpSYW5kZWVwDQoNCk9uIFRodSwgSnVuIDE5 LCAyMDE0IGF0IDc6MzQgUE0sIEdyb29tcywgRnJlZGVyaWNrIFcgPGZyZWRlcmljay53Lmdyb29t c0B4by5jb208bWFpbHRvOmZyZWRlcmljay53Lmdyb29tc0B4by5jb20+PiB3cm90ZToNCkp1c3Qg dXNlIHRoZSBvbmUgRW1haWwgRW5naW5lIGFuZCBwdXQgbXVsdGlwbGUgbWFpbGJveGVzIGluIHRo ZSBFbWFpbCBDb25maWd1cmF0aW9uIGZvcm0uICBPbiBTdGFydHVwIHRoZSBlbmdpbmUgcmVhZHMg dGhlIGNvbmZpZ3VyYXRpb24gYW5kIHNldHMgdXAgdGhlIG5lY2Vzc2FyeSB0aHJlYWRzLg0KDQpJ IGRvbid0IHRoaW5rIHRoZXJlIGlzIGEgd2F5IGZvciBhbiBFbWFpbCBFbmdpbmUgdG8gc3BlY2lm eSB3aGljaCBtYWlsYm94ZXMgaXQgd2lsbCBwcm9jZXNzIChZb3UgY2FuIHNwZWNpZnkgd2hpY2gg c2VydmVycywgYnV0IEkgZG9uJ3QgdGhpbmsgeW91IGNhbiBnbyBhbnkgZGVlcGVyIHRoYW4gdGhh dCBzbyBpdCBpcyBhbiBhbGwtbWFpbGJveGVzIG9uIHRoZSBzZXJ2ZXIgb3Igbm9uZSkuDQoNCkZy ZWQNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEFjdGlvbiBSZXF1ZXN0IFN5 c3RlbSBkaXNjdXNzaW9uIGxpc3QoQVJTTGlzdCkgW21haWx0bzphcnNsaXN0QEFSU0xJU1QuT1JH PG1haWx0bzphcnNsaXN0QEFSU0xJU1QuT1JHPl0gT24gQmVoYWxmIE9mIFRhdWYgQ2hvd2RodXJ5 DQpTZW50OiBUaHVyc2RheSwgSnVuZSAxOSwgMjAxNCA2OjExIFBNDQpUbzogYXJzbGlzdEBBUlNM SVNULk9SRzxtYWlsdG86YXJzbGlzdEBBUlNMSVNULk9SRz4NClN1YmplY3Q6IFJlOiBNdWx0aXBs ZSBpbmNvbWluZyBlbWFpbCBib3hlcw0KUmlnaHQsIGJ1dCBteSBxdWVzdGlvbiBpcyBtb3JlIG9u
Re: Multiple incoming email boxes
--_000_140326781578827255ugaedu_ Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable (Sorry - look like outlook issue struck me too.) Tauf, I also wonder if you separate the requests bulk mail into 2 mailboxes, if= you can control the order of which is polled first so that on each polling= interval the request box would be polled first. Don=92t know what contro= ls polling order =96 name, create date of mailbox configuration record, or = what. But maybe that would save you maintaining more than 1 email engine. David David Durling University of Georgia David Durling706-542-0223 Enterprise IT Servicesdurl...@uga.edumailto:durl...@uga.edu University of Georgia From: Action Request System discussion list(ARSList) arslist@ARSLIST.ORG = on behalf of Tauf Chowdhury taufc...@gmail.com Sent: Thursday, June 19, 2014 9:40 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes ** Thanks Randeep! Lots of good info here. I'll check it out and report back. Sent from my iPhone On Jun 19, 2014, at 9:28 PM, Randeep Atwal ratwals...@gmail.commailto:rat= wals...@gmail.com wrote: ** Hi Tauf, I had faced a similar problem in the past. Upwards of 30 mailboxes across = different departments. We did have just one email engine configured for al= l of them, but ran into large latency since it would go through them all se= rially, meaning that mailboxes with 1 or 2 unread messages could take a rea= lly long time to arrive since the email engine goes through each one serial= ly, and there would be some high volume 'bulk' type email boxes; pretty muc= h what you are describing. Here are a bunch of performance tips to speed up email processing in genera= l. This may help significantly with your issue. https://communities.bmc.com/docs/DOC-18514 However, if it is still not good enough for your customers, and you want to= get the best possible throughput, (i.e. process in parallel) yes you can i= nstall multiple email engines on a single server in seperate directories or= install multiple on a seperate server or even a set of servers. You want = to determine how to dothis based on available memory and cpu for each serve= r, but in your case with just two incoming email inboxes, two email engine = instances on the same machine should be fine. I would avoid putting email = engine as a service in a server group if you do this, and also recommend ke= eping email startup seperate from arsystem startup. After installing, and before starting it, you need to edit the emaildaemon.= properties for each instance to tell it which mailboxes it is responsible f= or. I think the installer will ask you for your target arserver name durin= g install, but the emaildaemon.properties also holds this information. com.remedy.arsys.emaildaemon.Mailboxes=3D If you run multiple email engines for a single server, this setting specifies which mailboxes this email engine should process. The value should contain comma-separated mailbox names. If the value is empty, the email engine processes all of the mailboxes configured for the server. If the value is not empty, the email engine processes the specified mailboxes only. HTH Thanks Randeep On Thu, Jun 19, 2014 at 7:34 PM, Grooms, Frederick W frederick.w.grooms@xo= .commailto:frederick.w.gro...@xo.com wrote: Just use the one Email Engine and put multiple mailboxes in the Email Confi= guration form. On Startup the engine reads the configuration and sets up t= he necessary threads. I don't think there is a way for an Email Engine to specify which mailboxes= it will process (You can specify which servers, but I don't think you can = go any deeper than that so it is an all-mailboxes on the server or none). Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIS= T.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 6:11 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes Right, but my question is more on the how to set it up on the server itself= or if I should use multiple servers each with it's own instance of the ema= il engine. That's where I'm fuzzy and the documentation isn't there either. Sent from my iPhone -Original Message- On Jun 19, 2014, at 6:18 PM, Grooms, Frederick W wrote: If you set up separate inbound mailboxes, each mailbox should have its ow= n threads Fred Original message From: Action Request System discussion list(ARSList) [mailto:arslist@ARSL= IST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 4:53 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes ** Thanks Shawn. Let me elaborate further on the issue. Right now, there's a single email address. This email is receiving both u= ser requests
Re: Multiple incoming email boxes
The easiest way to do it is that I have distribution lists with just the inbound Remedy email account, and filter the incoming emails based on those. For example, I may have remedyservert...@blah.commailto:remedyservert...@blah.com and remedyserviced...@blah.commailto:remedyserviced...@blah.com as two distribution lists that both contain only the remedym...@blah.commailto:remedym...@blah.com account. When an email to either of those are sent in (where you have to look at not just the To: line but the CC: line), Remedy has RBE rules to process them and create an Incident with a Template for the Server team, Service Desk, or whatever. Since inbound email uses Outlook profiles it seems like it might be kind of tricky or at least less stable to set up multiple instances on a single server so I’ve never gone with that approach. Thanks, Shawn Pierson Remedy Developer | Energy Transfer From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 3:22 PM To: arslist@ARSLIST.ORG Subject: Multiple incoming email boxes ** All, What is the best way to configure the email engine on the server side? I know you can set up multiple inbound email records in the Email config form but I'm more interested on the server side. Do I have to have multiple email engine services installed on the same box? Can I install the email engine on 2 separate servers? Thanks.. -- Tauf Chowdhury _ARSlist: Where the Answers Are and have been for 20 years_ Private and confidential as detailed here: http://www.energytransfer.com/mail_disclaimer.aspx . If you cannot access the link, please e-mail sender. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Multiple incoming email boxes
Thanks Shawn. Let me elaborate further on the issue. Right now, there's a single email address. This email is receiving both user requests and also what we call bulk requests from event management systems etc... So what is happening now is that the bulk requests which are high in number are being processed ahead of the user requests because of the order that they come in. This is leading to the user experiencing a delay in their ticket being generated. That is the crux of the issue that we are trying to figure out the best approach to. Logically, we thought that sending the bulk requests to a separate email address/mailbox and processing them separately would help. That is why I am trying to set up multiple boxes. On Thu, Jun 19, 2014 at 4:27 PM, Pierson, Shawn shawn.pier...@energytransfer.com wrote: ** The easiest way to do it is that I have distribution lists with just the inbound Remedy email account, and filter the incoming emails based on those. For example, I may have remedyservert...@blah.com and remedyserviced...@blah.com as two distribution lists that both contain only the remedym...@blah.com account. When an email to either of those are sent in (where you have to look at not just the To: line but the CC: line), Remedy has RBE rules to process them and create an Incident with a Template for the Server team, Service Desk, or whatever. Since inbound email uses Outlook profiles it seems like it might be kind of tricky or at least less stable to set up multiple instances on a single server so I’ve never gone with that approach. Thanks, *Shawn Pierson * Remedy Developer | Energy Transfer *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Tauf Chowdhury *Sent:* Thursday, June 19, 2014 3:22 PM *To:* arslist@ARSLIST.ORG *Subject:* Multiple incoming email boxes ** All, What is the best way to configure the email engine on the server side? I know you can set up multiple inbound email records in the Email config form but I'm more interested on the server side. Do I have to have multiple email engine services installed on the same box? Can I install the email engine on 2 separate servers? Thanks.. -- *Tauf Chowdhury* _ARSlist: Where the Answers Are and have been for 20 years_ Private and confidential as detailed here http://www.energytransfer.com/mail_disclaimer.aspx. If you cannot access hyperlink, please e-mail sender. _ARSlist: Where the Answers Are and have been for 20 years_ -- *Tauf Chowdhury* ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Multiple incoming email boxes
If you set up separate inbound mailboxes, each mailbox should have its own threads Fred Original message From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 4:53 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes ** Thanks Shawn. Let me elaborate further on the issue. Right now, there's a single email address. This email is receiving both user requests and also what we call bulk requests from event management systems etc... So what is happening now is that the bulk requests which are high in number are being processed ahead of the user requests because of the order that they come in. This is leading to the user experiencing a delay in their ticket being generated. That is the crux of the issue that we are trying to figure out the best approach to. Logically, we thought that sending the bulk requests to a separate email address/mailbox and processing them separately would help. That is why I am trying to set up multiple boxes. Original message On Thu, Jun 19, 2014 at 4:27 PM, Pierson, Shawn wrote: ** The easiest way to do it is that I have distribution lists with just the inbound Remedy email account, and filter the incoming emails based on those. For example, I may have remedyservert...@blah.com and remedyserviced...@blah.com as two distribution lists that both contain only the remedym...@blah.com account. When an email to either of those are sent in (where you have to look at not just the To: line but the CC: line), Remedy has RBE rules to process them and create an Incident with a Template for the Server team, Service Desk, or whatever. Since inbound email uses Outlook profiles it seems like it might be kind of tricky or at least less stable to set up multiple instances on a single server so I’ve never gone with that approach. Thanks, Shawn Pierson Remedy Developer | Energy Transfer Original message From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 3:22 PM To: arslist@ARSLIST.ORG Subject: Multiple incoming email boxes ** All, What is the best way to configure the email engine on the server side? I know you can set up multiple inbound email records in the Email config form but I'm more interested on the server side. Do I have to have multiple email engine services installed on the same box? Can I install the email engine on 2 separate servers? Thanks.. -- Tauf Chowdhury ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Multiple incoming email boxes
Right, but my question is more on the how to set it up on the server itself or if I should use multiple servers each with it's own instance of the email engine. That's where I'm fuzzy and the documentation isn't there either. Sent from my iPhone On Jun 19, 2014, at 6:18 PM, Grooms, Frederick W frederick.w.gro...@xo.com wrote: If you set up separate inbound mailboxes, each mailbox should have its own threads Fred Original message From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 4:53 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes ** Thanks Shawn. Let me elaborate further on the issue. Right now, there's a single email address. This email is receiving both user requests and also what we call bulk requests from event management systems etc... So what is happening now is that the bulk requests which are high in number are being processed ahead of the user requests because of the order that they come in. This is leading to the user experiencing a delay in their ticket being generated. That is the crux of the issue that we are trying to figure out the best approach to. Logically, we thought that sending the bulk requests to a separate email address/mailbox and processing them separately would help. That is why I am trying to set up multiple boxes. Original message On Thu, Jun 19, 2014 at 4:27 PM, Pierson, Shawn wrote: ** The easiest way to do it is that I have distribution lists with just the inbound Remedy email account, and filter the incoming emails based on those. For example, I may have remedyservert...@blah.com and remedyserviced...@blah.com as two distribution lists that both contain only the remedym...@blah.com account. When an email to either of those are sent in (where you have to look at not just the To: line but the CC: line), Remedy has RBE rules to process them and create an Incident with a Template for the Server team, Service Desk, or whatever. Since inbound email uses Outlook profiles it seems like it might be kind of tricky or at least less stable to set up multiple instances on a single server so I’ve never gone with that approach. Thanks, Shawn Pierson Remedy Developer | Energy Transfer Original message From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 3:22 PM To: arslist@ARSLIST.ORG Subject: Multiple incoming email boxes ** All, What is the best way to configure the email engine on the server side? I know you can set up multiple inbound email records in the Email config form but I'm more interested on the server side. Do I have to have multiple email engine services installed on the same box? Can I install the email engine on 2 separate servers? Thanks.. -- Tauf Chowdhury ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Multiple incoming email boxes
Just use the one Email Engine and put multiple mailboxes in the Email Configuration form. On Startup the engine reads the configuration and sets up the necessary threads. I don't think there is a way for an Email Engine to specify which mailboxes it will process (You can specify which servers, but I don't think you can go any deeper than that so it is an all-mailboxes on the server or none). Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 6:11 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes Right, but my question is more on the how to set it up on the server itself or if I should use multiple servers each with it's own instance of the email engine. That's where I'm fuzzy and the documentation isn't there either. Sent from my iPhone -Original Message- On Jun 19, 2014, at 6:18 PM, Grooms, Frederick W wrote: If you set up separate inbound mailboxes, each mailbox should have its own threads Fred Original message From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 4:53 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes ** Thanks Shawn. Let me elaborate further on the issue. Right now, there's a single email address. This email is receiving both user requests and also what we call bulk requests from event management systems etc... So what is happening now is that the bulk requests which are high in number are being processed ahead of the user requests because of the order that they come in. This is leading to the user experiencing a delay in their ticket being generated. That is the crux of the issue that we are trying to figure out the best approach to. Logically, we thought that sending the bulk requests to a separate email address/mailbox and processing them separately would help. That is why I am trying to set up multiple boxes. Original message On Thu, Jun 19, 2014 at 4:27 PM, Pierson, Shawn wrote: ** The easiest way to do it is that I have distribution lists with just the inbound Remedy email account, and filter the incoming emails based on those. For example, I may have remedyservert...@blah.com and remedyserviced...@blah.com as two distribution lists that both contain only the remedym...@blah.com account. When an email to either of those are sent in (where you have to look at not just the To: line but the CC: line), Remedy has RBE rules to process them and create an Incident with a Template for the Server team, Service Desk, or whatever. Since inbound email uses Outlook profiles it seems like it might be kind of tricky or at least less stable to set up multiple instances on a single server so I’ve never gone with that approach. Thanks, Shawn Pierson Remedy Developer | Energy Transfer Original message From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 3:22 PM To: arslist@ARSLIST.ORG Subject: Multiple incoming email boxes ** All, What is the best way to configure the email engine on the server side? I know you can set up multiple inbound email records in the Email config form but I'm more interested on the server side. Do I have to have multiple email engine services installed on the same box? Can I install the email engine on 2 separate servers? Thanks.. -- Tauf Chowdhury ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Multiple incoming email boxes
Hi Tauf, I had faced a similar problem in the past. Upwards of 30 mailboxes across different departments. We did have just one email engine configured for all of them, but ran into large latency since it would go through them all serially, meaning that mailboxes with 1 or 2 unread messages could take a really long time to arrive since the email engine goes through each one serially, and there would be some high volume 'bulk' type email boxes; pretty much what you are describing. Here are a bunch of performance tips to speed up email processing in general. This may help significantly with your issue. https://communities.bmc.com/docs/DOC-18514 However, if it is still not good enough for your customers, and you want to get the best possible throughput, (i.e. process in parallel) yes you can install multiple email engines on a single server in seperate directories or install multiple on a seperate server or even a set of servers. You want to determine how to dothis based on available memory and cpu for each server, but in your case with just two incoming email inboxes, two email engine instances on the same machine should be fine. I would avoid putting email engine as a service in a server group if you do this, and also recommend keeping email startup seperate from arsystem startup. After installing, and before starting it, you need to edit the emaildaemon.properties for each instance to tell it which mailboxes it is responsible for. I think the installer will ask you for your target arserver name during install, but the emaildaemon.properties also holds this information. com.remedy.arsys.emaildaemon.Mailboxes= If you run multiple email engines for a single server, this setting specifies which mailboxes this email engine should process. The value should contain comma-separated mailbox names. If the value is empty, the email engine processes all of the mailboxes configured for the server. If the value is not empty, the email engine processes the specified mailboxes only. HTH Thanks Randeep On Thu, Jun 19, 2014 at 7:34 PM, Grooms, Frederick W frederick.w.gro...@xo.com wrote: Just use the one Email Engine and put multiple mailboxes in the Email Configuration form. On Startup the engine reads the configuration and sets up the necessary threads. I don't think there is a way for an Email Engine to specify which mailboxes it will process (You can specify which servers, but I don't think you can go any deeper than that so it is an all-mailboxes on the server or none). Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 6:11 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes Right, but my question is more on the how to set it up on the server itself or if I should use multiple servers each with it's own instance of the email engine. That's where I'm fuzzy and the documentation isn't there either. Sent from my iPhone -Original Message- On Jun 19, 2014, at 6:18 PM, Grooms, Frederick W wrote: If you set up separate inbound mailboxes, each mailbox should have its own threads Fred Original message From: Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 4:53 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes ** Thanks Shawn. Let me elaborate further on the issue. Right now, there's a single email address. This email is receiving both user requests and also what we call bulk requests from event management systems etc... So what is happening now is that the bulk requests which are high in number are being processed ahead of the user requests because of the order that they come in. This is leading to the user experiencing a delay in their ticket being generated. That is the crux of the issue that we are trying to figure out the best approach to. Logically, we thought that sending the bulk requests to a separate email address/mailbox and processing them separately would help. That is why I am trying to set up multiple boxes. Original message On Thu, Jun 19, 2014 at 4:27 PM, Pierson, Shawn wrote: ** The easiest way to do it is that I have distribution lists with just the inbound Remedy email account, and filter the incoming emails based on those. For example, I may have remedyservert...@blah.com and remedyserviced...@blah.com as two distribution lists that both contain only the remedym...@blah.com account. When an email to either of those are sent in (where you have to look at not just the To: line but the CC: line), Remedy has RBE rules to process them and create an Incident with a Template for the Server team, Service Desk, or whatever. Since inbound email uses Outlook profiles it seems like it might be kind of tricky or at least
Re: Multiple incoming email boxes
Thanks Randeep! Lots of good info here. I'll check it out and report back. Sent from my iPhone On Jun 19, 2014, at 9:28 PM, Randeep Atwal ratwals...@gmail.com wrote: ** Hi Tauf, I had faced a similar problem in the past. Upwards of 30 mailboxes across different departments. We did have just one email engine configured for all of them, but ran into large latency since it would go through them all serially, meaning that mailboxes with 1 or 2 unread messages could take a really long time to arrive since the email engine goes through each one serially, and there would be some high volume 'bulk' type email boxes; pretty much what you are describing. Here are a bunch of performance tips to speed up email processing in general. This may help significantly with your issue. https://communities.bmc.com/docs/DOC-18514 However, if it is still not good enough for your customers, and you want to get the best possible throughput, (i.e. process in parallel) yes you can install multiple email engines on a single server in seperate directories or install multiple on a seperate server or even a set of servers. You want to determine how to dothis based on available memory and cpu for each server, but in your case with just two incoming email inboxes, two email engine instances on the same machine should be fine. I would avoid putting email engine as a service in a server group if you do this, and also recommend keeping email startup seperate from arsystem startup. After installing, and before starting it, you need to edit the emaildaemon.properties for each instance to tell it which mailboxes it is responsible for. I think the installer will ask you for your target arserver name during install, but the emaildaemon.properties also holds this information. com.remedy.arsys.emaildaemon.Mailboxes= If you run multiple email engines for a single server, this setting specifies which mailboxes this email engine should process. The value should contain comma-separated mailbox names. If the value is empty, the email engine processes all of the mailboxes configured for the server. If the value is not empty, the email engine processes the specified mailboxes only. HTH Thanks Randeep On Thu, Jun 19, 2014 at 7:34 PM, Grooms, Frederick W frederick.w.gro...@xo.com wrote: Just use the one Email Engine and put multiple mailboxes in the Email Configuration form. On Startup the engine reads the configuration and sets up the necessary threads. I don't think there is a way for an Email Engine to specify which mailboxes it will process (You can specify which servers, but I don't think you can go any deeper than that so it is an all-mailboxes on the server or none). Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 6:11 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes Right, but my question is more on the how to set it up on the server itself or if I should use multiple servers each with it's own instance of the email engine. That's where I'm fuzzy and the documentation isn't there either. Sent from my iPhone -Original Message- On Jun 19, 2014, at 6:18 PM, Grooms, Frederick W wrote: If you set up separate inbound mailboxes, each mailbox should have its own threads Fred Original message From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, June 19, 2014 4:53 PM To: arslist@ARSLIST.ORG Subject: Re: Multiple incoming email boxes ** Thanks Shawn. Let me elaborate further on the issue. Right now, there's a single email address. This email is receiving both user requests and also what we call bulk requests from event management systems etc... So what is happening now is that the bulk requests which are high in number are being processed ahead of the user requests because of the order that they come in. This is leading to the user experiencing a delay in their ticket being generated. That is the crux of the issue that we are trying to figure out the best approach to. Logically, we thought that sending the bulk requests to a separate email address/mailbox and processing them separately would help. That is why I am trying to set up multiple boxes. Original message On Thu, Jun 19, 2014 at 4:27 PM, Pierson, Shawn wrote: ** The easiest way to do it is that I have distribution lists with just the inbound Remedy email account, and filter the incoming emails based on those. For example, I may have remedyservert...@blah.com and remedyserviced...@blah.com as two distribution lists that both contain only the remedym...@blah.com account. When an email to either of those are sent in (where
