Subdomaining .local

I'm a web developer on Mac OS X 10.5.6 and I use my MacBook Pro as my primary development and testing machine. I have Apache 2 running and Entropy PHP 5.2.4. All of that works fine. In the past, I didn't use virtual hosts. Instead, I would divide my projects into subfolders of /Library/WebServer/Documents
One day, I wised up and created virtual hosts by adding the appropriate entries to /etc/apache2/extra/httpd-vhosts.conf and by adding a few corresponding hostnames to /etc/hosts.
In the hosts files, I "created" subdomains for each site. For example: If I was working on a site for Dairy Queen, I might add the following line to /etc/hosts:
127.0.0.1 dq.local
Then I would add the virtual host to /etc/apache2/extra/http-vhosts.conf and it would look something like the following:
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Library/WebServer/DairyQueen/Documents"
ServerName dq.local
<Directory "/Library/WebServer/DairyQueen/Documents">
Options FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
I've been setup in the above way for many months and it all works great. On my computer, I can enter dq.local in my browser and it pops right up.
I've even modified the hosts file in my Parallels Virtual machines running Windows. And from any browser in any of my Virtual machines, I can reach my various .local domains hosted by Mac OS X.
The Problem: If I want to browse the site from another computer on my local network (or my iPhone), they will not find my MacBook Pro in the .local domain without editing the /etc/hosts files on those devices -- which is a nightmare scenario because A) I can easily edit the /etc/hosts file on the iPhone, B) It's inconvenient to have to edit /etc/hosts files on the myriad of devices, and C) I would have to have my laptop set to a static IP -- something I could easily accomplish, but it's just not as clean of a solution as I'm looking for.
I realized that when using Bonjour, my MacBook Pro shows up to other computers as "Christophers-MacBook-Pro.local". I thought, hmmm ... maybe I could utilize that by dividing it into subdomains. For example, I would modify the vhosts file setting the new domain name to dq.christophers-macbook-pro.local, I would modify my own /etc/hosts file to say:
127.0.0.1 dc.christophers-macbook-pro.local
... and Voila! I'd be done, right? Nope!
Of course on the MacBook Pro that's hosting the sites, I can browse to dq.christophers-macbook-pro.local, and it works fine just like it did when it was dq.local.
On a PowerBook G4 (running a freshly installed and clean 10.5.6), going to dq.christophers-macbook-pro.local results in the wrong site from coming up. What!?
Note that when I go to just "christophers-macbook-pro.local" on the iPhone and the PowerBook, the correct site comes up -- from the MacBook Pro.
Turns out, my xServe running Leopard Server is responding to the request and serving up my photo gallery site on both the PowerBook and the iPhone!
I do have DNS running on the server. The other computers are connected wirelessly and via DHCP from an Airport Extreme Base Station that IS NOT getting DNS from the server, rather it's getting DNS from Comcast. The notbooks and the iPhone are getting DNS from the Base Station.
When I stop the DNS service on my xServe, there's no effect -- the web response is still coming from the server. (Yes, I flushed the DNS cache on the PowerBook just to be sure). I checked the virtual hosts on the server and none of them is configured with a wildcard as an alias. The photo site IS the first entry in the sites list -- the first virtual host.
So, how do I break my MacBook Pro's .local domain into subdomains? What am I missing?

MacWorks wrote:
What am I missing?
A functional nameserver. Clicking on a checkbox doesn't accomplish anything; you have to configure your zone files appropriately and actually make the other computers on the network care about the zones you've chosen to claim authority over.

Similar Messages

Trouble with creating subdomains for .local address

I'm a web developer on Mac OS X 10.5.6 and I use my MacBook Pro as my primary development and testing machine. I have Apache 2 running and Entropy PHP 5.2.4. All of that works fine. In the past, I didn't use virtual hosts. Instead, I would divide my projects into subfolders of /Library/WebServer/Documents
One day, I wised up and created virtual hosts by adding the appropriate entries to /etc/apache2/extra/httpd-vhosts.conf and by adding a few corresponding hostnames to /etc/hosts.
In the hosts files, I "created" subdomains for each site. For example: If I was working on a site for Dairy Queen, I might add the following line to /etc/hosts:
127.0.0.1 dq.local
Then I would add the virtual host to /etc/apache2/extra/http-vhosts.conf and it would look something like the following:
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Library/WebServer/DairyQueen/Documents"
ServerName dq.local
<Directory "/Library/WebServer/DairyQueen/Documents">
Options FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
I've been setup in the above way for many months and it all works great. On my computer, I can enter dq.local in my browser and it pops right up.
I've even modified the hosts file in my Parallels Virtual machines running Windows. And from any browser in any of my Virtual machines, I can reach my various .local domains hosted by Mac OS X.
*The Problem:* If I want to browse the site from another computer on my local network (or my iPhone), they will not find my MacBook Pro in the .local domain without editing the /etc/hosts files on those devices -- which is a nightmare scenario because A) I can easily edit the /etc/hosts file on the iPhone, B) It's inconvenient to have to edit /etc/hosts files on the myriad of devices, and C) I would have to have my laptop set to a static IP -- something I could easily accomplish, but it's just not as clean of a solution as I'm looking for.
I realized that when using Bonjour, my MacBook Pro shows up to other computers as "Christophers-MacBook-Pro.local". I thought, hmmm ... maybe I could utilize that by dividing it into subdomains. For example, I would modify the vhosts file setting the new domain name to dq.christophers-macbook-pro.local, I would modify my own /etc/hosts file to say:
127.0.0.1 dc.christophers-macbook-pro.local
... and Voila! I'd be done, right? Nope!
Of course on the MacBook Pro that's hosting the sites, I can browse to dq.christophers-macbook-pro.local, and it works fine just like it did when it was dq.local.
On a PowerBook G4 (running a freshly installed and clean 10.5.6), going to dq.christophers-macbook-pro.local results in the wrong site from coming up. What!?
Note that when I go to just "christophers-macbook-pro.local" on the iPhone and the PowerBook, the correct site comes up -- from the MacBook Pro.
Turns out, my xServe running Leopard Server is responding to the request and serving up my photo gallery site on both the PowerBook and the iPhone!
I do have DNS running on the server. The other computers are connected wirelessly and via DHCP from an Airport Extreme Base Station that IS NOT getting DNS from the server, rather it's getting DNS from Comcast. The notbooks and the iPhone are getting DNS from the Base Station.
When I stop the DNS service on my xServe, there's no effect -- the web response is still coming from the server. (Yes, I flushed the DNS cache on the PowerBook just to be sure). I checked the virtual hosts on the server and none of them is configured with a wildcard as an alias. The photo site IS the first entry in the sites list -- the first virtual host.
So, how do I break my MacBook Pro's .local domain into subdomains? What am I missing?

HI,
That's about 6 miles over my head but I can suggest that you post in the Apple Mac OS Technologies forum:
http://discussions.apple.com/category.jspa?categoryID=162
Carolyn

[Solved] postfix local mail delivery fails

Hi Guys,
on my home pc i use postfix (gmail as a smtp relay) and fetchmail for sending/receiving mails, this works very well, however sending a mail to a local user fails, I'm lost here and need your help guys.
if i send a mail like :
$>echo "Test" | mail -s "Test : local mail delivery" "andy"
The mail stays in the queue for ever...
$>mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
CC82513BCA* 455 Sun Aug 3 09:53:09 [email protected]
[email protected]
Sending to external addresses works without any problems.
Here some important info/config files :
$>whoami
andy
$>hostname
box
$>cat /etc/host.conf
# /etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost box
::1 localhost.localdomain localhost
192.168.1.3 lbox.localdomain lbox
$>cat /etc/postfix/main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/bin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /var/lib/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
#myhostname = mail.example.com
myhostname = localhost.localdomain
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
mydomain = localdomain
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
inet_interfaces = localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
#mydestination = localhost, localhost.localdomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $pr/oxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
relayhost = [smtp.gmail.com]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
alias_maps = hash:/etc/postfix/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
alias_database = $alias_maps
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
mailbox_command = /usr/bin/procmail
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
# Enable smtp auth
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/saslpass
smtp_sasl_security_options = noanonymous
# Enable tls
smtp_use_tls = yes
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
# Max message size limit
message_size_limit = 0
Please help
Last edited by Rumcajs (2014-08-05 06:16:11)

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

DNS Help: Configure for local and extenal services using same domain name?

Hello all. I'm setting up a 10.5 server, have scoured these great forums and gotten close, but am still stuck. Any help would be greatly appreciated.
My network setup is as follows: Internet (2xT1) > modem > router/firewall/NAT device > XServe > switches > rest of network, clients, etc. Pretty standard, I believe.
I'd like to use this XServe on our local network/intranet/LAN only for OD, networked home directories, AFP, iCal, Time Machine, Print and Software Update.
My website is hosted on an external server.
My email is also hosted on a (different) external server.
Domain is school.edu
XServe name is xserve.school.edu
XServe is 10.0.0.25
I've gone through Apple's recommended DNS setup (supplemented by some great info found here on the forums....), and am able to connect to other Internet sites (with client's DNS server set as 10.0.0.25), but unable to connect to www.school.edu, or send/receive mail to/from mail.school.edu.
In short, connecting to external domains that are NOT related to my school are fine, but I'm unable to connect to any domain that IS related to my school.
If anyone out there can shoot me some notes on how to configure the DNS settings, zones, forwarding, etc. to accomplish this, I'd be VERY appreciative.
Thanks, in advance, to anyone who can help me out.
Cheers,
Tim

In short, connecting to external domains that are NOT related to my school are fine, but I'm unable to connect to any domain that IS related to my school.
If your server thinks it's authoritative for 'school.edu' then you have to add records for every host in the school.edu zone.
For example, if you want to be able to resolve 'www.school.edu' then you have to have a 'www' record. If you want to send/receive mail you have to add an MX record, and so on.
It doesn't matter that you're not responsible for those servers, it's just that since this machine thinks it 'owns' school.edu it will only respond with records in its own zone and won't care about what any other name server says, even if that other name server is authoritative for the zone.
FWIW, that's often why people running stub servers like this choose a separate subdomain (like 'dept.school.edu') so they can leave the main school.edu records on the main server and have full control over a subdomain.

How do I configure snow leopard server to allow local client to access the server using its public domain name

I have SLS 10.6 running on my local network with DNS configured.
I can access the server from a client on the lan using server.local or server.domain where domain name is my publically registered domain,
From the internet I can access my server using the registered domain name i.e. www.domain.com.
Is it possible to set my server up so that www.domain.com also reaches the server when used by a client locally? At present I get a page not found error.

The configuration you're aiming for is called split-horizon or split-brain DNS, and it's quite possible. It can get slightly hairy when you have different stuff using the same host name for different purposes, for instance, and you'll need to track all external DNS entries in your internal DNS server when you're running "split".
Here is how to set up DNS services. Split-horizon is one of the options listed there.
My preference is to use a different domain or subdomain within the network, and to avoid using split-horizon where I can reasonably manage it. One domain name is configured for and reachable outside and is effectively public, and the other domain (or a subdomain) is inside and private and only reachable directly or via VPN, for instance.

Working with virtual host & hosts files on a local network

I'm setting up a small local web and production server here in my office running Leopard.
I'm setting up virtual hosts for users on the network to review and comment on websites in development. Ideally they'd access it as:
host1.webserver.local
host2.webserver.local
host3.webserver.local
Problem is, users on the network can see webserver.local just fine, but the subdomains need to be registered with hosts file on each computer.
Is there a way I can manage all computers hosts file easily? I was thinking of an SVN repository, but this still requires going to each computer to update the file.
Any suggestions here would be great.
Thanks
Rich

Hi jscher2000
Thank you for your interest.
I am using "manual prxoy configuration" option in firefox with port 8080. I have tried the option of "Use system proxy settings" but it doesn't help.

Adding alternative FQDN for local domain.

Hi,
I'm trying to configure RDS for my standalone Windows Server 2012 Essentials and it's almost done.
(Probablly) last thing i need to do is to change FQDN for my local domain to .com to use RDS externaly.
So, like i said, i've done dyndns config, added ssl cert, configured RDWeb, RD Gateway, RD License and RD Broker.
Now, when i'm logging into remote.mydomain.com/RDWeb , i can login with Active Directory credentials, get rdp i try login into server. But i can only try, becuase there is an error about wrong FQDN for server (know and not new error for anyone). So, what I
had done was changing FQDN for my domain by this powershell script http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80 (if anyone had problems with digitally unsigned script, google for "Set-ExecutionPolicy Unrestricted"), in
theory, this script changed FQDN, but in reality, i still have same problem trying to connect externally.
I also read that i should add new DNS Zone for my .com domain and there add (A) record for my subdomain for remote desktop, that points to internal IP adress of my server. When i tried that, it was even worse because i couldn't even open RDWeb site. When that
dns zone was deleted, everything came back to previous state.
And now i'm here, out of ideas. Any suggestion what I did wrong? Maybe it was something with this DNS Zone for .com ? Maybe there should be Zone, but not normal one but "stub zone"?
I would be happy for any suggestion.

" suspect we may have a basic mis-understanding of what each of us is trying to say. Let me try again.
There are (at least) three ways to reach a LAN computer from the internet with Essentials. Remote Web Access, direct RDP and VPN. There are also third party solutions, such as Go To My PC and Log Me In. The third party type
usually involve a subscription model with recurring charges, the others may involve a fee for SSL certificates, but they are (usually) much less expensive and do not rely on a third party."
Yes, i can agree we difinitelly had problem with mis-uderstanding so, sorry for that. I was talking about direct RDP to my server because Anywhere Access is already configured (but remote desktop from there to server opened only Essential Dashboard, that's
why i left this solution). Also, like i said, i'm aware of risks and i'll
take responsibility for that.
"Direct RDP is configured at the router and points the port (3389, but it can be changed) to the IP of the device you want to contact. then, simply opening the RDP applet on your remote computer and typing in the public IP of the router/firewall
will automatically connect you to the chosen computer. This is a very high security risk and should be avoided when ever possible."
Here is double facapalm for me - when you wrote about 3389 TCP port, i got enlightenment that i didn't do that (because i ealier tried to work on 443 with Anywhere Access and forgot about it), also information i got after tries to connect weren't usefull neither
- because Windows gave me back information about wrong FQDN, i was strictly focused on that problem, but like we know now, problem was in much different place. When i opened that port, everything started to be like i wanted (i also find out, after testing
RDP client from remoteapp in web menu that why i'm using this when i want to used direct RDP anyway). So much facepalm.
Next thing for now will be different port then 3389 and in future, VPN instead of direct RDP.
Anyway, really, thanks for help!

Advice needed on move to in-house email. DNS and subdomain newbie.

Hi there.
One of my hats says IT Manager and I have a decision to make regarding about email services for a fast growing company.
At present my company uses MediaTemple to host our web and email, but are presently finding many limitations particularly in the flexibility of email accounts specific to various sub domains. An example of a feature we need (but {mt} can't provide) is separate accounts for [email protected] and [email protected] MediaTemple will only allow a single mailbox.
We desperately require this functionality which leads to my questions (as I'm easily perplexed by DNS and BIND):
1. Is it possible to modify a DNS zone file so that subdomains can exist for both our website (which will continue to be hosted with MediaTemple) and also exist locally for email on our in-house Xserve G5 running Mac OS X Server 10.4.7?
2. Does the Mail Server in 10.4 allow individual mailboxes for the same name under different subdomains.
Sorry for the dubious explanations. I barely understand the process itself, but I'm learning.
Thanks in advance,
Aaron in Australia.
Apple Xserve G5 Single 2GHz, 2GB/750GB Mac OS X (10.4.7)

The answers are yes and yes...
Managing a mail server, even on a Mac, can be complex and require a significant investment in time. If this decision is difficult, imagine trying to make ongoing config decisions, battle spammers, hackers and maintain 24/7 uptime for your users. Are you ready for that?
I would think that your current mail hosting company can host mail for a subdomain, but probably not within the same hosting account. The level 1 people you are talking with may not have a clue. You may need a hosting account for each subdomain (with user accounts in each hosting account). If this email hosting provider doesn't support subdomains, then consider others (really any should). You'll need to make some DNS adjustments, something the hosting company can direct you on.
Jeff

Subdomain access problem

Hi - I'm having a problem with cross domain scripting. I've
got an admin interface at www.admin.mydomain.com and it's trying to
access a shim movie at www.mydomain.com. I've tried all possible
permutations of crossdomain.xml and system.security.allowdomain.
The swfs were authored in flash8 but I've just switched to flash10
and am publishing them for flash10 - the error messages when
debugging are more complete.
I've had to put the crossdomain.xml on the root of the server
and on the root of the subdomain (with
permitted-cross-domain-policies = "all") otherwise the admin swf
complains when the root crossdomain.xml tries to access it. I'm
explicitly calling system.security.loadpolicyfile in both movies.
I've tried setting system.security.allowdomain(_parent._url) in the
shim movie and system.security.allowdomain(_shim_mc._url) in the
admin swf (which is in the subdomain). This removed all of the
sandbox error messages (eg
*** Security Sandbox Violation ***
SecurityDomain '
http://www.mydomain.com/shim.swf'
tried to access incompatible context '
http://www.admin.mydomain.com/'
that I was getting when the shim loaded into the admin but
whenever cross scripting occurs I get the same error messages. I
don't believe it should be necessary to call
system.security.allowdomain every time I cross-script, at least
I've never read that anywhere and I've read a fair amount of
tutorials, helpfiles, whitepapers etc to try and understand what is
happening. Maybe I'm wrong - can anyone help? Below is my
crossdomain.xml

Hi,
FYI - The best method to demote a domain is, while demoting the last domain controller for a domain, you need to select the option
This server is the last domain controller in the domain option in the DCPromo tool, which removes the domain meta-data from Active Directory.
From your details, I remove the subdomain Sub.myCompany.local successfully. But when i try to connect to domain by othe clients i see SUB in the list of domains that client that connect to it.
This is due to the domain meta-data is not removed from the Active Directory.
Checkout the below KB article for removing the orphaned domains from the Active Directory,
How to remove orphaned domains from Active Directory
Regards,
Gopi
www.jijitechnologies.com

How do I make the autoreply channel respond to local domain users?

I'm running iMS5.1 on Solaris 8. This machine is only used as a mail store (called mailhost). The SMTP (sendmail) server handles aliases and mail lists. The autoreply channel identifies the "respond to" user's e-mail address as NOT local, DEBUG=3 in the options file. The address to respond to is [email protected] Yet, the message never gets sent, the following message is in the trace file:
WARNING: Add sender's address failed: One of the specified addresses does not comply to RFC 822
I checked the auto generated aliases by dumping the IMTA_ALIAS_DATABASE. They are of the form: [email protected]
When the mail message comes from outside our subdomain, autoreply works fine. The message gets sent to our SMTP server. Here are the relevant lines from the imta.cnf:
! Rules to select local users
mailhost.mysub.ourdomain.com \ $U%$[email protected]
mysub.ourdomain.com $U%$[email protected]
<snip> lots of stuff
! autoreply
autoreply defragment subdirs 20
autoreply-daemon
I tried changing the rewrite rules from $U%$D to simply $U and that fixed it, but it broke the "reply to" for incoming messages. Any insights from anybody?
Thanks,
RS

I'm running iMS5.1 on Solaris 8. This machine is only used as a mail store (called mailhost). The SMTP (sendmail) server handles aliases and mail lists. The autoreply channel identifies the "respond to" user's e-mail address as NOT local, DEBUG=3 in the options file. The address to respond to is [email protected]. Yet, the message never gets sent, the following message is in the trace file:
WARNING: Add sender's address failed: One of the specified addresses does not comply to RFC 822
I checked the auto generated aliases by dumping the IMTA_ALIAS_DATABASE. They are of the form: [email protected].
When the mail message comes from outside our subdomain, autoreply works fine. The message gets sent to our SMTP server. Here are the relevant lines from the imta.cnf:
! Rules to select local users
mailhost.mysub.ourdomain.com \ $U%[email protected]
mysub.ourdomain.com $U%[email protected]
<snip> lots of stuff
! autoreply
autoreply defragment subdirs 20
autoreply-daemon
I tried changing the rewrite rules from $U%$D to simply $U and that fixed it, but it broke the "reply to" for incoming messages. Any insights from anybody?
Thanks,
RS

Powershell add group to local admin group

how do I remotely use powershell to add a domain group to the local admin group on a machine?
thanks

When using above, I got:
[DBG]: PS C:\>> $remoteComputer = 'xxx.xxx.xxx.xxx'
[DBG]: PS C:\>> $groupname = 'Admin-Group'
[DBG]: PS C:\>> $fqdn = 'subdomain.domain.com'
[DBG]: PS C:\>> ([ADSI]"WinNT://$remoteComputer/Administrators,group").Add("WinNT://$fqdn/$groupName"):
Exception calling "Add" with "1" argument(s): "Access is denied.
At line:1 char:1
+ ([ADSI]"WinNT://$remoteComputer/Administrators,group").Add("WinNT://$fqdn/$group ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : CatchFromBaseAdapterMethodInvokeTI
I am wondering how $remoteComputer authenticate?

Subdomain authorization error

Hi All,
I have installed AM 2005Q4 on Solaris and Policy Agent 2.2 on Windows 2003 server. It works fine to protect the web resources. Both servers are in the same domain eg. am.abc.com.uk and w2k.abc.com.uk
I got a problem with Policy Agent 2.2 installed on another Windows 2003 with a subdomain name like xyz.cs.abc.com.uk. There is a forbidden error 403 for the protected web resources after login.
Please kindly advise how to fix this.
Thanks in advance.
Frank.

We are facing the same trouble here ....
on running NETSTAT in DOS here is the following report
Active Connections
Proto Local Address          Foreign Address        State
TCP    HP12109112533:4824     XXXXX.com:50000 TIME_WAIT
TCP    HP12109112533:4825     XXXXX.com:50000 TIME_WAIT
TCP    HP12109112533:4828     XXXXX.com:50004 ESTABLISHED
TCP    HP12109112533:4829     XXXXXMASK:50004      SYN_SENT
WHY is 50004 port coming in the picture ?
Also if i need to open the port 50000 sud it be on my desktop or at the server side ?
Regards,
Shabarish

Ims 5.2 patch2 local delivery problem when internet link is down

Hello, I have a ims 5.2 p2 server configured for direct LDAP and Symantec gateway 3.0.0.
I don't know why my server is unable to deliver local emails to exiting LDAP users when my internet connection is down. I have as bellow two channels tcp_scan for routing incoming emails to symantec port 2525 and tcp_noscan for the way back my server port 2500. Seems like my local emails don't get to the tcp_scan channel for some reasons, or they are stuck there.
I also have a smart host confgured in my tcp_local channel, and you may say it explains my problem, Not true, because if I remove the configuration needed for symantec and recompile ( cnbuild, restart dispatcher) , local delivery works OK even without internet. hereis the log line for an example:
28-Jan-2005 17:18:56.52 tcp_intranet tcp_scan E 1 [email protected] rfc822;[email protected] cristian.vladuta@ims-ms-daemon
28-Jan-2005 17:19:45.63 tcp_scan Q 1 [email protected] rfc822;[email protected] cristian.vladuta@ims-ms-daemon Failed MX lookup; try again later
Please give me a hint.
--------------imsimta.cnf
! ims-ms
! for Direct LDAP mode remove "filter ssrd:$A" from the keywords below
ims-ms defragment subdirs 20 notices 1 7 14 21 28 backoff "pt5m" "pt10m" "pt30m" "pt1h" "pt2h" "pt4h" maxjobs 1 pool IMS_POOL fileinto $U+$S@$D
ims-ms-daemon
! pipe
pipe single defragment subdirs 20
pipe-daemon
! tcp_local
tcp_local smtp mx daemon mr01.hq.xx.org remotehost inner switchchannel identnonelimited subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver saslswitchchannel tcp_auth
tcp-daemon
! tcp_intranet
tcp_intranet smtp mx single_sys subdirs 20 noreverse maxjobs 7 pool SMTP_POOL maytlsserver allowswitchchannel saslswitchchannel tcp_auth
tcp_intranet-daemon
! tcp_submit
tcp_submit submit smtp mx single_sys mustsaslserver maytlsserver
tcp_submit-daemon
! tcp_auth
tcp_auth smtp mx single_sys mustsaslserver
tcp_auth-daemon
! tcp_tas
tcp_tas smtp mx single_sys allowswitchchannel mustsaslserver maytlsserver deliveryflags 2
tcp_tas-daemon
! tcp_noscan
tcp_noscan smtp mx single_sys subdirs 20 noreverse maxjobs 7 pool SMTP_POOL allowswitchchannel
tcp_noscan
! tcp_scan
tcp_scan smtp mx single_sys subdirs 20 noreverse maxjobs 7 pool SMTP_POOL daemon 127.0.0.1 port 2525 dequeue_removeroute
tcp_scan
----mappings
ORIG_SEND_ACCESS
tcp_local|*|tcp_local|* $N$D30|Relaying$ not$ allowed
tcp_*|*|hold|* $N
tcp_*|*|pipe|* $N
tcp_noscan|*|ims-ms|*          $Y
tcp_*|*|ims-ms|* $N
SEND_ACCESS
tcp_*|*|*|*@[127.*] $X5.1.2|$NBad$ destination$ system
tcp_*|*|*|*@localhost.* $X5.1.2|$NBad$ destination$ system
! Delete the next two items for Direct LDAP mode
! *|*|inactive|* $X4.2.1|$NMailbox$ temporarily$ disabled
! *|*|deleted|* $X5.1.6|$NRecipient$ no$ longer$ on$ server
CONVERSIONS
     IN-CHAN=tcp_noscan;OUT-CHAN=*;CONVERT     NO
     IN-CHAN=tcp_*;OUT-CHAN=*;CONVERT     Yes,Channel=tcp_scan

Yes , I have a local DNS Server on my windows 2k tcp_scan box (pointing correctly to it) .
After disconnecting the WAN link, I query via nslookup for the mx record AAA.ORG and get the right result as inet01.test.AAA.org as mail exchanger and corresponding IP address. I have created a primary zone AAA.ORG and defined an MX record inet01.ro.undp.org Under it I have the RO subdomain and the A record of inet01.ro.undp.org
At first I thought it may be the problem that by disconnecting the cable the LAN interface goes down and therefore the IP cannot be resolved. Then I have associated the A record of the mx exchanger with 127.0.0.1.
Still my MX cannot be resolved apparently by the ims5.2 server!!!
Jay, I trully appreciate what you do here and I don't waist your time, and I really don't understand what I do wrong. Thank you very much

Leopard Web-Server with Subdomains?

Hi,
I am new to Leopard and maybe have a simple question – but it seems I cannot solve it by myself
I run Leopard Server 10.5.1 in a small company and would like to use the web-service with a subdomain.
My standard webserver url is: server.form-one.intern (uses standard webserver/documents folder)
Desired Subdomain: f1.form-one.intern (should use user/admin/sites folder)
So I set up a dns-service primary zone: form-one.intern with machine server to local IP 192.168 ...
If I now type server or server.form-one.intern in Safari it shows the webserver/documents site. Works great.
But when I type f1.form-one.intern it shows an error: server not found.
What must I do? I think I tried everything
Kind regards,
Carlo

What must I do? I think I tried everything
Well, for a start you have to add f1.form-one.intern to your DNS so that the name resolves to an IP address.
If the name is going to map to the same machine as server then you can just add 'f1' as an alias to 'server' in the DNS.
That way you'll at least get 'f1.form-one.intern' to resolve to your server.
The second step is to configure a virtual host in Apache that corresponds to the 'f1' site.
In Server Admin, add a site to the web server configuration and set its name to 'f1.form-one.intern', and set the DocumentRoot to the directory that corresponds to this site.
Now whenever Apache sees a request come in for the f1.form-one.intern server it will route the request through the second virtual host rather than the first.

Setup local server, use sub-domain or bonjour

I can not wrap my pea brain around this one.
I have a new server that I am using for File Sharing and now want to add iChat and iCal. I access the box for file sharing using the LAN IP, but I was wanting to use a sub-domain of my domain. I can do that easy enough from WAN, but for my LAN do I then need to have the DNS server running with a duplicate record of my domain master with the local IP for the sub-domain of my server? Is there a smarter way to access this box from both WAN and LAN for these services? I am not exactly sure what Bonjour provides, but is it a possible solution?
Thanks for any tips and help!
Thom

Guess I could just add the local subdomains to the /etc/hosts of the local machines.

Subdomaining .local

Similar Messages

Maybe you are looking for