Hello all
Currently I am working in a live production environment with 100+ Solaris servers . The environment has one DNS server and one SMTP server.
The problem that I am facing since the past 2 months is that the /var/spool/mqueue on my DNS server keeps getting full i.e. mails with name starting with qfr & dfr keeping on gathering up and I have to manually go and delete these mails.
Some sample outputs of these mail files are given below:
It seems that the issue is somewhat related to crons.
Does anyone know how I can get rid of such mails ? I have to empty the /var/spool/mqueue directory every 7-8 hours since the number of mails reaches 50,000 +
I keep having this msg on my SunOS console :
Jun 29 08:57:40 bersimis sendmail: NOQUEUE: low on space (have 0, SMTP-DAEMON needs 101 in /var/spool/mqueue)
I tried to make some space by deleting the files in it, but the msg came back ...
Any tips ?
Thanks (3 Replies)
Hi,
We have all the user account in a home direcory where their mail is stored and retrieved by email clients. We do however have /var/spool/mail with all the user accounts in it as well Our sendmail.cf is configured to use /var/spool/mqueue as the queue so .what is /var/spool/mail being used... (3 Replies)
Hi,
How can i get my mail on either /var/spool/mail or /var/mail?
I use mail and sendmail command to send mail. But everytime I send mail it comes to my outlook inbox and when I check with mail command I get the message "No mail for siba". (Note siba is my user Id.) (2 Replies)
Hello,
I have a bunch of cron jobs in the crontab. For some reason mail from the cron jobs started going to /var/spool/mqueue instead of being sent.
Does anyone know why mail from cron jobs would go to the queue instead of being sent? (9 Replies)
Hi, We have some 2-3 Solaris 9 servers with the following issue.
For every cron job which has email notifications, it is sending the emails, but it create files at /var/spool/clientmqueue/ which has similar contents.
"
V6
T1271362260
K1271362260
N1
P30359
MDeferred: Connection refused... (1 Reply)
Hi,
solaris : 9
can we delete the files from this location /var/spool/clientmqueue . I found around 40K files lying in this location.
Regards (1 Reply)
Hi
My box is running with AIX 6100-06 and Im the root user of this box
My /var gets filled up often to 100%
When I investigate I find that it is the below file which increases rapidly
/var/spool/mail/pdgadmin
I dont know why this file is growing up.
Can any one assist me on this.... (2 Replies)
Hi all,
I have some sort of problem with BIND DNS server my environment as follows.
bash-3.00# cat /etc/release
Solaris 10 6/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to... (3 Replies)
Hi guys .
I have a solaris machine serving as a DNS server for my environment. Everytime I go into /var/spool/mqueue , there are an aweful lot of emails with names likes:
qfqB6ChrpL006644.
When I cat the file , I get the following output:
H??Received: from machine.domain.com... (3 Replies)
Hi,
Am trying to configure DNS server and trying to keep the information in /etc/resolv.conf file as:
search server
nameserver 192.168.0.10
when i restart the network service with #service network restart, resolv.conf file is changing as:
nameserver 192.168.0.10
search server -... (5 Replies)
Discussion started by: raosr020
5 Replies
LEARN ABOUT DEBIAN
smtpdcheck
smtpdcheck(1) Mail Avenger 0.8.3 smtpdcheck(1)NAME
smtpdcheck - check SMTP servers
SYNOPSIS
smtpdcheck [--stop {ip-addr|name}] [--timeout seconds]
[prio:]server [[prio:]server]
DESCRIPTION
smtpdcheck checks to see if SMTP servers are available. The intent is for use on secondary mail servers, which have no reason to accept
mail when the primary server is available.
The argument consists of a list of server names, each of which may optionally be prefixed by a numeric MX priority and a colon. (This is
exactly the format for MX records returned by the avenger dns command.) smtpdcheck will attempt to connect to each server in succession.
If one of the servers specified on the command line is available, smtpdcheck will print its name to standard output and exit with status 1.
If smtpdcheck cannot connect to any of the servers, it will exit with status 0. If a system error occurs, smtpdcheck will exit with status
2.
OPTIONS
--stop {ip-addr|name}
Tells smtpdcheck to stop before checking a server with IP address ip-addr or hostname name. If such a host is encountered in the list
of servers and prio is specified, then smtpdcheck will consider it acceptable for other servers with the same priority to be available,
even if those servers were first in the list. In other words, given the following arguments:
smtpdcheck --stop s2.domain.com
10:s1.domain.com 10:s2.domain.com
20:s3.domain.com
This command will always succeed, regardless of whether "s1.domain.com" is up, because "s2.domain.com" has the same priority. On the
other hand, the following command will fail and output "s1.domain.com" if "s1.domain.com" is up:
smtpdcheck --stop s2.domain.com
10:s1.domain.com 20:s2.domain.com
30:s3.domain.com
If a gethostbyname lookup for the argument name fails, smtpdcheck will exit immediately with status 2.
--timeout {seconds]
By default, smtpdcheck spends 10 seconds probing each server. This includes the time to do a DNS lookup, to establish a TCP connection
to port 25 of the server, and to read the "220" SMTP code from the server's SMTP greeting message. To use a different value, specify
it with the --timeout option. The value 0 disables the timeout completely, which is dangerous since smtpdcheck might then end up
waiting forever to read the "220" string.
EXAMPLES
To refuse to relay mail at a secondary MX server when the primary server is not down, you might place the following in
/etc/avenger/secondary (assuming MxLocalRcpt is 1):
dns RECIP_MXES mx "$RECIPIENT_HOST"
setvars
server=`smtpdcheck --stop $MYIP $RECIP_MXES`
test -n "$server" && defer "Please use server $server"
SEE ALSO avenger(1)dbutil(1)asmtpd.conf(5),
The Mail Avenger home page: <http://www.mailavenger.org/>.
BUGS
smtpdcheck could achieve much lower latency by probing all the servers simultaneously. It should also include some kind of caching, to
avoid repeatedly trying to contact an unavailable server. Finally, hosts with multiple IP addresses could be handled more cleanly, though
what smtpdcheck does should probably work in most cases.
AUTHOR
David Mazieres
Mail Avenger 0.8.3 2012-04-05 smtpdcheck(1)