faqts : Computers : Internet : Mail Servers : qmail : Common Problems

+ Search
Add Entry AlertManage Folder Edit Entry Add page to http://del.icio.us/
Did You Find This Entry Useful?

72 of 177 people (41%) answered Yes
Recently 7 of 10 people (70%) answered Yes

Entry

i am facing problem when i send a mail from outlook express it says "553 ,sorry that domain isn't in my list of rcphosts(#5.7.1)"

Dec 3rd, 2003 13:47
Kevin S., Brian Coogan, vikas k, nitin jain,


While the answers below are helpful for the computer knowledgable, try 
this for Outlook for Dummies (Outlook 2003):
Go to Tools; Email Accounts: check change existing email account; 
Internet Email Settings; More Settings; Outgoing Server: check the 
authentication box, use the same settings; Finish
This should work.  If not, check with the computer savvy.
This is most commonly caused by the domain that the message is to not 
being listed in the rcpthosts control file (see man qmail-control).
The fix for this common cause is to set up tcprules so that 
RELAYCLIENT 
is set for messages coming from your local workstations.  See the FAQ 
examples for further info.
More peculiarly and rather obscurely, this "553... rcpthosts" message 
can also occur in MTA->MTA communication when one of a domain's 
nameservers is down.  This comes about when you have an A record 
defined for your domain and it is not listed in one of the MX records 
(ie it is your webserver; this is widely practised).  Somehow some 
MTAs 
look up MX records, probably using the broken nameserver and failing, 
and then fallback to the A record.  That machine has qmail loaded but 
complains with a "553 ... not in rcpthosts" as it should.  The problem 
is that some MTAs strip out the IP address of the complaining machine 
making it impossible to see what is going on -- unfortunately qmail 
also fails to identify itself in the message.  A partial fix would be 
for qmail to identify itself in the 553 message.  The fault, of 
course, 
does not lie with qmail.  This was seen on a system running Bind 9.1.0 
and a recent version of Sendmail as MTA.  Note - this is a relatively 
obscure cause of this problem :)