Re: Forwarding Not Working

On Thu, 06 Apr 2006 03:18:15 -0400, Steve Baker <bakesph@xxxxxxxxxxx>
wrote:

On Wed, 05 Apr 2006 23:13:25 -0500, Bob Simon <bsimon@xxxxxxxx> wrote:

I'm a novice but I wonder if your approach (trying to make an smtp
connection via telnet) is valid because the pop3 server requires an
ssl connection using port 995. Given this, would you expect a 450
busy message even if the server is operational?

Apples and oranges. The SMTP MX servers listen on port 25, that is the
standard all over the Internet. If you want to get email from the
Internet, you have an MX server listening on port 25, otherwise you don't
get any email. Sam found that the MX servers for ATT were "too busy" to
accept email. If that just happens every now and then it shouldn't be a
problem, but if that is an ongoing situation, sending servers could be
refused too many times and eventually give up on trying deliver email to
that outfit.
None of the above has anything to do with POP3. The normal sequence of
events would be for an MX server to accept email, and then have it put
into user mailboxes. Then, the users would use POP3 to check out the
email that had been put into their mailboxes. The standard POP3 port is
110, dunno if there is a standard POP3 SSL port, but that doesn't matter.
What matters is apples and oranges. SMTP and POP3 are apples and oranges.

Steve,
You're right, I did get SMTP and POP3 confused. Now that you've
straightened me out on that, let me try my question again:

Since the AT&T SMTP server requires that I set my Outlook client to
use authentication and an SSL connection on port 465, could that
explain why the server reported a 450 busy message to Sam's connection
attempt?

This server received and delivered to my account today's headlines
from NY Times, a daily newsletter, plus a half-dozen junk messages.
So even if it's overloaded, at least it's not down. On the other
hand, Outlook just popped up a window that said it could not connect
to my AT&T POP3 server, so there is at least some kind of intermittant
problem with their network or mail service.
Bob

--
Bob Simon
Please remove X from domain for direct replies.
.

Relevant Pages

  • RE: Exchange Problem
    ... successful at telnetting to the server on the SMTP port and the pop3 port. ... Outlook Express 6.00.2900.2869 ...
    (microsoft.public.windows.server.sbs)
  • Re: Some Questions
    ... remote pop3 which is hosted by Burst Data in Philadelphia. ... server from an outside connection. ... Logon to one of the client workstations in the SBS network. ... = e = Restart the Microsoft Connector for POP3 Mailboxes. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 sudden services problem over router based vpn
    ... I understand that your remote cannot receive POP3 emails through VPN ... SBS Server through routers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant send or receive e-mail to POP3 users on same domain--HELP!
    ... they are users who are all using the same Exchange ... "It can't seem to send messages to ANY POP3 ... thus do not use the Exchange server at all. ... you add the all individual user POP3 mailboxes into the POP3 Connector ...
    (microsoft.public.windows.server.sbs)
  • Re: Year 2038 issue...
    ... my msn pop3 account is over ten years old. ... forcing the user to utilize the IP's mail server. ... MSN expanded the ports list that can be used as alternates to port ...
    (microsoft.public.windowsxp.general)
Loading