port 587

[Alain Spineux]

On Thu, Mar 20, 2008 at 1:45 PM, Tobias Oed <tobias.oed at octant-fr.com> wrote:
> Hello,
>  some of my users are having problems reaching my server through port 25
>  because their isp blocks that port. I tell them to use ssl and port 465
>  and things work. I was wondering why kolab wasn't listening on port 587

Nobody know about port 587, nobody use it !

Port 587 must be able to do the same job as port 25, their is no difference
between sending or receiving and email when you send an email to
yourself on your own server!
Then why have 2 ports ?
When someone came with port 587 long time ago, SPAM was "unknown" and
openrelay was "the rules".
Today the rules must be strict and the same for "sending" and receiving.
Also 465 is smtpS with a for Secure or SSL and must force the use of
authentication.

Regards.



Because of spam

>  (mail message submission) with tls enabled. Is this just an oversight or
>  is there a deeper reason?
>  Cheers
>  Tobias Oed
>
>  --
>  *Tobias Oed* - Octant Informatique <http://www.octant-fr.com>
>  contact | tobias.oed at octant-fr.com <mailto:tobias.oed at octant-fr.com> -
>  04 76 50 82 38
>  image
>
>  _______________________________________________
>  Kolab-users mailing list
>  Kolab-users at kolab.org
>  https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you