No e-mail address given
I have been trying to set up my new 8500A printer all afternoon. It keeps asking for a e-mail address for the printer but when I try to access it, there is nothing there. When I use the touchscreen to find it, the word "connecting" comes on the screen with the HP logo and after a few moments, it times itself out. I have tried printing the paperwork 3 times and no where does it list an e-mail address. Any ideas? Someone? Anyone?
I too just purchased a new 8500A printer and am having trouble with the ePrint Email Registration.
I'm connected via ethernet and I'm able to access the WebServer and print to it and everything. I have applied the downloaded product updates with no issues.
When I try to activate the WebServices to get an ePrint Email address...I either get a "Unable to connect" error...or it DOES connect but never prints my ePrint document.
I've reset the factory WebServices settings and tried again with same issues.
BUT NOW...I can select the "Print Email Address" option and the display will "BLUE SCREEN" and then all lights flash with a "Please turn off and back on" error.
AND Now I cannot access the APPS option from the main screen either...saying it can't connect to hpeprintcenter.com.
Similar Messages
-
How to set up a new apple e-mail address when already have an existing Apple ID
Hello
Thank you for taking a look at my query - I have searched many posts but not found a specific answer to my question - so please help!
My dilemma:
I am in effect running everything smoothly - I am already on iCloud and have an @me.com mail address.
The problem arises in that I need to change my name (due to a divorce) and hence my e-mail address - I would like to use my maiden name for obvious reasons!
So what have I tried?:
I have set up a new Apple ID using a 'hotmail' address, as you need an existing address to set an ID, but would actually like a new 'apple' address. How do I do this? Since I have registered all my devices (iMac, iPad 3 and iPhone 3GS) with iCloud already using my married name ID it seems I am unable to get another appleID? Is this true? Is there a way around this?
Concerns:
I have many communications with lawyers and ex and various other things I would like to keep on my existing apple ID/mail account (and also itunes etc) I still need to be able to access this information. I am happy to keep this apple ID active at the same time as having the new ID if this is possible on all the same devices? Currently however I do not know how to do this, i.e. run two mail accounts through iCloud OR ideally transfer my info to the new ID - however from reading around I believe this latter (logical) option may be impossible?
So:
... I need a knight (or maiden) in shining armour to help me understand my options, answer the Q's above and provide the steps I have to follow to do this as I am no IT guru! And as there are many similar Qs without a clear answer I'm sure you will gain lots of points!
Thanking you kindly in advance!
PS. Apple if you are reading this please can you do something about this situation as there seem to be many questions around this issue. Unfortunately divorce and name changes are a frequent part of life these days and it would be good if you can accommodate this!OK, so I realised I was still within my 90days of being able to get support from Apple due to recent iPad3 purchase.
So between what I have gleaned from this forum and what I have learnt from the support call here I hope is a comprehensive one stop shop answer to the question... "How do I get another Apple e-mail address ?" It's not straight forward but bear with me as you will get a result (also if anyone with IT prowess can offer further advice or clarification please do reply to this so we keep all info in the same place)... right - we shall begin:
First a few points to bear in mind/wise words that I wish I was aware of before:
You preferably do not want more than one Apple ID so that syncing etc is straight forward. SO create an e-mail address that you will be happy to have no matter what, whether you are married/divorced (and yes it unfortunately could happen...) etc...
So...
1. First go to www.myinfo.apple.com, change your country as required and click on manage your account. Log-in. Should go straight to your Name, ID and e-mail tab.
2. OK you are now presented with one of two scenarios....
a) If your AppleID and primary e-mail address is a me.com (or mac.com) then you are unlikely to have an edit option next to this line - follow point 3. Another ID has to be generated, and unfortunately (as Winston Churchill above rightly pointed out, the problem that you will have on the whole is that any purchases you make from the iTunes Store under your previous account, will be inaccessible on many of your devices. - IF however all you wanted is a new e-mail address and you are happy to keep running your old ID at the same time - there is a way around this .... read on to point 3)
b) If your AppleID and primary e-mail address is not a me.com (or mac.com) then - follow point 4. This is the better option to have, hop skip and jump with glee as you will in effect have the same ID account and syncing will not be an issue. But note that your new ID will not be editable going forward so head my words of wisdom above.
NB. If you already have more than one ID and one of the 'Apple ID and primary e-mail' is editable i.e. 2b) then choose this option to change as it is simpiler to manage.
3. OK lots of steps here and explanations:
i) You need to create another Apple ID - there are two ways of doing this a) if you go to your iphone or ipad settings > iCloud > delete your account (Don't worry you are effectively only signing out and not deleting) (you'll be given an option what to do with your contacts) > The page will then give you an option to create a new Apple ID.... follow the steps, and you will get a new me.com AppleID and primary e-mail address.
b) If you do not have an iphone or ipad - use your computer: Go to sytem preferences > icloud > sign out of account (again you will be given an option to keep contacts on the computer etc. do what is appropriate for you). An iCloud window should then pop up - and there is an option to 'Create an Apple ID'... follow the steps, in 2nd step (after date of birth input) go for the free iCloud option and do not use an existing e-mail address (e.g. hotmail or gmail)... as it then gets more complicated (I did go down this route as I didn't know any better - so I can explain if you wish to know - just ask) - continue with the steps and you will get a new me.com AppleID and primary e-mail address.
ii) Now assuming you have an itunes account and other devices... and you will want to sync everything across devices... then ensure you log back into your OLD account and use this as your main account on all devices. This will keep all things synced between devices with no problems.
iii) To get your new e-mail account active go to all your devices and computer and just add the new me.com address as another account:
a) on iphone and ipad: settings > mail, contacts, calendars > "add account"
b) on computer assuming you use mail: Mail>preferences>account information> hit the '+' under the left hand account box and fill in the details... You will then effectively have two mail boxes running in mail - your previous and new one. What I have noticed is that you can drag and drop (which will copy) mailboxes you created in your old account into your new account - which is great as you can keep the stored messages to hand and effectively you can taper down use of the old account (or use as you wish) over time and eventually not notice the old account is in the background.
Hey presto you have a new e-mail address AND your devices are syncing itunes, photostream etc...
4) So - much better option....
i) create a new Apple ID as per point 3i) above.
ii) go back to www.myinfo.apple.com, change your country as required and click on manage your account. Log-in with old ID. Under Apple ID and primary e-mail adress - click edit and now insert your new me.com Apple ID. This will now be both your ID and primary e-mail address. This is where my knowledge (gleaned from this Forum) stops on this option - as unfortunately it did not apply to me. But I think it will get you where you want!
Hope all this info helps rather than hinders!! It definitely would have helped me
Enjoy. -
[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 -
Table for invoice mailing address
hi gurus,
is there any database table for the invoice mailing address?
thanks.Hi
Go through the link given below : you wil find tables related invoice.
http://www.erpgenie.com/abap/tables.htm
With Regards
Nikunj Shah
Edited by: Nikunj Shah on Jul 9, 2008 5:38 AM -
CSDK Java - Query by e-mail address
Does any body know what the required syntax is to construct a query for searching on email address?
I can query by name without any problems using either starts with or equals. I would like to be able to do the same around e-mail but either get no results back or a CAPI_STAT_LIBRARY_IMPLEMENTATION error. Is this supported?
I see in a vCard that the E-Mail address is not as simple as the Name field. E-Mail seems to either be EMAIL;TYPE=PREF;TYPE=INTERNET:[email protected] or EMAIL;TYPE=INTERNET:[email protected]
Given these extra attributes to the e-mail, any ideas on how the Query object needs to be constructed to do this.
Many thanks.
Dave.CAPI_STAT_LIBRARY_IMPLEMENTATION is the correct error code here and you were right the query on e-mail is not supported.
Currently the supported properties for the queries are N, FN, BDAY, TITLE, ROLE, NOTE, CATEGORIES, NICKNAME, X-ORACLE-SPOUSE, X-ORACLE-ANNIVERSARY, X-ORACLE-OFFICE,
X-ORACLE-ASSISTANTNAME
Jean-Philippe -
IPad is associated to invalid e-mail address
Hello! A customer of mine was given an iPad and it was registered with an e-mail address that no longer exists. She wants to reset the device to it's original state with her information but the e-mail ID is "stuck". I created a new account for her but there is no way for the device to associate her NEW info with the old e-mail. Nobody has the original password needed to reset the device and the e-mail associated with the password no longer exists. Pretty much a catch 22!!!!
Is the ANYWAY to nuke the device without the original password??? This thing is junk without being able to factory reset.
Thank you!!!Only the owner of an iTunes account can remove a device that it's tied, creating a new account won't help.
The person who gave the iPad to her, has he/she tried getting the password for the account reset via http://iforgot.apple.com (does he/she know the answers to their security questions ?) ? If they can't then they will have to contact Support in their country and see if they can reset the account's password for them (the owner of that iTunes account will have to do it as the need to prove their id and that it's their account).
Contacting Apple about account security : http://support.apple.com/kb/HT5699
Activation lock : Find My iPhone Activation Lock: Removing a device from a previous owner’s account -
More then one E-mail address per insurance provider
Hello to you all,
Does anyone have an Idea on how can I maintain more then one E-mail address per insurance provider?
In Tcode NG07/8/9 I am able to have only one which is not enough,
I would expect to have a multiple selection on that field like in customer master record Tcode FD01/2/3.
Regards,
YoavDear Yoav,
In the Tcode NG07 only one mail id is given because from here you can send the files directly on clicking the mail icon. Because when you click on mail icon(adjacent to box) it shows whom you are sending the data, here you can also mark CC & BCC to the different users.
In Customer you are not mailing directly. If you have any query you can reply back.
Regards
Piyush -
POP3 Mail & Address Book contacts have gone!
I recently did some housekeeping on my Mum's iBook G4 (OSX 10.4.10), part of which was purchasing and installing SpamSieve into Mail. This all went fine. Today she said all the mail in her POP3 inbox had gone, she couldn't send/receive and all her address book contacts had gone (Except hers and Apples).
I've got the iBook now and have noticed that her account type in Mail has somehow changed to a .Mac account (did I somehow do this, or did she???). This is obviously the root of the problem as the
email address now has '@mac.com' appended to the end and the incoming mail server is now 'mail.mac.com' and the outgoing is 'smtp.mac.com:heremailaddress' which is all wrong. I'm unable to change the account type back to POP or the incoming mail server from 'mail.mac.com' (it's greyed out) back to what it was.
I have now created a second account with the correct POP settings and have received in all unread email, but the read email messages have gone. I am unable to send as the new correct pop account is only offered the incorrect outgoing server ('smtp.mac.com:heremailaddress').
Having read several post on this forum, I feel the Mail/Address Book issues are connected and that maybe the application(s) database(s) have been corrupted. I've tried the Address Book remedy at http://discussions.apple.com/thread.jspa?messageID=5248351� but this does nothing. The 'user'>Library>Mail folder shows the two accounts as two separate folders. The recently recreated account folder has the new unread messages in the 'INBOX.mbox folder, but the older account folder (which now has 'MAC-' added to the front of its name) only has 'info.plist' in a 'INBOX.imapmbox' folder!
I don't believe any back-ups are available. Can anyone help me restore her old unread mail, and possibly her address book contacts?
I've also just noticed that SpamSieve does not launch as it should when I launch Mail, even though It was purchased and the scripts installed correctly.Didn’t you make a backup prior to the housekeeping?
I don’t know why would Spotlight find contacts that are gone from Address Book (if that’s what you mean), but as far as Mail goes, under some circumstances (e.g. lack of available disk space, filesystem corruption, repeated crashes), Mail may discard the current ~/Library/Preferences/com.apple.mail.plist preferences file and create a new one. This file is where all the account settings are stored. As a result, all the non-.Mac account settings (but not the messages themselves) are lost. If you had a .Mac account, its settings would appear to have been preserved because Mail would set up that account automatically using the System Preferences > .Mac settings.
What’s the capacity and space available on the startup disk? Take a look at the comments about disk space in the following article, in case they apply to you:
Problems from insufficient RAM and free hard disk space
Verify/repair the startup disk (not just permissions), as described here:
The Repair functions of Disk Utility: what’s it all about?
After having fixed all the filesystem issues, if any, and ensuring that there’s enough space available on the startup disk (a few GB, plus the space needed to make a backup copy of the Mail folder), quit Mail if it’s running, and make a backup copy of the ~/Library/Mail folder, e.g. by dragging it to the Desktop while holding the Option (Alt) key down, just in case something else goes wrong while trying to solve the problem. This is where all your mail is stored.
You have three options now:
(1) Restore ~/Library/Preferences/com.apple.mail.plist from a backup if you have one. Mail shouldn’t be running while you do this.
(2) Set up your mail accounts again (you may want to quit Mail and trash the new com.apple.mail.plist first to start over). If given the option to import existing mailboxes or something like that, don’t. Just enter the account information and Mail will automagically rediscover the data in ~/Library/Mail/ when done. You’ll also have to re-configure most of your settings in Mail > Preferences. For spam-related security reasons, the first thing you should do is go to Preferences > Viewing and disable Display remote images in HTML messages if it’s enabled.
(3) Mail may have renamed the old preferences file to com.apple.mail.plist.saved. If that’s the case, you may try trashing the new com.apple.mail.plist and renaming the old com.apple.mail.plist.saved back to com.apple.mail.plist. Again, be sure Mail isn’t running while doing this. Given the circumstances, there exists the possibility that com.apple.mail.plist.saved became corrupt, but that often is not the case and the settings can usually be restored by just renaming the file back to com.apple.mail.plist.
As a side effect of re-creating com.apple.mail.plist, Mail might rename Outbox (which is where messages waiting to be sent are stored) to Delivered. The name of that mailbox is actually a misnomer, as it would contain messages (if any) that couldn’t be delivered for some reason. You can delete that mailbox if you wish.
Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder. That is, ~/Library is the Library folder within the user’s home folder, i.e. /Users/username/Library. -
Transfering an e-mail address to Mobile Me account. Do I need to?
Hi everyone,
I'm not sure if this post should go here or perhaps in the Mobile Me area. It involves both iWeb and Mobile Me.
===
For about the last 10 years I’ve had my own domain name [www.morrisacevedo.com] It’s been hosted by various companies. The latest one was Network Solutions. However, I just moved my website over to my Mobile Me account. The reason is that I was able to make a much better looking and functioning website on my own with iWeb than I was able to with DreamWeaver given my limited skills.
My website is currently on the Mobile Me account and not on Network Solutions and is working perfectly. The Network Solutions account ends at the end of November but I wanted to move the website before it expired.
Here is my question:
I have also had my e-mail address for the website as [email protected] My e-mail is working but I think that it’s still going through Network Solutions. How do I transfer [email protected] over to Mobile Me so that it still works after my Network Solutions account ends in a couple of weeks?
I just have feeling that pointing [email protected] over to the Mobile Me hosting may not have taken care of my e-mail account as well. Does that make sense?I don't believe you can transfer/forward the email to MMe. When your contract ends with your current host so should the email address. If your site is up and running on MMe today, put a notice on your first page that you email address has changed and give it. But don't put it in text. Type in it iWeb and then take a screenshot of it and post the screenshot image file. You don't want spam crawlers harvesting your email address.
You could encode your email address by one of the methods in this demo page: Embedding Forms & Encoding Email Addresses.
You do know that you can create alias email addresses with your MMe account. You can have one for personal, one for business and one for online shopping (if you start getting span at that shopping email address you can delete it from the aliases and create a new alias).
Also, until your contract is up in November forward your old email to your new MMe email so your replies will be from your new email address. -
Request to Validate e-mail address Valid?
I received a request via e-mail from NI Community to click on a link to validate my e-mail. Given we have been cyber attacked, phished, etc. several times the link looked suspicious. Is NI Community sending out requests for validation of e-mail addresses or is this another potential cyber attack attempt? I can send a copy of the e-mail to NI if you can provide me with an e-mail address.
Solved!
Go to Solution.MetManager wrote:
Is NI Community sending out requests for validation of e-mail addresses...?
Yes - https://decibel.ni.com/content/groups/ni-community-help/blog/2013/02/11/e-mail-verification
Try to take over the world! -
BB Travel on Q10 won't allow setup or change of e-mail address
After (re)installing BBTravel (several times), I still can't set up e-mail scanning. After agreeing to the legal agreement I see the [Login] and [Register] buttons for a split second before that screen is involuntarily pushed aside and I'm presented with a "Enable Trip Scanning" dialog box with [Disable] and [Enable] buttons. I click [Enable] and [Login] and [Register] reappear for a split second before again being pushed aside and told I don't have that feature enabled. In other words, I'm never given a chance to set up the very thing I'm told to set up. Under Settings for BBTravel (V3.1.1.2) it shows my work e-mail address but I can't edit or delete that field; ditto the first and last name fields (which are empty). The app has been granted access to everything under Setup - Application Permissions.
I had all this stuff working just fine under BB7, so it's not like this app is new to me. (Yes I know it's a complete rewrite of the old one and not a simple port.)Note that I do not have the option to do Settings > Manage My Emails as per this Knowledge Base article. When I pull down the menu from the top and tap on the Setting gear I'm shown a few user settings I can change such as what units to use for temperature, but I can't add/modify/delete the e-mail field or the First Name and Last Name fields.
btsc.webapps.blackberry.com/btsc/viewdocument.do;jsessionid=E8B503FB2BBF69EF32F6224578F73762?externalId=KB33886&sliceId=2&cmd=displayKC&docType=kc&noCount=true&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl
Trip Scan is a feature that will scan the associated emails that are registered with BlackBerry Travel for any existing trip itineraries. If itineraries are found, they will be added to BlackBerry Travel.
To enable Trip Scan, the following must be performed:
The Trip Scan feature must be enabled during initial login, registration or from the Settings menu in the application.
Allow BlackBerry Travel Permission to Email
Note:
BlackBerry Travel will only scan email accounts that have been registered with BlackBerry Travel on the BlackBerry 10 smartphone.
The BlackBerry ID email address will be automatically registered.
Additional accounts can be added through the BlackBerry Travel application, under Settings > Manage My Emails. -
Can't verify my e-mail address.
I asked a question and was told I would need to verify my e-mail address by clicking on a link in an e-mail I would receive. I received the e-mail, and then clicked on the link. All seemed OK, until later when I went back to the site to see if my question was answered, there was a message that my e-mail could not be verified. There was no help given as to what to do about that or what to do next. I am at a loss.....and expect I will not be able to get this message thru either.
So, do I have to ask my original question again? Apparently my e-mail has now been "verified" .......
-
When is preferred e-mail address written back to the directory?
GW 2014
In the Admin Console, or via the REST API, it is possible to set a
preferred e-mail ID and preferred e-mail internet domain for a given
object. Why would this be necessary? Because GW is really neat and lets
you easily handle users from multiple internet domains (novell.com,
suse.com, netiq.com, etc.) at the same time, in the same system. Further,
it lets users of all systems get e-mails from all domains if wanted, which
really worked well when Novell was acquiring companies, and then when they
were acquired; if a user changed from novell.com to suse.com, their old
e-mail (targeted for the old address) still reached them. Smart smart smart.
If I set somebody to have a preferred address, specifically via REST
(because that is how the IDM driver for GW 2014 does it), their directory
address (in eDirectory) is not updated, though obviously a preferred
domain should be the one advertised in a directory (or so seems obvious to
me). If I use the REST API to tell GW to "commit" this change, then it
goes ahead and updates the directory; thanks Morris for fixing this in the
thread before this one: https://forums.novell.com/showthread.php?t=482628
My question (finally): Does GW automatically do a commit after some period
of time? Can it? I'm asking because I do not want to need to do this
manually, though I could with the IDM driver when pushing a value over to
GW; it would be nicer if GW would do the work for me and push back its
correct value (it is authoritative or e-mail addresses after all) back to
eDirectory as if I had asked it to commit. Perhaps I am just not patient
enough and eventually it will do so, but if so how is that configured?
Thanks.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...Short answer is no. There is no scheduled address publishing to the directory, It's only done when there is a trigger activated by changing something in either the Internet Addressing options, or if you go to the directory definition in the admin console.
You could create a cron job and do a publish for the system. you could put this curl command in a script for the cron job to run:
curl -k --user gwadmin:pwd -X POST -H "Content-type:application/json" --data "{\"commit\":true}" https://10.10.10.10:9710/gwadmin-ser...ectory/publish
--Morris
>>> ab<[email protected]> 3/23/2015 9:49 PM >>>
GW 2014
In the Admin Console, or via the REST API, it is possible to set a
preferred e-mail ID and preferred e-mail internet domain for a given
object. Why would this be necessary? Because GW is really neat and lets
you easily handle users from multiple internet domains (novell.com,
suse.com, netiq.com, etc.) at the same time, in the same system. Further,
it lets users of all systems get e-mails from all domains if wanted, which
really worked well when Novell was acquiring companies, and then when they
were acquired; if a user changed from novell.com to suse.com, their old
e-mail (targeted for the old address) still reached them. Smart smart smart.
If I set somebody to have a preferred address, specifically via REST
(because that is how the IDM driver for GW 2014 does it), their directory
address (in eDirectory) is not updated, though obviously a preferred
domain should be the one advertised in a directory (or so seems obvious to
me). If I use the REST API to tell GW to "commit" this change, then it
goes ahead and updates the directory; thanks Morris for fixing this in the
thread before this one: https://forums.novell.com/showthread.php?t=482628
My question (finally): Does GW automatically do a commit after some period
of time? Can it? I'm asking because I do not want to need to do this
manually, though I could with the IDM driver when pushing a value over to
GW; it would be nicer if GW would do the work for me and push back its
correct value (it is authoritative or e-mail addresses after all) back to
eDirectory as if I had asked it to commit. Perhaps I am just not patient
enough and eventually it will do so, but if so how is that configured?
Thanks.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below... -
Every time I open Reminders it brings up a reference to an account that is not mine and asks for a password for an e-mail address which is not mine. I have to cancel to proceed.
Does anyone else ever have physical access to your computer? Does the address belong to one of your friends/family/contacts? Have you recently had to take in your computer for repair, or given remote access to anyone?
It's very unlikely that you have been hacked - a hacker does not normally add their own email address to your system.
Matt -
FaceTime HD app won't go any further than verifying my e-mail address.
Does the ext directory have the php_oci8.dll? In the original steps the PHP dir is renamed. In the given php.in the extension_dir looks like it has been updated correctly. Since PHP distributes php_oci8.dll by default I reckon there would be a very good chance that the problem was somewhere else. Since this is an old thread I don't think we'll get much value from speculation.
-- cj
Maybe you are looking for
-
Opening Canon CR2 files in CS3 on a Mac
What Camera Raw plug-in do I need to open Canon CR2 files in Photoshop CS3 on a Mac? -Please send download link and installation instructions. Thanks
-
'vibration' with firefox in linux
i dont know if anyone else has notices this, but firefox seems to have some issues in linux. When i hover over a button/link on a website, sometimes it(the link/button) seems to vibrate in place for a fraction of a seconds before stabilising..it does
-
I recently upgraded both Pages 09 (I believe) and went to OSX 10.9 Maverick .... now I am unable to send a pages document to a friend on gmail. Google rejects the message and attachment with the following explanation - The reason for the problem: 5.
-
Can I perform transformations during propagation with message_grouping
IOW... I have Q_Source and Q_Dest on different instances. I want to use propagation to move them from one to the other. I wanted to queue an invoice type object... with 1 header object and a nested table of detail objects but I found I can't do that.
-
Adding pages to an existing pdf
I have an HP officejet 8600 and scanned pages to create a pdf, no problem. But now I have to add pages to that existing pdf and don't know how to do it.