Mailbox Limits
Hello ,
Environment : Exch 2010 sp3 ru3
Need to extract report of mailbox sizes, their limits,database default true or false.
I am trying Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited |Get-MailboxStatistics | Select-Object DisplayName,
ServerName, Database, TotalItemSize, ItemCount, StorageLimitStatus | Sort TotalItemSize -Descending | Export-CSV C:
\MailboxStatisticsReport.csv but not getting required output
Regards, Ajit
You can try the below script. A good resource about this is available at http://gallery.technet.microsoft.com/office/Get-Exchange-2010-Mailbox-00204388
You could use this script :
$dir = read-host "Directory to save the CSV file"
$server = read-host "Exchange Server Name"
get-mailboxstatistics -server $server | where {$_.ObjectClass -eq "Mailbox"} |
Select DisplayName,TotalItemSize,ItemCount,StorageLimitStatus |
Sort-Object TotalItemSize -Desc |
export-csv "$dir\mailbox_size.csv"
Moreover, you can try a exchange reporting
tool to get desired report.
Similar Messages
-
I have an Exchange Server 2010 mailbox which receives alert messages on the order of 800,000+ a day. I am working on getting the developers to change their code, but in the meantime, I am looking for ways to clear out the mailbox. I have
a Search-Mailbox script with the -deletecontent switch that works, but there appears to be an upper limit on the number of messages it can handle. Based on my experience the upper limit lies between 300,000 (my script does work here) and 690,000 (my
script does not work at this level).
I have tried using a Retention Policy, but that didn't work either. I am currently looking at the following options:
1) Put in an Inbox Rule that permanently deletes the error messages.
2) Investigate using a Transport Rule.
3) Letting the mailbox fill up again and let the Developers get the message that they need to clean up their code. - my favorite as I believe anything else is just enabling bad behavior.
Thoughts?
TIA
Nate
ncHi,
In your case, you can create Inbox rule or transport rule to delete these messages.
From my point of veiw, you need to figure out the root cause of this issue why this mailbox receives a large amount of alert messages.
You can check the application log to see if there is any related events.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support -
I am looking for an easy way to check individual mailbox limits without manually clicking my way through 3000 users.
I have looked up the Admin API for running a simple vbscript but the mailbox limits field isn't listed in the API reference. Surely someone has had to do this before?
thanks!Oppss!! Sorry for the confusion.
You can have a listing of the Mailbox Size Limit for each user doing a maintenance of the post office.
Try this.
1.-Do a GroupWise Mailbox/Library Maintenance
Select Action: Analyze/Fix Database
Select: Structure
Select: Contents
Select: Collect Statistics
Databases. Users (Selecet Message if you want)
Results: Send the results to you email.
2.- Wait by the end of the process
3.- Open the log file and search for "Disk space management values"
You can observe the following values for each user:
.- Size Limit - (n)KB
.- Threshold - (n)%
.- (n)kbytes in use by user's mail
I hope this help to you needs. -
What is the maximum size for mailbox per user (Exchange 2007)
Hello,
I'd like to know:
What is the maximum size per mailbox, and is it not recommended to exceed 3 GB and about the items how many is the maximum per folder (inbox, .. )
I've Exchange 2007 SP2, Outlook 2007 and 2010.
Thank you.Hi
There is no size limit on mailboxes up to the maximum size of your database. I normally recommend 2GB mailbox limits if you have some form of archiving in place. If you have no archiving in place then the limit should be set at the amount of
data people need to keep - it is not a good idea for people to store mail in PST files because there is a limit on their mailbox.
See this article for item count recommendations:
http://support.microsoft.com/kb/905803
Also you need to upgrade your Exchange 2007 server to SP3 ... SP2 has been out of support for nearly 3 years already:
Exchange 2007 Support Lifecycle
Steve -
Hi All,
Hope ur all doing very well..I have one general question regarding Mailbox Size Limit, let say I have mailbox Database DB1 it has no size limit defined. In this DB1 I have mailbox MB1, now let say MB1 is 5 GB in size and it has individually defined mailbox
size limit 10 GB, since it is already 5GB in size, what will happen if I change its limit from 10GB to 3GB?
VirgoHi All,
Hope ur all doing very well..I have one general question regarding Mailbox Size Limit, let say I have mailbox Database DB1 it has no size limit defined. In this DB1 I have mailbox MB1, now let say MB1 is 5 GB in size and it has individually defined mailbox
size limit 10 GB, since it is already 5GB in size, what will happen if I change its limit from 10GB to 3GB?
Virgo
Individual mailbox limits override any database set limits, so nothing will happen. The user will never know the difference.
If you change the mailbox quota limit from 10GB to 3GB, then the mailbox will be overquota and the user will not be able to send or receive mail.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
Get-mailbox storage limit view
I currently use this command to view the mailbox limits on the Exchaneg Server. I need to know what other commands to add in PowerShell so I can also view what the issue warning and prohibit send are at. thanks.
Get-mailbox |Get-MailboxStatistics| select DisplayName,Database,TotalItemSize,ItemCount,storagelimitstatus | export-csv C:\mailboxsizes.csv -Hi Badlands
For Quota on Individual
Get-Mailbox | Select-Object Displayname,Database,@{Name='TotalItemSize'; Expression={[String]::join(";",((Get-MailboxStatistics -identity $_.identity).TotalItemSize))}},@{Name='ItemCount'; Expression={[String]::join(";",((Get-MailboxStatistics -identity
$_.identity).ItemCount))}},IssueWarningQuota, ProhibitSendQuota | export-csv -path "c:\mailboxsizes.csv"
For Quota on Database
Get-Mailbox | Select-Object Displayname,Database,@{Name='TotalItemSize'; Expression={[String]::join(";",((Get-MailboxStatistics -identity $_.identity).TotalItemSize))}},@{Name='ItemCount'; Expression={[String]::join(";",((Get-MailboxStatistics -identity
$_.identity).ItemCount))}}, @{Name='IssueWarningQuota'; Expression={[String]::join(";",((Get-MailboxDatabase -identity ($_.identity).DataBase).IssueWarningQuota))}},@{Name='ProhibitSendQuota '; Expression={[String]::join(";",((Get-MailboxDatabase -identity
($_.identity).DataBase).ProhibitSendQuota))}} | export-csv -path "c:\mailboxsizes.csv"
Cheers
Zi Feng
Zi Feng
TechNet Community Support -
[SOLVED]Issue with Postfix sending to external mail addresses
I'm having a very silly issue with Postfix. I followed the wiki article at [link]https://wiki.archlinux.org/index.php/Postfix[/link], and everything seems to work properly, however I cannot send to emails outside of my domain.
I get the error:
550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!
Here is what the logs say:
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: connect from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: client=localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: reject: RCPT from localhost.localdomain[127.0.0.1]: 550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<sendingdomain.com>
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: lost connection after RCPT from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: disconnect from localhost.localdomain[127.0.0.1]
May 08 16:05:14 my.dns.stuff.org sudo[31476]: me : TTY=pts/0 ; PWD=/etc/postfix ; USER=root ; COMMAND=/usr/bin/journalctl
main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/BASIC_CONFIGURATION_README.html etc.
# For best results, 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 = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/bin
# 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/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /var/lib/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 = mail.sendingdomain.com
# 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 = www.sendingdomain.com
# 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
append_dot_mydomain = no
# 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 = loopback-only
#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
#mydestination = localhost
# 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]
default_transport = error: Local delivery only!
# 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
alias_maps = hash:/etc/postfix/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
alias_database = $alias_maps
# 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) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/bin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
#virtual_mailbox_domains = sendingdomain.com
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf
virtual_mailbox_base = /home/vmailer
virtual_uid_maps = static:5003
virtual_gid_maps = static:5003
virtual_minimum_uid = 5003
virtual_mailbox_limit = 51200000
Any help would be appreciated. Thank you.
Last edited by nadman10 (2014-05-14 14:36:10)Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide -
Offline Address Book and GAL corrupted.
I have and Exchange 2013 cluster with 3 servers all performing both CAS and MB roles. This environment was originally a 2003 server, then 2007, then 2010, and now 2013 so it has been migrated many times in the past. It seems at some point something was missed
and now we are having serious issues.
It started when I was unable to create new profiles in Outlook. After much troubleshooting and digging I found I was also having a problem creating new mailboxes in Exchange and even updating settings such as mailbox limits. When I try to create a new Mailbox
I receive the error:
The LdapRecipientFilter "(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=contact))(objectCategory=group)(objectCategory=publicFolder)(objectCategory=msExchDynamicDistributionList)
))" on Address List or Email Address Policy "\Default Global Address List" is invalid. Additional information: The attribute type 'mailnickname' or its syntax is not defined in the schema.
This all seems to come down to issues with the Global AddressList and the Offline Address List. Thanks to other posts and Google I found that I should simply update these list using Get-AddressList | Update-AddressList and Get-GlobalAddressList | Update-GlobalAddressList.
These commands however through some erros:
Get-AddressList | Update-AddressList
WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
\/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
group" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
administrative group" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
\/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
group" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
administrative group" is invalid and couldn't be updated.
[PS] C:\Windows\system32>Get-GlobalAddressList | Update-GlobalAddressList
WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
\/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
group" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
administrative group" is invalid and couldn't be updated.
Get-AddressList | Update-AddressList
WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
\/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
group" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
administrative group" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
\/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
group" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
administrative group" is invalid and couldn't be updated.
[PS] C:\Windows\system32>Get-GlobalAddressList | Update-GlobalAddressList
WARNING: The recipient "MyDomain.local/Users/HealthMailboxc5809e7b325d447f91bc3d7ea36c15e2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox6d5b50c9e47e4ad283e5ceef43f051e8" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Users/HealthMailbox033a6d5dc2734020861241094e333a83" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox3b9adbecf3224170aa5827a8b9dd8173" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailboxb55608d9ec2c42029346ccf54541fc45" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailbox70d4dd84317b4819a90a2dff0178614b" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 2" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 3a" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/OAB Version 4" is invalid and couldn't be
updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book -
\/o=MyDomain\/cn=addrlists\/cn=oabs\/cn=Default" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Offline Address Book - first administrative
group" is invalid and couldn't be updated.
WARNING: The recipient "MyDomain.local/Microsoft Exchange System Objects/Schedule+ Free Busy Information - first
administrative group" is invalid and couldn't be updated.
From what I read this is due to invalid characters in these entries of the Address Books. If I still had my 2010 box I could go in to the Exchange Toolbox, manage the Address Lists and change the Alias of these entries. I don't have a 2010 box though. All
I have is 2013 and from what I have read there is no way to manage the Address lists through the ECP.
I have tried changing them in the Shell with this command:
Get-Mailbox | Where {$_.Alias -like "* *"} | ForEach-Object {Set-Mailbox $_.Name -Alias:($_.Al
as -Replace " ","")}
But this did not work.
How do I fix this issue in an Exchange 2013 environment? Please let me know if more information is needed and thank you in advance for any help.Hi,
I suggest we rebuild the GAL by contacting a Microsoft Support, or it will be a non-support environment. For your reference, a simple version of the rebuilding steps:
1. Remove the current GAL
2. Run “/PrepareAD” and it will recreate the GAL.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support -
Provision for capacity alerts for Exchange 2010 servers on SCOM
Hi All,
This is one urgent requirement, please help.
We have around 25 exchange servers in our environment, we need to configure alerts to limit the threshold to 80-90% of mailbox.
My requirement is to configure SCOM alerts for mailboxes hosted on databases servers. In our environment we have set that a database should contain 208 mailboxes. So we need to have alert when mailbox limits reaches to 80% or 90% (say 180 mailboxes in number).
Please let me know hw to configure this alert and thresholds in SCOM?
Best Regards,
Harsha L PHi,
Have you import the Exchange management pack to your maagement group?
We may need to check the management pack guide to find if there is any monitor or rule which can do this.
Regards,
Yan Li
Regards, Yan Li -
How can I visualise Emails with large attachments?
Background: Working in corporate environment with Exchange with Mailbox limits.
From time to time I'm running out of quota, then I need to move Mails locally (by Smart Mailbox) or delete them.
Insted of doing this reactive I would love to see Emails marked in color (rules?) so I can take care of them while I read them so I don't need to touch them twice.
Thx
-Walter
P.s. Using Mail, not Outlook.What email service are you using to write your emails? Or are you using a Thunderbird?
If you use a webmail service like hotmail or GMail, you can probably find the information you are looking for in that service's help documents. Look for a link called "help" or "support" on the site where you read your emails. -
Real brain bender: virtual host or omni portlet issue? Take the challenge
We are having problems with a portal page that displays several omni portlets on several tabs. Here's the situation:
The page consists of 5 tabs, each representing a different demographic characteristic. On each tab there are four omni portlets. One omni porlet represents a selection list. The user makes a selection, which triggers an omni portlet event to pass the selection criteria to a page parameter. The other three omni portlets on the tab read the parameter value and retrieve data according to the selected parameter value.
Example: The user selects the Age tab and selects the link representing data for the Central Region. The omni portlet's event populates the page's "region" parameter with the value "Central." The other three portlets on the tab retrieve their respective data where region = 'Central'.
Since all the tabs on the page represent different demographic characteristics, the omni portlets on all the other tabs also perform their queries where region='Central' so that the user will see Central Region data displayed regardless of what tab they navigate to.
Also, when the user navigates to another tab and selects a different region, all the omni portlets on all the tabs perform their respective queries to capture data where region=<selected region>.
The page performs correctly until we configure a virtual host. In that case, when a user makes a selection of a particular county in one tab, the queries are performed but the page displays with a tab in view other than the one where the user made the selection.
Example: the user navigates to the Age tab and selects region='Central'. Then the user navigates to Gender tab and then Living Situation tab, viewing the results on each tab. Now the user returns to Gender tab and selects region='Western.' The portlets perform their queries and the page re-displays with the user on Living Situations tab, rather than Gender tab where the selection was made.
Obviously, we want the user to stay put on the tab in which they make their selection. I think it's a problem with the virtual host configuration. My DBA thinks it's a problem with the way the page is built. Has anyone else run into this kind of thing? Is there a trick to using Virtual Hosts?Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide -
DR design options - leveraging a "dial tone" in the DR datacenter
Hello,
I am looking to design a DR solution for our existing Exchange 2010 org. Currently, we have one DAG, two mailbox servers, three combo CAS/hub servers. The mailbox servers are connected to an EMC SAN. Unfortunately, there are no mailbox
limits so user mailboxes in some cases are huge, >10gb for a few. Fortunately, we only have around 300 mailboxes.
For DR, we have a site in Colorado that will have Internet access and we can failover all web components like OWA and ActiveSync, but we don't have the storage to accommodate what we have in our main production datacenter.
The business has indicated that they would support a solution where if there were a disaster and we lost the production datacenter, we would failover to Colorado and users would essentially get an empty mailbox to provide a dial-tone. So they can send
and receive mail, utilizing OWA, Active Sync and Outlook, but they will not have access to any of their previous data while in DR mode.
I am hoping to get some feedback from people who may have implemented a similar solution.
Thank you in advance.
JCI do agree it is not the most desirable solution, but I can only work with what I have available to me. But in answer to your last question, I actually think this solution would only be worth the effort if it were to be a long term solution. The
thought of going through the hassle of recreating user profiles and merging data back for an outage that only lasts a few hours or days seems pointless. Based on my calculations, we would have have enough storage in DR for at least a couple of months
if we start with zero. Of course, this is with the assumption that the business has signed off on the users not having access to older data while in DR mode. As long as the users can't lynch me personally, I'm cool with it.. ;-)
Well, in that case, it will work :P
I assume you will be able to do backups in the DR DC and otherwise most things will work as expected to keep Exchange happy.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
Limits for email move to archive mailbox?
Exchange 2010/Outlook 2010
Is there a limit to how many (or size) for moving emails from Exchange (on premise mailbox) to the Exchange Archive (on premise mailbox) using drag and drop within the outlook client?
I have a user who says it will work on the first move and fail on the second attempt. I do not know how much data they are trying to move, I do not have that information. Is there a limit? Is that limited by memory, network or some sort
of limit? Would cached or non-cached outlook make a difference?Hi,
I suggest to use this command to view statistics for that user's archive.
Get-MailboxFolderStatistics -Identity usename –Archive
Then compare the results with
mailbox archive quota.
More information for reference
Archive Quotas
https://technet.microsoft.com/en-us/library/dd979795%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396#AQ
Configure Archive Quotas for a Personal (On-Premises) Archive
https://technet.microsoft.com/en-us/library/ee633489(v=exchg.141).aspx
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support -
How to fetch size limits of users mailboxes in exchange 2007
Hi Team,
I've a list of users who scattered on different SGs of same server in exchange 2007. The Exchange Server is SCC cluster.
My query is to input the user list (.txt file) and find out the storage quota limits (IssueWarning, Prohibit Send and Prohibit send and recive) currently set on listed user mailboxes. The output shouold be in .txt or .csv file.
Please help me in writing the power shell command to fetch the required details
Thanking you
regards,
MiddaThis will read the names from the txt file and export the details to a csv file
Get-Content "C:\userlist.txt" | ForEach-Object {Get-Mailbox $_ | Select-Object DisplayName, IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota} | Export-Csv C:\Userquota.csv
But it will show unlimited if the user having database default quota. Below command will show you the database quota settings
Get-Mailboxdatabase | Select-Object Name, IssueWarningQuota, ProhibitSendQuota, ProhibitSendRe
ceiveQuota
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
Exchange 2007 to Exchange 2010 cross forest simultaneous mailbox move limits
Hi All,
I am testing the throughput of mailbox moves from Exchange 2007 to Exchange 2010 cross forest. Single mailbox moves seem to be quite fast and I am not concerned about network, disk IO or server resource limitations, however I have not tested multiple simultaneous
mailbox moves to determine what the Exchange limitations are. If anyone could identify the limitations of the items below it would be much appreciated:
Limit of Exchange 2007 simultaneous mailbox moves per database
Limit of Exchange 2007 simultaneous mailbox moves per Mailbox server
Limit of Exchange 2007 simultaneous mailbox moves per CAS server
Limit of Exchange 2010 simultaneous mailbox moves per database
Limit of Exchange 2010 simultaneous mailbox moves per Mailbox server
Limit of Exchange 2010 simultaneous mailbox moves per CAS server
Any other Exchange 2007 or 2010 hard coded limits
Thanks in advance.
Michael.My usual answer to this question is that Microsoft set these limits for a reason. Increasing them may not offer you much in the way of benefits if you end up slamming the server. I generally recommend that you leave them alone.
I have had occasional opportunities to change these constraints, most notably back during a migration to Exchange 2003 and international mailbox moves (Asia to U.S.) where the limiting factor was network latency. I was able to increase the number of
concurrent threads to 16 from the default 2 and there was still available bandwidth because the process was limited by the latency.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Maybe you are looking for
-
How can I use my Iphone as wireless internet receiver for my MacBook Pro?
Can anyone tell me how to use my Iphone 4 a wireless internet receiver for my macbook pro? Thanks & greeting from the Netherlands! Matthijs
-
I read images which are 300 DPI . I get it in BufferedReader, and do some pixel manipulation. When I save those pics as PNG or JPEG the image DPI becomes 72 DPI. There should be a way to set image DPI when converting from Bufferedeader to .pgn or .jp
-
Powerbook 17" S-Video Out to TV monitor
Hey all, If we go out of the S-Video out on a Powerbook 17" 1.5Ghz, and in to a television's Video In, is there a way to use the TV monitor for video only? Like how you can do that on a G5 tower, take the video out and make it extend your real estate
-
Opening files in cc on yosemite
I was finding that I couldn't open anything past 3 times in Photoshop, Illustrator, and even Dreamweaver. I still can't, but I've found out that if you use the shortcut, and tap at least 3 times, you will get the window to open where you can select
-
Trouble Installing WD My Book World Edition 1TB
Hi, Yesterday I bought a a network hard drive at Bestbuy to use with my two 13" Macbooks which both run Snow Leopard. The Mac section of the HDD manual basically says, "plug it in. it works." I wish this were the case. Some times my computer recogniz