views:

217

answers:

3

Neither poplib or imaplib seem to offer proxy support and I couldn't find much info about it despite my google-fu attempts.

I'm using python to fetch emails from various imap/pop enabled servers and need to be able to do it through proxies.

Ideally, I'd like to be able to do it in python directly but using a wrapper (external program/script, OSX based) to force all traffic to go through the proxy might be enough if I can't find anything better.

Could anyone give me a hand? I can't imagine I'm the only one who ever needed to fetch emails through a proxy in python...

** EDIT Title edit to remove HTTP, because I shouldn't type so fast when I'm tired, sorry for that guys **

The proxies I'm planning to use allow socks in addition to http.

Pop or Imap work through http wouldn't make much sense (stateful vs stateless) but my understanding is that socks would allow me to do what I want.

So far the only way to achieve what I want seems to be dirty hacking of imaplib... would rather avoid it if I can.

A: 

If I understand you correctly you're trying to put a square peg in a round hole.

An HTTP Proxy only knows how to "talk" HTTP so can't connect to a POP or IMAP server directly.

If you want to do this you'll need to implement your own server somewhere to talk to the mail servers. It would receive HTTP Requests and then make the appropriate calls to the Mail Server. E.g.:

How practical this would be I don't know since you'd have to convert a stateful protocol into a stateless one.

Dave Webb
You're 100% right, I forgot to mention socks capability. I removed HTTP from the title, sorry for that, I'm tired ;p
Vermillon
The 'CONNECT' method of an HTTP proxy would let you run any tcp client->server protocol. *IF* the HTTP proxy allows it, most default configurations restrict 'CONNECT' requests to port 443.
MattH
+2  A: 

You don't need to dirtily hack imaplib. You could try using the SocksiPy package, which supports socks4, socks5 and http proxy (connect):

Something like this, obviously you'd want to handle the setproxy options better, via extra arguments to a custom __init__ method, etc. You could probably do similar with the IMAP4_SSL.

from imaplib import IMAP4, IMAP4_PORT
from socks import sockssocket, PROXY_TYPE_SOCKS4, PROXY_TYPE_SOCKS5, PROXY_TYPE_HTTP

class SocksIMAP4(IMAP4):
    def open(self,host,port=IMAP4_PORT):
        self.host = host
        self.port = port
        self.sock = sockssocket()
        self.sock.setproxy(PROXY_TYPE_SOCKS5,'socks.example.com')
        self.sock.connect((host,port))
        self.file = self.sock.makefile('rb')
MattH
Nice find MattH, that's exactly the kind of thing I was looking for (didn't know SocksiPy). I'll give it a go. Thanks.
Vermillon
A: 

Answer to my own question... There's a quick and dirty way to force trafic from a python script to go through a proxy without hassle using Socksipy (thanks MattH for pointing me that way)

import socks
import socket
socks.setdefaultproxy(socks.PROXY_TYPE_SOCKS4,proxy_ip,port,True)
socket.socket = socks.socksocket

That global socket override is obviously a bit brutal, but works as a quick fix till I find the time to properly subclass IMAP4 and IMAP4_SSL.

Vermillon