Limiting User mailbox size in /var/spool


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Limiting User mailbox size in /var/spool
# 1  
Old 10-23-2009
Limiting User mailbox size in /var/spool

How can one limit the size of user mailboxes in /var/spool/mail?
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

/var/spool/mqueue issue

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)
Discussion started by: Junaid Subhani
3 Replies

2. AIX

/var/spool/mail/ issues

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)
Discussion started by: samsungsamsung
2 Replies

3. Solaris

/var/spool/clientmqueue

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)
Discussion started by: maooah
1 Replies

4. Solaris

Solaris 9, /var/spool/clientmqueue/

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)
Discussion started by: uxadmin007
1 Replies

5. UNIX for Advanced & Expert Users

Mail going to /var/spool/mqueue instead of being sent

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)
Discussion started by: xadamz23
9 Replies

6. UNIX for Dummies Questions & Answers

/var/spool/mail

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)
Discussion started by: siba.s.nayak
2 Replies

7. UNIX for Dummies Questions & Answers

Sendmail /VAR/SPOOL/MAIL

Hi, First Question: In our company our users have their mailboxes in /var/spool/mail When I look at the users file it seems as if every email sent/received is in that user file! Is this because IMAP is being used or is that just how sendmail works? Second Question: How is that when I create... (3 Replies)
Discussion started by: mojoman
3 Replies

8. UNIX for Dummies Questions & Answers

/VAR/SPOOL/MAIL question

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)
Discussion started by: mojoman
3 Replies

9. UNIX for Dummies Questions & Answers

Tell UW-Imap to read /var/mail/mailbox ??

Hi, I've got UW-IMAP installed on Gentoo. I'm using EXIM as the transfer agent. EXIM is working fine (I think)... all incoming mail - external and internal goes to /var/mail/username file. I can verifiy this by reading this file directly with nano. Also, IMAPd is running. It lets me login... (2 Replies)
Discussion started by: d11wtq
2 Replies

10. UNIX for Dummies Questions & Answers

/var/spool/mqueue !!!

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)
Discussion started by: Wingman21
3 Replies
Login or Register to Ask a Question
EXIM_LOCK(8)						      System Manager's Manual						      EXIM_LOCK(8)

NAME
exim_lock - Mailbox maintenance SYNOPSIS
exim_lock [options]mailbox-file DESCRIPTION
The exim_lock utility locks a mailbox file using the same algorithm as Exim. For a discussion of locking issues, see section 25.2. exim_lock can be used to prevent any modification of a mailbox by Exim or a user agent while investigating a problem. The utility requires the name of the file as its first argument. If the locking is successful, the second argument is run as a command (using C's "system()" function); if there is no second argument, the value of the SHELL environment variable is used; if this is unset or empty, /bin/sh is run. When the command finishes, the mailbox is unlocked and the utility ends. The following options are available: -fcntl Use "fcntl()" locking on the open mailbox. -interval This must be followed by a number, which is a number of seconds; it sets the interval to sleep between retries (default 3). -lockfile Create a lock file before opening the mailbox. -mbx Lock the mailbox using MBX rules. -q Suppress verification output. -retries This must be followed by a number; it sets the number of times to try to get the lock (default 10). -timeout This must be followed by a number, which is a number of seconds; it sets a timeout to be used with a blocking "fcntl()" lock. If it is not set (the default), a non-blocking call is used. -v Generate verbose output. If none of -fcntl, -lockfile or -mbx are given, the default is to create a lock file and also use "fcntl()" locking on the mailbox, which is the same as Exim's default. The use of -fcntl requires that the file be writable; the use of -lockfile requires that the directory containing the file be writable. Locking by lock file does not last for ever; Exim assumes that a lock file is expired if it is more than 30 minutes old. The -mbx option is mutually exclusive with -fcntl. It causes a shared lock to be taken out on the open mailbox, and an exclusive lock on the file /tmp/.n.m where n and m are the device number and inode number of the mailbox file. When the locking is released, if an exclusive lock can be obtained for the mailbox, the file in /tmp is deleted. The default output contains verification of the locking that takes place. The -v option causes some additional information to be given. The -q option suppresses all output except error messages. A command such as exim_lock /var/spool/mail/spqr runs an interactive shell while the file is locked, whereas exim_lock -q /var/spool/mail/spqr <<End <some commands> End runs a specific non-interactive sequence of commands while the file is locked, suppressing all verification output. A single command can be run by a command such as exim_lock -q /var/spool/mail/spqr "cp /var/spool/mail/spqr /some/where" Note that if a command is supplied, it must be entirely contained within the second argument - hence the quotes. BUGS
This manual page needs a major re-work. If somebody knows better groff than us and has more experience in writing manual pages, any patches would be greatly appreciated. SEE ALSO
exim(8), /usr/share/doc/exim4-base/ AUTHOR
This manual page was stitched together from spec.txt by Andreas Metzler <ametzler at downhill.at.eu.org>, for the Debian GNU/Linux system (but may be used by others). March 26, 2003 EXIM_LOCK(8)