LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   qmail: bouncing mail and unable to opendir todo/0 (https://www.linuxquestions.org/questions/linux-server-73/qmail-bouncing-mail-and-unable-to-opendir-todo-0-a-601504/)

leif_84 11-21-2007 01:34 PM

qmail: bouncing mail and unable to opendir todo/0
 
Hi!
I just installed qmail package from http://www.qmailrocks.org/ with bunch of extra software and patches. I didn't got any compilation errors, everything seemed to go smoothly. After I ran qmail, checked if smtp and pop3 is running, all ok:
Code:

25/tcp  open  smtp
110/tcp open  pop3

Then I created an account and sent mail from gmail account, but I got this error:
Code:

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    user@******.com

Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 13): 553 sorry, relaying denied from your location [66.249.92.172] (#5.7.1)

Then I checked to mail log, and got this error all over the log:
Code:

..
Nov 21 15:14:46 + qmail: 1195658086.152675 alert: unable to opendir todo/0, sleeping...
Nov 21 15:14:56 + qmail: 1195658096.157308 alert: unable to opendir todo/0, sleeping...
Nov 21 15:15:06 + qmail: 1195658106.161927 alert: unable to opendir todo/0, sleeping...
Nov 21 15:15:16 + qmail: 1195658116.166550 alert: unable to opendir todo/0, sleeping...
Nov 21 15:15:26 + qmail: 1195658126.178131 alert: unable to opendir todo/0, sleeping...
Nov 21 15:15:36 + qmail: 1195658136.175802 alert: unable to opendir todo/0, sleeping...
Nov 21 15:15:46 + qmail: 1195658146.180429 alert: unable to opendir todo/0, sleeping...
Nov 21 15:15:56 + qmail: 1195658156.185051 alert: unable to opendir todo/0, sleeping...
Nov 21 15:16:06 + qmail: 1195658166.189678 alert: unable to opendir todo/0, sleeping...
Nov 21 15:16:16 + qmail: 1195658176.194302 alert: unable to opendir todo/0, sleeping...
Nov 21 15:16:26 + qmail: 1195658186.198928 alert: unable to opendir todo/0, sleeping...
Nov 21 15:16:36 + qmail: 1195658196.203552 alert: unable to opendir todo/0, sleeping...
Nov 21 15:16:46 + qmail: 1195658206.208179 alert: unable to opendir todo/0, sleeping...
..

But I couldn't find 553 error or any other ones in the log. I'm not sure if these errors has to do anything with the 553 relay error. I'm running Slackware 11.0. I would really appreciate any help! thanks

mt83 11-25-2007 08:08 PM

Hi,

For first case, You should check your relay domain MX record is working correctly.
To check this use www.dnsstuff.com or dig or nslookup.
For second case, I don't have idea, probably unix permission problem.

mt83

trickykid 11-25-2007 08:13 PM

First issue is kind of blatant, it is your relay domain configuration. But did you send email to your server or new account or trying to send to a gmail account? I'm confused cause the IP in the error points to a google.com address/domain.

Second issue is a permission problem. Check the permissions.

leif_84 11-25-2007 11:18 PM

Thank you guys! My domain didn't pass all the tests:
Quote:

WARN MX records are not CNAMEs WARNING: When I looked up your MX record, your DNS server returned a CNAME. This is an unusual situation, and I can't handle it -- the following MX tests may not work properly. The problem is:
smtp.secureserver.net.->smtp.where.secureserver.net.
Quote:

FAIL MX A lookups have no CNAMEs WARNING: One or more of your MX records points to a CNAME. CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are:
smtp.secureserver.net.->smtp.where.secureserver.net.->64.202.166.12
Quote:

WARN Mail server host name in greeting WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit QUOTE, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

smtp.secureserver.net claims to be host pre-smtp22-01.prod.mesa1.secureserver.net [but that host is at 64.202.166.38 (may be cached), not 64.202.166.12]. <br />mailstore1.secureserver.net claims to be host pre-smtp24-02.prod.mesa1.secureserver.net [but that host is at 64.202.166.85 (may be cached), not 64.202.166.11]. <br />
Quote:

FAIL Acceptance of postmaster address ERROR: One or more of your mailservers does not accept mail to postmaster@********.com. Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.

smtp.secureserver.net's postmaster response:<br /> >>> RCPT TO:<postmaster@*********.com><br /> <<< 553 sorry, relaying denied from your location [74.53.59.133] (#5.7.1) <br /> mailstore1.secureserver.net's postmaster response:<br /> >>> RCPT TO:<postmaster@*********.com><br /> <<< 553 sorry, relaying denied from your location [74.53.59.133] (#5.7.1) <br />
Quote:

WARN Acceptance of abuse address WARNING: One or more of your mailservers does not accept mail to abuse@********.com. Mailservers are expected by RFC2142 to accept mail to abuse.

smtp.secureserver.net's abuse response:<br /> >>> RCPT TO:<abuse@*********.com><br /> <<< 553 sorry, relaying denied from your location [74.53.59.133] (#5.7.1) <br /> mailstore1.secureserver.net's abuse response:<br /> >>> RCPT TO:<abuse@*******.com><br /> <<< 553 sorry, relaying denied from your location [74.53.59.133] (#5.7.1) <br />
Quote:

PASS Open relay test OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here.

smtp.secureserver.net OK: 553 sorry, relaying denied from your location [74.53.59.133] (#5.7.1) <br />mailstore1.secureserver.net OK: 553 sorry, relaying denied from your location [74.53.59.133] (#5.7.1) <br />
Any tips whats up with the CNAME and does it has any effect on my problem? it appears that my smtp sends out the message >mailstore1.secureserver.net OK: 553 sorry, relaying denied from your location [74.53.59.133], so I guess thats a configuration problem then. I don't understand why it says mailstore1.secureserver.net, thats not my domain. Any tips please? Thanks!

trickykid 11-26-2007 07:40 AM

From the tests, sounds like you setup a CNAME and not an MX record for your mail server. In order for Mail to work, you have to have an MX record.

mt83 11-27-2007 12:21 AM

Hi,

Your Domain record should like this

@ 1D IN SOA test.com. hostmaster.test.com. (
42 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum

@ 1D IN NS c1.test.com. ← hostname+Domain
@ 1D IN MX 10 mx1.test.com. ← Mail Priority

If you use Customize Web Panel, you should check with your domain provider.

leif_84 11-28-2007 02:05 PM

Thanks! I have the domain registered at GoDaddy. But there ware listed two MX records, both ware something.secureserver.com, so I changed the first one to mail.mydomain.com, I'm not sure what should I do about the second one, should there be two? after I changed it, I tried to ping mail.mydomain.com and got:
Quote:

PING pop.secureserver.net (64.202.165.92) 56(84) bytes of data.
64 bytes from pop.secureserver.net (64.202.165.92): icmp_seq=1 ttl=112 time=91.0 ms
It still the same secureserver.net, but I guess I have to wait like 24 hours for the changes to take effect.

Whats the purpose of the second MX record, do I really need it? Thanks!

mt83 11-29-2007 03:41 AM

Hi,
My understanding on it is if u have two or more email server for this domain. U can set more than one MX record. Depend on your requirement.


All times are GMT -5. The time now is 12:24 AM.