Avatar of Mark
 asked on

sendmail stat=Please try again later

I've got a pretty urgent problem. I just changed IP's on my mail server. The A and MX records are hosted at networksolutions. I changed the IP there and now when I do `host mail.ohprs.org` it does come back with the correct IP. Mail is coming in, but I'm getting "please try again later" on all messages. Why?

sendmail 8.14.9 on Slackware64 14.1, kernel 3.19.17

/varl/log/maillog example:
Apr  2 22:30:43 mail sm-mta[30165]: t332UgQJ030165: from=<mfoley@server.novatec-inc.com>, size=1603, class=0, nrcpts=1, msgid=<201504030230.t332UMbB030452@server.novatec-inc.com>, proto=ESMTP, daemon=MTA, relay=cdptpa-outbound-snat.email.rr.com []
Apr  2 22:30:43 mail sm-mta[30165]: t332UgQJ030165: Milter change: header X-Spam-Status: from  No, score=-2.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00\n\tautolearn=ham version=3.3.2-_revision__1.4__ to No, score=-100.0 required=3.0 tests=USER_IN_WHITELIST\n\tautolearn=ham version=3.3.2-_revision__1.13__
Apr  2 22:30:43 mail sm-mta[30165]: t332UgQJ030165: Milter change: header X-Spam-Report: from  \n\t* -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP\n\t* -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%\n\t*      [score: 0.0000]\n\t*  0.8 AWL AWL: Adjusted score from AWL reputation of From: address to \n\t* -100 USER_IN_WHITELIST From: address is in the user's white-list
Apr  2 22:30:43 mail sm-mta[30165]: t332UgQJ030165: Milter change: header X-Spam-Checker-Version: from  SpamAssassin 3.3.2-_revision__1.4__ (2011-06-06) on\n\tserver.novatec-inc.com to SpamAssassin 3.3.2-_revision__1.13__ (2011-06-06) on\n\tmail.hprs.local
Apr  2 22:30:43 mail sm-mta[30165]: t332UgQJ030165: Milter add: rcpt: allmail
Apr  2 22:30:43 mail sm-mta[30165]: t332UgQJ030165: Milter: data, reject=451 4.3.2 Please try again later
Apr  2 22:30:43 mail sm-mta[30165]: t332UgQJ030165: to=<mark@ohprs.org>, delay=00:00:01, pri=31603, stat=Please try again later
Apr  2 22:30:43 mail sm-mta[30165]: t332UgQJ030165: to=/var/spool/mail/allmail, delay=00:00:01, pri=31603, stat=Please try again later

Open in new window

Email ServersLinux

Avatar of undefined
Last Comment

8/22/2022 - Mon
Chris H

Are you novatec-inc.com?

THe issue is the milter is generating a temporary failure.
Not quite sure what on data triggered the try again later response.

Note, the milter seems to have auto learn on spamd ( other question of yours)

If memory serves, a positive number identifies spam, does the milter have a file size restriction which this message exceeds? Or it passes the data/attachments  through anti-virus?

I am not sufficiently familiar with the milters exit explanations to identify the issue.

You are adding another recipient, copy of all incoming.  Not sure whether that or something else triggers the issue.

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

Are you novatec-inc.com?
Yes, but I'm seeing this problem from other senders to any recipient. I posted my test as an example.

Arnold: I have several milters which have all been working fine for months. The only thing changed is the IP address of eth0. I have spamass-milter which get the scoring from spamd; milter-bcc which simply copied spam to a mbox: /var/spool/mail/allmail; and clamav-milter which checks for viruses and quarantines if found. The maillog messages doesn't really say which milter is causing the problem.
Is your domain defined as local and you gave the aliases.db that maps the address to the local mailbox?
The lan domain is hprs.local. The "Public" domain is ohprs.org. Not sure what you're asking with respect to aliases.db
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.

Looks like I got it working! Arnold, you comment about aliases.db made me think about access.db. I stopped sendmail and all milters. I changed the relay entry in /etc/mail/access to:   RELAY

instead of the old IP. Then I started everything back up. It started working just fine! I don't know if it was the relay thing or just restarting things, but it is going OK now. Thanks for the clue.

Now, if you guys can just help me figure out my other problem as easily I can call it a night!


What is that ip? Relay allows that ip relay rights through your system.