Issue 2550770
Created on 2012-08-16 06:55 by vaibhavagg, last changed 2016-04-09 03:17 by rouilj.
Messages | |||
---|---|---|---|
msg4608 | Author: [hidden] (vaibhavagg) | Date: 2012-08-16 06:55 | |
Hi roundup experts, I have problem in connection roundup mailgw with microsoft mailexchane using rpc(remote procedure call) i cannot use imaps as it is blocked by my company.Please provide any solutions to this.Do we have any python scripts or something else to connect it. Any help will be appreciated thanks |
|||
msg4609 | Author: [hidden] (ber) | Date: 2012-08-16 07:07 | |
Hi Vaibhav, thanks for trying roundup. Can you give us more insight in your issue? Is is more a support request for your specific situation or a feature request? Just asking, because for support request, the -users list of roundup usally gives you the fastest and best results, because most users read there. I also would be interested to know which of the two ways of email you are concerned about: a) roundup -> outgoing b) incoming -> roundup And which platform your are running roundup on. So if you ask on the -users list you should include this info. |
|||
msg4610 | Author: [hidden] (rouilj) | Date: 2012-08-17 01:44 | |
If you have OWA available perhaps: http://code.google.com/p/weboutlook/ could work? Also what OS are you running roundup on? If you are on windows and have outlook available I think there is a COM interface to MAPI that may be usable. Google for python and these these terms. There are a ton of hits. In theory it should be possible to send and retrieve email this way, but AFAIK nobody has done the development to make this work with roundup. Also given that it's proprietary and poorly documented and keeps changing with different exchange versions, it's a hard way to do it. If you are running on linux, have the exchange people forward the email though the exchange server to your internal server and handle the mail there. |
|||
msg4615 | Author: [hidden] (vaibhavagg) | Date: 2012-08-21 10:46 | |
Thanks Bernhard Reiter (ber) for looking into my issue. I am using roundup on windows os.My problem is that i want to process the mails in my inbox and update the issues.I was using roundup-mailgw for this.But imaps,pop are disabled now by my adminstrator and i need to use RPC to connect to mail exchange 2010. i need for incoming-> roundup People send mails to roundup mail id to create new issue or update existing issue. So i need some python script which can solve purpose of roundup-mailgw but uses RPC instead of imaps or any other alternative |
|||
msg4619 | Author: [hidden] (ber) | Date: 2012-08-21 13:32 | |
Hi Vaibhav, could your Exchange admin add another delivery route for your email address to your exchange? Usually a smpt route should work, and then you would only need to run a small MTA on your side. Of course this depends on if your machine is running all the time. |
|||
msg4766 | Author: [hidden] (vaibhavagg) | Date: 2013-01-22 08:25 | |
Hi Bernhard, Mail admin is not ready to do anything for this. Everything I have to do myself. Is there any way that roundup can pick messages from my local machine somehow. I can save the messages to my local mail client (not owa). Appreciate your help |
|||
msg4767 | Author: [hidden] (ber) | Date: 2013-01-22 14:40 | |
Hi Vaibhav, yes, if you manage that emails get saved on your file system somehow, then you could use a periodic script to push them into roundup. So check into how to run a script periodically (if you don't find something looke for "cron" utilities, "cron" is the GNU/Linux name for it.) And then make it pipe each email into roundup-mailgw, every few minutes or so. Best, Bernhard |
|||
msg5502 | Author: [hidden] (rouilj) | Date: 2016-04-09 03:17 | |
Closing due to inactivity. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2016-04-09 03:17:37 | rouilj | set | status: new -> closed messages: + msg5502 |
2013-01-22 14:40:17 | ber | set | messages: + msg4767 |
2013-01-22 08:25:26 | vaibhavagg | set | messages: + msg4766 |
2012-08-21 13:32:42 | ber | set | messages: + msg4619 |
2012-08-21 10:46:35 | vaibhavagg | set | messages: + msg4615 |
2012-08-17 01:44:38 | rouilj | set | nosy:
+ rouilj messages: + msg4610 |
2012-08-16 07:07:17 | ber | set | nosy:
+ ber messages: + msg4609 severity: critical -> urgent |
2012-08-16 06:55:54 | vaibhavagg | create |