Re: MAPI client other then Outlook for a win 2003 server
We use IMAP4 to Exchange with SSL. The key to getting it to work is that you have to store the SSL certificate in a cert7.db file (for ARS 7.0 and 7.1, at least - I think they were updating it to a cert8.db file for 7.5, but am not certain). Now for the fun part - the cert7.db file format is really old, and there's not much around to modify it. I've heard rumors of a Java utility that can store the key in it, but don't know any details. We do it using Netscape Communicator 4.7 (yes, really). We start it, go to a web site that uses the same certificate used by Exchange, tell Netscape to permanently accept the certificate, and it saves it in the file. You then need to tell AR System where to find the file. In our case, it's in the default location, and so we add the following line to ar.cfg: AREA-LDAP-Cert-DB: C:\Program Files\Netscape\Users\default (That's the only reference that I can find to it so far, so I'm not sure if the e-mail engine uses that same information, or if it's also specified somewhere else that I just don't know about - it was set up before I got here.) Once the certificate is in the file, the e-mail engine works, and we can also authenticate using SSL to LDAP. We have noticed that the certificate seems to self-expire sometimes, and I don't know what's up with that. After a while, LDAP will stop authenticating and e-mails will sometimes stop coming in. If I open Netscape and go to the site with the certificate, it tells me it has a new certificate. I accept the new certificate, restart the plugin server process and the e-mail engine, and we're good to go again for a while. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of strauss Sent: Tuesday, May 04, 2010 11:08 AM To: arslist@ARSLIST.ORG Subject: Re: MAPI client other then Outlook for a win 2003 server Observations on AREMail integration: I have used MAPI for AREmail integration from the beginning (1998/ARS 3.2 for us - used the Exchange 5.5 Mail client before Outlook), but have recently seen many more problems with stability of the AREmail engine when used with Outlook 2007. Our 7.1 Email engine has crashed, hung, or died silently for the last two years and BMC has never been able to resolve it the problem. I have tried several times to use SMTP and IMAP4 for the engine, with no success. I attribute that to the fact that it is my own Exchange 2007 server, which means that no one with any serious expertise in Exchange is running it! By default, Exchange 2007 is locked down so tight that only MAPI works, but it does allow IMAP4 connections from Outlook Express clients. We keep OE running 24 hours a day - connecting to the production mailbox by IMAP4, and watching the outbound notifications in real time. Outlook Express connects over SSL on port 993 just fine; the AREmail service just throws "AUTHENTICATE failed" errors when given the same settings, and a "No login methods supported" error over non-SSL port 143. Recently we brought up an AR 7.5 server on a hosted VM where we could not join it to our AD domain, so it cannot use MAPI for email without great difficulty, and I tried SMTP and IMAP4 again. Our campus mail host (open-something on linux) is just fine for SMTP... if you want to use Exchange it takes more work. As we learned while trying to get AlarmPoint to send email using Exchange SMTP, you will need to have your email admin create a Hub Transport Receive Connector that allows anonymous relay from your AR Server - limited by IP address. Various attempts to use authenticated connections did not work, but I don't want the overhead of constant re-authentication either. Yesterday I tried to use POP3 instead of IMAP4, and was surprised to find that it worked fine - once I turned it on... the service was not even running on the Exchange server. With settings virtually identical to those of the IMAP4 service, just with different ports, the POP3 service had no problem accepting authenticated sessions from the domain account set in the AREMail configuration form - something it refuses to do if set back to IMAP4. Using POP3, the AREmail engine had no problem reading the Exchange mailbox, parsing incoming email messages, and storing them in the AR System Email Messages form. Switch the configuration form to IMAP4 and it throws authentication errors immediately on service start. Based on this, I would strongly suggest that you use POP3 instead of IMAP4 to connect AREmail to Exchange, if you don't want to use MAPI. On a side note, I have been stress-testing a MAPI setup with AREmail 7.5.00.004 for several weeks now and it has been solid (Outlook 2007 Sp2 minimal install on Win2K8 R2 x64 server). The only issue was when I applied SP2 it reverted to its apparent default setting of "Use Cached
Re: MAPI client other then Outlook for a win 2003 server
Observations on AREMail integration: I have used MAPI for AREmail integration from the beginning (1998/ARS 3.2 for us - used the Exchange 5.5 Mail client before Outlook), but have recently seen many more problems with stability of the AREmail engine when used with Outlook 2007. Our 7.1 Email engine has crashed, hung, or died silently for the last two years and BMC has never been able to resolve it the problem. I have tried several times to use SMTP and IMAP4 for the engine, with no success. I attribute that to the fact that it is my own Exchange 2007 server, which means that no one with any serious expertise in Exchange is running it! By default, Exchange 2007 is locked down so tight that only MAPI works, but it does allow IMAP4 connections from Outlook Express clients. We keep OE running 24 hours a day - connecting to the production mailbox by IMAP4, and watching the outbound notifications in real time. Outlook Express connects over SSL on port 993 just fine; the AREmail service just throws "AUTHENTICATE failed" errors when given the same settings, and a "No login methods supported" error over non-SSL port 143. Recently we brought up an AR 7.5 server on a hosted VM where we could not join it to our AD domain, so it cannot use MAPI for email without great difficulty, and I tried SMTP and IMAP4 again. Our campus mail host (open-something on linux) is just fine for SMTP... if you want to use Exchange it takes more work. As we learned while trying to get AlarmPoint to send email using Exchange SMTP, you will need to have your email admin create a Hub Transport Receive Connector that allows anonymous relay from your AR Server - limited by IP address. Various attempts to use authenticated connections did not work, but I don't want the overhead of constant re-authentication either. Yesterday I tried to use POP3 instead of IMAP4, and was surprised to find that it worked fine - once I turned it on... the service was not even running on the Exchange server. With settings virtually identical to those of the IMAP4 service, just with different ports, the POP3 service had no problem accepting authenticated sessions from the domain account set in the AREMail configuration form - something it refuses to do if set back to IMAP4. Using POP3, the AREmail engine had no problem reading the Exchange mailbox, parsing incoming email messages, and storing them in the AR System Email Messages form. Switch the configuration form to IMAP4 and it throws authentication errors immediately on service start. Based on this, I would strongly suggest that you use POP3 instead of IMAP4 to connect AREmail to Exchange, if you don't want to use MAPI. On a side note, I have been stress-testing a MAPI setup with AREmail 7.5.00.004 for several weeks now and it has been solid (Outlook 2007 Sp2 minimal install on Win2K8 R2 x64 server). The only issue was when I applied SP2 it reverted to its apparent default setting of "Use Cached Exchange Mode" on the account, which absolutely prevents the AREmail engine from working properly. Out of curiosity, I'd like to know how anyone else has managed to get AREMail 7.x to use an IMAP4 connection to Exchange 2007... where MAPI and POP3 work fine with the exact same account/mailbox credentials. Somewhere there must be a knob to turn that I have not found yet. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ARSList Sent: Monday, May 03, 2010 4:28 AM To: arslist@ARSLIST.ORG Subject: Re: MAPI client other then Outlook for a win 2003 server To test IMAPI you can just telnet to the IMAPI port 143 ie telnet myexchangeserver 143 and if it is all working you will see something like OK IMAP ready. Exchange supports POP3 if you prefer to use that - just get your Exchange admin to enable it - I think it is as simple as running a pop3 service. And as suggested you use SMTP as your outgoing port. To test that just telnet to port 25 on your Exchange server. eg telnet myexchangeserver 25 HELO MAIL FROM RCPT TO DATA some text . last bit is dot on its own line. If all that works oyur Exchange server is fine. Do whatever you do in remedy. Angus "Howard Richter" wrote in message news: ... > Angus, > > Thanks I am willing to try anything, since I do not have POP access. No > additional client would be the best way to go, however, I did try IMAPI with > no luck (the port might be locked down). > > Thanks to all, > > Howard > > On Sun, May 2, 2010 at 12:50 PM, ARSList wrote: > > > The original request was for a MAPI client. IMAPI is a totally different > > thing. > > > > If you don't install Outlook then you can
Re: MAPI client other then Outlook for a win 2003 server
To test IMAPI you can just telnet to the IMAPI port 143 ie telnet myexchangeserver 143 and if it is all working you will see something like OK IMAP ready. Exchange supports POP3 if you prefer to use that - just get your Exchange admin to enable it - I think it is as simple as running a pop3 service. And as suggested you use SMTP as your outgoing port. To test that just telnet to port 25 on your Exchange server. eg telnet myexchangeserver 25 HELO MAIL FROM RCPT TO DATA some text . last bit is dot on its own line. If all that works oyur Exchange server is fine. Do whatever you do in remedy. Angus "Howard Richter" wrote in message news: ... > Angus, > > Thanks I am willing to try anything, since I do not have POP access. No > additional client would be the best way to go, however, I did try IMAPI with > no luck (the port might be locked down). > > Thanks to all, > > Howard > > On Sun, May 2, 2010 at 12:50 PM, ARSList wrote: > > > The original request was for a MAPI client. IMAPI is a totally different > > thing. > > > > If you don't install Outlook then you can download a basic MAPI client from > > the MS website - I believe this to be the case. I have never it myself. > > > > Angus > > > > > > "Howard Richter" wrote in message news: > > ... > > Lyle, > > > > Thanks I will give it a try. > > > > On Fri, Apr 30, 2010 at 2:07 PM, Lyle Taylor > > wrote: > > > > > ** > > > > > > No, but there's not much to it, IMAP is a standard mailbox protocol and > > > supported by Exchange (I suppose so long as your administrators have > > enabled > > > it). Basically, you just configure the Mailbox in Remedy (for incoming > > > mail) to use IMAP as the protocol, enter the username and password for > > the > > > account you want to monitor and associate it with the correct outgoing > > > mailbox in Remedy. For outgoing mail, you generally just use standard > > SMTP > > > which Exchange also supports, entering your Exchange server as the SMTP > > > server. You'll need to ask your Exchange admins if IMAP support is > > enabled > > > in Exchange and if Remedy can send mail to port 25 on the Exchange > > server. > > > Some places have separate e-mail relay servers for sending e-mail (you > > > receive incoming e-mail using IMAP to the Exchange server, but send > > outgoing > > > mail to another SMTP server), but that is not an issue either. You just > > > would need to find out from you e-mail admins what SMTP server to use for > > > sending e-mail. > > > > > > > > > > > > I don't know if that's very helpful, but it really is fairly straight > > > forward (or at least, it should be). It's much more straightforward than > > > trying to get MAPI to work - at least in my experience. > > > > > > > > > > > > Lyle > > > > > > > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > > > arsl...@arslist.org] *On Behalf Of *Howard Richter > > > *Sent:* Friday, April 30, 2010 11:28 AM > > > > > > *To:* arslist@ARSLIST.ORG > > > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > > > > > > > > > ** > > > > > > Lyle, > > > > > > > > > > > > I am willing to try anything. Do you know of a FAQ on interfacing IMAP > > with > > > exchange for Remedy? > > > > > > > > > > > > Thanks > > > > > > > > > > > > Howard > > > > > > On Fri, Apr 30, 2010 at 12:29 PM, Lyle Taylor > > > wrote: > > > > > > ** > > > > > > Unless you have a real need for MAPI, I've had better luck using IMAP > > > instead. With that, there is no need to install a MAPI client. > > > > > > > > > > > > Lyle > > > > > > > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > > > arsl...@arslist.org] *On Behalf Of *LJ LongWing > > > *Sent:* Friday, April 30, 2010 9:26 AM > > > *To:* arslist@ARSLIST.ORG > > > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > > > > > > > > > ** > > > > > > Howard, > > > > > > Last time I checked, Microsoft was the main user/reason for existence of > > > MAP
Re: MAPI client other then Outlook for a win 2003 server
Angus, Thanks I am willing to try anything, since I do not have POP access. No additional client would be the best way to go, however, I did try IMAPI with no luck (the port might be locked down). Thanks to all, Howard On Sun, May 2, 2010 at 12:50 PM, ARSList wrote: > The original request was for a MAPI client. IMAPI is a totally different > thing. > > If you don't install Outlook then you can download a basic MAPI client from > the MS website - I believe this to be the case. I have never it myself. > > Angus > > > "Howard Richter" wrote in message news: > ... > Lyle, > > Thanks I will give it a try. > > On Fri, Apr 30, 2010 at 2:07 PM, Lyle Taylor > wrote: > > > ** > > > > No, but there's not much to it, IMAP is a standard mailbox protocol and > > supported by Exchange (I suppose so long as your administrators have > enabled > > it). Basically, you just configure the Mailbox in Remedy (for incoming > > mail) to use IMAP as the protocol, enter the username and password for > the > > account you want to monitor and associate it with the correct outgoing > > mailbox in Remedy. For outgoing mail, you generally just use standard > SMTP > > which Exchange also supports, entering your Exchange server as the SMTP > > server. You'll need to ask your Exchange admins if IMAP support is > enabled > > in Exchange and if Remedy can send mail to port 25 on the Exchange > server. > > Some places have separate e-mail relay servers for sending e-mail (you > > receive incoming e-mail using IMAP to the Exchange server, but send > outgoing > > mail to another SMTP server), but that is not an issue either. You just > > would need to find out from you e-mail admins what SMTP server to use for > > sending e-mail. > > > > > > > > I don't know if that's very helpful, but it really is fairly straight > > forward (or at least, it should be). It's much more straightforward than > > trying to get MAPI to work - at least in my experience. > > > > > > > > Lyle > > > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > > arsl...@arslist.org] *On Behalf Of *Howard Richter > > *Sent:* Friday, April 30, 2010 11:28 AM > > > > *To:* arslist@ARSLIST.ORG > > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > > > > > ** > > > > Lyle, > > > > > > > > I am willing to try anything. Do you know of a FAQ on interfacing IMAP > with > > exchange for Remedy? > > > > > > > > Thanks > > > > > > > > Howard > > > > On Fri, Apr 30, 2010 at 12:29 PM, Lyle Taylor > > wrote: > > > > ** > > > > Unless you have a real need for MAPI, I've had better luck using IMAP > > instead. With that, there is no need to install a MAPI client. > > > > > > > > Lyle > > > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > > arsl...@arslist.org] *On Behalf Of *LJ LongWing > > *Sent:* Friday, April 30, 2010 9:26 AM > > *To:* arslist@ARSLIST.ORG > > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > > > > > ** > > > > Howard, > > > > Last time I checked, Microsoft was the main user/reason for existence of > > MAPI, and as such I have never come across a client that does MAPI other > > than Microsoft clients.according to > > > > > > > > http://en.wikipedia.org/wiki/Messaging_Application_Programming_Interface > > > > > > > > Outlook express supports a limited version of MAPI..but Outlook is the > most > > common one I'm familiar with. > > > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > > arsl...@arslist.org] *On Behalf Of *Howard Richter > > *Sent:* Friday, April 30, 2010 8:47 AM > > *To:* arslist@ARSLIST.ORG > > *Subject:* MAPI client other then Outlook for a win 2003 server > > > > > > > > ** > > > > Good morning, afternoon and evening All, > > > > > > > > I am working with a an ARserver version 7.0.01 patch 5. What other > options > > do I have for a MAPI client (for a Win 2003 server) other then Outlook? > > > > > > > > As always thanks and take care, > > > > > > > > Howard > > > > -- > > Howard Richter > > Red Hat Certified Technician > > CompTIA Linux+ Certi
Re: MAPI client other then Outlook for a win 2003 server
The original request was for a MAPI client. IMAPI is a totally different thing. If you don't install Outlook then you can download a basic MAPI client from the MS website - I believe this to be the case. I have never it myself. Angus "Howard Richter" wrote in message news: ... Lyle, Thanks I will give it a try. On Fri, Apr 30, 2010 at 2:07 PM, Lyle Taylor wrote: > ** > > No, but there's not much to it, IMAP is a standard mailbox protocol and > supported by Exchange (I suppose so long as your administrators have enabled > it). Basically, you just configure the Mailbox in Remedy (for incoming > mail) to use IMAP as the protocol, enter the username and password for the > account you want to monitor and associate it with the correct outgoing > mailbox in Remedy. For outgoing mail, you generally just use standard SMTP > which Exchange also supports, entering your Exchange server as the SMTP > server. You'll need to ask your Exchange admins if IMAP support is enabled > in Exchange and if Remedy can send mail to port 25 on the Exchange server. > Some places have separate e-mail relay servers for sending e-mail (you > receive incoming e-mail using IMAP to the Exchange server, but send outgoing > mail to another SMTP server), but that is not an issue either. You just > would need to find out from you e-mail admins what SMTP server to use for > sending e-mail. > > > > I don't know if that's very helpful, but it really is fairly straight > forward (or at least, it should be). It's much more straightforward than > trying to get MAPI to work - at least in my experience. > > > > Lyle > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *Howard Richter > *Sent:* Friday, April 30, 2010 11:28 AM > > *To:* arslist@ARSLIST.ORG > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > ** > > Lyle, > > > > I am willing to try anything. Do you know of a FAQ on interfacing IMAP with > exchange for Remedy? > > > > Thanks > > > > Howard > > On Fri, Apr 30, 2010 at 12:29 PM, Lyle Taylor > wrote: > > ** > > Unless you have a real need for MAPI, I've had better luck using IMAP > instead. With that, there is no need to install a MAPI client. > > > > Lyle > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *LJ LongWing > *Sent:* Friday, April 30, 2010 9:26 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > ** > > Howard, > > Last time I checked, Microsoft was the main user/reason for existence of > MAPI, and as such I have never come across a client that does MAPI other > than Microsoft clients.according to > > > > http://en.wikipedia.org/wiki/Messaging_Application_Programming_Interface > > > > Outlook express supports a limited version of MAPI..but Outlook is the most > common one I'm familiar with. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *Howard Richter > *Sent:* Friday, April 30, 2010 8:47 AM > *To:* arslist@ARSLIST.ORG > *Subject:* MAPI client other then Outlook for a win 2003 server > > > > ** > > Good morning, afternoon and evening All, > > > > I am working with a an ARserver version 7.0.01 patch 5. What other options > do I have for a MAPI client (for a Win 2003 server) other then Outlook? > > > > As always thanks and take care, > > > > Howard > > -- > Howard Richter > Red Hat Certified Technician > CompTIA Linux+ Certified > ITIL Foundation Certified > E-Mail = hbr4...@gmail.com > LinkedIn Profile = http://www.linkedin.com/in/hbr4270 > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > NOTICE: This email message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy all > copies of the original message. > > > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > > -- > Howard Richter > Red Hat Certified Technician > CompTIA Linux+ Certified > ITIL Foundation Certified > E-Mail = hbr4...@gmail.com > LinkedIn Profile = http://w
Re: MAPI client other then Outlook for a win 2003 server
Lyle, Thanks I will give it a try. On Fri, Apr 30, 2010 at 2:07 PM, Lyle Taylor wrote: > ** > > No, but there’s not much to it, IMAP is a standard mailbox protocol and > supported by Exchange (I suppose so long as your administrators have enabled > it). Basically, you just configure the Mailbox in Remedy (for incoming > mail) to use IMAP as the protocol, enter the username and password for the > account you want to monitor and associate it with the correct outgoing > mailbox in Remedy. For outgoing mail, you generally just use standard SMTP > which Exchange also supports, entering your Exchange server as the SMTP > server. You’ll need to ask your Exchange admins if IMAP support is enabled > in Exchange and if Remedy can send mail to port 25 on the Exchange server. > Some places have separate e-mail relay servers for sending e-mail (you > receive incoming e-mail using IMAP to the Exchange server, but send outgoing > mail to another SMTP server), but that is not an issue either. You just > would need to find out from you e-mail admins what SMTP server to use for > sending e-mail. > > > > I don’t know if that’s very helpful, but it really is fairly straight > forward (or at least, it should be). It’s much more straightforward than > trying to get MAPI to work - at least in my experience… > > > > Lyle > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *Howard Richter > *Sent:* Friday, April 30, 2010 11:28 AM > > *To:* arslist@ARSLIST.ORG > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > ** > > Lyle, > > > > I am willing to try anything. Do you know of a FAQ on interfacing IMAP with > exchange for Remedy? > > > > Thanks > > > > Howard > > On Fri, Apr 30, 2010 at 12:29 PM, Lyle Taylor > wrote: > > ** > > Unless you have a real need for MAPI, I’ve had better luck using IMAP > instead. With that, there is no need to install a MAPI client. > > > > Lyle > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *LJ LongWing > *Sent:* Friday, April 30, 2010 9:26 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > ** > > Howard, > > Last time I checked, Microsoft was the main user/reason for existence of > MAPI, and as such I have never come across a client that does MAPI other > than Microsoft clients…according to > > > > http://en.wikipedia.org/wiki/Messaging_Application_Programming_Interface > > > > Outlook express supports a limited version of MAPI….but Outlook is the most > common one I’m familiar with. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *Howard Richter > *Sent:* Friday, April 30, 2010 8:47 AM > *To:* arslist@ARSLIST.ORG > *Subject:* MAPI client other then Outlook for a win 2003 server > > > > ** > > Good morning, afternoon and evening All, > > > > I am working with a an ARserver version 7.0.01 patch 5. What other options > do I have for a MAPI client (for a Win 2003 server) other then Outlook? > > > > As always thanks and take care, > > > > Howard > > -- > Howard Richter > Red Hat Certified Technician > CompTIA Linux+ Certified > ITIL Foundation Certified > E-Mail = hbr4...@gmail.com > LinkedIn Profile = http://www.linkedin.com/in/hbr4270 > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > NOTICE: This email message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy all > copies of the original message. > > > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > > -- > Howard Richter > Red Hat Certified Technician > CompTIA Linux+ Certified > ITIL Foundation Certified > E-Mail = hbr4...@gmail.com > LinkedIn Profile = http://www.linkedin.com/in/hbr4270 > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > -- Howard Richter Red Hat Certified Technician CompTIA Linux+ Certified ITIL Foundation Certified E-Mail = hbr4...@gmail.com LinkedIn Profile = http://www.linkedin.com/in/hbr4270 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
Re: MAPI client other then Outlook for a win 2003 server
No, but there's not much to it, IMAP is a standard mailbox protocol and supported by Exchange (I suppose so long as your administrators have enabled it). Basically, you just configure the Mailbox in Remedy (for incoming mail) to use IMAP as the protocol, enter the username and password for the account you want to monitor and associate it with the correct outgoing mailbox in Remedy. For outgoing mail, you generally just use standard SMTP which Exchange also supports, entering your Exchange server as the SMTP server. You'll need to ask your Exchange admins if IMAP support is enabled in Exchange and if Remedy can send mail to port 25 on the Exchange server. Some places have separate e-mail relay servers for sending e-mail (you receive incoming e-mail using IMAP to the Exchange server, but send outgoing mail to another SMTP server), but that is not an issue either. You just would need to find out from you e-mail admins what SMTP server to use for sending e-mail. I don't know if that's very helpful, but it really is fairly straight forward (or at least, it should be). It's much more straightforward than trying to get MAPI to work - at least in my experience... Lyle From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Howard Richter Sent: Friday, April 30, 2010 11:28 AM To: arslist@ARSLIST.ORG Subject: Re: MAPI client other then Outlook for a win 2003 server ** Lyle, I am willing to try anything. Do you know of a FAQ on interfacing IMAP with exchange for Remedy? Thanks Howard On Fri, Apr 30, 2010 at 12:29 PM, Lyle Taylor mailto:tayl...@ldschurch.org>> wrote: ** Unless you have a real need for MAPI, I've had better luck using IMAP instead. With that, there is no need to install a MAPI client. Lyle From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of LJ LongWing Sent: Friday, April 30, 2010 9:26 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: MAPI client other then Outlook for a win 2003 server ** Howard, Last time I checked, Microsoft was the main user/reason for existence of MAPI, and as such I have never come across a client that does MAPI other than Microsoft clients...according to http://en.wikipedia.org/wiki/Messaging_Application_Programming_Interface Outlook express supports a limited version of MAPIbut Outlook is the most common one I'm familiar with. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Howard Richter Sent: Friday, April 30, 2010 8:47 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: MAPI client other then Outlook for a win 2003 server ** Good morning, afternoon and evening All, I am working with a an ARserver version 7.0.01 patch 5. What other options do I have for a MAPI client (for a Win 2003 server) other then Outlook? As always thanks and take care, Howard -- Howard Richter Red Hat Certified Technician CompTIA Linux+ Certified ITIL Foundation Certified E-Mail = hbr4...@gmail.com<mailto:hbr4...@gmail.com> LinkedIn Profile = http://www.linkedin.com/in/hbr4270 _attend WWRUG10 www.wwrug.com<http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com<http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _attend WWRUG10 www.wwrug.com<http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ -- Howard Richter Red Hat Certified Technician CompTIA Linux+ Certified ITIL Foundation Certified E-Mail = hbr4...@gmail.com<mailto:hbr4...@gmail.com> LinkedIn Profile = http://www.linkedin.com/in/hbr4270 _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
Re: MAPI client other then Outlook for a win 2003 server
Lyle, I am willing to try anything. Do you know of a FAQ on interfacing IMAP with exchange for Remedy? Thanks Howard On Fri, Apr 30, 2010 at 12:29 PM, Lyle Taylor wrote: > ** > > Unless you have a real need for MAPI, I’ve had better luck using IMAP > instead. With that, there is no need to install a MAPI client. > > > > Lyle > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *LJ LongWing > *Sent:* Friday, April 30, 2010 9:26 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: MAPI client other then Outlook for a win 2003 server > > > > ** > > Howard, > > Last time I checked, Microsoft was the main user/reason for existence of > MAPI, and as such I have never come across a client that does MAPI other > than Microsoft clients…according to > > > > http://en.wikipedia.org/wiki/Messaging_Application_Programming_Interface > > > > Outlook express supports a limited version of MAPI….but Outlook is the most > common one I’m familiar with. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *Howard Richter > *Sent:* Friday, April 30, 2010 8:47 AM > *To:* arslist@ARSLIST.ORG > *Subject:* MAPI client other then Outlook for a win 2003 server > > > > ** > > Good morning, afternoon and evening All, > > > > I am working with a an ARserver version 7.0.01 patch 5. What other options > do I have for a MAPI client (for a Win 2003 server) other then Outlook? > > > > As always thanks and take care, > > > > Howard > > -- > Howard Richter > Red Hat Certified Technician > CompTIA Linux+ Certified > ITIL Foundation Certified > E-Mail = hbr4...@gmail.com > LinkedIn Profile = http://www.linkedin.com/in/hbr4270 > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > NOTICE: This email message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy all > copies of the original message. > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > -- Howard Richter Red Hat Certified Technician CompTIA Linux+ Certified ITIL Foundation Certified E-Mail = hbr4...@gmail.com LinkedIn Profile = http://www.linkedin.com/in/hbr4270 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
Re: MAPI client other then Outlook for a win 2003 server
Unless you have a real need for MAPI, I've had better luck using IMAP instead. With that, there is no need to install a MAPI client. Lyle From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ LongWing Sent: Friday, April 30, 2010 9:26 AM To: arslist@ARSLIST.ORG Subject: Re: MAPI client other then Outlook for a win 2003 server ** Howard, Last time I checked, Microsoft was the main user/reason for existence of MAPI, and as such I have never come across a client that does MAPI other than Microsoft clients...according to http://en.wikipedia.org/wiki/Messaging_Application_Programming_Interface Outlook express supports a limited version of MAPIbut Outlook is the most common one I'm familiar with. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Howard Richter Sent: Friday, April 30, 2010 8:47 AM To: arslist@ARSLIST.ORG Subject: MAPI client other then Outlook for a win 2003 server ** Good morning, afternoon and evening All, I am working with a an ARserver version 7.0.01 patch 5. What other options do I have for a MAPI client (for a Win 2003 server) other then Outlook? As always thanks and take care, Howard -- Howard Richter Red Hat Certified Technician CompTIA Linux+ Certified ITIL Foundation Certified E-Mail = hbr4...@gmail.com<mailto:hbr4...@gmail.com> LinkedIn Profile = http://www.linkedin.com/in/hbr4270 _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
Re: MAPI client other then Outlook for a win 2003 server
Howard, Last time I checked, Microsoft was the main user/reason for existence of MAPI, and as such I have never come across a client that does MAPI other than Microsoft clients.according to http://en.wikipedia.org/wiki/Messaging_Application_Programming_Interface Outlook express supports a limited version of MAPI..but Outlook is the most common one I'm familiar with. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Howard Richter Sent: Friday, April 30, 2010 8:47 AM To: arslist@ARSLIST.ORG Subject: MAPI client other then Outlook for a win 2003 server ** Good morning, afternoon and evening All, I am working with a an ARserver version 7.0.01 patch 5. What other options do I have for a MAPI client (for a Win 2003 server) other then Outlook? As always thanks and take care, Howard -- Howard Richter Red Hat Certified Technician CompTIA Linux+ Certified ITIL Foundation Certified E-Mail = hbr4...@gmail.com LinkedIn Profile = http://www.linkedin.com/in/hbr4270 _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
MAPI client other then Outlook for a win 2003 server
Good morning, afternoon and evening All, I am working with a an ARserver version 7.0.01 patch 5. What other options do I have for a MAPI client (for a Win 2003 server) other then Outlook? As always thanks and take care, Howard -- Howard Richter Red Hat Certified Technician CompTIA Linux+ Certified ITIL Foundation Certified E-Mail = hbr4...@gmail.com LinkedIn Profile = http://www.linkedin.com/in/hbr4270 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
