Issues with new 1TB WD external harddrive

Hi, I purchased a new WD 1TB portable hard drive. It running very slow. To transfer 500MB it's taking abound 1 hour or more. Do I need to format my new EXT.HDD according to mac. Please help me to sort it out this issue.
Thanks

Vishang wrote:
Do I need to format my new EXT.HDD according to mac.
Yes. Do the following:
Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

Similar Messages

Setting up and managing iPhoto with new Mac and external harddrive

First time Mac user and I'm stressing about iPhoto!
I have the new 13" Macbook Air.
I have my old PC (no longer using) that has all of my old photos on it.
Those photos are also on my Wireless Network Drive.
Have not done anything YET in iPhoto because I want to set it up properly.....that's where I'm stressing.....
Here is how I want it to work, which I fear is not possible or maybe I'm just not understanding the correct setup I need to do to meet my needs:
1. I want all of the old PC pics to stay on the Network Drive only UNLESS I decide to BRING the specific ones into iPhoto down the road.
2. I want new pics I take on my SLR to go to iPhoto (which they will) AND the Network Drive for back up (no problem here)
3. Every now and then I will MOVE the photos OFF of my Mac completely and to the Network Drive to make sure I always have space on the Mac.
I also have iCloud and Time Machine so maybe those could help me as well.
4. This is my biggiest complaint.....when I open a photo in iPhoto and edit it, I WANT TO SEE THE ORIGINAL FILE in iPhoto ALWAYS. After reading tons of message boards it sounds like yes, iPhoto does save the original BUT it is nearly impossible to find and it is labeled very poorly. (I know there is a trick to view the original next to the edited one while you're in iPhoto, but that isn't what I mean). I essentially want to see my edited photo and my original photo just like you would on a PC if you did 'save as new'. I want the original in iPHOTO next to/near the edited one(s) not in a hidden/impossible to find/archived path.
If I'm understanding correctly from what I've read, based on what I want, I may need to use a 'reference library' versus a 'managed library'?
I'm not crazy about doing that though because it seems there are risks because it isn't stored in the 'library package'?
To make a long story short, I want my new pics on my Mac, old pics can stay on the network drive (unless I want to edit them or show someone), and I want to be able to easily access the ORIGINAL file. I want everything to be safely backed up and want the option to move things to the network drive/time machine/cloud or w/e when space gets limited on Mac.
Any help/advice would be greatly appreciated.

New photos go to iPhoto, I organize, tag, create albums do whatever. These are also getting backed up in the Cloud and Time Machine (I think?? I still have to research more about how those works....sorry, Mac Newbie)
There is no iCloud backup of photos
Time Machine is good - but it appears that it does not backup the iPhoto library if iPhoto is running so be careful there
If I start to really run out of space, I can move them off Mac completely.
To do that correctly you need an external disk formatted Mac OS extended (journaled) with an iPhoto library on it and use iPhoto Library Manager - http://www.fatcatsoftware.com/iplm/ - to move photos between your MBA iPhoto library and the iPhoto library on the external drive
Regarding issue #4 about the original version, I read one of your posts which explained that the original version can be viewed by going to Home/Pictures/Photo Library Folder/Originals......so I could do that (as long as I don't mess with it). My only concern here is the naming convention that will use- I feel like it will be so hard for me to find the original one I want.
That is not a supported way to access the originals and is dangerous - any change no matter how small can corrput yoru library and cause loss of data and possibly photos - the simple rule is never go into the iPhoto library - there is no reason to - if you wnat the original photo you select it in iPhoto and export as kind = original
Maybe a program like Aperture may be better for me, but again, I'm open to suggestions since you're much more familiar with all of this than I am!
Aperature is more expensive and has many more capabilities including working well with referenced libraries
As to using iPhoto - no one here "encourages" anyone to use iPhoto - in fact for people who want to do things iPhoto does not do or ins not good at we often recommend using other programs - if you want to use it we can help use it correctly - we can not helop you use it incorrectly or make any changes in the way it works

Can Macbook Pro 13" Mid 2009 replace with new 1TB 2.5" SATA 3.0 hard drive?

Can Macbook Pro 13" Mid 2009 replace with new 1TB 2.5" SATA 3.0 hard drive? My hard drive is almost full and I need to place it with a new bigger capacity. Please advice. Thank you.

Yes, you can replace the drive.

When I open a new tab, an unwanted website opens instead of my desired home page. THIS IS ONLY AN ISSUE WITH NEW TABS; (opening the web browser AND clicking on the home button frings me to my desired home page.)

When I open a new tab, an unwanted website opens instead of my desired home page. THIS IS ONLY AN ISSUE WITH NEW TABS; (opening the web browser AND clicking on the home button frings me to my desired home page.)
I have attached the url of the unwanted site.

Use this add-on [https://addons.mozilla.org/en-US/firefox/addon/custom-new-tab/ '''Custom new tab'''].

How can i get my ps 3.0 to install on my laptop ? compatibility issues with newer version of windows

how can i get my ps 3.0 to install on my laptop ? compatibility issues with newer version of windows

It's hopelessly outdated. It's simply not compatible.
Mylenium

[SOLVED]Issue with Postfix sending to external mail addresses

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

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

Sleeping issue with new mac mini

i have a new c2d 2.0 mac mini all software is up to date. the first night i was able to put it to sleep without any problems but since then when i try to put it to sleep by eithre the apple menu or hitting (eject,apple,option) the dvd drive clicks and the mini wakes up all in 5 seconds.
another sleep problem is with both mac mini's (the c2d and g4 1.42) neither will go to sleep with an external harddrive connected (mounted or not and still powered on) I have looked for an answer to this problem for a while and have found nothing. i thought i saw a thread on this very subject but have yet to find it again
thanks for help
Nick

Hello,
It's nothing to really start worrying about, it's most likely down to a communication error between your hardware and your software. The simple solution is:
1) Unplug all cables from the computer, including the power cord.
2) Wait 15-20 seconds.
3) Press and hold the power button on the back of the computer
4) Whilst holding the power button, plug the power cord back into the machine
5) Release the power button
6) Press the power button once more to start up your Mac mini.
Everything should be sorted! (if not, call back here)
Good luck
-Pos

Firewire 400 issue with new iMac 20"

Hi all,
Maybe one of you can help. I've got a problem with my Western Digital myBook 500Gb external harddrive when I connect it to my (new) iMac 20" using the firewire 400 port. The drive does not show up on the desktop, not in diskutility and also not in the systemprofile (it just says 'FireWire-bus: Maximum speed: maximum 800Mb/sec').
To make sure there's nothing wrong with the port I connected a Canon DV camcorder (using the 400 port but using different firewire cable). I shows up correctly in the systemprofile and I can get data of that. So, I assume the port is functioning properly.
To make sure the external drive is working and there's nothing wrong with the firewire cable, i connected the drive to my 'old' iMac (a core duo 17") and it all works fine. So, the device must be ok and the cable aswell.
Some extra details:
- Both macs run osx 10.4.10.
- If I connect the drive using usb, it all functions correctly, i can even boot from the drive.
- When I booted the 20" mac for the first time i used the wizard to copy over the data from the old mac using the firewire cable. That all worked correctly.
Any ideas what could be wrong?
Any help would be very much appreciated.

Some more details: if i unplug the power from the drive and refresh the systemprofile it does find the drive, although it is listed as an unknown device:
Unknown device:
Manufacturer: Unknown
Model: Unknown device
GUID: 0x0
Maximum speed: Maximum 400 Mb/sec
Connectionspeed: Maximum 400 Mb/sec
(the above was translated from Dutch).
If I then plug in the power of the drive, sysprofile says 'FireWire-bus: Maximum speed: maximum 800Mb/sec' (also translated from Dutch).
Oh and zapping the PRAM did not make a difference, nor did removing WD files from the Library -> StartupItems folder. The LaunchDeamons folder was empty.
Message was edited by: Luca5

How can I get Lightroom 5.7 into the "Open With" menu on an external Harddrive?

Using Lightroom 5.7, I imported photo images as a .dng. I edited the images in lightroom. Then I dragged the file from the local Disk (C) to an external Hard drive (left panel of Library). When I look in the External harddrive, I would like to see thumbnails of the images. I think I would like to open the images in Lightroom but I cannot get Lightroom into the "Open With" dropdown menu. Photo shop, Adobe Reader and a bunch of Windows photo editing stuff is in there but I cant seem to get Lightroom into this menu.

The "open with" command is used to open images that are already in Lightroom in another external editor such as Photoshop or Photoshop Elements or some other photo editing program. And you are opening an image that you are already seeing in Lightroom. So Lightroom won't be on the list and cannot be on the list because you are already looking at the images in Lightroom.
Concerning the images that you moved to the external hard drive, if you actually moved them using Lightroom then you should be able to see that external hard drive in the library module library tree and be able to choose that folder. Then the images will be in Lightroom and you can continue working on them. There doesn't need to be any "open with" to do that. If you moved those images some other way, please explain.

Idoc flatfile to IDOC xml issue with new PI7.11 module SAP_XI_IDOC/IDOCFlat

Hi,
I am trying to develop a scenario as mentioned in the blog using the new module available in PI7.1,but I am getting this error
"Error: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ORDERS05" is unavailable."
I have made every configuration correct and IDOC meta data available in both SAP R3 and PI,but it is still complaning about the meta data does not exist.
Blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13743%3Fpage%3Dlast%26x-order%3Ddate
did anybody face issue with the new module available "SAP_XI_IDOC/IDOCFlatToXmlConvertor",please help me or give me mre information why I am getting this meta data error.
Thank you,
Sri

Hi Sri,
To Convert IDOC Flat file into IDOC xml from the given blog, the IDOC flat file should be present in standard format like:
E2EDK01005                    0000047110815000000000001.........
E2EDKA1003                    0000047110815000000000002.........
E2EDKA1003                    0000047110815000000000003..........
E2EDKA1003                    0000047110815000000000004........
The Flat file have relationship as IDOC Number "000004711081500000" and segment sequence "0000001".
If your flat file is not in this formate so i don't think that module is able to convert into IDOC xml. and if your file is already in this format then it may be issue with destinations which are created in NWA.
Thanks
Harish

Windows Media Player plugin does not install on a fresh install of Firefox 15. This is a real issue with new students.

I have them go to the correct site:
plugin download page on Interoperability Bridges.
My only options are:
1. Have them move some files over manually; which isn't feasible with students who are technically challenged.
2. Have them install an earlier version of Firefox. 11 is the last known good version that accepts the WMP install. The problem I am finding with this is even though I tell them not to update before installing WMP somehow they still manage to do it. A lot of times they don't know how to tell me what version of ANY browser they are using.
Firefox is one of the few browsers that work with our LMS well, but this plug problem is a real issue.
This only pertains to any student who has never had Firefox on their computer prior to 11.
Thanks in advance.

I noticed it after 11, however with 12 students students experienced problems with puzzles in Angel LMS. We had people roll back to 11.
13 came out and that's when the trouble started. I usually stay in beta so I can get a idea of what's working. Once again I had people roll back to 11.
I logged into a system here I had not logged into before and did a fresh install of 11 and I was able to recreate the problem myself.
Getting people on 11 is a little harder this semester because I had to locate the 11 install and send that along with the plugin to new users. The 11 install likes to force the 15 update so they have to get the plugin installed right away. Sometimes the concept is a little much for some people.
Edit: 12 might have been okay, since we were rolling back anyway. I don't recall any issues with WMP the few weeks students had been using it.
Edit 2: I do remember trying to search these forums for the issue and someone posted that they had been experiencing the same problems with 12 beta (at the time it was beta) and I think it was explained as being a beta issue and it never went anywhere else.

Quality issues with new Mac Mini 09?

I've been itching to hit the 'buy' button -- but in reading the many postings about the new Mac Mini, I'm seeing lots of issues with the bluetooth ... *wireless signal* ...
Is there anyone who's not experiencing any problems?
Sounds like it may be a hardware issue with connections... the last thing I want.
My other choice is the 2008 Mac Pro which seems trouble free.
What do you think?
Thanks.

There is a general issue/trend with the new Mini. There are plenty of reports in these forums and the news has begun to hit the wider press; I guess this is more important to a company with only 2-3% desktop share than posts to these forums. I went to the Genius Bar on Saturday and they have now lodged an official bug report with Apple. It looks like the Mini cannot pair with more than one HCI device. So if you pair with the mouse first the keyboard won't work and vice-versa. They don't think the Mini hardware is broken but that we will just have to wait for Apple to fix the firmware.
Where I do agree is that some issues are OS-X 10.5 related and can therefore affect all Macs. The WiFi has issues where it randomly drops, it doesn't seem able to re-connect at all to channels above 13 and only manually to channels below 12. The system resume function is unreliable. All these started when we moved from 10.4 to 10.5 and so far they have not been addressed. One issue is that there does not appear to be a way for users to log bug reports, except when software crashes. However, the bluetooth issues on the Mac do appear real and are either firmware or hardware related.

Issue with new abap webdynpro INBOX EHP5

Hello Experts,
I'm currently working on the configuration of ESS/MSS services in EHP5. We are using different services like Appraisal OSA, Learning solution,etc. I already configured the Launchpad ESS, it's working fine but now I have an issue with the new Abap webdynpro INBOX. The employee and manager see their workitem notifications correctly in their respective inbox.(I'm calling application: IBO_WDA_INBOX that I integrated in my launchpad).
My problem is that when clicking on a workitem in order that it opens me the appraisal document (in edit or display mode), I got an error saying: "There is no iView available for system "": object "SWF_WIOBN". For more information, contact your administrator."
I did some search on SAP help without any results. I'm wondering how should I register workflow tasks? I saw there is a table called IBO_C_WF_TAS (I added entries e.g:
IBO_WDA_INBOX TS99700031   EXECUTEAPPRAISALDOCUMENT).
I tried also to register all my custom tasks in transaction SWFVISU.
example:
TASK: TS99700013
Visualization Type: ABAP Webdynpro
APPLICATION:    HAP_MAIN_DOCUMENT
DYNPARAM   :    sap-wd-configId=HAP_AC_MAIN_DOC
NAMESPACE :    sap
SYSTEM_ALIAS: SAP_Webdynpro_XSS (I did create a system in sap portal under System Administration with as AS property /webdynpro/dispatcher )
Could you let me know what could be wrong, what I missed? Shall I create an iView, if yes which one? which properties?
I would really appreciate any help.
Thanks!

Hello Siddharth,
Thanks for you reply. Still the same issue. Following are the config I did till now:
In the PCD I created a new business object (SWF_WIOBN), an operation linked to the object (NAVIGATE).
I did create an iView (powl) in the custom folder, I integrated the operation within iView. I created a page that contains the iView.
In the properties of the iView I gave:
Application Name: HAP_MAIN_DOCUMENT.
Launch in New Window: "Display in separate Headerless Portal Window".
System: SAP_ECC_HumanResources
I added the required entries in tables:
IBO_C_WF_TTAS
IBO_C_WF_ACS
IBO_V_WF_TAC
IBO_V_WF_TTAC
etc...
I saw in the code of linked feeder class: CL_IBO_INBOX_FEEDER_WI that it's checking something called "Launch_Editor".. Is it a property that we can set somewhere?
Following are the parameters retrieved by system:
BO_NAME       = SWF_WIOBN
BO_OP_NAME = NAVIGATE
LAUNCHER_PARAMETERS -> empty.??
BO_RESOLVE_MODE = USER_SET_OF_ROLES
LAUNCH_EDITOR empty where must be set?
At the end I still get the error:
There is no iView available for system "": object "SWF_WIOBN". For more information, contact your administrator.
Any advice,
Thanks in advance

ISSUE WITH NEW VERSION OF BLACKBERRY MESSENGER ON DIFFERENT BLACKBERRY PHONES

Dear Madam / Sirs,
I would like to seek assistance in resolving an issue with my BLACKBERRY TORCH 9810 I installed the new version of BLACKBERRY MESSENGER on my phone and it does not work on WIFI ONLY MODE.
For example I traveled to Mexico and Panama and was on a WIFI ZONE with open access and tried to use my BLACKBERRY MESSENGER and it did not work...I tried to deleting the application and installing a previous version but was not possible. The same issue occurs on a different BLACKBERRY phone that it was working perfectly...but after updating to the new version of BLACKBERRY MESSENGER it did not work.
Please help me resolve this issue.
Thanks in advance
Polk Marin
E-mail: (personal info removed)@yahoo.com

and what version do you have installed? I dont see this on ver 6.2.0.56
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Strange Printing Issue With New HP & Pages

Hello!
I have a very strange printing issue with a new HP printer. I have written pages documents heavy in Texts which are located within tables. The documents print fine on a Cannon and Epson printer and look great but when I print the document on my new HP Laserjet Pro 400 Colour M451nw some of the text on some rows come out of the printer looking like they are bold / slightly fuzzy. This only happens with some of the rows of text, not all of them. The font is the same in every row with the same format.
You can see this in the attached image. The first line (Thanks very much) has printed correctly but the subsequent lines look bold / slightly fuzzy.
After a lot of testing the only way I can resolve this is if I copy the content into a new pages document and only then it will print and look ok with the HP printer.
This must be a problem within my origional document. I would simply copy and paste everything into a new document however this would take a very, very long time (over 5 years of work producing teaching materials and over 100 documents and thousands of tables and formatting that cannot be copied and pasted).
Also, on other printers you can see the lines seperating each row of the table. These lines are not visible on the HP print outs, even when the table is copied into a new document.
Has anyone come accross an issue like this before? Is there a way I can fix this without creating a new document? Do I need to get a new another new printer (the 4th printer this week!)?
Any advise, wise words would be greatly apprechiated!
Thanks!

Sorry, Fruhulda. After 4 hours on the phone with Apple care they are taking this issue further themselves. It seems to be a problem with our pages document and the compatibility with certain drivers. We have still not gotton to the bottom of it and Apple are going to get back to me when they have an answer.
We also worked out that the issue only happens when you print via Ethrenet & USB. Printing via Wifi is ok and there are no quality issues.
Very Strange!

Issues with new 1TB WD external harddrive

Similar Messages

Maybe you are looking for