Mail server appears to lockup

Hello, I have OSX Server 10.2.8 and it has been running fine for the past 3 years but now all of a sudden I have problems logging in to POP and IMAP accounts or even sending mail through it? The server appears to be unresponsive but then works again like it is processing to much work and then when it is done it will respond again like it should. I feel like it's under a DOS attack or something.
My mail error logs are littered with messages such as below:
May 14 2006 08:21:14 TCP connect error (22) Invalid argument.
May 14 2006 08:21:14 TCP connect error (61) Connection refused.
May 14 2006 08:21:14 TCP connect error (61) Connection refused.
May 14 2006 08:21:15 TCP connect error (61) Connection refused.
May 14 2006 08:22:31 TCP connect error (22) Invalid argument.
May 14 2006 08:29:35 TCP connect error (22) Invalid argument.
May 14 2006 09:02:23 TCP connect error (22) Invalid argument.
May 14 2006 09:02:24 TCP connect error (61) Connection refused.
May 14 2006 09:03:39 TCP connect error (22) Invalid argument.
May 14 2006 09:03:39 TCP connect error (61) Connection refused.
May 14 2006 09:03:39 TCP connect error (61) Connection refused.
May 14 2006 09:03:41 TCP connect error (61) Connection refused.
May 14 2006 09:04:56 TCP connect error (22) Invalid argument.
Its running on an old B&W with a 1G G3 upgrade and 512MB ram. I have all the latest updates and security patches installed.
Thanks for any help.
Tom

I apologize if I truncated an important part of the log in my effort for brevity. Here's what I think is the full section.
==========================
Dec 13 19:44:08 icoserver postfix/qmgr[25691]: 01A2568A82: removed
Dec 13 19:44:08 icoserver postfix/pipe[26262]: A5B7368AA0: to=<[email protected]>, relay=cyrus, delay=0, status=sent (mail.icocorp.com)
Dec 13 19:44:08 icoserver postfix/qmgr[25691]: A5B7368AA0: removed
Dec 13 19:49:17 icoserver postfix/smtpd[26298]: connect from smtp110.sbc.mail.re2.yahoo.com[68.142.229.95]
Dec 13 19:49:17 icoserver postfix/smtpd[26298]: CD79368AB1: client=smtp110.sbc.mail.re2.yahoo.com[68.142.229.95]
Dec 13 19:49:17 icoserver postfix/cleanup[26300]: CD79368AB1: message-id=<[email protected]>
Dec 13 19:49:19 icoserver postfix/qmgr[25691]: CD79368AB1: from=<[email protected]>, size=397919, nrcpt=1 (queue active)
Dec 13 19:49:19 icoserver postfix/smtpd[26298]: disconnect from smtp110.sbc.mail.re2.yahoo.com[68.142.229.95]
Dec 13 19:49:22 icoserver postfix/smtpd[26304]: connect from localhost[127.0.0.1]
Dec 13 19:49:22 icoserver postfix/smtpd[26304]: 0EC2168B04: client=localhost[127.0.0.1]
Dec 13 19:49:22 icoserver postfix/cleanup[26300]: 0EC2168B04: message-id=<[email protected]>
Dec 13 19:49:22 icoserver postfix/qmgr[25691]: 0EC2168B04: from=<[email protected]>, size=398365, nrcpt=1 (queue active)
Dec 13 19:49:22 icoserver postfix/smtpd[26304]: disconnect from localhost[127.0.0.1]
Dec 13 19:49:22 icoserver postfix/smtp[26301]: CD79368AB1: to=<[email protected]>, relay=127.0.0.1[127.0.0.1], delay=5, status=sent (250 2.6.0 Ok, id=25705-05, from MTA: 250 Ok: queued as 0EC2168B04)
==========================

Similar Messages

Outgoing mail server appears blocked by mobile network

I have already contacted Roadrunner to find out why the host name in the Outgoing Mail Server--mobile-smtp.roadrunner.com will not work. They state that it should read mobile-server.roadrunner.com. When I typed that in, it reverted back to the original phrase, and they said to get in contact with the mobile network. There must be a block in it. We tried a different port, however, that did not work either. Has anyone had this problem? I am receiving emails from roadrunner without incident.

Try deleting the account and selecting manual set up. Also you can also try using an email app from the play store like k9 mail.

Mail Server deaf to incoming SMTP

I'm running an EIMS 3.3 mail server, on a G5 iMac 1.8 ghz, OSX 10.4.11. The system worked well for years. I went to an Xserve colo, and now moved, and am trying to resurrect the EIMS mail server.
Email accounts hosted by the server exchange happily whether client is local or remote. Outgoing email to anyone goes through fine. My server sees no connections to deliver mail from the outside world (domains), but remote users can check their accounts.
telnet pacmult.com 25 gets me
Trying 127.0.0.1...
Connected to pacmult.com.
Escape character is '^]'.
Connection closed by foreign host.
Nothing in the error logs, mails hit their accounts ok, just no connections or mail coming in.
Wha???????? Any good SMTP geeks on call? Thanks.....
Message was edited by: pacmult No wifi or internal router, just a cable modem to the server, firewall is in the iMac only, and results are the same with firewall off.

Hi Pterry, thanks for piping up.
I checked all the logs (that I can find), and I don't see a reference to these connection failures. If you can name a particular log of interest, I'll copy it here.
My EIMS logs show no errors, either in the main error log, or receive error log, as it's the mail server appears to never see these incoming attempts.
It was a good idea to check, but I show no other mail services running that would interfere.
I called my cable company and asked if they had a smtp block on my leg, and they swore they different. My old ISP in LA said he's showing a smpt block of some sort.
I tried to send an email to a local account from my yahoo account, and got this daemon bounce:
Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[email protected]>:
Connected to 65.175.133.72 but connection died. (#4.4.2)
I'm not going to try again; this message has been in the queue too long.
I checked the mx record, and it appears to be correct.
Day 3, I'm still looking.......

HT201320 I want to set up a POP3 email account but in all the help I have found so far I should get the option to choose IMAP or POP. This doesn't appear and I need POP3 because I don't want anything deleted from the mail server. I have an iPhone 5s and

How do I set up a POP3 email account on my iPhone5s, using iOS 7.1.1. All the help I have found tells me to select IMAP or POP but I am not given the choice. I need to be able to set 'Don't delete from mail server' which can't be done in IMAP.

tim.fry wrote:
My email provider is BT and they do support POP3, that's what I have been using for a number of years
Okay.
Then set it up.

Need to have mail1 play nice with upstream mail server....

Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
On the debian box we're seeing:
2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
And mail isn't piping thru to the mail1 box. Here's the main.cf
sh-3.2# cat 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 = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) 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".
#mailbox_transport = lmtp:unix:/file/name
#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
xxgdb $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 = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
mydomain_fallback = localhost
message_size_limit = 52428800
myhostname = mail1.stanwood.wednet.edu
mailbox_transport = cyrus
mydomain = stanwood.wednet.edu
mailbox_size_limit = 0
enable_server_options = yes
inet_interfaces = all
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
smtpd_use_tls = yes
smtpd_enforce_tls = no
smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = gssapi,cram-md5,login,plain
content_filter = smtp-amavis:[127.0.0.1]:10024
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
owner_request_special = no
recipient_delimiter = +
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
# 02/02/09 Server Checkup by Alex
bounce_queue_lifetime = 6h
delay_warning_time = 6h
maximal_queue_lifetime = 2d
# Topicdesk Frontline Defense
disable_vrfy_command = yes
smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
virtual_transport = virtual
virtual_mailbox_domains =
sh-3.2#

Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
mail1:~ admin$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
bouncequeuelifetime = 6h
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
delaywarningtime = 6h
disablevrfycommand = yes
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maximalqueuelifetime = 2d
messagesizelimit = 52428800
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
mydomain = stanwood.wednet.edu
mydomain_fallback = localhost
myhostname = mail1.stanwood.wednet.edu
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
smtpdenforcetls = no
smtpdhelorequired = yes
smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
virtual_transport = virtual
mail1:~ admin$

How to setup e-mail account without deleting web mail server

When I delete e-mail on i-phone, it delete web mail server mail also.
I like to keep these web mail server mail.
Like old i-phone 4 was not delete web mail server mail, even I delete i-phone mail.
Please tell me how to set up e-mail on i-phone.
Thank you

I had things set up that way and it worked fine. However, last week on my iPhone, my bellsouth.com account kept coming up with "the POP server is not responding," but the account worked on my Macs and my iPad. I deleted the account and added it again. Now it seems to be an IMAP account (the POP server still does not respond). When I access the "advanced" tap in the setings, when I click "Deleted Mailbox" under "Mailbox Behaviors" it appears to show an option to leave mail in the server inbox but the word "Inbox" is in grey and not clickable. Has ATT changed its servers?

My email account in Mail.app is IMAP, but when I delete emails, they don't delete from other devices connected to the mail server with IMAP. Deleted mail on other devices delete as normal from the server and thus from other devices as normal.

MacBook Pro, late 2011 version. Up to date Mountain Lion.
My email account in the Mail.app is set up as IMAP, but when I delete emails in the Mac Mail App, they are not deleted from the mail clients of the other devices that are connected to the mail server with IMAP. IMAP works perfectly between Windows Outlook 2010, iPad Mail App and Android default mail client. Deleted messages behave correctly, as in delete from one device and the mail is deleted from all devices.
Having just tested in reverse order on the Mac; emails deleted from the email client on Windows, iPad and Android are not deleted in the Mac Mail App. It appears that the account is behaving like POP rather than IMAP.
Any advice on how to have IMAP work correctly on the MacBook Pro Mail.app?
Thank you.

Hi Csound1, thanks. The email host is 1and1.co.uk, however, i am going to fess up and make myself look like a plonker now -
the email account in question was set up in Outlook as POP - stupid, stupid, stupid me, wasted an afternoon on this! I have now changed the Outlook account to IMAP and Mail.app works perfectly - and looks much nicer than Outlook did. Im in the middle of converting from Windows to a Mac, and still finding my way around the Mac
The lesson learned, never assume - always double check! All my other email addresses with 1and1 are all imap, except this one, and it happened to be the first one I set up in the Mail.app. (bows head in disgrace!)
Thank you anyway for attempting to help me!
Cheers

Sane virtual mail server setup?

I'm giving up. I want a simple mail server setup (imaps, pop3s, smtps) with virtual user support that I can comfortably configure from the web (PostfixAdmin, web-cyradm, courier-web). I want to manage multiple users on multiple domains. It appears that the task I want to accomplish is insanely complex for some reason. I'd like to use as few different software packages as possible.
I can't find a simple and sane tutorial on the topic and I don't even care what software is going to be used. Of course, I did search and play around with the config for hours but to no avail. The tutorials in the Arch wiki are no good either, they are either outdated or do not allow me to do web configuration.
Help me out here, please.

It's always good to have alternatives, but out of curiousity, did you not try the courier-mta wiki? I used that wiki guide recently and it had me running with a system like what you describe without too much fuss. The only stuff I haven't tried/used is web-based administration or mail access; perhaps this was the problem for you?

While creating a new email, various portion of the mail will appear in the trash box.

after creating a new email and send sucessfully, breakdown of the full content in the mail will appear in the trash box without my intention. The breakdown were in seperate uncompleted mail/mails depending on the lenght of the email. Everytime after a simple email of about 3-5 sentences conpriseing of less then 30 words, 5 - 10 seperate trash box mail appeared. it worst when duration is longer while creating the email. Any advise to eliminate this situation??

You probably have "Store draft messages on the server" checked in the Mailbox Behaviors of the mail account(s) on which you are experiencing this, and the server's reaction to having a second, third, etc. draft of the same message stored is to put the older copy in the trash. Not all servers react like this, but some like Gmail seem to so do.
If you won't need to change Macs in the middle of composing an email message and can live with retyping a message you were composing at the time of a crash, you can probably turn off this feature.

Apple Mail app no longer connecting to incoming mail server

Hi.
I use the integral Apple Mail email client under OS X 10.8.
Until this afternoon, all was well and I could send & receive my emails without any problem. (Suggesting that all the server settings & preferences are correct in Mail.)
This afternoon Mail suddenly was unable to connect to my incoming (IMAP) mail server, and I still cannot get it to connect.
I do still receive email from the same server on my iPhone though, so that suggests that the server itself is working correctly.
I've tried quitting Mail and re-launching it, and I've tried editing the server settings, saving the new settings and then reverting to the old ones and re-saving, but to no effect.
The problem exists on both of the user accounts we have set up on this Mac, and both user accounts use the same IMAP server, but with different names of course.
I'm at a loss as to what might have occurred here, and an even further loss as to what else I can try to resolve the problem.
Anyone any ideas please?
ps. While I was typing this an email arrived in my Mail inbox! BUT... I still have the little !-triangles by the side of my account in Mail, and when I click on them the 'Alert' tells me that there 'may be a problem with the server or network' and, "The server returned the error: The connection to the server “imap.mail.yahoo.com” on port 993 timed out."
So it looks like I'm getting emails somehow, but there is still a problem somewhere.

I started having this same problem yesterday after installing the Safari 7.0.6 update. This has to be a coincidence.
I have 11 email accounts setup in Apple Mail. The only one working now is my work exchange email. The rest are either accounts I host on my own OS X Mavericks Server using IMAP and SMTP over SSL except for two of them which are GMAIL and iCloud.
Same issue. The iMac just displays the warning triangle symbol and when I click I get the Unable to Connect dialog with the message.
There may be a problem with the mail server or network. Verify the settings for account “iCloud” or try again.
The server returned the error: The server “p03-imap.mail.me.com” cannot be contacted on port 993.
I have verified the settings on all of my IOS devices and they are the same. As with the original post, my IOS devices are all able to connect to all of my accounts without any problems.
To try and troubleshoot this issue I switched to another user account and tried to connect to one of my mail accounts and got the same Unable to Connect issue. I then opened another email client (Thunderbird) and configured the email account exactly the same there (IMAP on port 993 and SMTP on port 587). Thunderbird was able to connect and retrieve my mail without any problems. As an additional test I opened up terminal and tried "telnet p03-imap.mail.me.com 993". I was immediately connected to the iCloud server.
To sum up this does not appear to be a problem with the iMac, the user account, my mail server or the network. It appears to be a problem with Apple Mail only.
I wonder if there is a plist file or something that needs nuking.

'our IMAP server appears to be temporarily out of service' - help !!

When logging in I get this error message on my e-mail:
'your IMAP server appears to be temporarily out of service'
Any assistance please? Much appreciated.....

Call your ISP or whoever hosts your mail server and ask them if something is going on...

Does anyone know whether BT has a mail server that...

Does anyone know whether BT has a mail server, other than mail.btinternet.com, that supports only POP3/SMTP and not IMAP? For those interested, the background is as follows.
I've been trying to get my iPad Mail client to connect to mail.btinternet.com using POP3/SMTP. When you try to set up an email account on the iPad in the normal way, you are not given the choice of using POP or IMAP. The Mail client appears to query mail.btinternet.com and, if it determines that the server supports IMAP, it then proceeds to set up a connection using IMAP. Now, I know a workaround to force the Mail client to connect using POP3/SMTP. That is not the problem. The problem is that Mail client does not appear to work properly with POP3/SMTP, and I suspect this is because some of the Mail client code, under the covers, still believes it is using IMAP.
For example, having setup an email account that uses POP3/SMTP, if I try to create a local mailbox/folder on the iPad Mail client, the operation fails with the message "Unable to Create Mailbox The mailbox couldn't be created on the server". So I ask myself, why is the Mail client trying to create a mailbox/folder on the server? The conclusion I have come to is that the Mail client still thinks it is using IMAP.
I suspect that there are defects in the iPad Mail client code. But, to test this, it would be good to experiment by setting up a connection to a mail server that supports only POP3/SMTP and not IMAP and then see whether the Mail client behaves any differently. Hence my initial request.
Solved!
Go to Solution.

Both my wife and I use the Outlook mail client on Windows for our "serious" email and we are very happy with Outlook.
The iPad is actually my wife's and she bought it for other reasons, such as to Facetime friends and relations, install the Kindle app and read Kindle books, use the BBC iPlayer app, and so on. But I have set up a separate btinternet email address for her to use on the iPad and she intends to give that email address only to certain close relations. But, so far, we have found that the iPad Mail client is just not usable with POP/SMTP, and she doesn't really want or need to use IMAP.
Edit: Sorry, forgot your specific question. No, it doesn't create the folder/mailbox locally. It fails completely.

Mail cannot access the mail server, but other email clients do.

My web host recently had extended problems with the mail server my sites are on. Now, Mail on my iMac Intel 27 Duo says it cannot access the server. However, Thunderbird and Entourage Mac have no problem. Sending from Mac Mail seems to be Ok as well. I've checked the settings over and over. I received no system disk for this machine when I bought it. Do I need to reinstall Mail, and if so, how?
The info below from Connection Doctor shows it appears to be trying to access through Port 25 but I have Mail set for 587 as instructed by the hosting company. I have renamed private info in the text below.
READ Jan 16 09:56:42.941 [kCFStreamSocketSecurityLevelNone] -- host:mail.myemail.com -- port:25 -- socket:0x11f51aed0 -- thread:0x122c48a20
250-servername-a41.g.webhostname.com
250-PIPELINING
250-SIZE 40960000
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250 8BITMIME

However, Thunderbird and Entourage Mac have no problem. Sending from Mac Mail seems to be Ok as well. I've checked the settings over and over.
Well if TB and Entourage can both send and receive but Mail can only send I can only conclude you missed something in you rechecking. Of course with you being the only one checking you are going to make the same "mistake" and never no it. So post the relevant POP server info for your ISP (edit out personal info and passwords of course):
Account Info:
Incoming Mail server: pop server address
User Name:             required user name POP server is looking for (censor)
Password:              password required by POP server (censor)
Advanced:
Port:      995, 25, default?
Use SSL:   yes or no
Auth:      kind of authentication

Mail.app and Eudora Mail Server using IMAP

I run five e mail accounts off three different mail servers. Ironically, the only one that doesn't work well is Eudora Mail Server running on our Apple network.
Here's what Eudora say:
"When using IMAP, OS X Mail does not appear to be compliant with section 7 of RFC 3501. As a result it will often ignore new mail that has arrived in a mailbox."
Has anyone else experienced this problem and, more importantly found a fix?
I need to use IMAP because I use 4 different computers. .Mac/iDisk and IMAP make it a breeze to move between machines.
I can use Entourage (which works fine) but then I lose the use of Spotlight, which has transformed the way I access my (badly filed) data!

Hello Neithan.
Assuming Preferences > Mailbox Behaviors > Move deleted messages to the Trash is ON, does having Store deleted messages on the server ON or OFF make a difference?
Does the problem persist if you take the account offline, then back online (e.g. by means of Mailbox > Go Offline/Online)?
Do you have any Mail plug-ins? In the Finder, go to each of the following folders (if they exist). What do you see there?
/Library/InputManagers/
/Library/Mail/Bundles/
~/Library/InputManagers/
~/Library/Mail/Bundles/
To make accurately reporting that information easier, open /Applications/Utilities/Terminal, type the following command (you can just copy it here and paste it in Terminal), and press <Return>. You can then copy the output of that command from Terminal and paste it in your reply to this post:
ls -1 /Library/InputManagers /Library/Mail/Bundles ~/Library/InputManagers ~/Library/Mail/Bundles
Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder. You can easily locate any of the folders referred to in this post by copying the folder path here, doing Go > Go to Folder in the Finder, and pasting the folder path there.

Setting mail server to check other (remote) POP accounts

Can someone tell me what technique is used to configure Mac OS X (Tiger) Server to retrieve mail from other POP servers? I am wanting to use an internal mail server at my organisation for main mail handling (most large emails are between people within the building) and have it automatically retrieve emails from various ISP mail servers.
This way, users appear to have a very fast connection to the mail server, and if it ever goes down they can still connect to the ISP's server and still be able to retrieve new messages.
Also useful for collecting a desparate collection of email accounts into one, and have the mail filters act on it.
I've come across etrn & uucp, but they don't sound like this is what they were designed for.
thanks,
Ray.

Thanks Jeff. Just the one word was required to send me off in the right direction. I had encountered sendmail, but couldn't recall it to get a man page on it.
One other question (couldn't find mention of it in discussions): I have played with it and got it working for my account by running it manually (and as a daemon under my user).
But the question is how do I get it to launch at startup? Do I put a .plist in the /Library/LaunchDaemons? And if started this way, will it automatically notice all the ~/.fetchmailrc files and process everyone's mail?
Thanks for your help.

Mail server appears to lockup

Similar Messages

Maybe you are looking for