Server Mail Quota

Hi everyone,
my boss got an alert the other day stating that he was nearing the mail quota I had set at 650 MB. This brought up several questions that I'm having trouble finding answers to; hopefully someone here can help me out.
1. At what percentage to the quota does the alert get sent out? 80% capacity? 90%?
2. Is there any way for me to check how close my boss or anyone else is to reaching their quota without actually having to be at their computer checking their mail clients?
3. Similarly, is there a way for my boss or anyone else to check their own quotas? I know how to check it using Apple's Mail, but can't find it anywhere in Outlook 2011, our (presently) preferred client on Mac.
Any help would be greatly appreciated, and I can certainly provide more information if it would be helpful.

It is possible to check the quota in the Mac Mail client although I have my doubts that it is accurate.
I can't see any suchQuota inspection in Thunderbird or MS Windows Live Mail clients.
in Mac Mail: ctrl+Click the email account in the Mail App "Mailboxes" section of the LH panel and click "Get Account Info" where you will then see a "Quota Limits" panel with each folder's size in MB and No of Messages under a slider that summarises the amount of quota taken.
Very nice .... except it doesn't seem to reflect individual Users' Quota overrides of the Global "Limit Mail to nMB" settings on the Server App's Mail panel. In fact I doubt this works on OS X Server 4 Yosemite .... be glad to be proved wrong here!

Similar Messages

Sun One Messaging server Mail quota

I am unsing directory server 5.2 and messaging server 6.0 + iDA 4.5 .
I have quota set for a doimain test.com well i am getting "ERROR: cannot modify maildomainstatus attribute for
domain test.com: Insufficient access"
Domain: test.com
diskquota size(K) %use msgquota num %use user
no limit 1800 N/A no limit 12 N/A
[email protected]
DOMAIN SUMMARY:
| Limit Usage
Percentage
-------------+-------------------------------------------
Disk Quota(k)| 1024 1800
100Msg Quota | no limit 12
N/A
Number of users: 1
Mail Domain Status: active
New Mail Domain Status: overquota
ERROR: cannot modify maildomainstatus attribute for
domain test.com: Insufficient access
Any Ideas.
Thanks
Haris

Hm. You're sure you're using that particular combination of products?
iDA 4.5 was never supported for Messaging Server. We had 1.0, 1.1 and 1.2 versions, provided with Messaging 5.0, 5.1, and 5.2.
Messaging 6.0 does not come with iDA, nor is it supported, at present. . .
Are you using Schema 1 or Schema 2 for your Messaging Server?
Have you tried using the commcli provided with Messaging Server?

Where can I configure mail quotas in Lion Server?

One (minor) problem for me, after upgrading from SnowLeopard Server to Lion Server is the fact, that I can't figure out where to administer the mail quotas. So far I have just managed to find the "Server Admin". Here, under Mail -> Maintenance I can see the quotas and under Mail->Settings->Quotas I can enable quota warnings and edit them. But I can't find a place to configure individual quotas. The quota settings from SnowLeopard server have been migrated and are still in place. But how should I change them. It used to be in WorkgroupManager. But in WorkgroupManager this item is gone.
Many thanks for your replies.

Followng up a bit,
In looking into OD records on my Snow Leopard Server via the Inspector in WGM, I see the following attribute for one of my users for whom I've set a 1024mb mail quota.
Name:
MailAttriute
Value:
<?xml version="1.0" encoding="UTF-8"?>
<dict>
          <key>kAPOPRequired</key>
          <string>APOPNotRequired</string>
          <key>kAltMailStoreLoc</key>
          <string></string>
          <key>kAttributeVersion</key>
          <string>Apple Mail 1.0</string>
          <key>kAutoForwardValue</key>
          <string></string>
          <key>kIMAPLoginState</key>
          <string>IMAPAllowed</string>
          <key>kMailAccountLocation</key>
          <string>[redacted].[redacted].org</string>
          <key>kMailAccountState</key>
          <string>Enabled</string>
          <key>kPOP3LoginState</key>
          <string>POP3Allowed</string>
          <key>kUserDiskQuota</key>
          <string>1024</string>
</dict>
I'm wondering if manually entering this attribute, and an XML value with at least the kUserDiskQuota key included will be all I need to do to implement per-user quotas in Lion Server.
If I get time, I will test and report back.

Mail quota and server issue

I keep getting one of two messages all of a sudden.
Connection Failed
There maybe a problem with the mail server or network. Check the settings for account "*%[email protected]" or try again.
The server error encountered was: The connection to the server "mail.mac.com" on port 993 timed out.
Or I get a message saying that I am at 99% of mail quota. What do either of these mean?

I was aware that you have a .Mac account based on the information you provided in your original post.
My question was/is, how are you accessing your .Mac account with the Mail application on your Mac - the account type - .Mac, IMAP or POP?
The default account type for a .Mac account with the Mail application is a .Mac type account which is really an IMAP account and behaves in the same way.
You can access a .Mac account as a .Mac type, IMAP or POP account with the Mail application and as an IMAP or POP account with another email client such as the Mail application on your Mac or on a Windows PC.
Very few (no others that I'm aware of) email account providers include/support such a choice of account types. The majority support a single account type - IMAP or POP with POP being the most common.
With a POP account, you have the option to remove messages from the server when downloaded by an email client such as the Mail application. There is no such option when accessing an IMAP account with an email client such as Mail. A .Mac type account or IMAP account received messages remain on the server until deleted from the account's Inbox mailbox or moved from the account's Inbox mailbox to a mailbox stored locally on your hard drive. Transferring a message from a server stored mailbox to a user created "On My Mac" location mailbox with Mail (which is stored locally on your hard drive) saves the transferred message locally on your hard drive and removes the message from the server at the same time.
The same doesn't apply to a POP account which is the reason for my question regarding the account type.
Go to Mail > Preferences > Accounts and under the Account Information tab for your .Mac account preferences will show the account type at the top.
You can raise the amount of server storage space allocated for email messages or remove messages from the server to get rid if the error message and back under your server storage limit.

Mail quota issues

Server Running mac osx 10.4
Server Admin does not reflect recent changes made within WGM in relation to Mail quota increases.
I have rebooted, refreshed mail system etc but the mail quota appearing in mail accounts is incorrect.
Please advise the best way to make the changes stick.
Thanks
Simon

It could be that the quotas need reconstruction. Download and install mailbfr (available here: http://osx.topicdesk.com/tools/ ) and issue:
sudo mailbfr -q
Failing that, please check /var/log/mailaccess.log for clues. Maybe your Cyrus DB is broken.
Also note, that quotas and mailboxes over 2GB will not work correctly.
HTH,
Alex

Snow Leopard Server Mail disables access

This has been an intermitten problem for over a year. Every once in a while multiple email accounts in the "Workgroup Manager: local" loose their check mark next to "access account".
On the client machine, the first indication that something is wrong is when the client (me) gets an error message saying the password does not work.
This is on a Mac Mini colocated in Florida. I have 3 IP addresses and the emails work except when this crazy thing de-accesses.
It happens to email accounts on any of the 3 IP's. There are no mail quota's set and they are all set for both POP and IMAP.
I can't add anyone else until this is fixed. I'm using 10.6.8 Mac OS X Server.

This is the problem I'm trying to describe. It is now happening multiple times every day.
Any advise would be appreciated. The problem is the accounts are being de-accessed.

Cyrus mail quota

Hi,
An important user of our xserver (using imap Cyrus) has about 4gb in his imap account. The biggest mailfolder contains 1.7 gb at the moment.
He gets a warning every now and then from Mail.app that his mailbox is almost full.
I read a lot about the hardcoaded limit of 2gb, and how users get over this 2gb, but are getting problems with their accounts.
Is this still the case?
And does this count per imap mail folder or for all the imap folders together in his account (which is now 4 gb)?
We did not set quotas our self, in Workgroup Manager all mail quotas are left at '0'.
Thanks!

I have been experiencing the same issue: a user is getting the '90% Quota' error when we have not set any quotas. I saw that you mentioned a 'hardcoded' 2GB limit, but when looking at Server Admin -> Mail -> Accounts, I see that user's account has a -374MB under 'Quota Used'.
Have you found any other possible solutions?

Increase Mail Quota

I have a Mac Pro with Leopard Server. I'm trying to increase the Mail Quotas for some of our users over 2GB.
When I update this value in WGM, everything seems to work ok, but the users, sitll get the warning over x% of mail quota.
Any idea what im doing wrong?

As you can see the server admin changes did not make their way to the database itself.
You can either try using cyradm (see man page tidbit below)
"setquota" root resource value [resource value ...]
"sq" root resource value [resource value ...]
Set a quota on the specified root, which may or may not be an actual mailbox. The only
resource understood by Cyrus is "STORAGE". The value may be the special string "none"
which will remove the quota.
Or look at downloading siradmin and see if that interface helps at all. Siradmin is easier than cyradm but if you are going to be administrating this mail server, you should learn cyradm..
Siradmin: http://explanatorygap.net/sw/SirAdmin.app.zip
I hope this helps..

Help with OSX server mail setup

Please if anyone can tell me what I am doing wrong, I would be very grateful. I have a company with an externaly hosted website and an an internally hosted email (OSX server). I have everything kind of working, but some things don't seem quite right. I'll explain below:
I have a purchased domain: mycompany.com hosted by godaddy.
I am using Godaddy name servers: ns65.domaincontrol.com and ns66.domaincontrol.com
The external godaddy DNS has an a name entry for my mail server: mail pointing to 123.123.123.123 (which is my companies external static IP address).
There is also a null (@) a name record for my website hosting service (squarespace) pointing to 456.456.456.456
There is a cName record www pointing to the squarespace domain "www.squarespace6.com" (know this is unusual, but it is how squarespace asks this to be set up and does not work otherwise)
There is an MX record with priority 10 and host name @ pointing to mail.mycompany.com
I have a airport extreme router with the appropriate ports forwarded to the OSX server.
The DNS servers on the router are pointed to the internal IP address of the OSX server
I did not change the domain name on the router (mistake?) it is currently san.rr.com
On the OSX server I have set up host name to be mycompany.comDNS is set up with primary zone being mycompany.com
Primary Zone entries include
nameserver = mycompany.com
machine record host name is mycompany.com and the IP address is the internal IP address of the OSX server
another machine record with host name "mail" and IP address is the internal IP address of the OSX server.
Finally, there is a mail exchanger record with mail server "mail.mycompany.com" and priority 10
There are 2 entries autocreated in the Reverse zone
Mail is setup and running on the OSX server providing mail for "mail.mycompany.com"
Users are setup with email address: [email protected] (note: without the mail subdomain - I think this is OK?)
I am using self signed certificate.
In my clients (windows Thunderbird, Mac Mail, iOS mail), the settings are for the incoming mail server host name to be "mail.mycompany.com" and the outgoing also to be "mail.mycompany.com"
I woud have expected this to be imap.mycompany.com and smtp.mycompany.com respectively, but it doesn't work when I input these values and works with the former. Have I set this up wrong?? imap seems to require SSL on port 993 and SMTP seems to require TLS on port 587.Outlook on PC gives me an error that after googling appears to be a problem with not recognizing a fuly qualified hostname form the SMTP client. I see the fix, but wanted to know if that meant that my server didn't have a fully qualified host name and whether I should change that rather than just remove that restriction???
The final problem is that my outgoing emails seem to be getting caught up in other people's spam filters too frequently. What is the main reason for this? Is it because I have set something up wrong and it brings up flags or is it simply because I am not a huge hosting company, or somethign else althogether?
If you've gotten this far, big thanks! If you can help me, even more thanks!

Well, actually they are both getting caught up in spam filters and bounced back. I actually realized that part of the problem is that I have a dynamic IP address, but it doesn't change. Regardless, on the bounce back it looks like hotmail and other domains are rejecting email from my IP and recognize it as dynamic. This was a test server that i would by physically taking to my business where there is a static business IP address (Cox).
Sorry for the very long original message, but it seems that most people don't post enough information for the problem to be solved in their original posts and I was hoping to provide as much detail as possible.
The other is the question of "are things set up right?" It seems strange to me that both my outgoing and incoming servers are "mail.mycompany.com" and not imap.mycompany.com and smtp.mycompany.com and I wonder if this is going to cause me to have problems?
Is it a problem that my email addresses are [email protected] and not [email protected]?
Was I supposed to change the domain name on the router?
Also is it going to be a problem that I am using a self signed certificate?

DMZ - DNS Server, Mail Server, Web Server, FTP Server

Hi,
I am looking at a router to support around 20-30 people. I have a DNS Server, Mail Server, Web Server, FTP Server (all on one box (PC). I was wondering how everyones experiences with DMZ and port forwarding have been with these protocols with Airport and supporting a group of this size? Do you forsee issues? Will the new Airport handle these requirements better?
Thanks

A record for mail.mydomain.com going for ip 199.99.99.999
MX record for mail.mydomain.com with destionation as mail.mydomain.com
That doesn't quite make sense. There must be an A record for "server.mydomain.com" or you wouldn't be able to reach it at all. You want the MX record to point to that.

OS X 10.9 Server Mail Domain Whitelisting

I just cannot understand why this isn't working.
I've added gmail, googlemail, mac, me, icloud to the whitelist, but emails from those domains still get greylisted:
$ sudo serveradmin settings Mail | grep whitelist
Mail:postfix:add_whitelist_domain:_array_index:5 = "gmail.com"
Mail:postfix:add_whitelist_domain:_array_index:6 = "googlemail.com"
Mail:postfix:add_whitelist_domain:_array_index:7 = "mac.com"
Mail:postfix:add_whitelist_domain:_array_index:8 = "me.com"
Mail:postfix:add_whitelist_domain:_array_index:9 = "icloud.com"
Mail:postfix:domain_whitelist:_array_index:5 = "gmail.com"
Mail:postfix:domain_whitelist:_array_index:6 = "googlemail.com"
Mail:postfix:domain_whitelist:_array_index:7 = "mac.com"
Mail:postfix:domain_whitelist:_array_index:8 = "me.com"
Mail:postfix:domain_whitelist:_array_index:9 = "icloud.com"
I tried:
$ sudo serveradmin settings Mail:postfix:whitelist_enabled = yes
2014-05-02 02:56:37.103 serveradmin[2894:507] Error: servermgr_mail: postconf read error: /usr/sbin/postconf: warning: whitelist_enabled: unknown parameter
2014-05-02 02:56:37.104 serveradmin[2894:507] unable to save key: whitelist_enabled (unknown parameter)
I've tried restarting the mail service and restarting the computer.
Has anyone been successful in whitelisting a domain on 10.9 Server?
May 2 02:37:47 example.com postfix/smtpd[1398]: connect from mail-oa0-f48.google.com[209.85.219.48]
May 2 02:37:47 example /usr/libexec/postfix/greylist.pl[1403]: Temporary message rejection to: <[email protected]> from: <[email protected]> sent from: [209.85.219.48] for: 60 seconds due to greylisting
May 2 02:37:48 example.com postfix/smtpd[1398]: NOQUEUE: reject: RCPT from mail-oa0-f48.google.com[209.85.219.48]: 450 4.7.1 <[email protected]>: Recipient address rejected: Service is unavailable; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail-oa0-f48.google.com>
May 2 02:37:48 example.com postfix/smtpd[1398]: disconnect from mail-oa0-f48.google.com[209.85.219.48]

#!/usr/bin/perl
use DB_File;
use Fcntl;
use Sys::Syslog qw(:DEFAULT setlogsock);
# Usage: greylist.pl [-v]
# Demo delegated Postfix SMTPD policy server. This server implements
# greylisting. State is kept in a Berkeley DB database. Logging is
# sent to syslogd.
# How it works: each time a Postfix SMTP server process is started
# it connects to the policy service socket, and Postfix runs one
# instance of this PERL script. By default, a Postfix SMTP server
# process terminates after 100 seconds of idle time, or after serving
# 100 clients. Thus, the cost of starting this PERL script is smoothed
# out over time.
# To run this from /etc/postfix/master.cf:
#    policy unix -       n       n       -       -       spawn
#      user=nobody argv=/usr/bin/perl /usr/libexec/postfix/greylist.pl
# To use this from Postfix SMTPD, use in /etc/postfix/main.cf:
#    smtpd_recipient_restrictions =
#          reject_unauth_destination
#          check_policy_service unix:private/policy
# NOTE: specify check_policy_service AFTER reject_unauth_destination
# or else your system can become an open relay.
# To test this script by hand, execute:
#    % perl greylist.pl
# Each query is a bunch of attributes. Order does not matter, and
# the demo script uses only a few of all the attributes shown below:
#    request=smtpd_access_policy
#    protocol_state=RCPT
#    protocol_name=SMTP
#    helo_name=some.domain.tld
#    queue_id=8045F2AB23
#    [email protected]
#    [email protected]
#    client_address=1.2.3.4
#    client_name=another.domain.tld
#    instance=123.456.7
#    sasl_method=plain
#    sasl_username=you
#    sasl_sender=
#    size=12345
#    [empty line]
# The policy server script will answer in the same style, with an
# attribute list followed by a empty line:
#    action=dunno
#    [empty line]
# greylist status database and greylist time interval. DO NOT create the
# greylist status database in a world-writable directory such as /tmp
# or /var/tmp. DO NOT create the greylist database in a file system
# that can run out of space.
# In case of database corruption, this script saves the database as
# $database_name.time(), so that the mail system does not get stuck.
$database_name="/Library/Server/Mail/Data/gldb/greylist.db";
$whitelist_host_file="/Library/Server/Mail/Data/gldb/whitelist_host";
$whitelist_domain_file="/Library/Server/Mail/Data/gldb/whitelist_domain";
$whitelist_db_name="/Library/Server/Mail/Data/gldb/whitelist.db";
$greylist_delay=60;
# Auto-whitelist threshold. Specify 0 to disable, or the number of
# successful "come backs" after which a client is no longer subject
# to greylisting.
$auto_whitelist_threshold = 10;
# Syslogging options for verbose mode and for fatal errors.
# NOTE: comment out the $syslog_socktype line if syslogging does not
# work on your system.
$syslog_socktype = 'unix'; # inet, unix, stream, console
$syslog_facility="mail";
$syslog_options="pid";
$syslog_priority="info";
sub add_whitelist {
          # check for null host name
          my ($_host_name) = $attr{"host_name"};
          if ($_host_name eq "") {
                    syslog $syslog_priority, "Warning: missing whitelist host name attribute";
                    return 0;
          # Open the database on the fly.
          open_whitelist_db() unless $whitelist_db_obj;
          # Is host already in white list
          $value = read_whitelist_db($attr{"host_name"});
          # Add host if not in database
          if ($value == 0) {
                    syslog $syslog_priority, "adding host: %s to whitelist host", $attr{"host_name"} if $verbose;
                    update_whitelist_db($attr{"host_name"}, 1);
                    open WHITELIST_FILE, ">> $whitelist_host_file" or
                              syslog $syslog_priority, "Error: unable to open whitelist host file: %s", $whitelist_host_file;
                    print WHITELIST_FILE "$attr{\"host_name\"}\n";
                    close WHITELIST_FILE;
sub add_whitelist_domain {
          # check for null host name
          my ($_domain_name) = $attr{"domain_name"};
          if ($_domain_name eq "") {
                    syslog $syslog_priority, "Warning: missing whitelist domain name attribute";
                    return 0;
          # Open the database on the fly.
          open_whitelist_db() unless $whitelist_db_obj;
          # Is domain already in white list
          $value = read_whitelist_db($attr{"domain_name"});
          # Add domain if not in database
          if ($value == 0) {
                    syslog $syslog_priority, "adding domain: %s to whitelist doman", $attr{"domain_name"} if $verbose;
                    update_whitelist_db($attr{"domain_name"}, 1);
                    open WHITELIST_FILE, ">> $whitelist_domain_file" or
                              syslog $syslog_priority, "Error: unable to open whitelist domain file: %s", $whitelist_domain_file;
                    print WHITELIST_FILE "$attr{\"domain_name\"}\n";
                    close WHITELIST_FILE;
# Demo SMTPD access policy routine. The result is an action just like
# it would be specified on the right-hand side of a Postfix access
# table. Request attributes are available via the %attr hash.
sub smtpd_access_policy {
    my($key, $time_stamp, $now, $count, $domain);
    # Open the database on the fly.
    open_database() unless $database_obj;
    # Open the whitelist database on the fly.
    open_whitelist_db() unless $whitelist_db_obj;
    # Check if domain is whitelisted
          $domain = get_domain_name($attr{"client_name"});
          $count = read_whitelist_db($domain);
          if ($count > 0) {
                    syslog $syslog_priority, "domain: %s is whitelisted", $domain if $verbose;
              return "dunno";
    # Check if host is whitelisted
          $count = read_whitelist_db($attr{"client_name"});
          if ($count > 0) {
                    syslog $syslog_priority, "host: %s is whitelisted", $attr{"client_name"} if $verbose;
              return "dunno";
    # Search the auto-whitelist.
    if ($auto_whitelist_threshold > 0) {
        $count = read_database($attr{"client_address"});
        if ($count > $auto_whitelist_threshold) {
              return "dunno";
    # Lookup the time stamp for this client/sender/recipient.
    $key =
          lc $attr{"client_address"}."/".$attr{"sender"}."/".$attr{"recipient"};
    $time_stamp = read_database($key);
    $now = time();
    # If this is a new request add this client/sender/recipient to the database.
    if ($time_stamp == 0) {
          $time_stamp = $now;
          update_database($key, $time_stamp);
    # The result can be any action that is allowed in a Postfix access(5) map.
    # To label mail, return ``PREPEND'' headername: headertext
    # In case of success, return ``DUNNO'' instead of ``OK'' so that the
    # check_policy_service restriction can be followed by other restrictions.
    # In case of failure, specify ``DEFER_IF_PERMIT optional text...''
    # so that mail can still be blocked by other access restrictions.
    syslog $syslog_priority, "request age %d", $now - $time_stamp if $verbose;
    if ($now - $time_stamp > $greylist_delay) {
          # Update the auto-whitelist.
          if ($auto_whitelist_threshold > 0) {
              update_database($attr{"client_address"}, $count + 1);
          return "dunno";
    } else {
          # Apple
          syslog $syslog_priority, "Temporary message rejection to: <$attr{\"recipient\"}> from: <$attr{\"sender\"}> sent from: [$attr{\"client_address\"}] for: $greylist_delay seconds due to greylisting";
          return "defer_if_permit Service is unavailable";
# You should not have to make changes below this point.
sub LOCK_SH { 1 };          # Shared lock (used for reading).
sub LOCK_EX { 2 };          # Exclusive lock (used for writing).
sub LOCK_NB { 4 };          # Don't block (for testing).
sub LOCK_UN { 8 };          # Release lock.
# Log an error and abort.
sub fatal_exit {
    my($first) = shift(@_);
    syslog "err", "fatal: $first", @_;
    exit 1;
# Open hash database.
sub open_database {
    my($database_fd);
    # Use tied database to make complex manipulations easier to express.
    $database_obj = tie(%db_hash, 'DB_File', $database_name,
                                        O_CREAT|O_RDWR, 0644, $DB_BTREE);
          if ( !$database_obj ) {
                    # don't prevent mail deliveries due to corrupt database
                    my $db_backup = $database_name . "." . time();
                    syslog $syslog_priority, "Warning: open failed for: %s : backing up to: %s",
                                                                                          $database_name, $db_backup;
                    rename $database_name, $db_backup ||
                              fatal_exit "Can't save %s as %s: $!", $database_name, $db_backup;
                    # try again
                    $database_obj = tie(%db_hash, 'DB_File', $database_name,
                                                  O_CREAT|O_RDWR, 0644, $DB_BTREE) ||
                                                  fatal_exit "Cannot open database %s: $!", $database_name;
    $database_fd = $database_obj->fd;
    open DATABASE_HANDLE, "+<&=$database_fd" ||
          fatal_exit "Cannot fdopen database %s: $!", $database_name;
    syslog $syslog_priority, "open %s", $database_name if $verbose;
# Open hash whitelist database.
sub open_whitelist_db {
    my($whitelist_db_fd);
    # Use tied database to make complex manipulations easier to express.
          $whitelist_db_obj = tie(%db_hash, 'DB_File', $whitelist_db_name,
                                        O_CREAT|O_RDWR, 0644, $DB_BTREE);
          if ( !$whitelist_db_obj ) {
                    # don't prevent mail deliveries due to corrupt database
                    my $db_backup = $whitelist_db_name . "." . time();
                    syslog $syslog_priority, "Warning: open failed for: %s : backing up to: %s",
                                                                                          $whitelist_db_name, $db_backup;
                    rename $whitelist_db_name, $db_backup ||
                              fatal_exit "Can't save %s as %s: $!", $whitelist_db_name, $db_backup;
                    # try again
                    $whitelist_db_obj = tie(%db_hash, 'DB_File', $whitelist_db_name,
                                                  O_CREAT|O_RDWR, 0644, $DB_BTREE) ||
                                                  fatal_exit "Cannot open database %s: $!", $whitelist_db_name;
    $whitelist_db_fd = $whitelist_db_obj->fd;
    open WHITELIST_DB_HANDLE, "+<&=$whitelist_db_fd" ||
          fatal_exit "Cannot fdopen database %s: $!", $whitelist_db_name;
    syslog $syslog_priority, "open %s", $whitelist_db_name if $verbose;
# Read database. Use a shared lock to avoid reading the database
# while it is being changed. XXX There should be a way to synchronize
# our cache from the on-file database before looking up the key.
sub read_database {
    my($key) = @_;
    my($value);
    flock DATABASE_HANDLE, LOCK_SH ||
          fatal_exit "Can't get shared lock on %s: $!", $database_name;
    # XXX Synchronize our cache from the on-disk copy before lookup.
    $value = $db_hash{$key};
    syslog $syslog_priority, "lookup %s: %s", $key, $value if $verbose;
    flock DATABASE_HANDLE, LOCK_UN ||
          fatal_exit "Can't unlock %s: $!", $database_name;
    return $value;
# Read database. Use a shared lock to avoid reading the database
# while it is being changed. XXX There should be a way to synchronize
# our cache from the on-file database before looking up the key.
sub read_whitelist_db {
    my($key) = @_;
    my($value);
    flock WHITELIST_DB_HANDLE, LOCK_SH ||
          fatal_exit "Can't get shared lock on %s: $!", $whitelist_db_name;
    # XXX Synchronize our cache from the on-disk copy before lookup.
    $value = $db_hash{$key};
    syslog $syslog_priority, "whitelist lookup %s: %s", $key, $value if $verbose;
    flock WHITELIST_DB_HANDLE, LOCK_UN ||
          fatal_exit "Can't unlock %s: $!", $whitelist_db_name;
    return $value;
# Update database. Use an exclusive lock to avoid collisions with
# other updaters, and to avoid surprises in database readers. XXX
# There should be a way to synchronize our cache from the on-file
# database before updating the database.
sub update_database {
    my($key, $value) = @_;
    syslog $syslog_priority, "store %s: %s", $key, $value if $verbose;
    flock DATABASE_HANDLE, LOCK_EX ||
          fatal_exit "Can't exclusively lock %s: $!", $database_name;
    # XXX Synchronize our cache from the on-disk copy before update.
    $db_hash{$key} = $value;
    $database_obj->sync() &&
          fatal_exit "Can't update %s: $!", $database_name;
    flock DATABASE_HANDLE, LOCK_UN ||
          fatal_exit "Can't unlock %s: $!", $database_name;
# Update database. Use an exclusive lock to avoid collisions with
# other updaters, and to avoid surprises in database readers. XXX
# There should be a way to synchronize our cache from the on-file
# database before updating the database.
sub update_whitelist_db {
    my($key, $value) = @_;
    syslog $syslog_priority, "store whitelist host %s: %s", $key, $value if $verbose;
    flock WHITELIST_DB_HANDLE, LOCK_EX ||
          fatal_exit "Can't exclusively lock %s: $!", $whitelist_db_name;
    # XXX Synchronize our cache from the on-disk copy before update.
    $db_hash{$key} = $value;
    $whitelist_db_obj->sync() &&
          fatal_exit "Can't update %s: $!", $whitelist_db_name;
    flock WHITELIST_DB_HANDLE, LOCK_UN ||
          fatal_exit "Can't unlock %s: $!", $whitelist_db_name;
# Parse hostname to obtain domain name
sub get_domain_name {
    my($in_host_name) = @_;
    my($value);
          my($count) = 0;
          @tokens = split(/\./, $in_host_name);
          $count = $#tokens;
          $value=$tokens[$count-1] . "." . $tokens[$count];
          return $value;
# Signal 11 means that we have some kind of database corruption (yes
# Berkeley DB should handle this better). Move the corrupted database
# out of the way, and start with a new database.
sub sigsegv_handler {
    my $backup = $database_name . "." . time();
    rename $database_name, $backup ||
          fatal_exit "Can't save %s as %s: $!", $database_name, $backup;
    fatal_exit "Caught signal 11; the corrupted database is saved as $backup";
    my $wl_backup = $whitelist_db_name . "." . time();
    rename $whitelist_db_name, $wl_backup ||
          fatal_exit "Can't save %s as %s: $!", $whitelist_db_name, $wl_backup;
    fatal_exit "Caught signal 11; the corrupted database is saved as $wl_backup";
$SIG{'SEGV'} = 'sigsegv_handler';
# This process runs as a daemon, so it can't log to a terminal. Use
# syslog so that people can actually see our messages.
setlogsock $syslog_socktype;
openlog $0, $syslog_options, $syslog_facility;
# We don't need getopt() for now.
while ($option = shift(@ARGV)) {
    if ($option eq "-v") {
          $verbose = 1;
    } else {
          syslog $syslog_priority, "Invalid option: %s. Usage: %s [-v]",
                    $option, $0;
          exit 1;
# Unbuffer standard output.
select((select(STDOUT), $| = 1)[0]);
# Receive a bunch of attributes, evaluate the policy, send the result.
while (<STDIN>) {
    if (/([^=]+)=(.*)\n/) {
          $attr{substr($1, 0, 512)} = substr($2, 0, 512);
    } elsif ($_ eq "\n") {
          if ($verbose) {
              for (keys %attr) {
                    syslog $syslog_priority, "Attribute: %s=%s", $_, $attr{$_};
                    if ( $attr{"request"} eq "smtpd_access_policy" ) {
                              $action = smtpd_access_policy();
                    } elsif ( $attr{"request"} eq "whitelist" ) {
                              $action = add_whitelist();
                    } elsif ( $attr{"request"} eq "whitelist_domain" ) {
                              $action = add_whitelist_domain();
                    } else {
                              fatal_exit "unrecognized request type: '%s'", $attr{request};
                    syslog $syslog_priority, "Action: %s", $action if $verbose;
                    print STDOUT "action=$action\n\n";
                    %attr = ();
    } else {
          chop;
          syslog $syslog_priority, "warning: ignoring garbage: %.100s", $_;

Upload Failed. The server storage quota has been exceeded

Dear All,
I have an Excel file on Document library which is more than 100Mb. I am working with it daily (Simple edit, update and save). Since yesterday I am getting error message "Upload Failed. The server storage quota has been exceeded. Save a copy". But
i have 10GB quota (I have checked in CA). Other users are fine. I am only the person who get this message. any idea?
Best Regards
lasantha

Were are you storing this file?in Mysite Document library or in general site document library? Considering other users are not facing problems i guess personal quota on mysite is exceeded
Go
to your Central Administration à Application
On the Application Management page, in the SharePoint
Site Management section, click Quota Templates.
On the Quota Template page, you can see the Personal
site’s Limit site storage is set to 100Mb by default
Make it 200mb

10.9 Server mail public folders missing after upgrade cannot get them back HELP

Help after upgrade my public folders dissapeared when using the same configuration used in previous ML server Mail would not work
Help Please.

Did you enable the ACL plugin (per instructions above) ?
create an ACL file
/Library/Server/Mail/Data/mail/public/dovecot-acl
with the contents something like this:
user=jeff lrwstipekxa
authenticated lri
This would give user jeff full access
authenticated users could drop files, but not read
Thats just an example.
Read-up on it here
http://wiki.dovecot.org/ACL
Make sure you give each subfolder an ACL.
Once setup, new folders created via imap will inherit the ACL from parent.

Could not connect to the server mail; the connection refused

Dear Sir/Mam
The thuderbird was working fine. All of sudden, when I click on Thunderbird it is showing the following message "could not connect to the server mail; the connection refused". I am attaching the connection setting in this mail. Please help me out.
Kind regards,
Server type: IMAP
Server Name: mail.ncbs.res.in
port: 993
Connection security: SSL/TLS

https://support.mozilla.org/en-US/kb/problems-sending-and-receiving-messages

Yosemite Server Mail and Google Domain Relay

I want to simply use the server to send automated emails from scripts. I have server installed. Over the course of two days I've have followed several posts:
http://www.anujgakhar.com/2011/12/09/using-macosx-lion-command-line-mail-with-gm ail-as-smtp/
http://blog.anupamsg.me/2012/02/14/enabling-postfix-for-outbound-relay-via-gmail -on-os-x-lion-11/
And the updated Yosemite version here:
http://blog.anupamsg.me/2013/12/22/enabling-postfix-on-osx-as-a-relay-revisited/
Yosemite Server configuration
http://krypted.com/mac-security/configure-the-os-x-yosemite-server-mail-service/
I've gotten no where. In my last attempt all sasl errors and no mech connections had stopped but mail did not appear to go anywhere. No trace. I stumbled across a post that said ssl connections from Mac OS X Yosemite are broken and just don't work.
Now the real rub. I have gotten the same thing working with Linux in 5 minutes following this post:
https://rtcamp.com/tutorials/linux/ubuntu-postfix-gmail-smtp/
Then within an hour my crontab and scripts were written, debugged, and blissfully sending email.
I would rather run this from my Mac server. I understand that this may become an in-depth discussion/debug session (remember the old sendmail.cf day?!) and would greatly appreciate someone's mentoring here.
-Tim

Hi,
maybe it helps or not, I solve a other performance problem which is more related to the mailbox speed but this error on client side is gone afterwards:
In Yosemite there is still also a problem with the automatic settings detection in Mail.
That means that the application try's to find a working authentication mechanism in combination with different ports and encryption.
So far so good, this feature would be okay but the application never stops to do that. So we are shortly connected but the connection becomes invalid again.
This leads to performance issues and the application becomes very slow!
If you refer your client log file maybe you can see some "Failed to start the SASL connection" issues (coming from Mail.app).
In case that you are running a OS X Server which is used by Mail you will see in /var/log/mail* /Library/Logs/mail* various login failures. In case that you have enabled the Adaptive Firewall it can be happen that your IP is blocked for 15 minutes.
Of course this must not be a issue for everyone I believe it strongly depends on your email server / provider which auth. stuff is supported or enabled.
To solve it:
1.) Open the Mail Preferences
2.) Goto "Accounts" and select your Provider/Account
3.) Klick Enhanced (the last right tab)
4.) Disable the automatic settings detection (first checkbox)
5.) In case you didn't enable "MailDrop"
This works in Mail 8.1 on Yosemite 10.10.1

Server Mail Quota

Similar Messages

Maybe you are looking for