I have been using seamonkey on suse 10.3 and 11.0, , on comcast for 2
years, no problem sending mail. Now I can't send mail.
Comcast was no help, as usual. I checked google and the problem was
that comcast does'nt use port 25 for smtp.comcast.net server,
they use port 587, So I changed the port from 25 to 587 folowing
instructions on internet.
Called comcast again, still can't send mail, they don't support seamonkey.
Comcast said they do this to protect me from viruses.
They want me to use Outlook and Internet Explorer,
I say thats where all the viruses are received, thats why
I use seamonkey or thunderbird in linux. Still no help.
They don't support linux.
I put my problem on comcast & seamonkey newsgroups but
the users there are micro$oft brainwashed.
I can use seamonkey in win XP to send mail.
Comcast did something to prevent linux users from using seamonkey or
thunderbird.
Perhaps someone at opensuse can help.

jozien

On Tue, 01 Jul 2008, in the Usenet newsgroup alt.os.linux.suse, in article
<YaGdncF8fejjXffVnZ2dnUVZ_gadnZ2d@comcast.com>, Joe Zien wrote:

>I have been using seamonkey on suse 10.3 and 11.0, , on comcast for 2
>years, no problem sending mail. Now I can't send mail.

And the error message is...

>Comcast was no help, as usual. I checked google and the problem was
>that comcast does'nt use port 25 for smtp.comcast.net server,
>they use port 587, So I changed the port from 25 to 587 folowing
>instructions on internet.

And the error message is...

>I can use seamonkey in win XP to send mail.
>Comcast did something to prevent linux users from using seamonkey or
>thunderbird.

And the difference in the configurations between the two are...

You've probably run into an authentication issue in addition to the
port change. Fire up a packet sniffer like tcpdump, ethereal, or
wireshark - and verify that your browser is trying to send to port 587
on the "correct" mail relay. You may also see it requiring authentication
in addition to your being on a comcast IP address, so verify that you've
set you Linux version the same as the xp version.

Old guy

Moe Trin wrote:
>>Comcast was no help, as usual. I checked google and the problem was
>>that comcast does'nt use port 25 for smtp.comcast.net server,
>>they use port 587, So I changed the port from 25 to 587 folowing
>>instructions on internet.
<snip>
> You've probably run into an authentication issue in addition to the
> port change.

Most likely, because 587 is SMTP with user autentification.


houghi
--
It's people. Source code is made out of people! They're making our
source out of people. Next thing they'll be breeding us like cattle
for code. You've gotta tell them. You've gotta tell them!

houghi wrote:
> Moe Trin wrote:
>>> Comcast was no help, as usual. I checked google and the problem was
>>> that comcast does'nt use port 25 for smtp.comcast.net server,
>>> they use port 587, So I changed the port from 25 to 587 folowing
>>> instructions on internet.
> <snip>
>> You've probably run into an authentication issue in addition to the
>> port change.
>
> Most likely, because 587 is SMTP with user autentification.

It's SMTP with SSL. You can have user authentication even with normal
SMTP on port 25. And you can have SMTP without user authentication on
SSL port 587.

Nikos Chantziaras wrote:
>> Most likely, because 587 is SMTP with user autentification.
>
> It's SMTP with SSL. You can have user authentication even with normal
> SMTP on port 25. And you can have SMTP without user authentication on
> SSL port 587.

OK. I was not specific enough. It is with autentification because port
25 is not used.
Some servers are set up to reject all relaying on port 25, but valid
users authenticating on port 587 are allowed to relay mail to any valid
address.
from http://en.wikipedia.org/wiki/Simple_...nsfer_Protocol

houghi
--
Quote correct (NL) http://www.briachons.org/art/quote/
Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren
Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html

On Thu, 3 Jul 2008, in the Usenet newsgroup alt.os.linux.suse, in article
<slrng6oqhk.hk1.houghi@penne.houghi>, houghi wrote:

>Nikos Chantziaras wrote:

>>> Most likely, because 587 is SMTP with user autentification.

No. http://www.iana.org/assignments/port-numbers

>> It's SMTP with SSL. You can have user authentication even with
>> normal SMTP on port 25. And you can have SMTP without user
>> authentication on SSL port 587.

No.

>OK. I was not specific enough. It is with autentification because
>port 25 is not used.

No.

>Some servers are set up to reject all relaying on port 25, but valid
>users authenticating on port 587 are allowed to relay mail to any
>valid address.
>from http://en.wikipedia.org/wiki/Simple_...nsfer_Protocol

Rather than the wankypedia, why not read the source (RFC4409)?

4409 Message Submission for Mail. R. Gellens, J. Klensin. April 2006.
(Format: TXT=34911 bytes) (Obsoletes RFC2476) (Status: DRAFT
STANDARD)

The earlier document (RFC2476) is referenced in passing in RFC2821.

Old guy

Moe Trin wrote:
>>from http://en.wikipedia.org/wiki/Simple_...nsfer_Protocol
>
> Rather than the wankypedia, why not read the source (RFC4409)?

OK, so I asume you have taken the time to correct it on that source or
is it bether to just moan about it?

houghi
--



This space left blank intentionaly

On Fri, 4 Jul 2008, in the Usenet newsgroup alt.os.linux.suse, in article
<slrng6rlat.djm.houghi@penne.houghi>, houghi wrote:

>Moe Trin wrote:

>>>from http://en.wikipedia.org/wiki/Simple_...nsfer_Protocol
>>
>> Rather than the wankypedia, why not read the source (RFC4409)?
>
>OK, so I asume you have taken the time to correct it on that source or
>is it bether to just moan about it?

If you feel you must use wankypedia, use it as a tool to find answers,
rather than assuming the material it provides is correct in any way.
I've long ago given up wasting time trying to correct misconceptions,
and errors of anonymously posted "information" there, but the references
it may include might lead you to the factual material - such as the
above mentioned RFC, which you could have found looking at the IANA
port list document http://www.iana.org/assignments/port-numbers

submission 587/tcp Submission
submission 587/udp Submission
# [RFC4409]

Old guy