[JDEV] "smtp transport" -- does that mean

Darrell Berry darrell at ku24.com
Wed Dec 4 04:13:52 CST 2002


The problem with that is if you have a circuit-level firewall/proxy
which actually checks that the traffic is actually following the mail
protocols (hence the question) -- many firewalls do the same thing on
port 80 -- i.e. if its not a valid http transaction, it doesn't get
thru...

-----Original Message-----
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org] On Behalf Of
Mike Mintz
Sent: 04 December 2002 01:26
To: jdev at jabber.org
Subject: Re: [JDEV] "smtp transport" -- does that mean

I don't see the point of B, when there already exists a similar concept
over 
HTTP port 80.  And even if port 80 was blocked, but 25 was open, it
would be 
more efficient to just connect over 25, use proper SMTP to identify as a

Jabber client, like with the HELO command, and then just pretend the 
connection is a Jabber connection from that point on to make things
simpler.




More information about the JDev mailing list