Lightroom 3.3 and New Preset for External Editor

I have a strange problem here. Using Windows XP Profesional, SP3 4gb Ram.
When I want to add a new External Editor, I open Edit -> Preferences ->Additional External Editor.
I set my parameteres, choosing Photoshop CS4...same as in the Edit In Photoshop CS4 section above it, except that this time, I want to change the Bit-Depth to 8-bit and the resolution to 300, I do that and save the new preset as "Photoshop 8-bit". All OK. I close Lightroom so that the changes can take effect (not sure if I need to).
When, in the Develop module, I find a picture that I want to edit in Photoshop, I right click the image (or Photo -> Edit In) and choose my new preset "Photoshop 8-bit".
The next dialogue opens, and behold...I get the standard Edit In Photoshop CS4 dialogue box. Clicking Copy File Options confirms that I am opening the file using the original Edit In Photoshop CS4 (the top option group in the Edit ->Preferences section). The bit-depth is back to 16 bit, and the resolution is back to 240.
What happened to my new preset? Why is the open file reverting to the original Edit in Photoshop CS4, and not my new preset conditions?
What have I done wrong? Solutions? It all looked pretty straightforward in Ms Kost's AdobeTV programme.
Thanks in advance for any suggestions
Regards
David

Hummmm....looks like this has been "answered" before. Looks like a possible bug Adobe?
http://forums.adobe.com/message/3358880#3358880

Similar Messages

New presets for AME CS6 now available

Several new presets for Adobe Media Encoder CS6 have been posted, including a set of ProRes presets (Mac only, requires the ProRes codec to be installed), MXF OP1a presets as well as presets for tablet devices. After you install these presets (installation instructions on the download page) these presets will be available inside Prelude.
You will find the links to the presets in the Add-ons section towards the bottom of the page.
Win - http://www.adobe.com/support/downloads/product.jsp?product=160&platform=Windows
Mac - http://www.adobe.com/support/downloads/product.jsp?product=160&platform=Macintosh

@tlc51369:
Thanks for the heads up. I know you've been on the lookout for this for awhile now.
Does anyone know: is this exactly the same as the v 4.0.1.078 that has already been distributed?

Is Lightroom 5 Student and Teacher suitable for upgrading?

I am using the Lightroom 5 Student and Teacher version.
Now I am asking myself, how I could upgrade to Lightroom 6. According to Adobe, there does not exist a Lightroom 6 Student and Teacher version.
Therefore, could I upgrade the Lightroom 5 Student and Teacher version to Lightroom 6?
Is Lightroom 5 Student and Teacher suitable for upgrading?

Does it mean that i need more than my last school certifiate? Cause i do not own a academic mail adress.
By the way: thanks for your reply.
And another question: If Adobe does not accept my student identification, can i reuse the Key from the Box, to sell it again or to use for a relative of mine who is studying? Cause in case Adobe does not accept my student identification, i have purchased a box of paper with a useless CD.
Best regards
Kammo

What is difference between additive delta and new status for change record

Hi Experts
Can any one explain me about the difference between additive delta and new status for change record with example
if any one has a document please post it iam thank full to u
thanks
Ahmed
Please search the forum before posting a thread
Edited by: Pravender on Feb 12, 2012 1:54 PM

Hi
Additive delta --- We will get the changed quantity.
say suppose you have sales order and quantity like 1111 30 which is loaded to cube(BW).
now same record qty has changed from 30 to 40. As we have additive delta, we will get new record as 1111 10.
new status for change record: This is same as like After image delta type in standard SAP data sources. for every change in record you should have new record.
say if you have any number which will be generated by system for new/changed record, then you can use this.
You can use this option when delta option set to "numeric pointer"
Regards,
Venkatesh

Photoshop and elements 13 Working in iPhoto Want to edit image using photoshop elements Did the following IPhoto Preferences Advanced Edit Photos: In drop down menu chose in Photoshop Elements Also control click and chose edit in external editor Drop

Photoshop and elements 13
Working in iPhoto
Want to edit image using photoshop elements
Did the following
IPhoto>Preferences>Advanced>Edit Photos: In drop down menu chose in Photoshop Elements
Also control click and chose edit in external editor
Drop down menu edit photos in external program>photoshop Elements
Go to to the image I'm working on --- selected the image, the clicked on edit. When nothing happened I double clicked the image. Still elements didn't open. Then I opened the Elements editor, went back to iphoto and tried the entire process again. the photo still didn't open on Elements 13 for editing.
I have 3 Elements 13 books as well as looked on line--all my references say the exact same thing ---- iPhoto>Preferences>advanced>edit in external program>photoshop Elements
I uninstalled and reinstalled both iPhoto as well as Elements.
I spoke with application technical support. There appears to be nothing wrong with my copy of iPhoto. However there is no support from Adobe. I waited for over 1.5 hours for chat support several days ago, and finally gave up.

You are probably choosing the obvious file rather than the correct file as the PSE editor. The actual editor is hidden away inside the Support Files folder. The PSE file at the top level of the PSE folder in Applications is just an alias for the welcome screen and what you're describing is exactly what happens when you choose that. You want this one:

Is there some new configuration for Design Editor in RH11 that I am missing?

I just upgraded from RH7 to RH11.
All topics in Design Editor appear as though the style sheet is not applied.
The Normal style appears as Times New Roman - 12pt font, but it is defined in the style sheet as Arial 10pt.
Hyperlinks appear in the correct font type, but 12pt instead of 10pt.
Headings seem to be the only styles that appear correctly.
When I preview the topic, or view it in a browser, everything looks correct, as it is defined in the style sheet.
Is there some new setting for Design Editor, like "Ignore part of the style sheet"?
Thanks...

Thanks for your response, but a look in the html and the GUI confirms that the correct style sheet is applied. In addition, (from my original post) "When I preview the topic, or view it in a browser, everything looks correct, as it is defined in the style sheet."
I just noticed that the 'Normal' style as seen in the RH GUI shows "Times New Roman" and 12 pt. even though the P style in the style sheet shows:
/*Created with Adobe RoboHelp 11.*/
P {
    font-size: 10.0pt;
    color: #000000;
    background-color: Transparent;
    font-family: Arial, sans-serif;
    margin-top: 5pt;
    margin-bottom: 5pt;
I simply edited the Normal style in the GUI to the Arial font and size.
All of the P styles, and all styles based on the P style, changed to the correct font and size.
The P style in the .css file did not change!
Another RH bug?

On creative cloud lightroom is not showing ps cc as external editor, what can I do to?

on creative cloud, lightroom is not showing ps cc as external editor, what can I do to?

What is showing?? Anything?? What is your OS?

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

Camera Raw brightness and contrast preset for art capture?

I'm capturing oil paintings for reproduction with a D3x tethered to Lightroom 3. I'm converting though in camera raw. My camera profile is created using Color Checker Passport software/target which uses a DNG file. Given that, the profile is build without brightness or contrast adjustments. My question is, for accurate color, tone and exposure capture should the default ACR presets for brightness and contrast be reset to 0?
Thanks!

Or use the Zero'd setting on import to get no initial settings. However, I thing you'll find doing your own is better.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

Is it possible to create a new preset for Export/Quicktime Conversion ?

Hi,
I was wondering if there is a way to make a new export preset for the Export with Quicktime Conversion, in FCE HD 3.5
I am working on preparing a file for YouTube, and finding that some of the video effects render differently when exported, so I am having to render a couple of tests, but with YouTube's new 640x360 16:9 format, there is no easy way to do this other than checking the settings at each export. If one could make a new preset, it would be much easier. Any ideas?
Thanks,
t

thankyousir.
I think that Apple could add this, easily, as a feature to what, essentially, is QT Pro, and its embedded brother in FCE. Apple could also release a tiny update for QT including the new YouTube format... I haven't checked if iMovie knows about this new resolution, though it does upload directly to the tube itself.
Thanks for your time,
T

MBP, too many pics, and new 1 TB external HD, advice on how to procede

Hi, new to the forum, and essentially apple. MBP running 10.4.11 and i have 2 new babies. lots of pictures movies etc. so i figured i'd put all the pics on an external HD to free up the internal.
so now i have a big (1 TB my book) and i'm thinking that i should probably partition it so as to make best use of the space. what should i use the partitions for though? backup (is that time machine? or is that only on leopard) photos obviously. anything else? a bootable partition?
thanks alot for the help, advice, and consideration

MMM.
For most effective use SuperDuper really needs a separate partition the same size as the internal drive too, OKC1234.
My own strategy in a situation like this (and I personally REALLY don't like having all the backups on the one drive, partitioned or otherwise, so I do much the same thing over several drives, but even partitions are safer than keeping it all on one volume!) would be to create a Time Machine partition twice the size of my internal drive (to allow for a fair amount of time before TM starts overwriting old files - lets face it - anyone using Tiger will almost certainly update to Leopard before long), a second SuperDuper partition equal in size to my internal drive, incrementally backed up automatically every day , to provide a "close to current" bootable backup, and whatever was left for a bit of extra free storage space for things I don't need on the internal HD all the time.
So I'd say three partitions minimum. I used to regularly partition my drives. For a while it became less necessary. Today, given Time Machine and Super Duper requirements, I think it makes good sense again.
Cheers
Rod
Message was edited by: Rod Hagen

Best rgb and gamma settings for external monitor with mountain lion

Hi,
I'm using an LG LED 22 inch monitor with my MBP mid 2010 via minidisplay to hdmi. on OS X side the settings have been default. On the LED side the settings , if set to preset RGB it tends to fade the whites a lot. when i set to user definied and let the preset rgb be at it is, the colors are quote decent. currently they are on R 50, G 58 and B 59 and Gamma 1. Which is the best RGB and Gamma value for OS X Mountain Lion?

Welcome to the forum.
First off, you need to go and buy a hardware monitor calibrator, such as an OptixXR or similar. This will build a custom monitor profile for your specific screen. Without this starting point you can forget ANY attempt at accurate colour matching.
Never (and I mean never) use a working space such as sRGB or Adobe98 as your monitor profile, that's not what they are designed for. Working spaces control what colours are possible in the image, monitor profiles control how those colours are shown on screen. Aperture uses it's own working space so you don't have to worry about that too much.
To answer the rest far too briefly, I'd suggest setting the proofing profile to sRGB and of course use sRGB for the export preset. The gamma setting you will have to adjust depending on how dark the Lightjet prints look compared to your screen. You will have to do test-strips to start with.
Your images looking crap on flickr on Windows machines is partly because Windows web browsers generally do NO colour correction, and only partly to do with the different gamma.
Ian

Unable to send and receive email for external domain

Hi,
I just installed Exchange Server on my 2K8 domain controller. I have set up the send connector and made necessary changes to the receive connector as well. I have updated the DNS records as well on my domain registrar. I can access OWA from outside my companies
network and is able to send and receive emails for my domain but unable to send or receive emails to any other domain. I have checked the delivery report and it says that the message has been queued on the server.
I also did nslookup. Results mentioned below:
C:\Users\Administrator>nslookup www.google.com
Server: localhost
Address: ::1
Non-authoritative answer:
Name:    www.google.com
Addresses: 2404:6800:4009:802::1014
          74.125.236.145
          74.125.236.148
          74.125.236.146
          74.125.236.144
          74.125.236.147
C:\Users\Administrator>nslookup www.microsoft.com
Server: localhost
Address: ::1
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to localhost timed-out
Any help would be much appreciated!

Hi hg01,
According to your description, I notice that you installed Exchange server on a DC.
It is not recommended to install Exchange server on a DC. I suggest install Exchange server on a member server. More details to see:
Installing Exchange on a domain controller is not recommended
http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.warninginstallexchangerolesondomaincontroller(v=exchg.150).aspx
About your issue, cannot send and receive externally, I suggest make sure the DNS can be resolved first.
Then, check whether Outlook Anywhere has been enabled. If not, please enable it on both Exchange server and Outlook client side.
Last, try to configure both Send Connector and Receive Connector.
More detailed error message will be helpful for the further troubleshooting.
Thanks

Why when i use a new apple Id and new id for icloud all my information is gone? For example all my contracts are all gone.

I don't know why when i used a new apple ID and new icloud ID all my information is done. My contracts are all gone. This only happen on on phone. When i was changing the other phones it works fine. Nothing is lost. So i dont understand when i was changing the apple ID and icloud Id the information is lost. You know when you go to setting and you click iCloud and i saw that the contracts book was light on. Does that matter? Does that cause i lost my contracts?

I don't think the iPhone is really designed for people to be switching from one Apple ID to another so when you do so you may experience problems. You have two options on the iPhone for where you can be accessing contacts, from iCloud and the iPhone itself. You can also pull contacts off of a SIM card but they are then stored on the iPhone and not accessed from the SIM card.
You could try this;
1. Go to Settings > iCloud
2. Sign in to the Apple ID that you want the Contacts from,
3. Turn "On" the Contacts slider and let it download all of your contacts
4. When it's done downloading, turn the slider back to "Off" and you should get a message like this..."What would you like to do with the previously synced iCloud contacts on your iPhone?"
5. Then select "Keep on My iPhone"
Then after that you can then sign out of that Apple ID and into your other Apple ID and the contacts shouls still be there.

How to configure and save presets for custom scanning?

There are 5 presets in Acrobat XI for scanning files: "Autodetect...", "Black &White...", "Grayscale...", "Color Doc...", and "Color Image".
There is also an option to to do a "Custom Scan..." and "Configure Presets" (modify the 5 above).
However, I could not find any way to create my own custom presets.. is that not possible?
I was hoping to at least save my configuration(and/or possibly create a few different custom scan templates) in the Custom Scan for future scans but that was also not an option.
I would gladly use the 5 presets and configure them to how I want them but its unfortunate there are no output options there to automatically append a scan to an existing file or create multiple files from a continuous scan.
So... 1) Can you create custom presets for scanning? 2) Is there a way to configure output options in the existing scan presets? Thanks!

Pavanmeet,
you have to set all activities in the workflow to "general task" as well, not only for WS12300111 itself (doubleclick on each symbol with the "triangle").
check the status of the sent leave request in transaction PTARQ (Display Documents). Here the "next agent" & the "pers. no" of the next agent is of interest.
logon with the user, that is saved in infotype 0105 of the above mentioned pers.no. there should be the approve request.
you can check the status of the workitems with SWI1 (i assume your system is prepared for workflows , check SWU3)
Message was edited by: Achim Hauck

Lightroom 3.3 and New Preset for External Editor

Similar Messages

Maybe you are looking for