james-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens B <jens.bengts...@gmail.com>
Subject Re: Using James to "proxy" a work server
Date Tue, 18 Jun 2013 09:46:11 GMT
Thanks for the input, but I can't see that fetchmail is able to fetch via

On Tue, Jun 18, 2013 at 11:44 AM, Shrivallabh Jagdish Deshmukh <
shrivallabhd@ivycomptech.com> wrote:

> A simpler solution would be to use fetchmail or any such tools with a Cron
> job.
> Using James might turn out to be an overkill IMHO.
> -----Original Message-----
> From: Jens B [mailto:jens.bengtsson@gmail.com]
> Sent: 18 June 2013 15:09
> To: general@james.apache.org
> Subject: Using James to "proxy" a work server
> Hi,
> I'm hoping this list is the right place to ask.
> I am looking to "proxy" my Exchange mail to Gmail to be able to use the
> Mailbox app - I am aware that this possibly violates IT policies, so this
> is a technical question, not a why and don't do it one ;)
> So, I have a Exchange server that can be accessed remotely on mobile
> devices (assuming via ActiveSynch, it's the Exchange option on the iOS).
> I want all mail from this server to end up in my gmail account, but
> forwarding is not enabled server side.
> What I wanted to do is to set up a proxy email server that fetches mail
> using the mobile protocol from the Exchange server, then allowing gmail to
> pull that mail with POP3.
> Would James be the right "proxy" for this? I have researched this a bit,
> and it looks to me like I would need to be able to fetch mail with POP3 for
> James to support this, which I can't.
> Any thoughts or pointers would be very appreciated.
> thanks,
> Jens
> This email and any attachments are confidential, and may be legally
> privileged and protected by copyright. If you are not the intended
> recipient dissemination or copying of this email is prohibited. If you have
> received this in error, please notify the sender by replying by email and
> then delete the email completely from your system. Any views or opinions
> are solely those of the sender. This communication is not intended to form
> a binding contract unless expressly indicated to the contrary and properly
> authorised. Any actions taken on the basis of this email are at the
> recipient's own risk.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message