Sending mail on guest network

Cannot send mail on wireless guest network. Initially successful, then deteriorated to display pane saying; " cannot send using server...." "smpt.mac.com cannot be contacted on default ports". So it worked at startup and then began to return the above message. Can receive mail...other internet is OK. MBA>>Airport Express>>Cable Modem. Other Mac users on network are fine.

Are you absolutely sure it says "smpt.mac.com"?
The correct server (for MobileMe accounts) should be "smtp.mac.com".
Matt

Similar Messages

Setting Up Mailserver to received and Send Mail for external Network

I have a G5 currenty running 10.3.9 Server with Mail services run and working fine, we are upgrading to 10.4 Server and would like our Sales Reps the ability to send and Receive mail from outside the office. How do I configure my server, Router, ISP and/or Mail clients to do this??? we are currently able to recieve mail from outside just not send.

I cannot find the Line #submission inet n - n -- smtpd in the Main.CF file...here is what I get when I open it
# Global Postfix configuration file. This file lists only a subset
# of all 250+ parameters. See the sample-xxx.cf files for a full list.
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see sample-virtual.cf).
# 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
# sample-smtpd.cf).
# 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
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination and $inet_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 sample-local.cf).
# 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
# $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
unknown_local_recipient_reject_code = 450
# 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 file sample-smtpd.cf.
# 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 restriction in the
# file sample-smtpd.cf 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,
# - 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 in the file sample-smtpd.cf.
#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 = 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 50 SMTP server process
# limit, this limits the mail inflow to 50 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
# Insert text from sample-rewrite.cf if you need to do address
# masquerading.
# Insert text from sample-canonical.cf if you need to do address
# rewriting, or if you need username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# Insert text from sample-virtual.cf if you need virtual domain support.
# "USER HAS MOVED" BOUNCE MESSAGES
# Insert text from sample-relocated.cf if you need "user has moved"
# style bounce messages. Alternatively, you can bounce recipients
# with an SMTP server access table. See sample-smtpd.cf.
# TRANSPORT MAP
# Insert text from sample-transport.cf if you need explicit routing.
# 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
# and unknown@[$inet_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. See the file
# sample-smtpd.cf for an elaborate list of anti-UCE controls.
# 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 the sample-filter.cf file.
#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".
# By default, Postfix maintains deferred mail logfile information
# only for destinations that Postfix is willing to relay to (as
# specified in the relay_domains parameter). For other destinations,
# Postfix attempts to deliver ALL queued mail after receiving the
# SMTP "ETRN domain.tld" command, or after execution of "sendmail
# -qRdomain.tld". This can be slow when a lot of mail is queued.
# The fast_flush_domains parameter controls what destinations are
# eligible for this "fast ETRN/sendmail -qR" service.
#fast_flush_domains = $relay_domains
#fast_flush_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 = 10
# 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 don't have X installed on the Postfix machine, try:
# 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
# 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
# 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.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
# THE FOLLOWING DEFAULTS ARE SET BY APPLE
# bind to localhost only
inet_interfaces = all
# turn off relaying for local subnet
mynetworks_style = host
# mydomain_fallback: optional domain to use if mydomain is not set and
# myhostname is not fully qualified. It is ignored if neither are true.
mydomain_fallback = localhost
myhostname = jamestownpress.com
mailbox_transport = cyrus
enable_server_options = yes
luser_relay =
maps_rbl_domains = dun.dnsrbl.net
message_size_limit = 0
mydestination = $myhostname,localhost.$mydomain
smtpd_use_tls = no
smtpd_enforce_tls = no
smtpd_tls_loglevel = 0
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 = plain
server_enabled = 1
relayhost =
smtpd_client_restrictions = permit_mynetworks reject_rbl_client dun.dnsrbl.net permit
always_bcc =
mynetworks = 127.0.0.1/32,192.168.0.0/16,192.168.1.98,192.168.1.3,192.168.1.13,192.168.1.5,1 92.168.1.22,192.168.1.18,192.168.1.41
content_filter = smtp-amavis:[127.0.0.1]:10024
so what do I need to change

Mail can't send mail on home network

I am trying to help a friend who wants to move from Entourage to Mail. He has a MacBook Pro with 10.6.4 installed and his company uses Exchange 2003. He is moving to Mail due to serious calendar and contact syncing issues through Entourage and his iPhone/iCal/Address Book.
I have setup his Mail account to use IMAP with the Exchange Server. He can receive mail this way, but he cannot send it. Actually he can only send mail when he is at work on his company's network. I have turned off SSL and authentication is through Username and Password.
Funny thing is that Entourage can send and receive mail anywhere he has a connection, but Mail cannot. His company's IT department says that the settings I have in place should work.
How can I further troubleshoot this problem? Is it a server problem? I know 10.6's Mail doesn't support Exchange 2003, but I am not looking for full integration of exchange services.

You may be SOL as you need an SMTP server to send mail and the IT folks may not have it set up. You need a proper SMTP relay to send the mail, period. It doesn't matter what it's called, though convention usually has it set to smtp.example.com. mail.example.com would more often be the address for IMAP or POP connections.
Regarding the inability to send mail from an external network, this is the same problem: You still need an SMTP server to send emails. It's just that the SMTP server on the external network is likely different than the corporate SMTP server. What external network is it, and what is the SMTP server they have set up for machines within their network? Note that many networks don't enable outbound SMTP for random clients due to SPAM reasons.

Can't send mail on other networks

We have been touring the country for two months now and find we often can't send mail (using Mail) on wireless networks in hotels and it happens when we are visiting friends as well. We can always receive mail, however. It's frustrating as we're keeping friends and family posted on our trip's progress. Any ideas??? We can send e-mail through our .mac account on the Apple web site but sending photos doesn't work as well.
Some hotel's systems work just fine.

Hello Frederick.
Most, if not all ISPs now block the use of SMTP servers that are outside of their network (or not provided by the ISP) on Port 25 which is the standard port used by SMTP servers.
Some ISPs allow the use of an authenticated SMTP server only (such as the .Mac SMTP server) on Port 25 but some block its use regardless.
These restrictions are in place as part of an overall effort to prevent spam emanating from the ISP's domain.
Some free wireless networks (at hotels) will allow using an SMTP server that is outside of their network on Port 25 if the SMTP server is not authenticated (and why is a good question if so) and in that situation, selecting None for SMTP authentication should work.
Basically, you need to check with the hotel or the hotel's internet service provider regarding their required settings for using an SMTP server that is outside of their network.
When visiting friends and connecting to the internet via their ISP, you can try the following:
Go to Mail > Preferences > Accounts and under the Account Information tab for your .Mac account preferences at the SMTP server selection, select the Server Settings button below.
Enter 587 in place of 25 in the Server Port field and when finished, select OK to save the changed setting.
If this doesn't allow you to send mail with your .Mac account and SMTP server, you can try entering and using the SMTP server provided by your friend's ISP to send mail with your .Mac account which is invisible to all recipients.
When accessing free wireless networks at hotels, you can try using 587 for the Server Port for the .Mac SMTP server but as previously provided, you need to check with the hotel or the hotel's ISP to determine the required settings for using an SMTP server that is outside of their network.
If using 587 for the SMTP Server Port works, you should be able to keep this setting for the .Mac SMTP server when returning home. I use Port 587 for the .Mac SMTP server when connected to my ISP at home and I've also used it successfully when connected to a friend's wireless network via a different ISP.

HELP: Cannot send mail when off network??

Hi we have set up the mail server on our Leopard server to host mail for our domain, we can successfully recieve and send mail when clients on on our internal network, and when off network can send as well. But when a client is not on the internal network (e.g. StarBucks or at home), they can not send mail using our server, even when on VPN. We have selected to use authentication, and the connection doctor in mail shows it is able to log in and connect with the server. any ideas?

I see it's been a month with no on-line response to your problem from Apple or anybody. That may indicate there isn't one that works 100%. I am having the exact same problem with all of the same companies. Add to it that I cannot get e-mail on my PC at home/office when the I-phone is turned on. I too have been in contact numerous times with Charter and Verizon, and have received zero return phone calls from either when promised. It seems that many people have these problems, but so far nobody can fix them? And I paid for this phone? I never thought I'd be at a point where I would consider returning to my Blackberry.

Help configuring mail so a user can send mail from outside network via IMAP

Using OS X 10.4.11. IMAP and POP3 are enabled and when a user uses IMAP from within the network they have no trouble but one of our people moved to a different office outside the network.
I can configure Outlook to use IMAP and see all her folders and get mail but when she tries to send I get the message "Helo command rejected: need fully-qualified hostname" This same error comes up when I configure it for POP3.
She could use squirrelmail but Outlook is nicer for folders, contacts, etc. and since she will be at this different office for a long time I would like to get it working.
I assume it has to be a configuration on the server end but I don't have a clue where to look. Any help would be appreciated.
Thanks

This typically indicates a misconfiguration on the server.
You've probably built your server by setting postfix's 'myhostname' parameter to something like 'mail'. This should be the fully-qualified hostname of the server, e.g. 'mail.mydomain.com'.
You can change this in Server Admin, or by editing /etc/postfix/main.cf, or via the command line:
postconf -e 'myhostname = mail.mydomain.com'
Note, for the record, you don't send mail via either IMAP or POP. Those are receive protocols. All outgoing mail uses SMTP.

I cant sending mails to other networks

Hi
this is pandu from Bangalore we have 7 mail ids from your outlook.com we are try to
sending other network id s its given errors ( yahoo.com, gmail,com rediff.com ) i have sending error in below please resolve this problem
mails our life its urgent i hope in your service
my num mob : 9986400678
Reporting-MTA: dns;snt0-omc2-s19.snt0.hotmail.com
Received-From-MTA: dns;SNT153-W30
Arrival-Date: Thu, 10 Apr 2014 01:06:54 -0700
Final-Recipient: rfc822;[email protected]
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120]

Hi,
Are you using Outlook clients? Is this problem reproduceable when sending on Web?
I've seen some of this issues were caused by the wrong time/date or timezone settings, please make sure you have configured the time, date and timezone correctly on your PCs.
There are some other possible causes for this issue, if your email was not accepted, maybe the message in question may contain characteristics that the targeted server will not accept for policy reasons.
For example, it is against some mails' policy to accept messages with malicious content or manipulated header information, such as:
A falsified origination point.
An altered sending date.
A forged email address.
If you're the administrator for the mail server in question, we ask that you review outgoing messages for potentially objectionable content or practices.
Regards,
Melon Chen
TechNet Community Support

Why do I get an "unable to connect - There may be a problem with the mail server or network." message from iCloud. I have verified the settings. I can access my iCloud account online but can't send or receive e-mail via the mail account.

Text limits to the "Question" link prevents a full explanation:
This is a long-time problem. I have tried to resolve it with Apple but their "Customer Support" is merely a name.
I can go online and access my e-mail but when I try to send or receive e-mail via iCloud through my internet server (Google fiber now but the same situation existed with my prior service), I receive "There may be a problem with the mail server or network. Verify the settings for 'Apple Email' and try again.
"The server returned the error: The server 'p0-imap.mail.me.com' refused to allow a connection on port 143."
Well, I have verified the setting and tried again and again and …
Well, you get the idea …

JungleTaxi Cabbie wrote:
Csound1: iCloud: Configuring Mail with Mac OS X v10.6 or iOS 4
Enter your Incoming Mail Server, User Name, and Password using the following settings:
Incoming Mail Server: mail.me.com
User Name: Your iCloud email address (excluding @me.com)
Password: Your password
Last Modified: Jun 27, 2013
Maybe you should test these things before calling people out, because these settings do function perfectly well.
iCloud is not supported on Snow Leopard or lower, why bother to mention it?
The OP has an iCloud account, and that can not be opened without Lion or Mountain Lion (on a Mac), IOS5 or 6 (on an iPhone/iPad)
The document I linked to is Apples documentation for iCloud on current devices,I don't care whether you believe that you know better than they do, but it will affect the people who follow your advice as it won't work
JungleTaxi Cabbie wrote:
Also, if you're not running Lion or Mountain Lion, there is no "Mail, Contacts & Calendars" prefpane.
I never said that there was, perhaps you imagined it.

Can't send mail due to local network IP

I bought and installed a new Airport Extreme base station, everything's working so far with 2 wireless computers connecting online and an ethernet connection as well. The problem is with sending mail via entourage, the error message is "Entourage cannot find the server. Verify the server information is entered correctly in the Account Settings, and that your DNS settings in the Network pane of System Preferences are correct."
Those DNS settings show an ip of 10.1.1.2 subnet 255.255.255.0 while a whatsmyipaddress.com search shows an ip of 70.66.xx.xx
The computer sending the mail is connected directly via ethernet. How do I configure to be able to send my mail?

Sometimes a system power cycle will get things straightened out.
If you haven't done this yet, power down everything. Then, power up the modem first and let it run 2-3 minutes, then power up the Extreme for 2-3 minutes, then your computers.
It's also possible that your ISP detected a change on your account and automatically blocked the outgoing port to prevent spam, etc. Check with your ISP on this.

Can only send mail if I reset Reset Network Settings

When I try to send mail from my wifi account, i get an error message unless I reset network settings, which in turn prompts me for my wifi password, then mail in my outbox will send. How do i overcome this?

No, that has nothing to do with syncing. You need to copy the iTunes folder from the old computer to the new one. If you really don't have access then you will need to sync to the new one, which will erase everything on your iPhone, then start loading everything back on. You can download apps, iTunes music, Books, etc. at no charge.

Cant send receive e-mail on 3G network

I have e-mail with sbcglobal and Gmail. T-mobile is my 3g provider. With N900 I cannot send or receive e-mails on 3G network. However, it works fine when I am on wifi. Does anyone have any suggestions on how to solve this problem.
Solved!
Go to Solution.

Narf, I'll use same tree
So, I suspect that problem is on network (although my operaton elisa seems to disagree). Problem is that my 3G or so connections do not work now without having a call on somewhere - well at least you can call and surf at the same time but
ppl are getting **bleep** if I call them all-the-time without anything to discuss
3G works with diff operator sim, its only 3g use thou, but works. I wonder could this be some sim card problem again? Yh?
And another operators sim works too (saunalahti, uses same network than elisa?). Anyone had this king of problem? Is it me or my device or am I again right and the network sucks (they dont like my exessive traffic
-j

Mail box frozen. Cannot send or receive. Network connections all working. Help?

Mail box frozen. Cannot send or receive. Network connections all working. Help?

Ernie,
Thanx a lot. It seems my domain name ran out, and I didn't get a 'renew soon' email cuz the auxiliary address they had had changed over the years.
That said, even tho I renewed I'm still not getting service. Pair mentioned it'll take up to an entire day to get reconnected; so I'll wait until tonight.
Thanx for chiming in.

IPad will not send mail, but iPhone works. Outgoing servers are set up the same. I tried shutting off iPhone to not confuse the wireless network. Still doesn't work.

Can't send mail from iPad but IPhone is sending. Outgoing servers are set up exactly the same. I closed both safari and mail on the iPhone to try and avoid conflicts with iPad. I also shut down and restarted iPad. Still won't send.

Usually it's because you are not making internet connection via wifi.
Look at iOS Troubleshooting Wi-Fi networks and connections http://support.apple.com/kb/TS1398
iPad: Issues connecting to Wi-Fi networks http://support.apple.com/kb/ts3304
Additional things to try.
Try this first. Turn Off your iPad. Then turn Off (disconnect power cord) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
Change the channel on your wireless router. Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
How to Quickly Fix iPad 3 Wi-Fi Reception Problems
http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
If none of the above suggestions work, look at this link.
iPad Wi-Fi Problems: Comprehensive List of Fixes
http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
Fix iPad Wifi Connection and Signal Issues http://www.youtube.com/watch?v=uwWtIG5jUxE
 Cheers, Tom

Cannot Send Mail in Wi-fi Networks

I know this has been an issue, but can't seem to get an answer. I can receive mail in wi-fi networks, but not send. Message comes on saying, "Cannot connect to earthlink server......."
I have checked mail preferences. I know I can use Mail2Web or something, but seems I should be able to send.
Any help? Thanks.

HI,
Try here. Can Receive But Not Send Mail
That link says 10.5. The information is relevant to 10.6 also.
Also Brendan. Your forum profile indicates you are rugging 10.6 It's important to keep your system software up to date. Installing the v10.6.2 Combo Update may help your Mail issues.
If you install that update, make sure and repair disk permissions.
Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac. If you see a long list of "messages" in the permissions window, it's ok. That can be ignored. As long as you see, "Permissions Repair Complete" when it's finished... you're done. Quit Disk Utility and restart your Mac.
Carolyn

Cannot get or send mail using Apple Mail on iPhone and iPad

Everyone in my household cannot get or send mail on their Apple Mail for iPad and iPhone. We all get the same message: "The user name or password for [account] is incorrect." This just started happening yesterday afternoon. No problems before that. I called my hosting company and Apple, and both blamed the other. My Apple system is always updated, so I have the latest version of Maverick. Had no problems with it up until now.
However, I awoke this morning to find downloaded emails in the same program, but when I go to "get mail," it says the same thing, and still won't allow me to send or receive.
Here's the kicker. I also use Gmail with the exact same accounts (yes, I need both since Apple Mail does things that Gmail doesn't, and vice versa). No problem! I get all my emails and can send with no problem. So, my hosting company claims it can't be them (makes sense). It only happens using Apple Mail, and I have several email addresses. None of them work (other than the strange phenomena of suddenly getting some of them downloaded for no apparent reason).
What do I do from here? I've changed passwords, deleted and tried to set up my emails, only to get the message that they probably will not work. And they don't. I have shut down and restarted my iPad and iPhone, to no avail.
Thank god for my Gmail account, or my business would be closed.
Again, this is happening on four devices in my home: 2 iPads and 2 iPhones.

I have a comcast account I use on my phone and use it for receiving and sending mail. When you look at the account in settings, you need to check each of these
incoming mail server: mail.comcast.net
username: the part of your email address before the @
password: your password
outgoing mail server: smtp.comcast.net
Under Advanced
Use SSL: On
Authentication: Password
Server Port: 995
If you cannot make it work from changing settings in the account, delete the account and start over. Use the "Other" setting when starting the account. It is a POP3 account and make the entries I gave you. Once you do that, it should check the entries and validate the account. You shouldn't have any trouble from there. Those settings will work from either the iPhone on cell, or wireless. Mine will even work when I'm at home on my wireless there, which is on the Comcast network.
Hope that helps you.

Sending mail on guest network

Similar Messages

Maybe you are looking for