Re: Forwarding Not Working
- From: Steve Baker <bakesph@xxxxxxxxxxx>
- Date: Thu, 06 Apr 2006 03:18:15 -0400
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 Baker
.
- Follow-Ups:
- Re: Forwarding Not Working
- From: Bob Simon
- Re: Forwarding Not Working
- References:
- Forwarding Not Working
- From: bobneworleans@xxxxxxxxx
- Re: Forwarding Not Working
- From: Sam
- Re: Forwarding Not Working
- From: Bob Simon
- Forwarding Not Working
- Prev by Date: Re: Database email storing ...
- Next by Date: C++ library for MIME
- Previous by thread: Re: Forwarding Not Working
- Next by thread: Re: Forwarding Not Working
- Index(es):
Relevant Pages
|