> Am 2007-03-20 12:14:26, schrieb Matus UHLAR - fantomas:
> > the submission - still more often, because outgoing SMTP connections from
> > dynamic addresses (and often even static) are being blocked by ISPs in an
> > attempt to stop spam spreading from them.
On 04.04.07 20:21, Michelle Konzack wr
Hello *,
Am 2007-03-20 12:14:26, schrieb Matus UHLAR - fantomas:
> the submission - still more often, because outgoing SMTP connections from
> dynamic addresses (and often even static) are being blocked by ISPs in an
> attempt to stop spam spreading from them.
Since I am more or less mobile in a
> > On 18.03.07 14:13, Albert Dengg wrote:
> > > and everything that is for communication with the users can in
> > > prinziple run on any port you want, since you can tell then how to
> > > configure your clients, but there is no mechanism to tell other
> > > smtp servers "talk to me on port 666"
Matus UHLAR - fantomas wrote on Sunday, March 18, 2007 9:39 AM -0500:
> On 18.03.07 14:13, Albert Dengg wrote:
> > and everything that is for communication with the users can in
> > prinziple run on any port you want, since you can tell then how to
> > configure your clients, but there is no mecha
> > On Sun, Mar 18, 2007 at 02:13:08PM +0100, Albert Dengg wrote:
> >> to my knowlege, port 587 is for _authenticated_ message transmission,
> >> e.g. from your own users, not for server<->server.
> Roberto C. Sánchez wrote in Article
> <[EMAIL PROTECTED]> posted to
> gmane.linux.debian.user:
> >
Roberto C. Sánchez wrote in Article
<[EMAIL PROTECTED]> posted to
gmane.linux.debian.user:
> On Sun, Mar 18, 2007 at 02:13:08PM +0100, Albert Dengg wrote:
>> to my knowlege, port 587 is for _authenticated_ message transmission,
>> e.g. from your own users, not for server<->server.
>>
> Actually,
On Sun, Mar 18, 2007 at 02:13:08PM +0100, Albert Dengg wrote:
> to my knowlege, port 587 is for _authenticated_ message transmission,
> e.g. from your own users, not for server<->server.
>
Actually, 587 us the submission port. It has nothing to do with
authentication. Basically, the RFCs are wri
> > On 16.03.07 09:13, Easthope wrote:
> > > I am trying to understand how SMTP uses ports.
> > > Ultimately I want it to work through a SSH tunnel.
> > >
> > > Normally SMTP uses port 25 but in some cases it uses 1025.
> On Sat, Mar 17, 2007 at 10:40:12PM +0100, Matus UHLAR - fantomas wrote:
> >
On Sat, Mar 17, 2007 at 10:40:12PM +0100, Matus UHLAR - fantomas wrote:
> On 16.03.07 09:13, Easthope wrote:
> > I am trying to understand how SMTP uses ports.
> > Ultimately I want it to work through a SSH tunnel.
> >
> > Normally SMTP uses port 25 but in some cases it uses 1025.
>
> in what cas
On 16.03.07 09:13, Easthope wrote:
> I am trying to understand how SMTP uses ports.
> Ultimately I want it to work through a SSH tunnel.
>
> Normally SMTP uses port 25 but in some cases it uses 1025.
in what cases? there is port 587 designed and reserved for message
submission via SMTP.
> Accord
On Fri, Mar 16, 2007 at 09:13:12AM -0700, Easthope wrote:
> Normally SMTP uses port 25 but in some cases it uses
> 1025. According to
> http://www.iana.org/assignments/port-numbers
> 1025 is assigned to blackjack! (blackjack?) So what
> is SMTP doing with it?
I've never seen SMTP use 1025.
2007/3/16, Easthope <[EMAIL PROTECTED]>:
Debian Users,
I am trying to understand how SMTP uses ports.
Ultimately I want it to work through a SSH tunnel.
Normally SMTP uses port 25 but in some cases it uses
1025.
25 is the default (ie. the one that all computers in the Internet will
attempt to
12 matches
Mail list logo
