Re: Forwarding email ports

2007-02-05 Thread Michael_google gmail_Gersten
SMTP inside TOR has so many little issues it makes my brain hurt. Then let me ask a little question: I've been running this for about half a day now, I figure the directory servers have properly propagated the open port information, can anyone at least actually use this to send encrypted email?

Re: Forwarding email ports

2007-02-05 Thread Michael Holstein
Port 465 doesn't have this problem though as the entire conversation is encrypted. Assuming the client doesn't accept a bad certificate and leave themselves open to a MITM attack. Who among us actually pays Verisign (et.al.) for a SSL cert for their personal MTA? Besides .. in an anonymous

Re: Forwarding email ports

2007-02-05 Thread Mike Cardwell
* on the Mon, Feb 05, 2007 at 09:45:20AM -0800, Michael_google gmail_Gersten wrote: >> Nope .. 587 is an alternative to 25. Unlike the other two, it's not >> encrypted. > Whoops! I've taken that one off my list of ports then. I'm not sure what was suggested is actually correct. Port 25 is for SM

Re: Forwarding email ports

2007-02-05 Thread Michael_google gmail_Gersten
Nope .. 587 is an alternative to 25. Unlike the other two, it's not encrypted. Whoops! I've taken that one off my list of ports then. As for blocking IP, I'm dynamic :-).

Re: Forwarding email ports

2007-02-05 Thread Michael Holstein
(responses inline) : I read through the january archives on email ports, specifically 465, 587, and 995. First, are these the ports needed to support standard secure email (SMTP and PoP)? Except for tcp/587 (submission), yes. 465 is smtps (smtp via SSL) and 995 is pops (pop via SSL). tcp/587

Re: Forwarding email ports

2007-02-04 Thread Michael_google gmail_Gersten
Alright, can someone test and see if I have this set up right? All four ports should now be accepted by "stbmac".

Re: Forwarding email ports

2007-02-04 Thread Dan Mahoney, System Admin
On Sun, 4 Feb 2007, Michael_google gmail_Gersten wrote: I read through the january archives on email ports, specifically 465, 587, and 995. First, are these the ports needed to support standard secure email (SMTP and PoP)? 465 is smtp-over-ssl (auth typically required -- ssl being part of the

Re: Forwarding email ports

2007-02-04 Thread Ringo Kamens
1. The same argument could be used "if I'm an exit server that redirects any traffic" so you shouldn't worry. 2. If you are an open relay, yes (if you run your own mail server). If you are not one, probably not. 3. Just as likely without email enabled 3. Just as likely without email enabled. Ringo

Forwarding email ports

2007-02-04 Thread Michael_google gmail_Gersten
I read through the january archives on email ports, specifically 465, 587, and 995. First, are these the ports needed to support standard secure email (SMTP and PoP)? Second, why were there three of them for two protocols? Did I misunderstand something? Third, what are the implications -- both