Mailserver on subdomain?

After som serious head scratching I've gotten a mailserver up and running.
The software I've chosen is postfix and dovecot.
It works fine and I can send and recive mail without problems. I do have one question. How do I make the servers listen on mail.domain.com instead of domain.com as it is now. I want the e-mail address to be [email protected] but the servers to be mail.domain.com
Could someone give me any hints on how to decipher the config files and MX-records?

You should have no problem with postfix accepting mail for both domain.com and mail.domain.com, providing mail.domain.com is your mailserver's name. If it isn't, then you can also accept mail by hacking main.cf to accept mail for all kinds of domains.
check out the line in main.cf with mydestination in it:
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, mail.$mydomain, www.$mydomain, ftp.$mydomain.
For the MX record, your named zone file should look something like this one, assuming that you are using BIND:
$ORIGIN .
$TTL 86400 ; 1 day
domain.com IN SOA server.domain.com. yourmailacct.domain.com. (
46 ; serial
10800 ; refresh (3 hours)
900 ; retry (15 minutes)
604800 ; expire (1 week)
86400 ; minimum (1 day)
NS server.domain.com.
MX 10 mail.
$ORIGIN domain.com.
server A 192.168.1.1
mail A 192.168.1.2
$TTL 300 ; 5 minutes
be aware of the dots at the end of the domains.

Similar Messages

Creating a mailserver subdomain

L.S,
I'm currently working on a 100% pure Java email server system. I've got server sockets listening at ports #25 (SMTP) and #110 (POP3). However, I haven't yet found out how to create a subdomain "mail.mycomputer" on my existing DNS "mycomputer". I believe I need to do this in order to allow other systems sending email messages to all@mycomputer.
Also, I've read there's something I need to do with MX records. Those, I think, should relate to email accounts or something or other.
Can anyone please help me out, pointing me to relevant information on the Internet or any books that I should read? Maybe someone can even provide a small sample demonstrating how I can access and manipulate DNS information from within Java (I thought this is JNDI related, but I'm not sure).
Thanks for reading this.

No problem,
As far as I know MX records are only to do with SMTP.
There are two options with routing SMTP mail.
You can either try to resolve the target system by looking up the MX records for the address. In your example the domain sun.com and then trying to communicate with the server(s) that that lookup returned.
If you ISP provides you with a "smart" mail server just pass on all email to that and let them do the delivery for you. This is by far the best method if you have a dial up or slow connection.
If you are going to try to deliver directly you need to be able to do the following.
Try to resolve the domain part of the address (sun.com) by doing an MX type lookup and getting one or more servers. Pick a server and try to communicate to it on port 25.
The MX lookup may fail in which case the domain portion of the address should match a host name in the DNS i.e. [email protected]
If you can't find a matching A record then you give up.
Also be aware that somebody@[1.2.3.4] is also a legal SMTP address. (No lookups required there though!)
DNS record types
MX - mail exchanger (normally for a domain or subdomain) and there can be more than one.
A - Address record this should have the actual IP address of the target system. This is at a HOST level. You can't have an A record for a domain.
CNAME - Regard this as a type of alias which should point to an A record as in my last post or possibly another MX record.
With regards to needing an MX record in your DNS, you will if you have other SMTP servers using your DNS server to send mail unless the mail you are receiving is address to somebody@theactualhostname in which case just an A record will do.
Check out RFC2821 in particular section 5.
Try this address
http://community.roxen.com/developers/idocs/rfc/rfc2821.html
rgds,
SH

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

Cannot send email to subdomain

iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)
libimta.so 5.2 Patch 2 (built 19:30:12, Jul 14 2004)
SunOS stud.usm.my 5.9 Generic_117171-17 sun4u sparc SUNW,Sun-Fire-V240
We have a domain xxx.com and a subdomain stud.xxx.com...the first domain is for our staff and the second one is for our students...the problem we have now is we cannot send email from xxx.com to stud.xx.com and vice versa...
when we click send button to send email from [email protected] to [email protected], we'll see a pop-up window
SMTP Error: 5.1.1 Unknown or illegal alias: [email protected]

We have 3 servers, 1 directory and 2 messaging
xxx.com is in one server
stud.xxx.com is in another server
both point to the directory server
I created users using IDa and ldapadd
The domains :
dc=xxx,dc=com,o=internet
objectClass=top
objectClass=domain
objectClass=inetDomain
objectClass=mailDomain
objectClass=nsManagedDomain
dc=xxx
description=DC node for xxx.com hosted domain
inetDomainBaseDN=o=xxx.com, dc=xxx,dc=com
inetDomainStatus=active
mailDomainStatus=active
preferredMailHost=xxx.com
mailDomainDiskQuota=-1
mailDomainMsgQuota=-1
nsMaxDomains=1
nsNumUsers=1
nsNumDomains=1
nsNumMailLists=0
dc=stud,dc=xxx,dc=com,o=internet
objectClass=top
objectClass=domain
objectClass=inetDomain
objectClass=mailDomain
objectClass=nsManagedDomain
dc=stud
description=DC node for stud.xxx.com hosted domain
inetDomainBaseDN=o=stud.xxx.com, dc=xxx,dc=com
inetDomainStatus=active
mailDomainStatus=active
preferredMailHost=stud.xxx.com
mailDomainDiskQuota=-1
mailDomainMsgQuota=-1
nsMaxDomains=1
nsNumUsers=1
nsNumDomains=1
nsNumMailLists=0
user instance:
uid=helpdesk, ou=people, o=stud.xxx.com, dc=xxx,dc=com
objectClass=top
objectClass=person
objectClass=organizationalPerson
objectClass=inetOrgPerson
objectClass=inetUser
objectClass=ipUser
objectClass=nsManagedPerson
objectClass=userPresenceProfile
objectClass=inetMailUser
objectClass=inetLocalMailRecipient
mail=[email protected]
mailUserStatus=active
dataSource=NDA 4.5 Delegated Administrator
mailHost=stud.xxx.com
givenName=Helpdesk
cn=Helpdesk
uid=helpdesk
sn=
inetUserStatus=active
memberOf=cn=Domain Organization Administrators,ou=2005-student-,o=stud.xxx.com,dc=xxx,dc=com
mailDeliveryOption=mailbox
preferredLanguage=en
nswmExtendedUserPrefs=meDraftFolder=Drafts
nswmExtendedUserPrefs=meSentFolder=Sent
nswmExtendedUserPrefs=meTrashFolder=Trash
nswmExtendedUserPrefs=meInitialized=true
pabURI=ldap://dir.xxx.com:389/ou=helpdesk, ou=people, o=stud.xxx.com, dc=xxx,dc=com,o=pab

Changing the internal domain to a subdomain -- Help!

Hello, so I have a huge project coming up and i was wondering if someone had some experience on this that could give me some advice.
So, started working on this company that has an internal domain called.. lets say abc.com and external alphabetaghama.org .. the problem we have is that we cannot get certs for our internal domain for public access like our exchange
server fqdn for example is exchange.abc.com ... Someone else owns abc.com which prompted my new boss to fix this and now i have a project to change our internal domain to match our external but I know that the best practice is to have a
subdomain as the internal domain and I think that's the route my boss wants to go with.. which brings me to my question.
What will I have to do to get this accomplished... our external domain name is really just a forward zone and i dont have a forest so does that mean that i will have to build a alphabetaghama.org forest and add a subdomain like corp.alphabetaghama.org
for our internal and then migrate everything over?
We currently have exchange 2007 with 2008R2 DC's.. our new domain would be on 2012R2 DCs with the same exchange server..
Sorry if something doesn't make sense, I'm a little new to a major project like this...

Hi,
This really depends on the requirements. As the Domain restructure is a huge project, we'd better have some experts with good experenses at hand. And if the problem (to get public access) is solved, it is recommended to have a good consideration
if the rebuilding is needed.
Regarding the internal domain name, maybe you want to have a look into the below MS article:
How Domain Rename Works
http://technet.microsoft.com/en-us/library/cc738208(v=WS.10).aspx
For your reference:
ADMT Guide: Migrating and Restructuring Active Directory Domains
http://technet.microsoft.com/en-us/library/cc974332(v=WS.10).aspx
One thing to mind is ADMT tool may cannot
be installed on a Windows Server 2012 DC, so please make sure in the target domain we have a Windows Server 2008 DC to be the ADMT server.
ADMT 3.2 and PES 3.1 installation errors on Windows Server 2012
http://support.microsoft.com/kb/2753560
Hope this may help
Best regards
Michael
If you have any feedback on our support, please click
here.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How can you set up your subdomain pages in a subdirectory to show without the subdirectory name but the subdomain instead

I am trying to understand how I can set up a series of pages for each of several subdomains such that when you view that web page it shows on the subdomain without the subdirectory name. Essentially I suppose I am wanting to point the subdomain at a folder...
For example I have my main site with the domain mysite.com.au and have 3 subdomains sub1.mysite.com.au, sub2.mysite.com.au etc... I want to then store the pages relating to each subdomain in their own subdirectories /dir01, /dir02 and /dir03 or otherwise named as something appropriate.
What want is to I have the page page1.htm in each of these subdirectories such that I can view the page with the url "http://sub1.mysite.com.au/page1.htm" and have the url displayed as such once loaded rather than having to enter http://mysite.com.au/dir01/page1.htm
Is this a simple or complicated process to put in place?

Hello Julie.
Your junk filter appears to not be working properly. Try this first:
1. Go to Preferences > Junk Mail and disable junk mail filtering.
2. Quit Mail, then open it again.
3. Go to Preferences > Junk Mail, enable junk mail filtering, and configure it however you wish -- I recommend you to leave it at the default Automatic settings.
4. Reset the junk filter database (Preferences > Junk Mail > Reset).

PCNS -- forest Subdomain -- the SPN you Specified could not be found on any accounts in this domain

Hello there Fim lovers,
i'm having few issues with PCNS hope you can help out,
so my Active directory Infrastrucutre is made out of a Root Domain "company.net" and lots of subdomains
"sub1.company.net", "sub2.company.net" ....
the FIM Server and service accounts are all in the Root domain and my users are in the subdomains as is the case usually...
i ran the setspn on the service account in the root domain then ran the pcnscfg on the subdomain DC where my users are stored...
i get the following warning :
The Service Principal Name you specified could not be found on any accounts in this domain. (which is normal since the service account is in the root domain)
did i do smthn wrong ? or can i ignore this warning ?
thanks for any help !!!
Hitch Bardawil

Hi,
Check this note - KBA 1671522, it holds good for RFC also.
Arun

How do I set up subdomains pointing to folder in your site

I am trying to determine whether it is possible to set up a series of subdomains such that each points to content within a folder in your site with the URL of pages displayed showing the subdomain without the subfolder name.
Case in question… If I have a website at say mysite.com.au with subfolders, dir01 and dir02 that each contain the pages I want displayed in relation to subdomains. I set up subdomains sub01 and sub02.
Is it possible to have my BC site working such that I can reference a page, say page01, within the subfolder to be displayed with its subdomain name as sub01.mysite.com.au/page01 rather than seeing it as mysite.com.au/dir01/page01
I know I can point the home page for the subdomain to a page within the folder but it still shows the subfolder in the url – I want the pages within the subfolder to be related to the subdomain and show/use url’s based on the subdomain without reference to the subfolder.
Is this possible and if so is this a simple or complex process to put in place?

Hi, I think this may help:
Create a landing page where your main domain will point to and add this code within the HEAD tag and just specify the folder for your countries as bellow demonstrated.
<head>
<script> window.location =
{% if globals.visitor.country == 'AU' %}
"/au"
{% elsif globals.visitor.country == 'US' %}
"/us"
{% elsif globals.visitor.country == 'GB' %}
"/gb"
{% else %}
"/store-unavailable"
{% endif %}
</script>
</head>
DONT FORGET THIS WILL ONLY WORK IF YOU ENABLE YOUR BC.NEXT RENDERING FOR LIQUID CODING.
I normally use it to display messages on my site for each country as a welcome.

How do I set up a redirect from a subdomain to a specific path in my site?

Running OS X Tiger Server 10.4.11 (all latest updates).
For our online Web site we want to be able to allow users to type in a simple URL to get to our sign-in page which has a terribly long URL.
User types http://signin.ourdomain.com ---> goes to ---> http://www.ourdomain.com/cj/priv/auth/signin.php
Here is what I have tried so far:
1) Set up an "A" record with host name "signin" pointing to the IP address of this Web server in our DNS.
2) Set up 2 redirects (just in case) in Server Admin that look like this:
Redirect http://signin.ourdomain.com http://www.ourdomain.com/cj/priv/auth/signin.php
Redirect signin.ourdomain.com http://www.ourdomain.com/cj/priv/auth/signin.php
This seems to be right, but I cannot get it to work. Im missing something here. Typing http://signin.ourdomain.com simply takes me to http://www.ourdomain.com and not to the full path set up in the redirect.
I seem to be missing something here??? I've restarted Apache to ensure the changes take effect (restart graceful) but I still am not taken to the URL I want in the redirect.

Camelot,
I had the same idea last night (late) while I was stressing about getting this working. I tried the exact setup you mentioned and it still does not work. I am baffled!
Here is what I have:
1) An "A" record in my DNS with host = "signin" and IP address the same as my www.mydomain.com address
2) In Server Admin, created a new Web site called "signin.mydomain.com" with the Domain Name=signin.mydomain.com, same IP address as the www site, port 80.
3) set its document root to "/Library/WebServer/Documents/signin" which is just a subdirectory in my doc root. I even have an index.html file there that also does a redirect!
4) Added a redirect under the "Aliases" tab with the following: Style=Redirect, Pattern= / , Path=http://www.mydomain.com/cj/priv/auth/signin.com .
What baffles me to no end is that I even set up an index.html file in the new docroot for signin.mydomain.com that does an HTTP redirect to the signin page and it doesn't work either. It is like all my settings are being ignored by the server??? I made sure there was an entry in the /sites/ directory via terminal to ensure that Server Admin wasn't being flaky, it looks okay.
If I manually type the URL http://www.mydomain.com/signin/ it does the redirect just fine. The "signin" subdomain is active, since it at least takes me to www.mydomain.com, whereas if I entered one that was invalid like monkey.mydomain.com I would get a "failed to open page" error.
This can't be this hard? I must be missing something incredibly simple and stupid in my setup, but for the life of me, It all looks okay to me.

Path in subdomain

hello,
I am developing web application with subdomain
domain: www.mydomain.com
subdomain: cms.mydomain.com
in the subdomain is an a xx.jsp and I try to get I get the absoulute path in it
    String myPath = request.getSession().getServletContext().getRealPath("/");
    but by output myPath =""   //empty String
    what shoud be the problem


hello,
I am developing web application with subdomain
domain: www.mydomain.com
subdomain: cms.mydomain.com
in the subdomain is an a xx.jsp and I try to get I get the absoulute path in it
    String myPath = request.getSession().getServletContext().getRealPath("/");
    but by output myPath =""   //empty String
    what shoud be the problem
       regards

How can I set up the Dreamweaver CS6 server for a subdomain of an alias

Through my hosting provider, GoDaddy, my primary domain is oldstraycat.com. I successfully added a mobile site by entering this for the server information: Root Directory (blank), Web URL: http://oldstraycat.com/. That worked.
I also have an alias under that account, twoflutes.com. For that I entered this information: Root Directory: amy, Web URL: http://www.twoflutes.com. That worked, too. Now I need to add a mobile site for twoflutes, and here is where I run into problems. At GoDaddy I set up a subdomain for twoflutes.com: the subdomain is mobile and the folder is mobile2. Leaving http://www.twoflutes.com/ as it is for the URL, in the Root Directory box I entered amy/mobile and amy/mobile2, but when I hit the Test button I get the message "Cannot open the server at amy/mobile2". So then I tried entering just mobile2 in the root folder but the result is an error message page on my mobile device that reads, "Ever feel like you are in the wrong place?"
What am I doing wrong? I would really appreciate your help.

You will need to enable file sharing in System Preferences
as well as setting up sharing and permissions for the
directories that you want shared. You may also want to
setup a non-administrative user or allow limited guest
access. The user would require entering a user name and
password to make the connection, but would allow remotes
to change files, if set up tat way.
As for serving iTunes media, better to post in the iTunes forum.

Email address with subdomain doesn't show up as sender

My email address from work has a subdomain: "[email protected]".
Although my mac Mail account is set up correctly with that email address in the account settings, when I send mail, users receive it showing that the sender (from:) is "[email protected]" - it drops the subdomain.
When respondents reply to the email, the reply is sent to "[email protected]" and the delivery fails.
Is there any way to maintain the subdomain so it the address shows up correctly for replies?
Thanks very much.

Figured out iTunes was looking at the Entourage address book instead of the Apple one. Now just need to figure out how to get it to look at the Apple one...

I need a mail server without SMTP authentification. Which is the right one? Or how to configure OSX Lions Mailserver?

Hello folks,
our HP Scanner with email delivery is one the most used pieces of hardware in our office. Just scan and get delivered to your inbox. That works easy and perfect.
Unfortunately we had to change our standard mail server and now a prerequsisite is the smtp authentification. But the HP admin interface on the scanner does not allow to enter smtp auth credentials. It only supports smtp delivery without username/password. Now I have a serious problem. I cannot find any external provider that supports smtp mail delivery without smtp authentification (against spam of course, I understand that).
I have a OSX Lion Server running as a file server in our network. But I have no clue if there's a way to use it's mailserver without smtp auth.
Is there anyone who can help me out?
Cheers,
Joo-Chen

I have a OSX Lion Server running as a file server in our network. But I have no clue if there's a way to use it's mailserver without smtp auth.
Sure. Turn it on.
The default mode is to not require authentication. You have to turn on authentication if you want it.
Changing authentication on/off is a matter of clicking a radio button.

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

Business Catalyst released subdomain not reusable

When developing my first Muse site, I used a number of temporary sites on BC for live testing with the client. Once everyone was happy then this was published to their server using the FTP feature. Having been brought up correctly, I then went onto BC and deleted all the test domains (which were blueapplenn.businesscatalyst.com - where nn = 01-05), which I did yesterday.
The client is so pleased with the new website that I have started working on Mk II so tried to use blueapple01 (and 02) again - when I publish everything in Muse works fine and I sit there twiddling my thumbs while it uploads but the trouble is I can't get onto the website (http://blueapple01.businesscatalyst.com/index.html) as the browser says the server can't be found. I tried a name which I hadn't used before, and this now worked fine.
So it looks as though BC is holding on to the old subdomain definitions somwhere?
Peter

This is fixed. Should be working now, if not please try after an hour or so.
Thanks,
Vinayak

Mailserver on subdomain?

Similar Messages

Maybe you are looking for