[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sylpheed
Subject:    [sylpheed:27749] Re: Strange: Sylpheed cannot send mails
From:       Frank Fabian <frfabian () gmx ! de>
Date:       2006-03-26 16:59:23
Message-ID: 20060326185923.ba341dc4.frfabian () gmx ! de
[Download RAW message or body]

Hello Henryk,

Am Sun, 26 Mar 2006 18:45:35 +0200
schrieben Sie (Henryk Plötz <henryk@ploetzli.ch>):

> Moin,
> 
> Am Sun, 26 Mar 2006 18:23:58 +0200 schrieb Stefaan A Eeckels:
> 
> > Your KMail connection uses port 465 (secure SMTP) not 25.
> 
> Ok, then it's clear: Frank is (probably?) using T-Online which has
> been blocking port 25 outgoing for quite some time. Instead,
> customers are supposed to use T-Online's own SMTP server (which will
> overwrite the From: address with the address of the owner of the
> current dial-in connection) or use a special relay (for some extra
> money). Note: That's all strictly "If I Recall Correctly", but a
> quick Google brings this up:
> http://www.teltarif.de/arch/2003/kw04/s9712.html
> http://service.t-online.de/c/00/01/35/1350.html (sorry, German only
> because it's a German only problem).
> 
> Simplest solution, as already indicated: Switch to 'STMP over SSL' to
> bypass all that packet filtering nonsense. Luckily GMX supports this,
> so the problem should be solved by enabling SSL (not STARTTLS) in the
> account-settings. Nice by-product: No more outgoing cleartext emails
> (Germany currently has a slight problem with overzealous
> pro-data-retention people).
> 
> You are also strongly encouraged to enable POP3 over SSL, GMX supports
> this too.

sounds interesting, and my DSL connection is indeed by T-Online. But until Monday, it worked without \
problems without using SSL. So T-Online, according to your theory, must have started to block port 25 \
after that? Anyway, I enabled SSL for both SMTP and POP3, so I shouldn't have any more problems.

Regards

Frank


[prev in list] [next in list] [prev in thread] [next in thread]