Setting a proper domain name and adding hosts for quick name resolution

I have 3 other computers in my house.
Two run linux at this time.
I want to do 2 things. Right now my machine says Steve.local for its hostname right? I want to change that so it reads Steve.mydomain.net.
Am I correct that I need to
sudo /etc/hostconfig
And change the hostname line from -Automatic- to =
HOSTNAME=Steve.mydomain.net
And for quicker resolution of the small number of hosts on my network (primarily so I can use hostname instead of IP for ssh) can I add static hosts to the /etc/hosts file on my machine ala:
sudo /etc/hosts
Is this the proper way to do these things in Mac OS X?
Also to change my workgroup for Samba:
Open the Directory Access utility (under Applications -> Utilities)
I highlight SMB and click configure and just change the Workgroup entry there. Is that correct as well?
Just checking before I go tooling up my machine tonight for better integration into my home network.

Ok update changing the hostname in the field does NOT allow me to edit the .local part. In fact it converts Steve.mydomain.net.local to Steve-mydomain-net.local.
But I got my windows workgroup changed and I am showing up with the correct workgroup name from my other servers.
Also, lets say you only have a couple of computers on your home network right? So dedicated dns is kind of overkill especially when most of them are laptops rebooting all the time.
Well, your mac os x box has a hosts file. /etc/hosts as in if you want to edit sudo vi /etc/hosts. So you keep the computers pretty much in sync from those files.
I was afraid the information would not be persistent across a reboot. It was.
So, two out of three ain't bad. I read in the server forum its a pain in the ***. I was almost thinking of doing the hostconfig trick but I saw an Apple bulletin saying do NOT do that.

Similar Messages

Table name and field required for Project name

Hi Guys
I need to print Transfer order print out
Which Table and field I need to take to print Project number (Original format) BSA01.000045.00002

hello,
if i am right in understanding your question, then you wanted to know the technical details about the project number or should i say project id, from which wbs elements are created, on which we finally place the orders.
if this is what you want, then for getting the prject number for a particular order, at the table level, follow the below steps -
using the po number or order number as an input in ekkn table, along with the po line item, you will get the wbs element for the order number for that particular po line item.
and using this wbs element as an input in prps table, you can find the current project number.
finally using this current project number as an input in the table proj, you can find the project id or project number = proj-pspid
so you will require 3 tables to get the required details.
hope this helps you.
Regards,
Zafar.

I've used the Domains Administrator and added 45 domains. Where is that information recorded ?

I've used the Domains Administrator and added 45 domains. Where is that information recorded ?
Thanks,
Bob Larsen

The should be in defaultdomains.xml which will be in your system types directory (if you defined one), otherwise it is in a folder where you installed data modeler.

How to get service name and listening host to connect to oracle DB server?

I have successfully installed oracle db client 10g release 2 on my winXP. But when I tried to use Net Congiguration Assistance to connect to oracle db server. I do not know what is the "service name" and listening "host" I supporse to enter. Where can I get the names?
PLEASE HELP! THANKS!

machine name or IP = machine name or IP address of the database server
To know the service name do the following on the server :
$ lsnrctl services
LSNRCTL for Linux: Version 10.1.0.3.0 - Production on 30-DEC-2005 00:24:28
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0
         LOCAL SERVER
Service "test10" has 1 instance(s).
Instance "test10", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0 state:ready
         LOCAL SERVER
The command completed successfully
$The service name is test10 in my case. Of course you have to use yours.

I use IMAC upstairs connected to the house wifi downstairs where the networked printer is. I have 'found' the network printer on my IMAC settings but when i send to print I am getting a pop-up box which has 'apple' as user name and is asking for password.

I use IMAC upstairs connected to the house wifi downstairs where the networked printer is. I have 'found' the network printer on my IMAC settings but when i send to print I am getting a pop-up box which has 'apple' as user name and is asking for password. I have tried my own IMAC password but to no avail. The printer also shows a pop-up box stating 'awaiting authentication.
Any help appreciated

You are asking several different questions. If you need to store your photos, music, and movies on an external volume, you certainly can. Any externally connected hard disk drive will work, connected either directly to your Mac or to your Time Capsule as a shared volume.
You should not rely upon using that as a backup device though. Although you certainly may use it for both purposes, it is a better idea to have dedicated backup devices for a variety of reasons not limited to redundancy. You would not want to simultaneously lose all your pictures as well as your backup. If they are all on the same device, that could happen. Furthermore, a backup cannot back up the volume on which it is running.
As for adding an Extreme or Express, using its LAN port for your iMac, and then enable Internet sharing so you can effectively use the iMac as a "hotspot", you can do that too, but I am unclear on what benefit you believe this arrangement would convey for you.
An Extreme's Guest network is separate from its Main network; that is the reason for having it.

Passing the file name and file type for mime_download

HI All,
Can You Please let me know how to pass the parameters file name and file type for mime_download.
Thanks in Advance.
Regards,
Haritha.

Hello Haritha,
Please see the SAP help:
http://help.sap.com/saphelp_nw70/helpdata/en/46/9bd97240b81e5be10000000a1553f6/frameset.htm
Edgar

Have base station and added extender for downstairrs. Worked great upon initial setup, but now it won't connect despite an "excellent" signal. What's wrong? Thanks!!

Have base station and added extender for downstairs. Worked great upon initial setup, but now it won't connect despite an "excellent" signal. All i get is a blinking amber light; only get green if I bring it into the same room as the base. Both units are the latest models; purchased 2 months ago. What's wrong? Thanks!!

Power off both the AirPort Extreme and AirPort Express
Wait a minute
Power up the AirPort Extreme and let it run for a few minutes
Now locate the AirPort Express about half way between the AirPort Extreme and the general area where you need more wireless signal coverage, and report on your results.
The more that you can minimize obstructions between the AirPorts like walls, ceilings, etc. the better the wireless will operate.

My husband gave me his iPod touch, even after resetting all settings, and even though I have a user name and password whenever I need to update apps it shows his previous user name, and is asking for his password. How do I fix that?

My husband gave me his iPod touch, even after resetting all settings, and even though I have a user name and password, whenever I need to update apps it shows his previous user name, and is asking for his password. How do I fix that?

dom59 wrote:
Ok, when I go into my Apple ID account, everything looks right. It does show my user name. It's only on the iPod that it shows my husband's previous user name, and it asks for his password. Everything in iTunes and my account looks right. The issue only seems to be with the actual device, iPod Touch 4th gen.
There is more than one way to access the Apps Store and the iTunes store. One is via iTunes on your computer, and the other is via the apps on your iPod.
Just because you are logged in on your computer does not mean you are logged in on your iPod.
The reason your husband's user name comes up is because he was the last one to log on. You can change that by going to Settings>Store. Tap the Apple ID, Tap Sign Out, Tap Sign In, Tap Use Existing Appel ID, enter your e-mail address and Apple ID password, and tap OK.

Design and Testing Suggestions for Different Screen Resolutions

Intermediate Dreamweaver CS3 user, in need of "Design and Testing Suggestions for Different Screen Resolutions".
Thank you, J. Chavez

Adobe Browser Labb and BrowserShots.org

My HP office jet 6500 printer is stuck on pause. I do not have an admin name or password as it is a wireless printer and I never had to set one up. It keeps asking me for admin name and password...

My HP office jet 6500 printer is stuck on pause. I do not have an admin name or password that it keeps prompting me to give, as it is a wireless printer and that info was not required when we set up the printer. I have checked all diagnostics and connections and they are all good/passed. I am so frustrated!!! This has never happened in the past.

What is asking you for an admin name and password? What does the dialog say, exactly?
What model iMac are you using, and which OS version?
If it is earlier than Lion or Snow Leopard, try deleting the printer and adding it again as explained in this document
http://support.apple.com/kb/TS3140
Otherwise you can "reset the printing system" as explained here
http://support.apple.com/kb/HT1341
and here
http://support.apple.com/kb/TS3147
Download the latest drivers here (Lion, Snow Leopard)
http://support.apple.com/kb/DL907

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

How to label proper PMS colours and separated files for screenprinting

hello,
I have to submit an Illustrator document to have a t-shirt screenprinted and the instructions ask that I "label the proper PMS colors that you expect the ink to be on the finished design." I don't know what this means, let alone how to do it. I've googled it and it seems to have something to do with Pantone colours., but I couldn't find how to do this. The design is all one colour, so I hope that helps me! Also, it asks for separated Illustrator files. I know this means separate it into layers, but I didn't design it in layers. If I submit it in eps format does it matter that it's all in one layer?
Could anyone please help me out with some details on this?
Thanks for any help you can offer.
Mary

...the instructions ask that I "label the proper PMS colors...I don't know what this means...
It's an example of self-proclaimed "experts" in the various print industries using inaccurate terminology which confuses their would-be customers, even when they are ostensibly trying to provide instruction.
PMS is abreviation for Pantone Matching System. Pantone is a company which produces inks for commercial offset printing, and which publishes color specifications and swatch books for those inks. Because it has long been the predominate player in that market since long before mainstream graphics computers, it has become used as a sort of defacto "standard" for conveying desired colors. But Pantone is not the only such system.
To my knowledge, Pantone doesn't even produce silkscreen inks (which are more like paint, really). When people throw around the "PMS" and "Pantone" words like this, they often reveal their own misunderstanding about what Pantone really is. In all likelyhood, the screen printer you are using thinks that Pantone Matching System is some kind of universal color standard. They will most likely look up the Pantone color number(s) you give them, then either look at a cross-reference or just manually mix their screen printing inks to obtain a match.
... I've googled it and it seems to have something to do with Pantone colours., but I couldn't find how to do this...
In most screen printing, your concern is to use spot colors in your design as opposed to process colors. Pantone produces color specs for more than just spot color inks. It produces inks and references for process color inks, metallic inks, and even flourescent inks. The various Pantone standards are represented in Illustrator as "Swatch Libraries," which are accessible via the Swatch palette's flyout menu.
You can define any color Swatch you use in Illustrator as a spot color. When you do so, all this means is that when the file is printed as color separations, each spot color is printed to its own separation plate. "Plate" is a throwback term which refers to the metal sheets on which reside the images for individual inks in commercial offset printing. In screen printing, a separate screen is built to carry the image for each ink used in the design.
You can also name any Spot Color Swatch you define, using any name you want. The name has no functional effect on the printed result. Each color separation plate is a black image, regardless. The actual color is determined by the actual ink that is loaded into the press (or silkscreen) when it is printed. This is why, when you work in a program like Illustrator for any project destined for print, you should think in terms of inks, not in terms of colors.
For example: You can define a Spot Color Swatch in Illustrator. It can be set to display any color you want. You wouldn't want to, of course, but for the sake of explanation, let's suppose you set the Spot Color Swatch to display in Illustrator as a green color. You then name that Swatch "Pantone 185", which is actually a red. If you now print the file as color-separations to a PostScript printer (or "print" it to a color-separated PDF), everything to which you have applied the Swatch named "Pantone 185" will print to a single sheet (or PDF page). That sheet will contain a black image, and will be labeled "Pantone 185".
In fact, when working with a local screen shop, I typically create spot color Swatches, and name them not according to Pantone (or any other) references, but to the names of the actual brand of screen inks that the screen shop will be using.
So really, your screen printer is just instructing you to build your design using a limited number of color Swatches, with each defined as a Spot Color. He is further implying that you should name your Spot Color Swatches according to color numbers used in the Pantone Matching System, just because that's the color-naming library most commonly familiar to designers.
The simplest way to do this is, for each ink you want to be printed on the T-shirt:
1. Go to the Swatches palette flyout menu.
2. Select Open Swatches Library>Color Books>Pantone Solid Coated (or Pantone Solid Uncoated; it doesn't really matter much for screen printing).
3. Browse through that list and select the color you want. It will be added to your document's Swatches list.
The design is all one colour, so I hope that helps me.
As someone else mentioned, because your design is all one color, you could simply design it using only black, and then tell the screen printer what color ink to use. But there are some caveats.
You would need to print the file as composite (normal, full color), not as separations. This is because if you merely use a Swatch that looks black on your screen, that "black" swatch may in fact be built up out of a combination of RGB or CMYK values (depending upon the color mode of your document). Printing as color-separations may not result in a solid black image on the black plate. The same goes for the advice to design using just one color. If you want the ink to be red, and you want to design using red, then the red Swatch needs to be defined as a spot color. Otherwise, printing that red as either separations or composite will not yield a solid black image.
Also, it asks for separated Illustrator files.
Again, imprecise language. There is no such thing as a "separated Illustrator file." Any Illustrator file can be printed (or saved as PDF) as color-separations. Again, what the printer should be specifying here is that you build your Illustrator file such that it can be printed as separations, with each separation corresponding to one ink that will be loaded into his silkscreens. In practice, this simply means be sure to use only spot color Swatches in your artwork.
Also again, this exemplifies the fact that just because a technician working in a particular print environment may be "expert" in his shop, does not mean he knows didly about software and workflows used on the design front-end.
For most commonplace local screen shops, the safest way to prepare an Illustrator file that leaves nothing to question is to:
1. Make sure you know how many different inks will be used to print the design. (Remember: Think inks; not "colors.")
2. Build your design using nothing but Spot Color Swatches, and only one Swatch for each ink. Don't use any process Swatches. In fact, best practice is to remove all Swatches not actually used in your design.
3. "Print" the Illustrator document, using Adobe PDF as the "printer." (I think you may have to have Adobe Acrobat installed in order to see the Adobe PDF as a printer selection. I'm not sure, because I'm never without Acrobat Professional.) In the Output pane of the print dialog, specify Separations, not Composite.
Doing this will result in a PDF which contains a separate page for each ink. The image on each page will be black. That's exactly what the screen printing shop needs to print to "film positives" (which nowadays are often translucent paper, not film) which he will in turn use as masks when "burning" his screens.
...I know this means separate it into layers, but I didn't design it in layers...
Don't confuse color-separation with Layers. They are completely independent functions. Layers is just a way to organize the objects you create in your file. Color separation is a print function. It occurs when you print to a device that understands color-separation (i.e.; a PostScript device), or when you export to a color-separated PDF, as described above.
This is a common misconception (miss-assumption) among beginners. If programs like Illustrator required you to design with each object that is colored with a particular separation ink to reside on a Layer dedicated to that particular ink, it would be absurdly debilitating. Again, Layers is just a "bracketing" of the stack of objects in your file. Those objects can be in any stacking order, and on any number of Layers. That has nothing to do with printing to color separations. (Stacking order does come into play when overprinting is involved, but even that still does not require Layers to correspond to separation inks.)
If I submit it in eps format does it matter that it's all in one layer?
EPS does not help you here. Think of EPS as nothing but a file format which puts the content of your Illustrator file into a "black box" so that it can be "passed through" to the printer by programs which don't really understand PostScript. If the content of your Illustrator file is built wrongly for the target printing method, so will be the content of the EPS. Nowadays, PDF is more versatile and easier to work with than EPS anyway.
JET

If i want to install any software or update it is asking administrator name and password. what is administrator name

if i want to install any software or update it is asking administrator name and password. what is administrator name

When the computer was first set up you created an account and assigned a password to it. That first account is your admin account.

5.2 -- GOTO SE16 and enter TSTC for TABLE NAME. TCODE FIELD /VIRSA*

Should the following tcodes work? If so, how do I troubleshoot the ones that don't work? If not, how do they get configured to work? Can someone provide a link for documentation?
TCODE                                  TTEXT
/VIRSA/ALERTGEN                  Activity Monitoring
/VIRSA/MICCONFIG                  Virsa MIC User mapping Configuration
/VIRSA/ORGUSRMAPPING    Maintain ORGUSERS table
/VIRSA/RE_DNLDROLES       Role Expert 4.0
/VIRSA/VFAT                  Firefighter
/VIRSA/VRMT                  Role Expert
/VIRSA/ZMGMTRPT                  Management Report Graphical View
/VIRSA/ZRTCNFG                  Risk Terminator Configuration
/VIRSA/ZRTDELLOCK            Delete Role Lock
/VIRSA/ZRTRGLOG                  Risk Terminator Role Generation Log
/VIRSA/ZVFAT_U02                  FirefightId Log summary
/VIRSA/ZVFAT_U03                  Reason/Activity report
/VIRSA/ZVFAT_U04                  FirefightId Transaction Usage
/VIRSA/ZVFAT_U05                  Invalid Firefighter Ids/Owners/Cntrl
/VIRSA/ZVFAT_U06                  SOD Conflicts in Firefighter
/VIRSA/ZVFAT_U07                  Data Migration from Master to Text
/VIRSA/ZVFAT_V01                  Log Report
/VIRSA/ZVFAT_V02                  Log Report
/VIRSA/ZVRAT                  SAP Compliance Calibrator
/VIRSA/ZVRATBAK1                  Update data for Mgmt Graphical View
/VIRSA/ZVRAT_C01                  Security & Controls Policies
/VIRSA/ZVRAT_COVN            Conversion of CC tables, Old to New
/VIRSA/ZVRAT_D01                  Download Spool Requests by Job Name
/VIRSA/ZVRAT_L01                  Conversion Utility for CC Text Table
/VIRSA/ZVRAT_L02                  Conversion Utility for Long Texts
/VIRSA/ZVRAT_M01                  Upload/Download CC tables
/VIRSA/ZVRAT_M02                  Where Used list of Mit. Control Id/M
/VIRSA/ZVRAT_M03                  Analyze disabled SOD TCode & Object
/VIRSA/ZVRAT_M04                  Optimizer for SOD Data Table
/VIRSA/ZVRAT_M05                  Where Used list of Control Id/Monit
/VIRSA/ZVRAT_MG1                  Management Cockpit
/VIRSA/ZVRAT_P01                  Display changes to Profiles
/VIRSA/ZVRAT_R01                  Count authorizations in roles
/VIRSA/ZVRAT_RB2                  Rule Architect
/VIRSA/ZVRAT_RB3                  Rule Architect Conversion
/VIRSA/ZVRAT_S01                  Monitor Conflicts & Critical Trans.
/VIRSA/ZVRAT_S021                  Monitor Conflicts & Critical Trans.
/VIRSA/ZVRAT_S03                  Download Objects for Tcodes
/VIRSA/ZVRAT_S04                  SOD Conflicts for TCodes and Objects
/VIRSA/ZVRAT_S05                  SOD Rule Wizard
/VIRSA/ZVRAT_S06                  SOD Rule Validation Tool
/VIRSA/ZVRAT_S07                  Non Reference Report
/VIRSA/ZVRAT_S08                  User Access Report
/VIRSA/ZVRAT_S09                  Comparing diffrent SOD Matrices
/VIRSA/ZVRAT_S10                  Tcodes by Roles/Profiles, never exec
/VIRSA/ZVRAT_S11                  Authorization object by Roles/Profs
/VIRSA/ZVRAT_S12                  Transactions executed by Users
/VIRSA/ZVRAT_S13                  Comparing Critical Tcode Matrices
/VIRSA/ZVRAT_S14                  Comparing SOD Authorization Matrices
/VIRSA/ZVRAT_S15                  Compare Sod Tcode & Authorization
/VIRSA/ZVRAT_S16                  Comp.Calibrator Data Maintenance
/VIRSA/ZVRAT_U01                  Count authorizations for Users
/VIRSA/ZVRAT_U02                  Analysis of called trans in Cus.code
/VIRSA/ZVRAT_U03                  Management Report
/VIRSA/ZVRAT_U05                  Expired and Expiring Roles for Users
/VIRSA/ZVRMT_U01                  Check Role Status
/VIRSA/ZVRMT_U02                  Check Tcodes in Menu & Authorization
/VIRSA/ZVRMT_U03                  Compare Users Roles
/VIRSA/ZVRMT_U04                  List roles assigned to a user
/VIRSA/ZVRMT_U05                  Where used list for roles
/VIRSA/ZVRMT_U06                  List roles and transactions
/VIRSA/ZVRMT_U07                  Create/Modify Derived Roles
/VIRSA/ZVRMT_U08                  Analysis of Owners Roles and Users

Hi Greg,
   Most of the TCodes work but they are not being used. Which products do you currently have? Most of these tcodes are obsolete as they were part of old Virsa products. Here is the explanation:
-> At the start, Virsa had five different products namely Compliance Calibrator (CC), Fire Fighter (FF), Role Expert (RE), Risk Terminator (RT) and Access Enforcer (AE). Except AE, all other products were developed into SAP R/3 using ABAP so the transaction you see are coming from those four products. As of now, CC and RE has been moved to Java (same as AE) but RT and FF still reside in ABAP side.
-> You should be able to configure Tcodes related to FF and RT. You do not need to configure Tcodes for CC and RE.
-> You must be wondering how did you get all these Tcodes? Through the RTA (Real Time Agent) you have installed for GRC AC 5.2 in your SAP backend system. Even though, AC 5.2 does not need full blown products in the back-end, RTA still contains all of those products.
-> To start using these products, you will have activate BC sets. I do not recommend you to use CC and RE, if you are already using those products via Web front-end. FF and RT has some pretty good features.
-> Please follow AC 5.2 configuration guide to configure FF and RT.
If you don't want to use any of these, don't bother. These tcodes don't affect anything in your system.
Regards,
Alpesh

HELP! my mac has logged me out and now asking for a name and password?

I was logged on shopping on top-shop online and suddenly the mac shut down.
It seems it has reset its self! My icon has disappeared and its now asking for a name and password.
i have tried my log in but it is not working.
Is there another way to reset the password?
can i reset it to log back in what can i do?
I have rebooted the computer several times but i dont know what to do!

First, make sure caps lock is not on.
Another reason why your password might not be recognized is that the keyboard layout (input source) has been switched without your realizing it. At the login screen, you can cycle through the available layouts by pressing the key combination command-space or command-option-space. See this support article.
If the user account is associated with an Apple ID, and you know the Apple ID password, then maybe the Apple ID can be used to reset your user account password.
Otherwise*, start up in Recovery mode. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. In the window that opens, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window opens. Close the Terminal window to get it out of the way.
Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Follow the prompts to reset the password. It's safest to choose a password that includes only the characters a-z, A-Z, and 0-9.
Select
 ▹ Restart
from the menu bar.
You should now be able to log in with the new password, but your Keychain will be reset (empty.) If you've forgotten the Keychain password (which is ordinarily the same as your login password), there's no way to recover it.
*Note: If you've activated FileVault, this procedure doesn't apply. Follow instead these instructions.

Setting a proper domain name and adding hosts for quick name resolution

Similar Messages

Maybe you are looking for