SMC cripple with NIS+
This is my story.
I installed Solaris 9 on my V880 and setup nis+. I had a hard time to make user template working. One of the support guy told me that there is a bug and gave me a patch to make it work. After that patch, 114503-01, template started working. However, I had another problem. Whenever I create a user, SMC pops up a warning message and sometimes it just hangs. I later found out that SMC threw the following exceptions:
java.lang.NullPointerException at com.sun.admin.usermgr.common.WBEMClient.HomeDirProxy.createHomeDir(HomeDirProxy.java:147)
at
com.sun.admin.usermgr.common.WbemServiceWrapper.addUser(WbemServiceWrapper.java:1211)
at
com.sun.admin.usermgr.client.users.AddUserWithTemplDlg$2.run(AddUserWithTemplDlg.java:613)
So, I called the support again and told them my story. Tech support guy told me that SUN can NOT give a suuport because I am not using /home for user home directories. I asked him if there is any document
says I had to use /home. He simply refused to answer my question and just threw me a bunch of manuals. So I gave it a rest a month or two because there was no point in talking to him any more.
When I called again to follow up the case, the operator told me my ONE year support ran out so they can't help me even though it's ongoing problem.
So Here I am still have many problems with SMC and no support from sun. I believe many other problems I am having are related this one. Here is a list of some of them:
1. user can't change the passwd
2. SMC put mail wrong mail alias for each user I edit
3. ...
I would appreciate any comment on this.
Anyone knows what I could have done wrong?
John ([email protected])
Hii Ed,
Hello, see how many of these you can answer...
See if the Disk is issuing any S.M.A.R.T errors in Disk Utility...
http://support.apple.com/kb/PH7029
Open Activity Monitor in Applications>Utilities, select All Processes & sort on CPU%, any indications there?
How much RAM & free space do you have also, click on the Memory & Disk Usage Tabs.
Open Console in Utilities & see if there are any clues or repeating messages when this happens.
In the Memory tab, are there a lot of Pageouts?
One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
Reboot, test again.
If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed.
Check the System Preferences>Other Row, for 3rd party Pref Panes.
Also look in these if they exist, some are invisible...
/private/var/run/StartupItems
/Library/StartupItems
/System/Library/StartupItems
/System/Library/LaunchDaemons
/Library/LaunchDaemons
Has it had extended disconnect from AC power in the past?
Similar Messages
-
Firefox 8.0 compatibility issues with NIS 2012
I have just installed NIS 2012 (previously had NIS 2011) and now NIS features (Identity Safe logins, Norton toolbar, and Norton Safe icons) do not function.
All of these are working in IE and also they worked previously with NIS 2011.
Any ideas on how to fix this?
Thanks!Please do not double post questions. Continue at --> https://support.mozilla.com/en-US/questions/899226
Moderator: Duplicate. Please LOCK this thread. -
Start the SMC GUI with special configuration/look and feel
Hello,
I forwarding alarm to another management system. Now I might again back.
I woulkd like to launch the SMC console and the Alarm tab should be shown directly.
It would be even better if directly the information of an special alarm is shown.
Does somebody have an idea for it?
ThanksHi Dholze,
I need only the part "that link back to the specific
alarm information withing a SunMC console".
Do you have an idea how to create this Back-URL?
CheersI know we have a small Java utility will launch the SunMC Console against one host in particular (i.e. instead of the user being dropped in a Domain and having to hunt for the correct system (default) they open directly to the host with the alarm (like double-clicking the icon for that host in the Console)).
They will be in the Module Browser tab so they can see the alarm lit up in colour, not in the Alarms tab though.
I think it's shipped with our Netcool integration software, but it can be used anywhere.
Regards,
[email protected] -
Programmatically change PXIe-2529 topology with NISE
Hi !
I have a PXIe-2529 that I control through NISE to test some products. These products require the matrix topology to be changed while I'm testing them.
Is there any way to do this programmatically ?
Opening/closing NISE session might be solution (even if I would prefer not to close it), but I can't find an option string xorking to change the topology...
Any ideas ?
thanks !
Solved!
Go to Solution.zyl7,
Unfortunately there is no way to change the topology on the fly with NI Switch Executive. A better method would be to have two NISE Virtual Devices, one for the 4x32 2 wire configuration, and one for the 8x16 2 wire configuration. You would close out the NISE session from VirtualDevice1, and open a session to VirtualDevice2 that references the same hardware. Of course, you would need to make sure that the external connections are connected properly, but this should change the topology for you.
Note: Closing the NISE session for VirtualDevice1 and Opening the NISE session for VirtualDevice2 will reset the switch module and cause all previous connections to open.
Hope that this helps!
Frank,
National Instruments
Staff Software Project Engineer -
Performance crippled with audit_trail=db in 12.1.0.2 CDB/PDB
Performance tanked as soon as I set audit_trail=db, and all I see in EM Express is buffer busy waits. Tracked it to object sys.aud$ with 100% of buffer busy waits. I have been using Oracle auditing for years and never see this type of impact. Anyone else see this?
Oracle 12.1.0.2 on 64-bit Oracle Linux 6.5 with kernel 3.8.13-44.el6uek.x86_64.
Created container database using DBCA with one pluggable database.
Ran benchmarks to baseline performance. Very good.
set audit_trail=db, bounced the database, logged into the PDB and enabled audit on select, insert, update, delete on all my application tables.
Transactions per minute dropped 95% and write I/O throughput dropped 75%.
I collected AWR reports with and without audit_trail set. These are shown below.
Each benchmark is 5 minutes with 2 minute ramp-up time, and 40 users no key/think time.
BEFORE SETTING AUDIT_TRAIL (IT IS UNSET). Buffer Busy Waits is only 1.2 seconds total.
Top 10 Foreground Events by Total Wait Time
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Total Wait Wait % DB Wait
Event Waits Time (sec) Avg(ms) time Class
log file sync 2,500,409 6224.2 2.49 54.9 Commit
DB CPU 5166.3 45.6
enq: TX - row lock contention 16,155 14.3 0.88 .1 Applicat
library cache: mutex X 83,598 13.6 0.16 .1 Concurre
db file sequential read 87,145 10.4 0.12 .1 User I/O
SQL*Net message to client 2,739,811 8.3 0.00 .1 Network
cursor: pin S 3,631 3.9 1.07 .0 Concurre
latch: In memory undo latch 86,392 2.9 0.03 .0 Concurre
buffer busy waits 45,740 1.2 0.03 .0 Concurre
cursor: mutex X 1,004 .9 0.94 .0 Concurre
NOW RE-RUN SAME BENCHMARK WITH AUDIT_TRAIL = DB. Buffer Busy Waits over 8000 seconds!
Top 10 Foreground Events by Total Wait Time
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Total Wait Wait % DB Wait
Event Waits Time (sec) Avg(ms) time Class
buffer busy waits 12,024,693 8002.1 0.67 68.1 Concurre
DB CPU 3253.5 27.7
log file sync 151,536 255.6 1.69 2.2 Commit
enq: TX - row lock contention 5,549 199.6 35.98 1.7 Applicat
enq: TX - contention 959 110.3 114.98 .9 Other
enq: HW - contention 177,020 95.9 0.54 .8 Configur
Data file init write 2,232 1.9 0.84 .0 User I/O
db file scattered read 19,037 1.7 0.09 .0 User I/O
db file sequential read 19,363 1.4 0.07 .0 User I/O
library cache: mutex X 36,060 1.2 0.03 .0 Concurre
Buffer Wait Statistics DB/Inst: NORM/NORM Snaps: 60-61
-> ordered by wait time desc, waits desc
Class Waits Total Wait Time (s) Avg Time (ms)
data block 14,204,039 7,922 1
segment header 1,288,059 22 0
undo header 286,303 2 0
1st level bmb 1 0 0
Segments by Buffer Busy Waits DB/Inst: NORM/NORM Snaps: 60-61
-> % of Capture shows % of Buffer Busy Waits for each top segment compared
-> with total Buffer Busy Waits for all segments captured by the Snapshot
-> When ** MISSING ** occurs, some of the object attributes may not be available
Tablespace
Owner Name
Buffer
Subobject Obj. Busy % of
Object Name Name Type Obj# Dataobj# Waits Capture
SYS SYSTEM
AUD$ TABLE 499 499 15,496,081 100.00Hi,
Happened to me that parameter values of a workspace were defaulting to the values in <configdir>/defaults.xml instead of the ones in the <workspace>,xml.
When you setup a database (e.g..java -jar ords.war setup --database mydb), you will have mydb.xml, mydb_al.xml and mydb_rt.xml under the <configdir>/ords created for APEX_PUBLIC_USER, APEX_LISTENER and APEX_REST_PUBLIC_USER, respectively. When a config entry is not present in mydb_al.xml or mydb_rt.xml, one would expect that it would be read from mydb.xml. However, that is not what happens. It reads from defaults.xml under the configdir.
That is the case for db connection parameters as well.
So, inspect all three xmls and make sure entries with
key="db.hostname"
key="db.password"
key="db.port"
key="db.servicename"
exist in all three xmls.
P.S. That should be the case for other parameters as well, but haven't verified.
Ege -
HP Deskjet 990cxi crippled with Intel iMac
Has any one been able to get the above printer to be fully operational with an Intel iMac?
I have lost the ability to print in draft and have not been able to get two sided printing to work although it should(under Layout) using the Gimp Driver.
I have two versions of the printer installed one with HP's Driver 2.7.1 and the other with Gimp's 5.0.0 beta
Have also sent an E-Mail to HP with no reply as yet.
My G4 Powerbook with HP's 2.7.1 driver prints just fine over my wireless network.According to the above article that I linked, the latest HP driver for the Deskjet 990cxi would have been included with the Tiger 10.4.4 that came installed on your iMac Intel:
"All included printer drivers are installed by default with Mac OS X 10.4.4"
I have the HP Deskjet 6840 and it is on the same list using that same 3.3 driver. When I open Applications>Utilities>Printer Setup Utility and then select (highlight) my printer, wait a few seconds and the "Show Info" button above becomes bold so that I can click on it, the report shows Driver Version: 3.3
I did not install 3.3, it was just there in the OS when I unpacked and started up the iMac.
Also, this list from the HP website indicates that the latest 990cxi driver was built into the Tiger software. I did the same search as you at the HP website and see the same thing you found, that it states that the driver is 2.7.1, however, in looking at the date, it is a 2005 date, so that is old, pre-iMac Intel information that I'm sure HP will someday get around to updating. As an enormous company, selling just tons of quality printers, HP has to closely cooperate with Apple to see that Mac users have available, through Apple, the latest updated drivers and software at all times.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c00317516 -
hi. my MacBook pro went off without me turnng it off. i tried turning it on again, but it wouldnt come on. i also tried doing the SMC thing, no avail. please any other thing to do ? (This notebook is still very new for anything to be wrong with it).
There is no way I would do the smc thing with a laptop that won't come on.If it's new and you're anywhere near an Apple Store, take it in. If it's less than 14 days old you can exchange it. If it's more they'll repair it for you.
-
Invisible WRE54G with Vista + NIS 2009
I have a WRE54G set up and working with by BT Homehub (WEP connection). It works just fine from my Widows XP laptop but is totally ignored by my new Vista 64bit desktop computer with Norton IS 2009 installed. And by ignored I mean even ping doesn't work, let alone browsing to 192.168.1.240. This desktop computer does see it loud and clear when viewing available networks but will not connect ("No response from access point"), then if I turn the WRE54G off, connect the desktop to the weak hub network and turn the WRE54G on again, the laptop sees it but it remains invisible to the Vista desktop.
For some reason I suspect the NIS 2009 (which is not installed on the laptop) so am interested in whether anyone has had experience of this working with the WRE54G. I plan to try it with NIS 2009 deinstalled, but am just checking something with Norton first.
Thanks....Partial progress.....
The main change I made was to stop SSID broadcast from my main router so that only the repeater was broadcasting. After that I got it working consisently as a repeater from my Vista desktop (traffic visible on the WRE54G). I can also now ping from there but I can't get at the setup page (192.168.1.240) - in fact if I attempt that it times out in the browser and also disables the repeater until it is powered off and on again.
However, I have now tried with my 3rd computer, an XP desktop (with NIS 2009) and it always fails to acquire an address when trying to connect to the network. The repeater was previously, but not consistently, working with this desktop.
More experiments tomorrow.... -
Need to have mail1 play nice with upstream mail server....
Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
On the debian box we're seeing:
2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
And mail isn't piping thru to the mail1 box. Here's the main.cf
sh-3.2# cat main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /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 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,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
# 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]
# 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
# 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,
# 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
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = _postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
mydomain_fallback = localhost
message_size_limit = 52428800
myhostname = mail1.stanwood.wednet.edu
mailbox_transport = cyrus
mydomain = stanwood.wednet.edu
mailbox_size_limit = 0
enable_server_options = yes
inet_interfaces = all
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
smtpd_use_tls = yes
smtpd_enforce_tls = no
smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
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 = gssapi,cram-md5,login,plain
content_filter = smtp-amavis:[127.0.0.1]:10024
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
owner_request_special = no
recipient_delimiter = +
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
# 02/02/09 Server Checkup by Alex
bounce_queue_lifetime = 6h
delay_warning_time = 6h
maximal_queue_lifetime = 2d
# Topicdesk Frontline Defense
disable_vrfy_command = yes
smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
virtual_transport = virtual
virtual_mailbox_domains =
sh-3.2#Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
mail1:~ admin$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
bouncequeuelifetime = 6h
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
delaywarningtime = 6h
disablevrfycommand = yes
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maximalqueuelifetime = 2d
messagesizelimit = 52428800
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
mydomain = stanwood.wednet.edu
mydomain_fallback = localhost
myhostname = mail1.stanwood.wednet.edu
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
smtpdenforcetls = no
smtpdhelorequired = yes
smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
virtual_transport = virtual
mail1:~ admin$ -
[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 -
How can I re-run the SMC and EFI driver updaters ?
When I bought my iMac Intel 20" in mid-2006, I immediately had a problem with the video driver when the computer woke up from sleep : the screen was badly flickering.
After lengthy talks with Apple, I was sent two updaters (one for the SMC and one for EFI) which solved the problem. Just to make sure, I deactivated completely the energy saver.
No problem for two years and a half.
Last night, for a reason unknown to me, the computer went into sleep mode and when it woke up, the whole screen was flickering and had vertical lines in it, despite having up-to-date SMC and EFI drivers.
Assuming that they had been corrupted, I wanted to re-run the updaters. But the computer refuses, saying that it is not needed.
So, my question is "HOW CAN I FORCE A RE-RUN" OF THE SMC AND EFI UPDATERS ?"
I have tried everything else, resetting the PRAM, resetting the SMC, tinkering with the monitor settings. But nothing works.
I believe that running again the updaters is the only possibility left, but they are up-to-date
Here is a summary of the iMac system info :
iMac (20-inch, Early 2006) IM41.0055.B08 (EFI 1.1) 1.1f5 (SMC 1.0).
Many thanks in advance for any suggestions
Patrice
PS : I have tried to contact the "experts" at Apple Support but, because my machine is two years old, they want me to buy time to ask this question from them, despite the fact that the problem stems clearly from a faulty design at the beginning of the iMac life, and that the knowledge base says that there is no unresolved issue presently with this model !
Well, the problem is still there after two years and I only avoided it by deactivating the energy saver.
But Apple never mentioned how to force running an updater if the machine does not want to ...You can restore a backup only by using the iOS Setup Assistant.
iOS: Back up and restore your iOS device with iCloud or iTunes -
Help! I seem to have got myself into a terrible mess with catalogues, etc.
Morning all,
I have an issue which is causing me endless grief:
Recently, I upgraded from 3.0 to 3.4 and on the same day tried converting all my RAW files to .dng in the belief that this would save me hard disc space and allow me an extra degree of security (having the changes written into the file). However, during this conversion of 36,000 files, there was a power cut and the catalogue became corrupted, so I can no longer return to that catalogue.
No problem. I simply re-imported all my files to my HD from my external back-up drive and added them to my catalogue, causing many thousands of duplicate files, spread across different folders. The catalogue doesn't contain any duplicates, however.
(I would like to point out that, in my defence I was, following surgery, acting under the influence of some very heavy pain killers when I made the decision to do all of the above. It semed like a good idea at the time.)
Now this has completely maxed out my internal drive and I don't know how to remove the duplicate files from the HDD except to go through them manually, one-by-one, which isn't really an option. I could just swap out the HDD for a new one, but would that lose me all the work I'd done on files imported since?
Can anyone recommend any software for doing this, or a routine within LR that could save me all my changes, or am I just going to have to face up to losing a whole lot of work here?
I really would appreciate some help with this as it's putting a strain on my ability to work and, as a result, my marriage too (really!) So, please save me from the divorce lawyers!
Nick.Hal,
Yes, I see what you're getting at, and that would work if all of the duplicates weren't in just one LR catalogue folder. That's 30,000+ duplicates in one folder. I'd go ahead and delete them all, but the trouble is that it also contains copies of files that aren't in the catalogue that I'd like to retain access too. I can't see a way round that, but maybe you can. A venn diagram would probably be really helpful at this point, I think...
Frank,
That's the technique that works if there are dupes in the catalogue, right? I don't have those.
But you're right about pain, and pain-killers: makes you do some crazy stuff. I'm only just getting round to putting the pieces back together after the removal of some very troublesome wisdom teeth; I can't imagine how much worse it would have been if I'd been crippled with back pain.
I think what's happened here is that I've reached an understanding of the problem without the actual answer coming from you guys - and I mean no disrespect whatsoever. It's forced me to think VERY hard about my system and how I back-up - or not - and how best to proceed from now on.
So, having read a lot of David Marx's blog posts, I think I'll be folloing his example in 3-2-1 back-up procedure in future. I'll also be having a "Year Zero" event on my workstation and changing to Win7, re-naming my HDDs in order and switching to an external HDD for running my catalogue and image files side-by-side, which will make syncing with the new laptop much easier.
Lastly, given that sorting through 30,000+ dupes in one folder and then checking them against the contents of all my other folders could take a year, I've decided to go the whole hog and archive almost all of my catalogue except my folio images (they get built into my website from the Lightroom Galleries plugin, so I need access to them on a regular basis) which I can re-work in less time than I would spend trawling through the whole HDD, and start afresh with a proper, logical system.
This has been a painful and potentially costly lesson, but it could have been so much worse. At least I have my RAW archive...
Thanks once again,
Nick.
EDIT. Wait. Maybe I have it. Hal, (or anyone) could you let me know if you think this might work:
Delete the entire folder of 'duplicates and everything else', then reimport the contents of my RAW archive into the top level LR folder. LR should then auto-reject suspected duplicates, and replace the non-duplicate contents of the folder that were lost when I deleted the dupes-and-all folder.
D'you reckon that'd do it? -
Firefox 11 is screwing with Norton ID Safe on Paypal
With FF11 when I go to Paypal my Norton Internet Security's Identity Safe fills in my username (which is an email address) as it should. When I go to "Send Money" I have to fill in the email for the person the money is going to. I do this. Then I select "|Continue", which should get me a page asking me to verify the transaction. Instead, NIS ID Safe replaces the email for the person I want to send money to with MY email, and I get a Paypal notice saying I cannot send money to myself. When I go to Paypal using Internet Explorer, the ID Safe fills in the initial Paypal login info (my email and password), I log in and go to "Send Money", I fill in the payee's email, and when I select "Continue" that email IS NOT changed by the ID Safe and I DO get the "confirm transaction page". This problem with the ID safe changing the payee's email to my email is obviously endemic to Firefox, and is not a problem with either Norton's or Paypal's code.
As it was the ONLY thing I could do, I tried deleting cookies. As I suspected, that had absolutely no effect on the problem. I ALSO noticed that the "clear cache" option in Tools - Options has disappeared from FF11. Smart move, people.Nope, the problem isn't in Firefox's password stuff, it's in Norton's Identity Safe, that's what's removing the payee's email and replacing it with my email when I try to submit a payment thru Paypal. I tried Norton support, and it turns out it was a waste of time. Although I was originally sure it culdn't be the browser, they insisted it wasn't Norton, and had me try IE instead of Firefox, and it worked OK, and uninstalling FFX 11, then cleaning out the registry to make sure noithing was left there, and installing FFX 9, everything worked OK then, too. So I gave in and agreed with them that it must be Firefox, specifically FFX 11. But then today I found FFX 9 had the same problem, and sao did IE. It sems that the first time a browser is used after install, there's no problem. But after that the Norton Identity Safe replaces email addresses with my own email address at Paypal as well as some other sites that have my email as my username. So the problem IS Norton's ID Safe, which was recently updated". The "improvements" have rendered it useless, at sites that need you to fill in an email someplace after you've already logged in, the ID Safe will overwrite the address you typed in with your oen email when you try to submit the page. I should have known better than to believe one of the idiots at a 3rd party "tech assistance" outfit in India. I did some more research today and discovered that others are having the same problem with the ID Safe, some of them using Norton Internet Security and some using Norton 360, both of which have the ID Safe.he only way to0 fix things is to go back to the ID Safe version 5, which I can only do by going back to Norton Internet security 2011. Which I also can't do. To go "backwards with NIS, you have to uninstall the one you have and reinstall the older one. Luckily, I do have the setup files for NIS 2011 (which can't be gotten from Norton now), but..... If you want to keep all your usernames and passwords, you have to save them into a separate file, then reload them when you've installed the version of NI you want to use. And Norton has made THAT impossible. NIS 2012 saves the info in a .dat file, and NISs 2011 uses a .npm file. And, of course, NIS 2011 cannot read or even recognize a .dat file. So even saving the file FROM NIS 2012 onto the desktop before uninstalling it, and then placing that file manually in the right folder after installing NIS 2011 doesn't work. WHY do we pay people like this so much money just to let them screw things up and then provide "tech assistance" by people who don't even understand what you tell them half of the time, even if they DID pass some English language exam? Hell, I once passed a linguist exam that got me an official linguist classification in the Army, and my German language ability was about what a typical 9 or 10 year old German kid would have. Less than that, actually, where proper grammar was concerned. It's not as hard to pass a language exam as it is to actually do anything useful using that language. Oh, yeah, when I called Norton back today (actually yesterday, now) and demanded to talk to the next level of support the guy
"transferred" my call to that section. I'll admit they have better "hold" music than just about any I've ever run into, but after being on hold for OVER 2 and a half hours I finally hung up. And I'm paying these A..holes $89.99 a year for their wonderful service. My recommendation: If you have ANY other reasonable option, DO NOT use Norton software, if you already have it look for a replacement and buy that instead when it's time to renew the Norton subscription. -
Media keys not working with iTunes 12.0.1
MacBook Pro, 15" Mid-2010
Software: OS X Yosemite 10.10.1
iTunes: 12.0.1.26
Hello, ever since I upgraded to OS X Yosemite/iTunes 12 back in October I have been unable to use the back, forward, and play/pause buttons with music playback on iTunes. I've tried an SMC reset with no luck and I'm not really sure what to look for in keyboard settings that might help. Thanks in advance!Howdy PigJiggin,
Thanks for using the Apple Support Communities.
To troubleshoot this issue where your function keys on your keyboard are not performing the special feature depicted in the icon, please check your keyboard settings as shown in the article linked to below.
How to change the behavior of function keys on your Mac - Apple Support
Cheers,
Alex H. -
ITunes Only Runs with Anti Virus disabled
I had the same problem a lot of people are having when upgrading to the latest iTunes.
I have reinstalled QT and iTunes separately and have finally gotten it to run. My problem now is that iTunes only opens if I have Norton Internet Security disabled. When Norton is enabled, iTunes doesn't open at all - no error message - but it runs because I get a message from Norton to designate the type of access I want to give to iTunes. I choose "permit all" but it doesn't open. Itunes appears to continue running because I have to force the computer shut each time because it is unable to end the program. Also, sometimes I get an end program error "SMAX4PNP" - the pc also cannot end the program and I have to force it shut.
But when I log into iTunes with Norton disabled, everything works smoothly.
When I go into the personal firewall for Norton, I am unable to find iTunes as an option to "permit all".
Also, when I go to the task bar to end running processes, I try to end itunes.exe but it does not end it.
Can you help? I have combed through the discussion pages for an hour and a half now but cannot find the specific fix to my problem.
ThanksThanks for your comments Cameron.
I followed your steps. The uninstall and install went fine but I am still unable to open iTunes with NIS on. I believe I did something wrong.
After scanning, I couldn't find the programs you mention in the program scan box (or in the personal firewall configure box): iTunesHelper.exe, iTunes.exe and the QuickTimeInstaller.exe. All I saw in the scna box was Apple iTunes and Apple Quicktime.
You also said to leave all programs on the list - did you mean leave them as they appeared with the "Internet Access" field on Automatic?
Also, once scanning is complete, I couldn't find an "accept" or "ok" button and the "next" button was never enabled, even after tinkering with the programs....should I just close the window?
I think I need your help again.
Thanks
Maybe you are looking for
-
Site lost activation out of nowhere - How do I find and enter the activation key through VPN?
I had a message that site comms went down. My clients sent somebody on-site and all is working but the OnPlus agent still shows comms down. I VPN'd in and can get to the web page for the unit but it's asking me to activate it. Is there a way to fi
-
How to edit digitally signed pdfs
How to edit signed pdf ? am getting the message that you are currently viewing a signed version. All editing and interactive features are disabled. Save a copy and reopen to edit this document , please help how can I remove this signature or disable
-
hi, i develop in flash 8 (AS2) a car game where i run a race with 1 car. i want to transform this game into multiplaeyr with media server, can someone give me an idea on what do i need to do ?? thanks. any help will be glad
-
Arial font rendering problem in AIR
Hi, I am new to flex. I have a problem in rendering arial font in Label in AIR application. I have attached the screen shot.The letter W has been cutted. Regards, Jayagopal.
-
Hi, Is there a limit to the number of rows thats a tree can deal with. I have a tree with about 120,000 nodes and using the APEX tree and the DHTML tree example and both take 2-3 mins to render, the DHTML version is quicker Is this just too many for