Separate mail for subdomain
given the domain bar.org (which already has a working e-mail server, and mx record),
how can i set up an iMS server that will receive mail @foo.bar.org (and not @bar.org).
i have created the subdomain foo.
my dns looks like this for bar.org
mailserver = mail.bar.org
rank = 1st
for domain = bar.org
is it possible for dns to route mail to a sumdomain, e.g. could i add a dns mx entry that looks like this:
mailserver = foo.bar.org
rank = 2nd
for domain = foo.bar.org
or is this handled by configuration of the first mail server, to relay, or something else?
You should be able to do it either way, depending on how the mail is addressed.
If the mail is addressed to "[email protected]", and you have a DNS MX record, mail should be routed per that MX record
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 -
Setting up Mail for the first time with OSX Server 10.5.6
I just got done reading the 100+ page mail services administration manual. A few things are unclear and I wanted to clear those up prior to embarking on my first adventure configuring mail services.
The questions I have are the following:
1. When using mail for incoming and outgoing, do I 'have' to use local DNS services or can I simply change the MX records by my DNS Provider?
2. I have more than one IP on the server using the 'IP Alias' command. Will the mail server be able to distinguish the different mail domains base on IP Address, or will virtual domains need to be configured?
3. If virtual domains need to be configured, is this configuration simple or is it semi complex?
4. Provided the answer to questions two and three, what is the best configuration for the firewall settings on the server? Allow IMAP inbound, POP3, and SMTP? What else?
Thanks in advance1. Mail service relies heavily on DNS. You may run your own DNS servers on the same network as your mail server or you can use a DNS provider to host your zone data including your MX record.
2. Your server will listen on all available network devices by default. It will only accept those messages for the hosts that are listed in the general pane, the local host list, or the virtual domain list under the advanced pane. No virtual domains need to be configured if all users are real users (i.e. shows up in WorkGroup Manager).
3. As stated in (2), you do not need virtual domains to receive e-mail for multiple hostnames or domain names, but you may want to do so if you want separate accounts with same usernames for different domains. E.g. [email protected] and [email protected] will go to two separate inboxes. It's not that difficult, but rather tedious if you already have a lot of e-mail accounts set up.
4. You must allow SMTP through the firewall to receive mail from the outside world. Depending on your clients, you may open IMAP or POP. There are no other specific ports necessary for mail to work at this level... except for Submission (587). Many ISP's block port 25 for mail clients. You may want to use port 587 for submissions so that your mobile users don't have to switch back and forth between the two ports when they change locations. This is done by editing /etc/imapd.conf manually. -
Hello. I have two devices and two accounts, so what i want is this:
I only want to store mail from both accounts in a remote place and copy most important mails to local folders.
(I will be grateful for any ideas as to where/how this "cloud" can be - specially free places)
* Can I have a copy of these local folders in both devices and the remote storage?
* Could i synchronize devices so that: when i move a mail to a local folder in any device, its copied to the same folders in
the other device and the remote storage place?
* The remote storage place will have many other folders. When I open Thunderbird, I also want to see these and the mail
inside, and also be able to move mail from the inbox to these folders.
* One of the accounts is gmail. In Account Setting tool, there is an option for synchronization. If there is no easier way, I can have mail for other account copied to gmail, and just syncronize gmail mail. For this, how will I copy my present folder structure to gmail. And how can I syncronize the local folders on the two devices?
Thanks in advance.The first awkwardness I see is that there's no obvious format in which to store messages remotely such that you can work with them in an email client. It may be possible to set the "Local Directory" option in the account in Thunderbird to point at some remote folder (DropBox comes to mind) but I have never tried this and I'd be nervous about what happens if connection can't be made, or if you happened to access it from two different places simultaneously. The other concern is that mail stores get big, quickly, and you'd be forever uploading and downloading large (multi gigabyte) files. Thunderbird stores what looks like a folder containing many separate messages as one big file, so there's no simple opportunity for incremental changes to be up/down loaded.
The whole idea of Local Folders in Thunderbird is to detach messages from servers, so they don't track what happens on servers. I say this to point out the distinction between files stored locally and permanently ("Local Folders"), versus cached copies of online files ("synchronized"). It's not safe to regard your synchronized folders as permanent.
So, synchronized folders on an IMAP server are "mirrored" in Thunderbird so you do have a local (albeit temporary and transient) copy of messages; this is done mainly to avoid repeatedly downloading messages if you re-read them, and it makes searching faster an more efficient. But these "synchronized" message track what's being done on the server, and so if they are deleted anywhere, all synchronized devices will at some point also see the deleted messages vanishing. (Unless you made a local copy in the Local Folders account.)
I use a gmail account pretty much as you have described; I copy or move messages to that account so they are visible in my phone, my tablet, my own laptop and my works computer. It's free, and it's "in the cloud"; the only reservation I have is its privacy. There are other providers (e.g. 1&1/gmx) who don't seem to have the data collection fetish that google thrives on.
It's fairly simple to create filters in Thunderbird to automatically copy messages to your "cloud account"; even better is to set up forwarding rules on the other accounts' servers, so your messages are automatically sent on and waiting for you when you next login, already in the cloud account. -
We are a family of 4, each with their own apple device. Is it best for us to set up individual apple ID's for things like ITunes? If we do can the same e-mail address be used for all of them or do we need to create e-mails for the kids?
Thank-you1. Yes, it is.
2. You may be able to use the same address by adding a plussed suffix to it, such as [email protected] If that doesn't work, create separate emails.
(103279) -
How do I set up two accounts with two separate mail applications?
My wife and I have two separate email accounts. At home she gets her mail on her computer and mine on my computer. While traveling I would like to be able to allow her to get her email on my laptop. I set up the 2nd account and activated it but her email comes in mixed with mine. How can I set up a separate mail program for her account?
Thanks in Advance,
Jim ConradHello Jim.
As already provided, open Inbox to reveal the Inbox for each account. Selecting an account's Inbox mailbox reveals messages received by that account only in the message list. Selecting Inbox reveals a "blended" Inbox mailbox for all accounts.
The same applies to Drafts, Sent, Trash and Junk in the mailboxes drawer.
If you want these accounts to be truly separate, create a login account on your iBook for your wife - with or without admin privileges. Your wife can create her email account only in Mail under her login account and you can delete her account from Mail under your login account.
This way, each others' email accounts are kept completely separate along with all other data in each other's Home folder/directory. OS X was designed for multiple users in this way.
You can enable Fast User Switching which makes the process of switching between multiple login accounts a fast and easy process.
There are some families with 4 or more family members that use a single Mac in this way. Each login account can have their own Desktop background and settings, etc., etc. so when logging in to their account the Mac seems like it is theirs only.
This link focuses on setting up separate user login accounts for kids but the effect is the same.
http://www.apple.com/macosx/features/family/ -
Hi,
I have an E52. A couple of days ago I configured mail for exchange. I thought it was be right. But after a couple of days, I want to sent an email back. Then there is a problem I get an error massage that this isn't possible.
My agenda and incoming mails works fine but only to sent an email doesn't work.
Could someone help me?
I am using a gmail account.I got the same problem but my old E61i is using exchange v3 and no problem.
For my E52 (v051.018), I got the same problem, don't know why? But, what I did was creating a separate gmail account and @ exchangemail, I set not to sync for email. -
I registration to apple ID but I can't got e-mail for verification.
I registration to apple ID but I can't got e-mail for verification. I log-in to manage your account on computer and resend to verification e-mail . I not got verification e-mail.com.
This is not an area where I have any expertise, but you may want to consider using separate Apple IDs and using the recently released Family Sharing capabilities which still allow you to share your music and apps.
http://www.apple.com/ios/whats-new/family-sharing/
https://www.apple.com/support/icloud/family-sharing/ -
Help to configure msoutlook separate inbox for each accounts in office 365 in mac
i have installed office 365 in mac pro book and configured 3 accounts. all the mails are downloading to same inbox. please let me the configuration to receive mail in separate
inbox, sent, draft, etc.. for each accountsHi,
By default, the Outlook folder list groups similar folders, such as inboxes, from all of your mail and Microsoft Exchange accounts. This feature can make it easier to read all your messages at once, without having to move around between mail folders.
If you want, you can turn off this feature so that each account and all its folders are separated in the folder list:
http://office.microsoft.com/en-us/mac-outlook-help/show-separate-inboxes-for-each-account-HA102928387.aspx
Also, this is the forum to discuss questions and feedback for Windows-based Microsoft Office client, better to post your question to the forum of
Office for Mac:
http://answers.microsoft.com/en-us/mac/forum/macoffice2011?tab=Threads
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Thanks,
Ethan Hua CHN
TechNet Community Support -
About Ready to Ditch Apple Mail for Outlook
I've been using Apple Mail for several years with no issues. Suddenly that has changed. A few weeks ago I noticed I am unable to rename Mailboxes that I've created in the past (i.e., I rename them and get an error message). I posted a separate question about that on February 23, 2012 and have had no comments or responses to that post.
Yesterday I did two things in Mail:
Created a new mailbox named 2012 HOUSTON, and
Dragged about 3 mailboxes to put them in a different order than they appeared
This morning I received an email I wanted to put into the 2012 HOUSTON folder.......and it was GONE. Completely gone. I did a search for the email I placed in that folder yesterday and it also was gone. Also, one of the other folders I had reordered had returned to its previous position near the bottom of the mailboxes.
This is unacceptable behavior for Mail and I can't find any solution. I am a hair's breadth away from moving to Outlook, something I've resisted for a long time because Entourage (Microstop's old email program) was so buggy, and having been a Mac user since 1988 I do my utmost to use Apple products.
HELP, ANYONE!!!Okay, now you're confusing me. Me.com is IMAP mail and there is no setting as you described unless you set it up for POP3.
-
Multiple POP accounts: Can I set up separate mail windows
New mac user. I was able to switch identities using Outlook Express on my PC so that multiple users' mail were not downloaded when one user logged on. My desire is to not see other people's email, nor they mine. Is there a way to accomplish this?
lmac Mac OS X (10.4.8)Instead of switching identities in Mail, you do it at the OS X level i.e. create multiple accounts on your computer and use Fast User Switching. Each user of your computer then has their own separate environment for all applications including Mail.
I hope that helps. -
I had multiple iPhones and iPads associated with the same apple account and I have now created a separate account for two of them. The question that I have is whether there is a way to transfer the icloud email address to the new account?
Welcome to the Apple community 1960gmd.
Once an iCloud address is used for an Apple ID, you can't use it for any other.
Why would you want to use another Apple ID if you already have the address you want to use in another.
If you want your email on all devices but use a different ID for iCloud add it as a secondary account at settings > mail, contacts, calendars and just enable mail. -
Mail application: Is it possible to have 2 separate Mail applications running?
(I am currently running Snow Leopard but planning to switch to Lion soon.)
I know this seems unlikely, but is there a may to run 2 separate Mail applications on the same Mac?
On my office computer I use Mail for my Personal email and Entourage for my Work email. I do not need to use Entourage for any work related reason, I use it solely to keep my Personal and Work email separated in different applications.
I really love Mail and am not married to Entourage. If there was a way to run two separate Mail applications I would move my Work email to Mail.
Again, I anticipate the answer to be no, but I figure there is no harm in asking.
Thanks,
MarcantonioYou can run Apple Mail and use it for two (or more) totally separate email accounts, e.g. one for work and one for personal.
You set up each account separately in Mail by going to Preferences ... and Accounts.
In the Accounts pane, you will see a small "+" and "-" at the bottom left of the pane. That's to add ("+") or delete ("-") accounts. You need to enter all the correct server and account information separately for each of your two accounts.
When you run Apple Mail after dloing this, you can view the email for those accounts SEPARATELY for each of the Inbox, Sent, and Trash. Or you can view them all together if you choose (e.g. you can view one Inbox that has all your work and personal email together). You can basically do this however you want.
For instance I use earthlink (POP) for one of my personal accounts, I use a different account at work via MS-Exchange (IMAP). I get them both on Apple Mail, and I always keep them completely separate (separate Inbox, Sent, Trash folders).
I use Outlook for the MS-Exchange "work email", but that's just the most recent version of MS email clients for the Mac, Entourage is an older version. -
I don't think I see my situation addressed. I have one mobile me account and a separate appleID for purchases. I have 4 devices and my wife has two. Right now they are all using the same mobile me account to sync just the calendar and address book.
1.) I want to add email syncing for my 4 devices and email syncing for my wife's two devices separately, but we want to sync and share the same calendar and address book. Is this possible?
2.) I also have 5 different calendars, one for work, one for home, one for... etc. Is there a way to have different devices only sync certain calendars and not others or is it an all or nothing deal?
Thanks in advance for any tips!
STo begin with, I would like to try to explain Apple's confusing nomenclature in regard to iCloud.
Apple have called the whole cloud thing iCloud, there are a number of features under the iCloud umbrella, some of which require their own login. iTunes is one of these, another is what Apple have unfortunately also called iCloud.
You can use the same Apple ID (account) to login to both iCloud and iTunes, but you don't need to and often users will login to each service using a different ID.
The part that you need to remember is that the services available when you log into iCloud are completely different and unrelated to those when you log in to iTunes. Your iCloud login enables mail, contacts, calendars, find my phone, Back to My Mac, Documents & Data sharing and photosstream, it does not affect any of your iTunes services.
To avoid confusion when discussing your problem, when I mention iCloud, I am referring to the services under the iCloud login, Whereas I will refer to the whole cloud thing as The Cloud.
Generally speaking it is not a good idea to share an iCloud account between different people, it often results in contracts, calendars et cetera being deleted by others. Saying that however you can add secondary iCloud accounts to your devices at settings> mail, contacts, calendars. Secondary accounts do not have all the features of a primary account, but are often very useful. Because you can enable or disable each individual feature of an iCloud account, you can cover almost any situation by using secondary accounts. -
Two Separate Mail Accounts w/Two Separate Address Books?
I want to set up two separate mail accounts with two separate address books. I've been using Mail for several years and love it. My wife has been with AOL but now wants to move to Mail.
Is there a way to have two separate accounts, two address books, and two separate Mail icons to click to open, so we aren't tempted to look at each other's incoming/outgoing mail? Also, our address books are very different and we'd rather not intermingle them.Hi StacheCache!
She could also retrieve her AOL Email online, without a separate User Account on your shared Mac.
She would log in to AOL Webmail using her AOL Screen Name and password.
ali b
Maybe you are looking for
-
After running the upgrade to the latest ITunes I cannot run Itunes. I get a Error 7 Windows error 1114, and a R6034 C runtime error. It was working before. Help!
-
ITunes Library out of whack - I was stupid and need help...
OK, so I keep my iTunes collection on an external drive (just won't fit on my 512GB SSD right now) and I have Windows 7 installed under Parallels Desktop. I stupidly downloaded iTunes for Windows and pointed it toward my iTunes library on my external
-
I am using premiere elements and created a film. I burned a DVD and all was fine. Now I added pictures and some music to the film and when I try to burn a DVD I get the indexing window and nothing happens -- even waiting for an hour. So, what c
-
How to spool to a file with changing name
How can you spool to a file using a passed parameter as part of the filename. If you try: spool c:\temp\&1_report.txt it says that the spool command is invalid. Any ideas? I seem to remember doing this before but I can't remember how....
-
FDQM - Financial Data Quality Management
Can anyone assist me to fix this problem from FDM? I received the error below when I tried to logon to FDM from the Web client. Your help would be appreciated. Server Error in '/HyperionFDM' Application. Runtime Error Description: An application erro