View Full Version : Can Untangle scan gmail accounts?
MoreDakka
10-30-2007, 09:01 PM
I would think this would be a hard thing to scan as it's connection is on port 995 through ssl but it would be nice to see scanning on that as well.
Thanks.
Just my personal opinion here, but I use all the webmail clients to avoid using my hardware ... server software ... client software ... anti-virus ... anti-phishing ... maintenance time. Not to mention that if the poop hits the fan, its their fan and their poop! It seems like Hotmail and Yahoo are useless for checking spam but Gmail seems to do a pretty good job. I guess Gmail doesn't have anything they want you to buy to get better performance.:eek:
hescominsoon
10-31-2007, 06:19 AM
Just my personal opinion here, but I use all the webmail clients to avoid using my hardware ... server software ... client software ... anti-virus ... anti-phishing ... maintenance time. Not to mention that if the poop hits the fan, its their fan and their poop! It seems like Hotmail and Yahoo are useless for checking spam but Gmail seems to do a pretty good job. I guess Gmail doesn't have anything they want you to buy to get better performance.:eek:
the only way it could scan gmail is if it conducted a man in the middle attack like scenario. Copfilter does this(since gmail uses ssl) but i'm not sure if untangle does.
juank
10-31-2007, 07:53 AM
In theory, YES, you can.
As you may know, you can get your GMAIL mail via IMAP, which Untangle will scan for you.
gotkimchi
10-31-2007, 10:43 AM
I have personally tested the gmail scanning. The Untangle can only mark or pass the gmail traffic.
juank
10-31-2007, 11:13 AM
Yes, that's the only "thing"... Untangle can only quarantine SMTP traffic.
Spiral
05-01-2008, 03:26 PM
- added pop3 ssl support, configure your email client to check for email on port 995 without SSL !
since you are doing normal pop3 on port 995, p3scan will know that you want a ssl pop3 session and
will then open poo3-ssl session to your mail server
So basically, this means:
1) user connects to p3scan over "secure" LAN to p3scan port 995 instead
of 110 (redirected), but uses plain pop3
2) p3scan notices the connection is intended to be pop3s (because the
user connects to p3scan on port 995) - and connects to the destination
pop3s server over insecure internet using secure SSL/995/pop3s
3) any pop3s server certificate has to be accepted by p3scan, as there
is no possibility to let user check it and accept it (or not)
4) p3scan downloads the messages from the pop3s server, decrypts them,
and sends unencrypted to the users mail client