Very delayed mail delivery

I have been eperiencing delays of up to 8 hours for delivery of email seommy verizon.net account for the past week. Is something being done to correct the issue?

I, too, have been having some messaged delayed for as much as a day and sometimes more. I may try to get on a live chat with a Verizon rep this morning.

Similar Messages

Delayed mail delivery after Rollup 6 install

After updating Exchange 2010 Sp3 to rollup 6, users are reporting that emails delivery is very slow and takes several hours to appear in Outlook. Mail delivery in OWA is instant.
The problem is fixed by disabling the Exchange cached mode option in Outlook but is not the best solution for laptop users.
Is this a known issue with rollup 6 or any patches available to fix this?
thanks.

Disabling the cache mode means it's not using a OST instead it's online with exchange all the time, if the behavior is only seen when in cached mode then it's having difficulty synchronizing the OST, if you have users with large mailboxes this could be causing
slowness.
Creating a new profile or removing and alternative to a new profile the ost and letting it recreate may solve for now, if you have outlook 2013 you can turn on cached mode but only cache 1 month of data this may be a solution for large mailboxes.
It is possible you have tipped the scales with the rollup install and are taxing the server just a little to much, is it a VM can you add Memory and see if there is some relief.
You can also try to run the exchange best practice to see if something else is going on.

Delayed mail delivery error with 1 internal user

We have an Exchange 2010 with 100 mailboxes 1 of our users is not getting any emails suddenly today after a server restart last night . She is not getting email from internal or external to the organization. All senders get a delayed delivery response
back from the exchange server when sending a message to her. All other users can send/receive internal and external. I ran the mail flow tool and there were no red checks for errors. User is not disabled in exchange nor in AD. I am lost at where to go next.

Yes they are sitting in the queue. Here is one test message that we tried to send:
Identity: emailserver\7223\31205
Subject: Test
Internet Message ID: <[email protected]cal>
From Address: [email protected]
Status: Ready
Size (KB): 6
Message Source Name: FromLocal
Source IP: 255.255.255.255
SCL: -1
Date Received: 5/21/2014 11:31:57 AM
Expiration Time: 5/22/2014 11:31:57 AM
Last Error: 250 2.0.0 OK
Queue ID: emailserver\7223
Recipients: [email protected]

Delayed mail delivery

Hi gurus,
I run a script for statistical purposes. The script reports the results via mailx.
This mail takes 15 minutes until I can see it in Outlook on my Windows.
Is there anybody out who can point me to the source of this behavior.
Thanks Erindia

Hi, I started sendmail with the option -q1m but nothing changed.
Shortly I restarted sendmail via init.d script. Now ps shows
root 1799 1 0 08:41:44 ? 0:00 /usr/lib/sendmail -bd -q15m -C /etc/mail/local.cf
smmsp 1800 1 0 08:41:44 ? 0:00 /usr/lib/sendmail -Ac -q15m
Then I send the following test mail
hostname | /bin/mailx -s "test" [email protected]
Below you find /var/log/syslog since restart of sendmail
Feb 2 08:41:43 wdfdvs-dino sendmail[1799]: [ID 702911 mail.info] starting daemon (8.13.8+Sun): SMTP+queueing@00:15:00
Feb 2 08:41:43 wdfdvs-dino sendmail[1800]: [ID 702911 mail.info] starting daemon (8.13.8+Sun): queueing@00:15:00
Feb 2 11:34:19 wdfdvs-dino sendmail[925]: [ID 801593 mail.info] o12AYJ8B000925: from=freyh, size=77, class=0, nrcpts=1, msgid=<[email protected]>, relay=freyh@localhost
Feb 2 11:34:19 wdfdvs-dino sendmail[926]: [ID 801593 mail.info] o12AYJ8x000926: from=<[email protected]>, size=407, class=0, nrcpts=1, msgid=<[email protected]>, proto=ESMTP, daemon=NoMTA4, relay=localhost [127.0.0.1]
Feb 2 11:34:19 wdfdvs-dino sendmail[925]: [ID 801593 mail.info] o12AYJ8B000925: to=[email protected], ctladdr=freyh (8008/100), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30077, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (o12AYJ8x000926 Message accepted for delivery)
Feb 2 11:49:18 wdfdvs-dino sendmail[928]: [ID 702911 mail.info] STARTTLS=client, relay=email.realtech.de., version=TLSv1/SSLv3, verify=FAIL, cipher=RC4-MD5, bits=128/128
Feb 2 11:49:18 wdfdvs-dino sendmail[928]: [ID 801593 mail.info] o12AYJ8x000926: to=<[email protected]>, ctladdr=<[email protected]> (8008/100), delay=00:14:59, xdelay=00:14:59, mailer=esmtp, pri=120407, relay=email.realtech.de. [195.234.217.62], dsn=2.0.0, stat=Sent ( <[email protected]> Queued mail for delivery)
Ihope that will help you

Long delays in mail delivery to mailboxes when msg is recieved at server

Mail arrives at Exchange server we know this because we have logging turned on, but the mail appears to go into limbo for anything up to 2 hours before it gets delivered to users mail box, there is no difference between outlook client or if the
user logs on using owa, the email is not shown. when exchange does decide which it does it will deliver all messages it has received in one go so all show up with in 30 seconds at the same time in users in box. we have put on the recent Exchange
SP1 hopping this would solve the issue, the server is brand new and has 2tb of storage available CPU is hardly doing anything. all other aspects of server are normal file shares printing etc. Just mail delivery is VERY VERY slow and then
it all comes at once.
We have tried restarting the server some times this does help other occasions it makes not difference. server has I3-3420 cpu with 16gb ram. This is driving us bonkers please can some body give us some guidance as what to do check or alter.
Thanks in advance.
Richard

Hi Richard,
I recommend you to do few testing to narrow-down the root cause
Does this mail delivery getting delayed only for external users or its both for internal and external users ?
How many Exchange servers you have ? Is this a combination of HUB & CAS together if its 2013 or you have them Separately?
Do you have any antispam configured in your environment ?
Is there any antivirus installed in the exchange servers?
I would recommend you to run Get-TransportAgent and see the list of transport agents installed on your Exchange servers
As a part of testing i would suggest you to disable all the transport agents installed on the servers disable antivirus send a test email and check if the delay is happening or not . Also disable the exchange antispam if its installed and see if the mail
delay exists. Because mostly any transport agents acting in the categorization part might be causing this problem if their configuration has any problem.
Let us know the results so that we can proceed further.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish
Sathish

Delayed email delivery using mail app in Lion

I'm having issues with delayed email delivery using the mail app in Lion. Specifically I have an IMAP account (AOL) that is working fine on other macs running snow leopard and on both an iPhone and an iPad. I receive an email that shows up on all other devices but does not get delivered on the Macbook Air. Clicking get new messages does not delivery the email, even if other emails have been delivered in the interim. The only way to get the email to show up is to exit Mail and restart it - and then the email shows up, in the correct date/time order and the correct read status (since I had already read it on another device).
This has happened twice now with my AOL account in the past 24 hours (I've only had the new Macbook Air since Monday). It might also be happening on my other IMAP email accounts but I have not noticed it yet. It's intermittant as I've received many other emails correctly and ontime.
Anyone else seeing something similar? I've never seen this with earlier versions of Mac OS X or on devices running iOS.
This is a Macbook Air running Lion 10.7.1. I have 4 IMAP accounts set up. Mail is set to check for email once a minute and I have my IMAP accounts set to use the IDLE command.

I have the same problem, some photos are not loaded completely and partly grey. This occurs only in Mail.app but not in the web interface of the email provider. Did you find a solution, Florian? Does somebody else have a suggestion?
Greetings from Finland

Delays in mail delivery

I've recently noticed big delays in the time that messages show up in my Mail app, sometimes hours after they were sent to me. Today I noticed that there were at least ten messages visible to me on the mac.com web site, but I couldn't get those messages until I forced a mailbox synchronization.
Is anyone else experiencing something similar? Any resolution to this?
Thanks
Nestor

Hi Richard,
I recommend you to do few testing to narrow-down the root cause
Does this mail delivery getting delayed only for external users or its both for internal and external users ?
How many Exchange servers you have ? Is this a combination of HUB & CAS together if its 2013 or you have them Separately?
Do you have any antispam configured in your environment ?
Is there any antivirus installed in the exchange servers?
I would recommend you to run Get-TransportAgent and see the list of transport agents installed on your Exchange servers
As a part of testing i would suggest you to disable all the transport agents installed on the servers disable antivirus send a test email and check if the delay is happening or not . Also disable the exchange antispam if its installed and see if the mail
delay exists. Because mostly any transport agents acting in the categorization part might be causing this problem if their configuration has any problem.
Let us know the results so that we can proceed further.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish
Sathish

[Solved] postfix local mail delivery fails

Hi Guys,
on my home pc i use postfix (gmail as a smtp relay) and fetchmail for sending/receiving mails, this works very well, however sending a mail to a local user fails, I'm lost here and need your help guys.
if i send a mail like :
$>echo "Test" | mail -s "Test : local mail delivery" "andy"
The mail stays in the queue for ever...
$>mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
CC82513BCA* 455 Sun Aug 3 09:53:09 [email protected]
[email protected]
Sending to external addresses works without any problems.
Here some important info/config files :
$>whoami
andy
$>hostname
box
$>cat /etc/host.conf
# /etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost box
::1 localhost.localdomain localhost
192.168.1.3 lbox.localdomain lbox
$>cat /etc/postfix/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/.
# 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 = virtual.domain.tld
#myhostname = mail.example.com
myhostname = localhost.localdomain
# 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
mydomain = localdomain
# 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
inet_interfaces = 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
#mydestination = localhost, localhost.localdomain
# 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 $pr/oxy_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]
relayhost = [smtp.gmail.com]
# 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"
mailbox_command = /usr/bin/procmail
# 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/sbin/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
# Enable smtp auth
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/saslpass
smtp_sasl_security_options = noanonymous
# Enable tls
smtp_use_tls = yes
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
# Max message size limit
message_size_limit = 0
Please help
Last edited by Rumcajs (2014-08-05 06:16:11)

I have solved it, and this was the problem (main.cf) message_size_limit = 0 i have set this to unlimited "0" so bigger mails not get rejected by postfix, the defualt value was 10240000 (~10 Mb) after finally checking the postfix log with journalctl -u postfix (because /var/log/mail.log) is not used anymore i found this line : "fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit" after setting mailbox_size_limit to unlimited "0" postfix starts to delivery local mail.
Last edited by Rumcajs (2014-08-05 06:17:23)

How can I stop getting 30 - 50 "Mail Administrator" or "Mail Delivery Errors" from occorring in my e-mail on a daily basis

Every time I log in to my e-mail I see 30 to 50 "mail delivery" errors. This is very frustrating to each time having to delete those items. I have blocked and clicked on spam, but there is no change.

For goodness sake, it is most likely [http://en.wikipedia.org/wiki/Backscatter_%28email%29 backscatter], changing your mail password probably will not help but is a prudent thing to do, but it is actually quite unlikely that anyone is trying to use your mail account.
There is basically nothing that can be done about backscatter, as the article I linked to advises.

Mail delivery errors

Hi, recently I'm getting tons of Mail Delivery System errors. 69 today alone. When I delete them, they come right back. Many are the same email and sometimes the page is blank. Very weird. The only thing i did differently was to try and set up a rule for people to know I was on vacation. Did not work, and had hundreds of MDS errors upon my return. Have deleted the rule but still not working properly. I also have to force quit on mail often to get it to shut down. Any ideas how to clean this up?
Cheers

I've got the same problem. One thing that helped was to clean out my inbox on my ISP's server. That stopped the force quit problem, at least for now, and also stopped a problem where mail received after that Mail delivery error message wouldn't come into my Mail application. BUT I'm still getting the tons of Mail Delivery System error messages, and yes, even when I delete them, they come right back. The message, which seems blank until I double click on it to open it in a new window, was correct. One address I'd sent an email to is no longer good, which is why one of those messages would have made sense. I see that there is a Windows virus that does this, and am wondering if there might be a Mac one also???

Create a rule on mail delivery failure

Hello,
Is it possible to create a rule in the Groupwise client, that when a message bounce back (mail delivery failure) from our relay provider, that the email will be forwarded to an internal recipient.
At the moment I cant get it to work. Moving that bounced email to a folder in Groupwise does work.

Originally Posted by laurabuckley
Hi,
I've just created a rule to test the above scenario and have built the rule as follows:
When new mail is received and subject contains "mail delivery failure"
then
Move mail to folder called Undeliverable
then
Forward message as attachment (my preferred forward method to preserve mime header information) to [designated address]
End Rule Processing
I've tested the above rule and it works perfectly on my GW8.0.2HP2 system with GW8.0.2HP3 client.
Perhaps post more details of your rule here and we can assist you with troubleshooting it.
Cheers,
I have a very similar issue to this. If I have a bounce back, I want to have that email address extracted to another doc... can be anything... TXT file, Word, Excel.... just something where I can maintain bad emails. Any Ideas anyone?

Yosemite mac mail drowning in mail delivery failed messages I didn't send!

babs bellNov 14, 2014 7:03 PM
Since upgrading to Yosemite, I am getting hundreds (tens of thousands this week!) emails that read:
From: Mail Delivery System
Subject: Mail delivery failed: returning message to sender
But I didn't send any of the emails! I've spent this entire week deleting them, working on phone with my server who claims to have fixed it (NOT!), and 5 hours on phone support with Apple today. Still happening. There must be a setting that is screwed up in Yosemite, eh? Who can help me? Using Mac Mail on Mac Book Pro. I'm drowning here! GLUG. Thanks!
Edit

Did all of that with Apple and they nor my server thought this was the problem, nor did they get it resolved. I'm wondering if there's a rule in Mail preferences that I accidentally deleted that could be the cause. There were two rules and neither made any sense to me but as soon as I deleted the first one, I realized I probably shouldn't have. And there's been a huge problem since...not sure that's why but I must find the resolution. I did have genieo somehow installed so Apple got it uninstalled and did tons of things to my system to clean this and that. BUT the problem remains. If you use mac mail and Yosemite, can you check the two rules that automatically were in the mail preferences window to tell me what rule I deleted? Thank you so very much!

Mail delivery failed: returning message to sender

Each time a form is submitted I get the following email and it's very time consuming and frustrating. Any help in resolving this issue will be greatly appreciated.
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
[email protected]
    SMTP error from remote mail server after RCPT TO:<[email protected]>:
    host adobe.com.mail5.psmtp.com [64.18.5.10]: 550 No such user - psmtp
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from austindo by gator3132.hostgator.com with local (Exim 4.80.1)
      (envelope-from <[email protected]>)
      id 1VLxH1-0004pa-ES
      for [email protected]; Tue, 17 Sep 2013 10:33:07 -0500
To: [email protected]
X-Autorespond: Getting started with your Adobe FormsCentral Plus account
MIME-Version: 1.0
X-Loop: [email protected]
Precedence: auto_reply
X-Precedence: auto_reply
From: "Austin Dog Rescue" <[email protected]>
Content-type: text/plain; charset=utf-8
Subject: Adoption Contract Confirmation
Message-Id: <[email protected]>
Date: Tue, 17 Sep 2013 10:33:07 -0500

Do you still have this issue? You can turn off email notifications (under the Options Tab > Email Notifications in FormsCentral) if you do not wish to receive any email when a form is submitted
Or are you saying you want to receive the email but the format is bad? If this is the case do you mind forwarding one of the email to me ([email protected]).
Gen

Mail delivery issues

i primarily use this forum to seek assistance from members who are more adept at solutions and advice about problems i occasionally encounter with my lenovo x201.[cto3249].
but in the last few weeks, i haven't received emails to and from community members. instead, my inbox is plastered with "Mail Delivery Subsystem" messages from "[email protected]" and a message that reads: "Delivery to the following recipient has been delayed:
"[email protected]"
then, two or three days later, the actual message appears.
i would appreciate advice about why this may be happening, and if there's anything i can do to prevent it.
thanks so much

I think the stock email client has a software bug. I have two Inc 2s in my house and both of them froze when opening the native email app. Then both phones had a terrible lag afterward. I read on a couple of tech forums that there's a bug that HTC needs to fix.
The solution for us was to delete our accounts from that email app, and use K-9 Mail instead. So far it's working flawlessly.

Mail Delivery System

I've had my Iphone for a week. Yahoo is my email. I can't take a picture and send it. It doesn't get to the destination.
Also I keep getting the messate Mail Delivery System Delayed Mail (still being retried)
This is followed by ###################################
Can anyone help?

Hi there dpfoff,
You may find the troubleshooting steps in the article below helpful.
iOS: Troubleshooting Mail
http://support.apple.com/kb/ts3899
-Griff W.

Very delayed mail delivery

Similar Messages

Maybe you are looking for