Messages Stuck in /var/spool/mqueue.in

[James Pifer]

On Thu, 2003-12-18 at 09:34, lester lasad wrote:
> My mail started getting stuck again late afternoon yesterday. This has
> happened before, but stopping and starting mailscanner a bunch of
> times did not work this time.
>
> I saw the previous post where spamassassin was causing the issue.
>
> -I'm already on 2.60.
>
> -I tried upgrading top 2.61 but keep getting an error: Makefile:94:
> *** missing separator. Stop.
>
> -I rebuilt the baye db with sa-learn --rebuild
>
> Still no go. I upgraded MailScanner to the latest.
>
> Here's what I get in my messages log:
>
> Dec 18 09:05:06 sammy last message repeated 4 times
>
> Dec 18 09:08:14 sammy named[981]: lame server resolving
> '70.62.6.69.in-addr.arpa' (in '62.6.69.in-addr.arpa'?): 69.6.25.84#53
>
> Dec 18 09:08:15 sammy named[981]: lame server resolving
> '70.62.6.69.in-addr.arpa' (in '62.6.69.in-addr.arpa'?): 69.6.25.125#53
>
> Dec 18 09:08:31 sammy named[981]: lame server resolving
> '162.180.156.161.in-addr.arpa' (in '156.161.in-addr.arpa'?):
> 206.74.254.2#53
>
> Dec 18 09:08:31 sammy named[981]: lame server resolving
> '162.180.156.161.in-addr.arpa' (in '156.161.in-addr.arpa'?):
> 206.74.254.10#53
>
> Dec 18 09:09:16 sammy MailScanner: succeeded
>
> Dec 18 09:09:18 sammy last message repeated 2 times
>
> Dec 18 09:10:45 sammy named[981]: lame server resolving
> '132.34.52.157.in-addr.arpa' (in '52.157.in-addr.arpa'?):
> 157.33.227.3#53
>
> Dec 18 09:10:45 sammy named[981]: lame server resolving
> '132.34.52.157.in-addr.arpa' (in '52.157.in-addr.arpa'?):
> 157.33.227.4#53
>
> Dec 18 09:11:12 sammy MailScanner: MailScanner -15 succeeded
>
> Dec 18 09:11:12 sammy MailScanner: succeeded
>
> Is my problem something with DNS? If so, what generally causes lame
> server resolving messages?
>
> Thanks,
>
> James
>
>
>
> ______________________________________________________________________
> Do you Yahoo!?
> New Yahoo! Photos - easier uploading and sharing

I had someone post this message for me. My mail is now routing again,
but what a pain in the ***. At around 5PM EST yesterday it all just
stopped.

After going through tons of mailscanner restarts trying different
options, ie with spamassassin(2.60), without spamassassin, with spam
checks, without spam checks, upgrade mailscanner, tried upgrading
SpamAssassin, rebuild bayes database, on probably more I'm forgetting.

It's finally delivering mail once I restarted the whole machine and had
Spam Checks = no and Use SpamAssassin = no. Of course it delivered all
my spam too... :-(

I reenabled Spam Check and SpamAssassin and it's still delivering. I
have no idea what happened and why, but it's fustrating when it does
happen. (2nd or 3rd time now for me over the last year)

Maybe the problem really was DNS since my mail server is also a DNS
server and maybe restarting the box fixed that. I had not tried
restarting the DNS service (wish I had). Normal lookups seemed ok since
I could browse the net, etc. Maybe reverse lookups were screwed up.

Thanks,
James