Re: Fire the moron who came up with 553 sorry, that domain isn't in my
From: Vanguardx (see_signature)
Date: 09/17/04
- Next message: spo kuptoj: "Re: registry problem"
- Previous message: Steve S: "Re: Outlook Shutdown"
- In reply to: sscjeff: "Fire the moron who came up with 553 sorry, that domain isn't in my"
- Next in thread: sscjeff: "Re: Fire the moron who came up with 553 sorry, that domain isn't i"
- Reply: sscjeff: "Re: Fire the moron who came up with 553 sorry, that domain isn't i"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 17 Sep 2004 07:16:24 -0500
"sscjeff" <sscjeff@discussions.microsoft.com>
wrote in news:8742A506-9D36-4107-9425-9D496FD8E0FB@microsoft.com:
> For no apparent reason my Outlok 2003 will just decide not to send my
> email and I need it like I need another spoof or virus. There seems
> to be no one on the planet that knows what this is or where it comes
> from:
> "Your message did not reach some or all of the intended recipients.
>
> Subject: Meet Comp?
> Sent: 9/16/2004 7:42 AM
>
> The following recipient(s) could not be reached:
>
> name@sea.samsung.com on 9/16/2004 7:42 AM
> 553 sorry, that domain isn't in my list of allowed
> rcpthosts (#5.7.1)"
Are you using the SMTP server for the domain to which you connect to the
Internet? That is, when you connect to a network, like your ISP
(Internet Service Provider), are you using *their* SMTP server, or are
you trying to use an SMTP server that is somewhere else and off their
network? Are you connecting to network-A but trying to use network-B's
SMTP server?
The network to which you are connecting may ban SMTP traffic originating
on their network from going off their network to use an SMTP server
somewhere else. That is, they block any SMTP traffic (port 25) that
does not use their SMTP on that same network. This is to reduce
spamming by letting the user abuse network-A to hide that is the home
domain of the spammer by abusing a mail server or open relay on
network-B. Also, some networks will not accept SMTP traffic that
originates from off their network. This is the reduce spamming by
preventing someone from somewhere else from abusing their mail server;
i.e., network-B won't allow use of their SMTP server by some unknown
coming from network-A. Network-B doesn't know who the hell is the user
coming from network-A because the user authenticated to network-A to get
Internet access and never authenticated to network-B to ensure that user
has rights to access network-B's resources.
Solutions:
- Use the SMTP server provided by the network to which you connect
(i.e., use your ISP's SMTP server). That's the one you have rights to
use because you have authenticated to that network and have an account
with THAT network to use their resources.
- Authenticate to the SMTP server if connecting to it from off its
domain. You should be able to reuse the same username and password for
the SMTP authentication as you specified for the POP3 connection. If
you are trying to use an off-domain SMTP server, this only works if the
source network permits outbound off-domain SMTP traffic (i.e., lets it
go out of their network) and the target network permits inbound
off-domain SMTP traffic via authentication (i.e., lets it come in from
off their network).
Yes, spammers are morons. They caused the problem and the resultant
reaction to limit the misuse of SMTP.
-- _________________________________________________________________ ******** Post replies to newsgroup - Share with others ******** Email: lh_811newsATyahooDOTcom and append "=NEWS=" to Subject. _________________________________________________________________
- Next message: spo kuptoj: "Re: registry problem"
- Previous message: Steve S: "Re: Outlook Shutdown"
- In reply to: sscjeff: "Fire the moron who came up with 553 sorry, that domain isn't in my"
- Next in thread: sscjeff: "Re: Fire the moron who came up with 553 sorry, that domain isn't i"
- Reply: sscjeff: "Re: Fire the moron who came up with 553 sorry, that domain isn't i"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|