NIS Setting

I am trying to reinstall solaris 8 on my used ultra 5. It was previously set up as a networked system and upon boot up looks for the ethernet connection. I want to run the system as a single user system at home NOT networked. Because I have no passwords, I am trying to reinstall solaris 8 so that I can undo all the configurations. When I type "sys-unconfig" it tells me that I can't use this command at this level. So I try to reinstall sol8 and no matter what I enter, it shows up as a networked system(even when I choose not networked)
and whatever I choose for the NIS setting(Which I choose none) shows up as NIS in the confirmation. Then I get an error message saying " trying to set up the NIS binding directory to facilitate automatic serrver location"
All I want to do is reinstall solaris 8 so that I can set the system up for myself. Does anyone have any clues how I can get past this? Thanks!h

Hi,
I suggest you to re-install the solaris8 as standalone m/c and disable the NIS settings in these ways:-
You have to remove the entry from 3 files
a./etc/defaultdomain
b./etc/nodename
c./etc/hostname.hme0 ( may be hme0 or your interface name)
step1. Login as root in single user mode
step2.remove the contents from the above files or remove the file itself .
#rm /etc/defaultdomain
#rm /etc/nodename
#rm /etc/hostname*
Now you can use 'sys-unconfig' command or else reinstall solaris 8 into your system.
Hope this answer your query.
Rgds,
Dhana_slash.

Similar Messages

  • Advantages and disadvantages NIS in Sparc & i386 (Intel based machine)

    Hi Sun Experts
    I have a query can any one tell me the advantages and disadvantages of Nis setting up in Sparc box and i386 .
    My query's are ........
    1. If i set up NIS in i386 box what is the advantage and disadvantage.
    2. if i set up NIS in sparc what is the advantage
    Thanks in advance

    The SPARC/x86 question doesn't really seem relevant here, NIS should work the same whether you run it on a SPARC or X86 box.
    The disadvantages of NIS are, as always that its insecure, insecure and about to be EOL.
    The advantages are that its easy, easy to maintain, fairly reliable if maintained correctly, stable and works across most platforms and operating systems
    .7/M.

  • Accesing music store - A FIX

    Calling all with acces problems......................
    now I'm not taking credit for this but thought other frustrated users needed to know!
    I use a Linsys wireless router and connect to AOL broadband. I was having problems with V5 for weeks, upgraded to v6 and still couldn't access music store. Changed all my NIS setting etc but to no avail. Anyway I tried this and hey presto its worked I've got music back!!! Oh sweet sounds.....
    In your router settings change the WAN tab to manual and set it to 1400.
    ernest polden, "Can`t access Music Store" #21, 03:36am Oct 15, 2005 CDT

    On other routers this will be the MTU (Maximum Transmission Unit) setting. By changing it, you are lowering the the size of data packets handled by the router. It sounds reasonable to me that this could work, particularly if the server is very busy, or traffic in your neighborhood is high.

  • Help setting up NIS

    I'm trying to set up NIS on Solaris 9...my first time using NIS. I am using the documentation provided by Sun but having no luck. After running ypinit -m, it does it's thing but bombs out. Error below:
    make: Warning: Target `all' not remade because of errors
    Current working directory /var/yp
    *** Error code 1
    make: Fatal error: Command failed for target `k'
    Error running Makefile.
    Just a few notes. I have set the domainname and copied nsswitch.nis to nsswitch.conf.
    Any ideas??

    Well again:
    The instructions "The first step in my lab is to set up a static ip address in my linksys wan interface" are insufficient. In order to setup a static IP address you need at least an IP address and a subnet mask. If the router is supposed to provide internet connectivity you also need a gateway IP address and at least one IP address of a DNS server.
    Someone must provide this information unless you know to which network the WAN port of the router should be connected to and have all the IP information on that network.
    But saying "set a static WAN IP address 1.2.3.4 on your router" is simply insufficient. It lacks the necessary information required to set up a static IP address. You need at least the subnet mask to set up anything at all. And you need gateway and DNS server IP addresses to get internet.
    You should not fail for incomplete, insufficient information with the instructions....

  • Setting Banner Certralised (Through NIS Server)

    Hi
    I have to set banner for both telnet and ftp . is it possible to do it centralise i mean through NIS server.
    I have one NIS server (Sun server) and 200 other servers(Sun Servers).
    Actually it is very difficult for me to set banner on all the 200 sun servers
    Thanks in Advance
    RK

    I am not sure if these links will help, but there is a problem with the lp command in Leopard:
    http://discussions.apple.com/thread.jspa?messageID=7128688&#7128688
    http://discussions.apple.com/thread.jspa?messageID=6919636&#6919636

  • Setting up NIS on Mac 10.5 which is not a server

    I understand that I can set up an NIS client on a Mac using the Directory Utility.
    How do I set up the NIS server? Can this be done without a Mac Server?
    What are the differences between a Mac running regular 10.5 and a Mac server?

    mad1 wrote:
    I understand that I can set up an NIS client on a Mac using the Directory Utility.
    How do I set up the NIS server? Can this be done without a Mac Server?
    I saw the ypbind command is there. I think you can do it, but in the unix way.
    It's been eons since I did it. I vaguely remember I had to start from the classic /etc/passwd, "give" it to a makefile to build the yp database and then start ypbind.
    I'm afraid either you have to read the man pages or you wait for someone that remembers these things better than me..
    What are the differences between a Mac running regular 10.5 and a Mac server?
    The server has a lot of utilities (well.. actually two, but they do everything) to let you set and start various services in the mac way.
    Ciao,
    Ermanno

  • Soo much trouble setting up NIS (and if possible AutoFS)

    Hi,
    I have recently started a company, and run an office with 4 workstations running ArchLinux and a server running Debian (Wheezy).
    Ultimately I want this out of the network:
    1. Centralised user accounts
    2. Centralised home directories (mounted over network)
    3. All users should be able to FTP in to the server externally, and reach all the files in their home directory.
    As of now I will be happy just to get NIS working. The homedirectories i can sync over the network with Rsync and then easily share via FTP with VSFTP. So far, I have followed these guides:
    http://www.server-world.info/en/note?os … _7.0&p=nis
    http://penguin.triumf.ca/recipes/nis-auto/
    NIS Problems:
    1. I cant get change passwords. If I run yppasswd on a client, I will get "segmentation fault (core dumped)". Somewhere I read that if you only have one master server, no slaves, you can only change passwords in the server. I tried using yppasswd locally, but that just results in "NIS not being able to change password"
    2. I want to have a seperate passwd and shadow file for NIS, so I was thinking of putting them in /var/yp/etc/, but will login through FTP work?
    General questions:
    1. Is it completely retarded of me to think i can get this working running ArchLinux clients? If so, what do you guys recommend?
    Please. I'm running on 12 hours with this shit now and I just find more and more errors. I need help.

    Set up another box running ArchLinux just to see if i could get it running...
    Followed the wiki on NIS, but I cannot start ypbind. I have up to starting the daemons, without problem. The make command runs fine, but i cannot start the goddamn ypbind daemon. Running systemctl status ypbind gives me.
    ypbind.service - YP Bind
    Loaded: loaded (/usr/lib/systemd/system/ypbind.service; disabled)
    Active: failed (Result: exit-code) since Wed 2014-01-08 22:47:11 CET; 7s ago
    Process: 492 ExecStart=/usr/bin/ypbind (code=exited, status=1/FAILURE)
    Journalctl -xn does not give me anything.
    Last edited by iOfWhy (2014-01-08 22:49:58)

  • Warnings & Errors in Setting up NIS master server

    Hi All,
    I am setting up NIS for that first time & I am getting the following Warnings & errors when I use # /usr/sbin/ypinit -m
    1) make:Warning:Don't know how to make target '/etcdir/services' current working directory /var/yp.
    Where /etcdir is the substitute for /etc which I am using for DIR=/etcdir & PWDIR=/etcdir
    2) make:Warning:Target 'all' not remade because of errors current working directory /var/yp.
    3)***Error Code1***
    make :Fatal Error : Command failed for target 'k' error running Makefile.
    Thanks in Advance,
    Shwetha

    Hmm, does "/etcdir/services" exist? Apparently not.
    You should populate the directory with the ascii yp map sources, so that there's something from which yp
    maps can be built.

  • Errors & Warnings in setting up NIS Master server

    Hi All,
    I am setting up NIS for that first time & I am getting the following Warnings & errors when I use # /usr/sbin/ypinit -m
    1) make:Warning:Don't know how to make target '/etcdir/services' current working directory /var/yp.
    Where /etcdir is the substitute for /etc which I am using for DIR=/etcdir & PWDIR=/etcdir
    2) make:Warning:Target 'all' not remade because of errors current working directory /var/yp.
    3)***Error Code1***
    make :Fatal Error : Command failed for target 'k' error running Makefile.
    Thanks in Advance,
    Shwetha

    Hmm, does "/etcdir/services" exist? Apparently not.
    You should populate the directory with the ascii yp map sources, so that there's something from which yp
    maps can be built.

  • How to fix NIS domain name not set after upgrade

    I finally updated after thousands of years. As pacman was spewing, I noticed that it moved /etc/conf.d/nisdomainname to .pacsave. Uh, whatever, says I. Must be a package issue. So I just reboot...and of course ypbind can't connect to anything because nisdomainname isn't set.
    Just cd to /etc/conf.d and mv nisdomainname.pacsave nisdomainname
    Then it will work again.

    start here with the knowledge base + FAQ plus forum.
    https://communities.vmware.com/community/vmtn/fusion

  • Set Up Native LDAP without NIS?

    The Blueprint documents covering native LDAP support for Solaris 8 are very NIS-centric. I do not have NIS configured for my workgroup, and I do not wish to create the whole NIS domain just to turn around and import it into LDAP.
    The 'dsimport' command information says:
    "The dsimport command takes a text file in /etc/files format as input. Typically, you use the same files that are maintained to generate your NIS maps." Okay, I'm game...
    When I attempt to use the dsimport command, it first core-dumped without doing anything. I obtained a newer version from patch 106621-09, but this one insists on finding the current
    /etc/opt/SUNWconn/ldap/current/dsserv.conf, which is the NIS-to-LDAP agent daemon. Not a good solution!
    What am I missing here? I don't relish the idea of keying every detail through the Directory Console. This was supposed to make management easier, not harder!

    I'm not should your problem coming from. Did you apply the Solaris Extensions for Netscape Directory Server 4.X patch 109953-02. If not, try to apply it first. Because original version have a lot of unknown problem.
    For download, goto http://www.iplanet.com/downloads/patches/ & find
    Solaris Extensions for Netscape Directory Server 4.X patch 109953-02
    Lucas

  • Solaris 10 NIS Client user account home directory

    Hi all,
    I am newbie of NIS in solaris and i am setting up NIS(central authentication of user) ,So related to this i have setup and server and client but
    i am getting problem while accessing user account in client side.
    in client side i can login user which i have created in server but it is not able to find its home dir .even though i added user with the -m option on server and home dir of user is created in server side .
    *(No directory! Logging in with home=/)*which i have created in NIS server.
    also i am not able to create any directories or files in the client system it says.
    bash-3.00$ mkdir a
    mkdir: Failed to make directory "a"; Permission deniedBoth the server and client have same domainname and NIS service is also running properly.
    on the server side this is the entry of the /etc/auto_home
    # Copyright 2003 Sun Microsystems, Inc. All rights reserved.
    # Use is subject to license terms.
    # ident "@(#)auto_home 1.6 03/04/28 SMI"
    # Home directory map for automounter
    +auto_home
    * SS09:/export/home/&here SS09 is the NIS server name and i can see it both server and client side .
    bash-3.00$ ypwhich
    SS09
    bash-3.00$
    bash-3.00$
    bash-3.00$ svcs nis/client
    STATE          STIME    FMRI
    online         11:53:05 svc:/network/nis/client:defaultSo please help me regarding this ...
    Thanks
    anuj
    Edited by: anuindia on Apr 16, 2009 11:02 PM
    Edited by: anuindia on Apr 16, 2009 11:03 PM

    Look over on http://docs.sun.com for the NIS guide for your version of Solaris.
    alan

  • NIS install on solaris 9

    I am trying to install NIS on solaris 9 but I don't have a Makefile in /var/yp. I tried copying the Makefile from one of my solaris 8 boxes but then I ended up missing a bunch of files from /usr/lib/netsvc/yp. I think I must be missing some packages but I can't find any listing of packages necessary to install NIS. I installed the developer bundle on the solaris 9 box that appears to be missing packages. Does anyone know what pkg(s) I am missing?
    Some of the files I am missing from /usr/lib/netsvc/yp are mutli, ypxfer udpublickey and many more. Any help would be greatly appreciated.
    Thanks,
    Daniel

    The Oracle documentation was pretty scarce on this but there were other docs on the Net which pointed out the correct parameters to edit. I added the following lines to /etc/system:
    set semsys:seminfo_semmni=100
    set semsys:seminfo_semmns=1024
    set semsys:seminfo_semmsl=256
    set shmsys:shminfo_shmmax=4294967295
    set shmsys:shminfo_shmmin=1
    set shmsys:shminfo_shmmni=100
    set shmsys:shminfo_shmseg=10
    After adding these lines, reboot your server and you can verify the values using the system command.
    Hope this helps.

  • 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

  • Spry Data Set, include external page and javascript

    I have a problem with Spry Data Set... I have necessity to
    include a html page with javascript functions (static html page) in
    another but doesn't work.
    This is an example with "Elevator Panel Magic" extension
    (projectseven.com):
    Home page with dataset (home.html)
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
    Transitional//EN" "
    http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="
    http://www.w3.org/1999/xhtml"
    xmlns:spry="
    http://ns.adobe.com/spry">
    <head>
    <meta http-equiv="Content-Type" content="text/html;
    charset=UTF-8" />
    <title>Untitled Document</title>
    <script src="../SpryAssets/SpryData.js"
    type="text/javascript"></script>
    <script src="../SpryAssets/SpryHTMLDataSet.js"
    type="text/javascript"></script>
    <script type="text/javascript">
    <!--
    var ds1 = new Spry.Data.HTMLDataSet("include_header.html",
    "header_menu_test");
    ds1.setColumnType("column0", "html");
    //-->
    </script>
    <link href="p7epm/epm1/p7EPM01.css" rel="stylesheet"
    type="text/css" media="all" />
    <script type="text/javascript"
    src="p7epm/p7EPMscripts.js"></script>
    </head>
    <body>
    <span spry:detailregion="ds1">{column0}</span>
    </body>
    </html>
    External page with elevator panel magic
    ("include_header.html")
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
    Transitional//EN" "
    http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="
    http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html;
    charset=UTF-8" />
    <title>Untitled Document</title>
    </head>
    <body>
    <div id="header_menu_test">
    <div id="p7EPM_1" class="p7EPM01">
    <div id="p7EPMt_1" class="p7epm_trigs">
    <ul>
    <li class="t1"><a href="#p7EPMc1_1"
    id="p7EPMtrg1_1">New Heading Text 1</a></li>
    <li class="t2"><a href="#p7EPMc1_2"
    id="p7EPMtrg1_2">New Heading Text 2</a></li>
    </ul>
    <div class="p7epm_ie5clear"> </div>
    </div>
    <div id="p7EPMdw_1">
    <div id="p7EPMw1_1" class="p7epm_cwrapper">
    <div id="p7EPMc1_1" class="p7epm_content pan1">
    <p>Lorem ipsum dolor sit amet, consectetuer adipiscing
    elit. Quisque congue tristique eros. Nulla facilisi. Quisque sem
    mauris, ullamcorper ac, gravida id, mattis id, sapien. Nullam
    adipiscing enim dapibus felis. Fusce a nisi in odio pulvinar
    fringilla. Nunc blandit interdum metus. Duis leo nunc, sollicitudin
    ut, fermentum congue, pharetra eu, massa. Suspendisse potenti.
    Morbi commodo mauris. Ut at pede. Ut id nisi. Donec scelerisque
    urna quis ligula. Praesent est. Vestibulum scelerisque. Curabitur
    quam. Fusce rhoncus pellentesque ipsum. Aenean venenatis metus ac
    quam. Maecenas lacus lacus, sagittis vitae, congue at, euismod eu,
    urna. Maecenas vitae purus. Praesent eros lectus, porta et, semper
    nec, molestie eget, tortor.</p>
    </div>
    </div>
    <div id="p7EPMw1_2" class="p7epm_cwrapper">
    <div id="p7EPMc1_2" class="p7epm_content pan2">
    <p>Lorem ipsum dolor sit amed sed diam nonummy nibh
    euismod tincidunt ut. Duis autem vel eum iriure dolor in hendrerit
    in vulputate velit esse molestie consequat, eu feugiat nulla at
    vero eros et accumsan et odio qui blandit praesent luptatum augue
    duis dolore te feugait nulla facilisi.</p>
    <p>Lorem ipsum dolor sit amed sed diam nonummy nibh
    euismod tincidunt ut. Duis autem vel eum iriure dolor in hendrerit
    in vulputate velit esse molestie consequat, eu feugiat nulla at
    vero eros et accumsan et odio qui blandit praesent luptatum augue
    duis dolore te feugait nulla facilisi.</p>
    </div>
    </div>
    </div>
    <!--[if IE 5]><style>.p7epm_trigs a {height:
    1%;}.p7epm_ie5clear {clear: both;}</style><![endif]-->
    <!--[if IE 6]><style>.p7epm_trigs, .p7epm_trigs
    a {height: 1%;}</style><![endif]-->
    <script type="text/javascript">
    <!--
    P7_opEPM('p7EPM_1',1,1,1,0,0,1000,0);
    //-->
    </script>
    </div>
    </div>
    </body>
    </html>
    **********************

    I think it is a bit too late you're 'finally experimenting' with Spry.
    Spry has been deprecated from Adobe and is now been made Open Source on GIT - meaning Adobe will no longer officially support Spry tools. The next major release of DW will most probably get rid of Spry, for good.
    Read here: http://blogs.adobe.com/dreamweaver/2012/08/update-on-adobe-spry-framework-availability.htm l
    jQuery is the way ahead. You may want to switch to jQuery - since anyway you've mentioned you're just 'experimenting' at the moment. That way, you're not spending time on something that is no longer being supported/ developed by their developers.
    -ST

Maybe you are looking for

  • HT4437 Trying to use airplay from my iPad to my TV.........when airplay code comes on screen how do I input the number on my iPad?

    I am trying to use my iPad with Airplay on my TV.  When I attempt to link up with TV a code appears on the screen.  Where and how do I input the code?

  • Conecting a JVC HDD GZ-MG150 to mac

    Can somebody give an idea what actualy JVC means " 1. Click on the "DOWNLOAD". 2. Double click on the "JVCVideoDecoder.sit" icon. 3. Drag the "JVC Video Decoder" icon to the "System Folder",then drop the icon there. 4. Click the "OK" button when the

  • Can't install Lightroom 2 on Mac 10.8.2

    Error message says "The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance". Do I need to update in order to install on a Mac running Mountain Lion? thanks, david

  • PICEXPORT file type WMF

    Hi, I have problems using the following "PICEXPORT" sentence: Call PICEXPORT("C:\Test D9.WMF","WMF",1,768,1024) 1-  When saving a graphic in WMF format the resulting image dimensions are different than the requested on the sentence (768x1024) I'm doi

  • ANOTHER FIX FOR UNRECOGNIZED IPODS WITH COMPUTER FREEZES

    Wonder of wonders, Apple has actually done something about this problem. Here's what they told us to do: 1. Download the latest version of iTunes FROM THE WEBSITE. It's version 6.0.1.3. 2. Back up your music just to be safe. 3. Go to Add/Remove Progr