Allowing mail to inbox eventhough exceeded mailbox quota

Is it possible to allow mail to continue coming to the user's inbox even though it has exceeded the mailbox quota? We would like to allow mail to continue coming in but block the user from replying e-mail until he has cleared his mailbox.
I'm running Messaging Server 6.2-8.04 on Solaris 10

Hi,
Is it possible to allow mail to continue coming to
the user's inbox even though it has exceeded the
mailbox quota? We would like to allow mail to
continue coming in but block the user from replying
e-mail until he has cleared his mailbox.Although this may sound like a simple enough request, the devil tends to be in the detail.
Let me start by saying that blocking a user from sending emails is difficult unless you have a strictly controlled environment namely, all users are forced to authenticate when sending emails (so you can identify them by username) OR they only have access to webmail/UWC to send emails. Otherwise if they use any email client they can just change their FROM address and you have no way of 'blocking' their emails since you can't identify that they are the ones sending it.
So does the above apply to your situation?
On the second front, allowing emails to be delivered to overquota accounts. This is possible by sending emails via the special tcp_tas channel which overrides quotas.
Do you want all emails to have the ability to send to overquota accounts or do you just want select users/lists/sending systems etc. to have this ability (so for example just users X,Y,Z and any emails from the system 1.2.3.4?
Regards,
Shane.

Similar Messages

Exceeding mailbox quota

I keep getting this message even though Ihave deleted all my e-mails. people also get this message below when they send me an e-mail:
delivery failure:
The message you sent to entrac-petroleum.com/info was rejected because it would exceed the quota for the mailbox.
What do I have to do to solve te problem. BT help desk did not help.
thanks

HR wrote:
I keep getting this message even though Ihave deleted all my e-mails. people also get this message below when they send me an e-mail:
delivery failure:
The message you sent to entrac-petroleum.com/info was rejected because it would exceed the quota for the mailbox.
What do I have to do to solve te problem. BT help desk did not help.
thanks
Hi. Welcome to the forums.
The problem is with the email address on that domain entrac-petroleum.com when sending emails to it.
Can you drop a reply back with some extra info regarding people emailing you, are they emailing a BTinternet email address ?
Are you forwarding emails to that domain by any chance ?, do you have anything to do with them ?
http://www.andyweb.co.uk/shortcuts
http://www.andyweb.co.uk/pictures

Export Mail inbox and sent mailbox to an Outlook 2003 compatible file

I need to export my Mail inbox and sent mailbox to a file or files that can be imported into MS Outlook 2003 on a PC.
I can find menu options for importing files (although no Outlook files) but don't see a menu entry for exporting mailboxes.
Anyone know how to get this done? I'm going to be a very unhappy camper if this can't be done!

Thunder?????????? Would that be shorthand for Thunderbird from Mozilla?
I just bought a new iMac, and although I've had brushes with Macs before (Systems 6, 9.x, and OS X Jaguar) this is my first serious attempt at using a Mac. Switching from Windows.
But I'm not new to personal computers, my first one was, and still is as I have it in storage, an Atari 800 if you are old enough to have heard of those.
In anticipation of using either Boot Camp or Parallels (I've settled on Parallels because I want "side-by-side operation), I did take the precaution of setting Mail up to leave copies of the emails on the server. So now I only have to deal with my Mail sent mailbox.
Ken

Mailbox Quota Wrong

Hello,
I keep getting a message saying that I've exceeded my mailbox quota. When Get Info on the IMAP mailbox, it reports:
Currently Used 20.8 MB
Capcity 15.0 MB
Then it lists:
Inbox: 10.3 MB
Sent: 110 KB
Personal Folder: 37.2 KB
Junk: 0
Trash: 0
Just looking at the folder list I don't see the total anywhere near 20.8MB.
When I actually add up the sizes of all messages in my Inbox, it totals around 146 KB (not MB).
So I'm confused. Anyone have any clue what's going on?
Thanks
Tony.

Hello Tony.
You may try using another mail client, such as Thunderbird, and see what happens there.

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
#       mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in
#   the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

Unity Connection 8.5 mailbox quotas

I configured mailbox quotas for user mailbox
Send/receive quota is 3 Mgb
Send Quota is 2 Mgb
Warning Quota is 1 Mgb
User mailbox is already 3.5 Mgb
HOwever, when i call this user from internal or external number - i still can leave a mesage for this user ( i expected system DOES NOT ALLOW to leave any new mesage for this user because his voicemail box is already exceeds Send/receive quota which is 3 Mgb )
Checkbox for option "Full Mailbox Check for Outside Caller Messages"is already checked in
What is wrong in this config ?

Here is how send/receive quotas impact things:
Quota Handling for Outside Caller Messages
By default, if an outside caller attempts to send a message to a user whose send/receive quota has been exceeded, Cisco Unity Connection allows the caller to record a message for the recipient. This can be changed by checking the Full Mailbox Check for Outside Caller Messages check box on the System Settings > Advanced > Conversation page.
If the recipient mailbox has not yet exceeded the send/receive quota at the time an outside caller records a message, but the quota is exceeded in the act of delivering the message, Connection delivers the message regardless of the quota or the setting of the Full Mailbox Check for Outside Caller Messages check box.
Quota Handling for User-to-User Messages
If a user whose voice mailbox has exceeded the send quota signs in to Connection and attempts to send a message to another user, Connection indicates that the send quota has been exceeded, and does not allow the sender to record the message. If the user calls another user and is forwarded to a voice mailbox, the user is able to leave a message, but the message is sent as an outside caller message.
If a user attempts to send a message to another user whose mailbox has exceeded the send/receive quota, or if the quota is exceeded in the act of delivering the message, Connection sends a nondelivery receipt to the message sender.
Connection delivers read receipts and nondelivery receipts to users regardless of whether their quotas have been exceeded.
HTH,
Chris

Creation of Microsoft Azure Website failed. Cannot move or create server. Subscription ' id ' will exceed server quota.

I'm trying to create a new MVC website with azure cloud server. However, when creating my project/solution in visual studio I get the following error.
Creation of Microsoft Azure Website failed. Cannot move or create server. Subscription '<id>' will exceed server quota.
During the day I created several MVC projects, as a learning exercise, and it worked fine. Now it's failing every time I create a new MVC website with Azure.
Every time I created a website, I have always deleted any generated Azure sites and databases via the management portal. Currently I have no websites in Azure. Thus I don't see how I've reached a quota,
Any ideas what might be going wrong?
My subscription is pay as you go.
Thanks for your time,
Rob

Hi,
It might be due to various other resources (sql DB, application insight, etc) that you may have created while deploying earlier websites, and filled up your Quota. Due to which, creating new resources would exceed the quota limit.
Check for the unused resources and clear them. It may clear the error and allow you to create new websites.
Otherwise, It should be an Account related issue than Technical issue. I suggest you contact Azure support, it is a best choice for you, Please contact support team by creating a support ticket at
http://www.windowsazure.com/en-us/support/contact/
Regards,
Manu Rekhar

Mail Crashed - Inbox Deleted - Trying Data Recovery - Help

I am running a G4 Powerbook 10.3.9 and Mail 1.3.11 locked up and crashed. My old Inbox is wiped out. Last July, I accidentally deleted my Sent emails but that was intentional (as in I thought I was in the Trash window, selected All and Deleted but as I was in my Sent window, that's what got deleted). I bought Data Rescue II and was able to restore almost all of my deleted Sent email.
So I tried to do the same today. I recovered large "mail" files to the CBR folder. These files are marked as Mail-00034.mbox where the number goes up. Some files are 100MB while others are smaller. I also recovered the INBOX.mbox file but I cannot import either file type into Mail (as in the Import Mailbox function).
I have recovered plenty of big files but none that can be imported into mail. Any thoughts. Thanks in advance

The current INBOX.mbox contents include
content_index 128K
Info.plist 4K
mbox 236K
mbox.SKindex 30.3MB
mbox.SKindex.isValid 0K
tableofcontents 4K
The file size of the mbox.SKindex does not make complete sense as I have only about a dozen or so emails currently in my INBOX (those received after the crash). Either way, the entire INBOX file is way too small (compared with a 1.2G SENT box). I believe the INBOX file size was around 900MB prior to the crash.
As for what the Data Recovery II program found, it recovered a folder called CBR and in it is a folder called Mail, and in that a folder called AppleMail, and in that about 120 files (using the mailbox icon) all labeled "Mail-######.mbox" where the ###### refers to 00001 (the first file) up to 00120 (the last file). File sizes vary from several at 100MB down to 1MB. There is a great deal of data there. When I try and import these files into Mail, the import seems to work but the IMPORT folder is empty.
Data Recovery also got a INBOX.mbox file that when opened, is blank. It too reads as 30.3MB (vs. the 30.7MB INBOX.mbox file noted above). When this is opened, there are 0 emails in it.

Best Practices for Setting up MailBox Quotas in Unity Connection.

Hi all,
I've just completed migrating from Unity 4.0.5 to Unity Connection 8.0.2c and all seems to be working well at the moment. I am looking into setting up quotas for subscriber mailboxes and I would like to find out what are the rules of thumb when assigning disc space to user mailboxes ? and How much disc space does it take for a one minute message ?
Thanks in advance for any inputs/suggestions !!!
D.

D. Tran,
Here are some things to consider:
–Mailbox Quotas
•Specifies a mailbox size in MB for Warning, Send, and Send/Receive Quotas on mailboxes
•Can be applied system-wide and customized on a per-user basis (maximum mailbox size is 2GB)
•Default Warning Quota = 12 MB (25 min of recording with G711)
•Default Send Quota = 13 MB (27 min of recording with G711)
•Default Send/Receive Quota = 14 MB (29 min of recording with G711)
When you use G711, the space requirements for a message are:
•480Kb/min when using G.711
–Message Aging Policy
•If enabled, it applies system-wide but can be disabled on a per-user basis.
•If disabled, no message aging policies are applied and cannot be enabled on a per-user basis.
Should you need to be more aggressive in your Message Aging Policy, you can optionally choose to move saved messages to the Deleted Items folder within a specified timeframe. This is disabled by default.
I typically recommend giving users access to the deleted items (it allows them to access deleted messages for a period of time after they delete them). This is set in the Class of Service here:
–Class of Service > Message Options > Uncheck “Delete Messages Without Saving to Deleted Items Folder”
Hope this helps.
Hailey
Please rate helpful posts!

Messages In Inbox and sent mailbox have disappeared

I have been using my mac e-mail for a considerable time with no problems however in the last month, I have lost virtually all of my messages in both my inbox and sent mailbox> I have checked my preferences and the deletion of e-mails is set to 'never'. Does anyone know what might be causing this and how to stop it from happening. Thanks.

You’re welcome.
If the *.emlx files associated with those messages are gone from the filesystem, rebuilding mailboxes or re-creating the index cannot make them reappear.
There is no way to know what may have happened if you don’t know when it happened and what did you do that could have a bearing on it. What you mention about moving data between computers could certainly have a bearing on it when it happened the first time, but there is no way to know what the problem exactly was in that case either with the information you’ve provided...
If the messages are nowhere to be found and you don’t have a backup, you may try to salvage as many deleted *.emlx files as possible with a data recovery tool such as Data Rescue II, TechTool Pro, or FileSalvage. Of these, the only one I know for sure that can currently recover deleted *.emlx files is FileSalvage. Beware, however, that anything you’ve done with the computer since the messages were deleted may have caused them to be overwritten, which makes me believe your chances of recovering them now are pretty low...

Mailbox quota on Cisco unity, quick question

Hello guys,
I was facing a probleme with an unity connection cluster. I had a message which tell something like that
"no disk space avalaible, user cannot depose message..."
So I tchecked my space on disk (screenshot attached) with the show cuc dbserver diskspace command, but I don't know what I need to see to diagnose an eventual problem.
I changed the mailbox quota for my users from 15 to 40MBytes and all is right now.
But what is the good practise ?
- tell my user to delete their mailbox ?
- expand my mailbox quota ?
- others ideas ?
Thanks for your good ideas
Kévin

I would consider implementing a aging policy. You could notify users via email before aging out messages.
I will be careful expanding mailbox size unless your system is over provisioned to handle your environment. Also larger mail store will cause issues with daily backups and etc.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx/8xcucsag190.html#pgfId-1050845

Where does Mail keep inbox and sent box?

I need to sync my office machine and my laptop from time to time. I can sync the Mailboxes excepting the inbox, sentbox, and drafts (and junk), from the user/library/mail/mailboxes. Should I just sync the Mail folders, or is that likely to screw something up? Or can I find the inbox and sent boxes somewhere else and sync them separately? Both machines are running Mail v3.6, but I know some little things display differently on the two machines. Who knows how deeply those differences go...
I don't want to get involved with mac.com to do this, it's not a daily requirement.

The inbox and sent mailboxes should be in /Mail/your email account/ and the others in /Mail/Mailboxes/

Percentage free in mailbox quotas are wrong

Mostly a cosmetic issue, but kind of worrying.
The 'percentage free' column for mailbox quotas in Server Admin is completely inaccurate.
Nearly all accounts are listed as 100% or 99%, despite actually being 30% free or some such other markedly different value. One account is even listed as 101% free.
This doesn't bother me too much, because the actual values are there as well. The only issue might be whether users are getting their warning messages in time to actually do anything about it.
In one or two cases the quota has been filled to the extent where the user cannot even delete messages to free up space; an IMAP quota limit error returns when attempting to delete messages in Mail.
By the way, cyrus-quota gives accurate results.
Any ideas?

I have a similar problem, in Server Admin, under Mail > Maintenance > Accounts.
I have 5 users and, let's say "user1" and "user2" show negative values under "Quota Used (MB)". As far as I managed to search there is an issue in Quota over 2 Gigs. User 1 and 2 are over that quota. All the mail that is in user mailboxes are imported via Mail.app from another pop3 server, and Outlook Express 2003 also from a pop3 server. Now we are using 10.5.5 leopard server (Imap). Mail is working fine as far as I can see, and mailfbr shows corect values. Please if anyone has this bug post here or let me know if this is a known bug.
Thanks!

Every time I move emails from the inbox to another mailbox, then click on any mailbox, and then go back to the inbox, the moved messages have returned to the inbox

Every time I move emails from the inbox to another mailbox, then click on any mailbox (the emails are there fine), and then go back to the inbox, the moved messages have returned to the inbox. I have moved them out of the inbox to other mailboxes again and again, but then they keep showing up in the inbox again as soon as I click on any mailbox other than the inbox. Very frustrating.
This has only happened since I installed Mavericks on both my Macbook Pro and my iMac. It happens on both of them.
Any ideas how to fix it?
peter

This may be one of the known issues with Gmail and it's IMAP settings working with Maverick's Mail.
It all comes down to if you have the ALL MAIL folder visible or not via IMAP.
If you do not, then you get the behavior you are describing.
If you do have ALL MAIL visible, then there isn't a problem.
Odd, I know.
Anyway, check out this article on Wired which describes the problem and work around. You may have to click on the NEXT button at the top of the window to advance to the proper gallery image that describes this issue:
http://www.wired.com/gadgetlab/2013/10/mavericks-issues-and-fixes/#slideid-23460 1

Mail won't let me respond quoting the text of the original message

Mail does not allow me to respond to an email quoting the original message.
I tried going to preferences>composing and selecting "quote the text of the original message." under responding. But Mail doesn't allow me to select this option.
I've also tried selecting the text in the email that I want to respond to in my reply message and that doesn't show up when I hit reply.
Has anyone else encountered this problem?

I think I've discovered what was causing my problem. In the "Preferences, Composing" section, there's a pair of radio buttons for "When quoting text in replies or forwards". Mine was set to "Include selected text if any, otherwise include all", which means that if you have any text selected, only that text is included. It would appear that I was often selecting text while browsing through.
Setting the other radio button ("Include all of the original message") makes the behaviour go away.
I suspect that this may not be the only problem in this thread, but the fix worked for me!

Allowing mail to inbox eventhough exceeded mailbox quota

Similar Messages

Maybe you are looking for