> testing
Looks like a success.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum
I have news.aioe.org working as a news source, but can't
determine how to configure the server for postings.
smtp.sf.sbcglobal (port 25) is what I'm using now.
I'm using SeaMonkey if that matters.
<snip>
>> I have news.aioe.org working as a news source, but can't
>> determine how to configure the server for postings.
>>
>> smtp.sf.sbcglobal (port 25) is what I'm using now.
> smtp.sf.sbcglobal.net
>>
>> I'm using SeaMonkey if that matters.
Eh? What is 'smtp.sf.sbcglobal.net'? It does not work for me:
| C:\utils\ns_bench>telnet smtp.sf.sbcglobal.net 25
| Connecting To smtp.sf.sbcglobal.net...Could not open connection to the host, on
| port 25: Connect failed
|
| C:\utils\ns_bench>nslookup smtp.sf.sbcglobal.net
| Server: dnsr1.sbcglobal.net
| Address: 68.94.156.1
|
| *** dnsr1.sbcglobal.net can't find smtp.sf.sbcglobal.net: Non-existent domain
No connection possible to a non-existent host!
smtp.sf.sbcglobal.net is the default network setting for SeaMonkey.
Thunderbird is using smtp.att.yahoo.com Port 563 with secure connection.
> NormanM wrote:
>> <snip>
The only valid SMTP servers that I know of do not have '.sf.' in the name:
'smtpauth.flash.net'
'smtpauth.prodigy.net'
'smtpauth.sbcglobal.net'
'smtp.sbcglobal.net'
'mail.nvbell.net'
'mail.pacbell.net'
'mail.swbell.net'
Attempting 'nslookp' on 'smtp.sf.sbcglobl.net' returns NXDOMAIN
("non-existent domain"), and connection to a non-existent domain is not
possible on any port.
The only server using '.sf.sbcglobal.net' that I know of is the news (NNTP)
server: 'news.sf.sbcglobal.net'. Accessible on port 119 (NNTP port), but not
on port 25 (SMTP port); and going away on, or about, 15 July 2009.
> Thunderbird is using smtp.att.yahoo.com Port 563 with secure connection.
That is also not possible, considering that 'smtp.att.yahoo.com' is an SMTP
server, and should be accessed using an SMTP client on port 465. How do you
access that server as an NNTP server (secure NNTP port 563)?
Something is not right with your configurations, or your understanding of
the client, or of the services offered (maybe even all of the above)!