proc mail not flushing /var/spool/mqueue messages periodically
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mandrakes,Redhats,Debians.Suses and FreeBSD
Posts: 52
Rep:
proc mail not flushing /var/spool/mqueue messages periodically
Hi
I am using Centos 5.2 32bit Sendmail/Fetchmail (sendmail-8.13.8-2.el5 and fetchmail-6.3.6-1.el5) for our local maildelivery from a common account.I can able to send mails through this server.But while receiving all mails are queued in /var/spool/mqueue directory.
Even if i flush these mails by executing "/usr/sbin/sendmail -q -v ", shows messages are locked. It was working 3 years without any problem, suddenly this problem arises.Another interesting point is if i restart the machine mails are flushed out and users got their mails.
I am using Centos 5.2 32bit Sendmail/Fetchmail (sendmail-8.13.8-2.el5 and fetchmail-6.3.6-1.el5) for our local maildelivery from a common account.I can able to send mails through this server.But while receiving all mails are queued in /var/spool/mqueue directory.
Even if i flush these mails by executing "/usr/sbin/sendmail -q -v ", shows messages are locked. It was working 3 years without any problem, suddenly this problem arises.Another interesting point is if i restart the machine mails are flushed out and users got their mails.
Any tips will be more helpful ?
Regards
Gopal
tail -f sendmail logs whilst flushing.
send output here
Distribution: Mandrakes,Redhats,Debians.Suses and FreeBSD
Posts: 52
Original Poster
Rep:
Hi
Thanks for the info. Upon further deep checking, for each entry in the /var/log/mqueue, while doing flush ( sendmail -q -v ), i got an entry as "timeout waiting for input from local during Draining Input" in the /var/log/maillog.
Hope this help further.
Note : I dont have any spam filter like spamassasin in my server.
Thanks for the info. Upon further deep checking, for each entry in the /var/log/mqueue, while doing flush ( sendmail -q -v ), i got an entry as "timeout waiting for input from local during Draining Input" in the /var/log/maillog.
Hope this help further.
Note : I dont have any spam filter like spamassasin in my server.
well i told you why you get the locked message, now it is up to you to find out why these messages are taking so long to deliver. start by checking the content of the messages..etc
Distribution: Mandrakes,Redhats,Debians.Suses and FreeBSD
Posts: 52
Original Poster
Rep:
Hi
Thanks for the info. Let me explain my scenario. We are getting support emails from various companies, and it will be fetched to a local user mailbox. In my aliases file i configured such that all the support mails will be copied to some other users also and these mails are not flushed and available in the /var/spool/mqueue.
I setup OTRS locally, and this fetch support mails periodically from the local user mailbox. After googling i find out something like this,
If e-mail is delivered to a program which generates too much output, then sendmail may issue an error:
timeout waiting for input from local during Draining Input
I have sent a mail to OTRS mailing list.Meanwhile is there anything to be
monitored or noticed in the sendmail server.
Thanks for the info. Let me explain my scenario. We are getting support emails from various companies, and it will be fetched to a local user mailbox. In my aliases file i configured such that all the support mails will be copied to some other users also and these mails are not flushed and available in the /var/spool/mqueue.
I setup OTRS locally, and this fetch support mails periodically from the local user mailbox. After googling i find out something like this,
If e-mail is delivered to a program which generates too much output, then sendmail may issue an error:
timeout waiting for input from local during Draining Input
I have sent a mail to OTRS mailing list.Meanwhile is there anything to be
monitored or noticed in the sendmail server.
Cheers
Gopal
ah...if only you gave this info earlier
anyway, simple answer is, i know nothing about OTRS
but i do know that if it gives you more trouble, try using RT.
Distribution: Mandrakes,Redhats,Debians.Suses and FreeBSD
Posts: 52
Original Poster
Rep:
Hi
After drilling down all the logs, and i found the culprit.Also when i stop the dovecot service,the mails getting flushed and if i start it, then mails are accumulated in the queue.So, it must be a process that sending bulk mails to the server.Upon investing all the logs and procmail running sessions, i found one machine constantly available in the proc sessios delivering mails.I disconnected that one from network,everything seems to start ok... and all mails are flushed immediately.
There must be a worm/virus constantly doing this,(by the way the machine has AVG network edition with latest update),so i am going to erase the Windows XP OS.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.