Manage e-mail addresses - password issue

Dear Community!
I have got a following issue, I hope you can give me any solutions:
I just logged in to my skype account to change the primary email address, but when I tried to save it it asked for my password, and it would not like to accept it. However, some minutes before it was all right for logging in, and in parallel, I used it for logging in to onedrive, too. I use my Microsoft Account to sign in to skype, as I am an old Messenger user, keeping that account to sign in. What should I do for arranging my emails? (Caps Lock and Num Lock are off, so it should not affect the password.)
I am waiting for a helpful answer.
Babraba

try this
http://community.skype.com/t5/Security-Privacy-Trust-and/So-you-want-to-change-your-primary-mail-but...
it does work.

Similar Messages

Two accounts on the same address password issue

Not sure if this is the right spot to put this but i have two accounts on the same mail address... i have forgotten the password of my main accoutn but every time i ask for my password it resets the password for this account instead. I have tried switching this account address to a different account to free it up but it doesnt seem to work. Any ideas?

Hi, Kainaq, and welcome to the Community!
I will confess I am mystified why the same e-mail address is allowed to be used as the registered e-mail address for multiple accounts. Apparently, most of the time, a password re-set request is tied to a Skype name and/or account. However, when this happens as you relate it, the only recourse is to file with Skype Customer Service. contact customer service
We here in the Community are not authorized to resolve account-releated matters.
Best regards,
elainem77
Was your question answered? Please click on the Accept as a Solution link so everyone can quickly find what works! Like a post or want to say, "Thank You" - ?? Click on the Kudos button!
Trustworthy information: Brian Krebs: 3 Basic Rules for Online Safety and Consumer Reports: Guide to Internet Security Online Safety Tip: Change your passwords often!

ICloud mail address setup issue

I have a @mac.com Apple ID with @me.com iCloud mail address. When setting up iCloud on my iPhone 4, the email address always defaults to ****@mac.com, when infact I need the email address to be @me.com. The @mac.com address is not actually an email, just the ID. The @me.com address was just setup after the release of iCloud, and is associated with the @mac.com ID. If I go to iCloud.com, I can sign in with either the @mac or the @me.com and both bring me to the same Apple ID @mac.com....man this is long winded..
So, how can I use iCloud with my iPhone if it defaults to a non-existant address and won't let me change it? Anyone else had this issue?

Ooops... Found this
https://discussions.apple.com/message/16561259#16561259

BT internet mail address - password reminder

We have two BTinterent emial addresses and keep getting endless reminders on the screen to re-enter our usermanes & password.
Im not sure why this is but how can I stop it once and for all?
Regards

I absolutely detest web mail as we have 1 BT main and 4 BT sub accounts and I use Windows Live Mail which isn't an insignificant Mail Client, with more than one email address it is difficult and time consuming to use web mail.
There must be millions of BT customers who use this software.
We regularly at some time in almost every day experience login problems when accessing our emails.
All the user names, passwords and settings etc. have not been changed.
So why oh why on earth cannot BT sort out their systems so they work properly.
I was advised to use ports 995 for incoming mail and 465 for out-going mail, this made absolutely no differnce at all.
Some days I have spent half a day waiting for important incoming mail to be received, it would almost have been quicker by Snail Mail.
BT get yor proverbial finger out please. You are one of the worlds largest communication businnesses but are one of the worst companies to be able to communicate with either on the phone by voice contact or the internet.

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&#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.

Login & password issues.

Is there a way to create one command or macro for entering my e-mail addresses, passwords, etc. so I don't have to type it in everytime?

Not advised. However, maybe you would like this utility.

[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

I can't remember my Apple ID password or my security question answers. When I try to reset my password it wants to send it to my e-mail address but I can't get the e-mail because I don't have security answers or the password. How do I reset password?

I can't remember my Apple ID password or my security question answers. When I try to reset my password it wants to send it to my e-mail address but I can't get the e-mail because I don't know my security answers or the password. How do I reset password?

Alternatives for Help Resetting Security Questions and/or Rescue Mail
     1. If you have a rescue email address or a Security Questions issue, then see:
         If you forgot the answers to your Apple ID security questions - Apple Support.
         Manage your Apple ID primary, rescue, alternate, and notification email addresses - Apple Support
     2. Fill out and submit this form. Select the topic, Account Security. You must
         have a Rescue Email to use this option.
     3. This is the only option if you do not already have a valid Rescue Email.
         These are telephone numbers for contacting Apple Support in your country.
         Apple ID- Contacting Apple for help with Apple ID account security. Select
         the appropriate country and call. Ask to speak to the Account Security Team.
     4. Account security issues almost always require you to speak directly to an
         Apple representative to securely establish your identity as the account holder.
         You can set it up so that Apple calls you, either immediately or at a time
         convenient to you.
            1. Go to www.apple.com/support.
            2. Choose Contact Support and click Contact Us.
            3. Choose Other Apple ID Topics and choose the appropriate topic for
                your issue.
            4. Follow the onscreen instructions.
         Note: If you have already forgotten your security questions, then you cannot
         set up a rescue email address in order to reset them. You must set up
         the rescue email address beforehand.
Your Apple ID: Manage My Apple ID.
                        Apple ID- All about Apple ID security questions.

New e-mail address, so created new apple id, iTunes store asks for password for old e-mail/apple id

There are lots of posts on this subject over the years about this problem but none of the solutions work for me.
Apple id problems go back many years, if they cant handle that, how do we trust them in security issues?
anyway, here is what it says.
Sign into iTunes store
Enter the Apple ID password for
"old e-mail address"
So I enter the password (same one as before, it works in Mail etc on the iPad, only a problem on iTunes store.
App updates would not work, but they finally did when I did a iPad reset and backup restore.
But the iTunes store apple id problem is still there.
I am a user of Apple since 1982, do not like where things are going, honestly, but they are the only game in town. Not a fan of overly automated system processes with no feeling of "transparency" in the way things happen these days.
Can anyone help? If not I will live with it, but..........this is not the old Apple any more.

It may not be called Express lane any longer, but this is where you find it now: https://getsupport.apple.com/GetproductgroupList.action
On your old email - Apple does not assume an email will not change. This is why they provide for recovery if you no longer have access to the email. In order for that to work however, you needed to have followed their recommendation and set up your security questions and/or provided a secondary email address. If you not longer have access, they you can try calling Apple and asking for the Account Security Team. If you can convince them you are who you say you are, they may be able to help reset your password.
Are you saying iTunes on your computer is updating all Apps? If so, I don't understand how. Apps purchased on your old Apple ID are able to be updated only using the Apple ID used to purchase or download them. If what you ar esaying is true, I suspect only thos apps tied to your new Apple ID are being checked and updated. If it is happening as you describe, your iPad is the one behaving as it should, not iTunes on your computer.
Please do not take offence to this but it still seems as if you don't understand how the Apple ID works, not just that you don't agree with it. I've refined my analogy a bit, so please bear with me. I am not trying to be condesending but I HAVE tried to made it as simple as possible for anyone else that may read this.
Imagine you buy a house. You have keys to the house and once inside, you buy all the funrniture you need - with one condition - because of some complicated distribution agreements with the furniture manufacturers, the seller mandates that the furniture you buy must be used only in that house.
Some day in the future, you lose the keys to your house so you buy the house next door with its own new set of keys. You go inside the new house and wonder where all your furniture has gone. Simply, you own both houses but
Upset at this situation, you try to recover your keys to your first house by asking the bank to mail them. You once had the chance to give the bank an alternate address to which they could mail keys but didn't so not they can only mail them to the first house. Since you can't get inside, you cannot retrieve the new keys that they send.
After getting some good advice, you decide to talk to visit the bank personally. You convince them you are the owner of house #1 and they give you a new set of keys. Yay!
You go back to house #1 and finally manage to get in. But, since house #2 is newer, you decide to live there. Now you want to move your furniture so you have a comfortable place to sit and sleep. Oops, you can't take the furniture from the old house because of your agreement with the Furniture seller so you have to buy new furniture.
House = Apple ID
Keys = Password
Furniture = Apps and other content purchased with the first Apple ID
Keys = Password
Alternate Address = Alternate Email Address
Furniture Seller = Apple
Furniture Makers = App Developers, Film and Music Rights Holders
You may not agree with this, but the fact is, Apple owns very little of the content they sell - basically only their own apps and iOS itself. Allowing merging of Apple IDs or transfering ownership of Apps from one Apple ID to another is a logistical nightmare and would create major issues with app developers, music and film rights holders and anyone else who provides content for sale through iTunes or the App Store.
You cannot compare a functioning iCloud with non-functioning iTunes and App Stores. iCloud doesn't care about your apps - it's about syncing and identification (iMessage, Facetime, iCloud services like Find My iDevice) only. So long as you are using the same Apple ID on each device, it will sync between them any supported content you decide. In fact you can use a different Apple ID for all there if you wanted. The key is to be CONSISTENT.
One additional thing we have not brought up already. If the iPad was activated with your original Apple ID and you ever need to restore it (not an uncommon possibility), you will run into a problem with Activation Lock. It's a security feature designed to discourage iDevice theft by rendering it useless if one tries to activate it using anything other than the Apple ID used to activate it originally.
Again, you may not agree with how it works, but I hope this finally makes sense and you at least understand how it works.

Since the upgrade, my Icloud account is picking up a former account name-e mail address I no longer have that address and cannot seem to be able to edit it to change it the password is always wrong, no matter what i try

since the upgrade, my I phone I cloud account is picking up my former e mail address/account name and I cannot access it because it keeps denying the passwords I try I no longer have that e mail address either I can access I cloud and I tunes on my laptop with the correct account name/password,but not my phone the i tunes account works fine on the phone--correct name--just not i cloud i tried changing it from my computer back to the old address then changing it to the new address and verifying by e mail but nothing happened

Hello there, Nana2054.
The following Knowledge Base article provides some great recommendations for resolving your issue:
iOS 7: If you're asked for the password to your previous Apple ID when signing out of iCloud
http://support.apple.com/kb/TS5223
This additional article can provide some assistance as well, if you are still getting an error message concering your password for that account:
iCloud: "Incorrect Apple ID or Password" alert when setting up iCloud after upgrading to iOS 7
http://support.apple.com/kb/TS5207
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

HT204053 I no longer have the e-mail address associated with the apple ID for iCloud. The password I have written for that account is deemed wrong, as is the security information (i.e. my birthdate). How do I eliminate this incorrect account and start a

I no longer have the e-mail address associated with an Apple ID. I do not know the password for that account, nor are the security questions correct (e.g. it asked my birth date, but, when I listed it, I was told it was not correct). I have no way to get into the program, to correct an information. How do I delete this account and start anew?

If you still have access to your old email address, go to https//appleid.apple.com, click Manage my Apple ID and sign in with your iCloud ID. Tap edit next to the primary email account, tap Edit, change it back to your old email account and verify it. Then edit the name of the account to change it back to your old email address. You can now use your current password to turn off Find My iPhone on your device. Then go to Settings>iCloud, tap Delete Account and choose Delete from My iDevice when prompted (your iCloud data will still be in iCloud). Next, go back to https//appleid.apple.com and change your primary email address and iCloud ID name back to the way it was. You can now go to Settings>iCloud and sign in with your correct iCloud ID and password.
If you don't have access to your old email address, you will have to contact Apple to have them reset the password so you can disable Find My iPhone and sign into your iCloud account. You can either go to https://expresslane.apple.com, select "More Products and Services", then "Apple ID", then on the next page select "Other Apple ID Topics", then "Lost or forgotten Apple ID password" and click "Continue"; or you can contact Apple Support (http://www.apple.com/support/icloud/contact/).

Can I use my existing E-mail address to retrieve my password reset through security questions

Can I use my existing E-mail address to retrieve my password reset through security questions instead of through E-mail. When I try retrieving my new Apple password through reset through security questions? On the Apple id, it will not allow me to do so becasue I forgot my security answers to the question. I'm naming one or two of the wrong vechiles which is what the questions ask me for for security questions.
For icloud do you reccommend that I keep that same E-mail address or create a new one for my iCloud mail aside from my G-mail address name?
I asked support community for the very first time to reset my security questions and it wanted me to create a new user name for iCloud when I already have *****l for my original Apple id.
<Email Edited By Host>

TheresaEW,
I’d recommend contacting Apple directly to resolve your security question issue.

HT4847 I had a previous e-mail address associated with my Apple Account. I change this, but Cloud did not update with the change. Now I can't log-in under the old I.D. and when I try to provide a password or get through by providing my BD it says it is

For some reason when trying to get ito Cloud, I can't get into my previous e-mail address to make changes, which I must do to delete it. Cloud does not recognize my old password and the system does not seem to associate my BD with it. I knowlonger have the old e-mail address associated with Cloud.
I have a new e-mail associate with my Apple account and a new password. The problem is trying to get Cloud to recognize my new I.D.

You have to delete the old account, provide the password for the old ID when prompted to turn off Find My iPhone, then sign back in with the ID you wish to use. If you don't know the password for your old ID, or if it isn't accepted, go to https//appleid.apple.com, click Manage my Apple ID and sign in with your current iCloud ID. Tap edit next to the primary email account, tap Edit, change it back to your old email address and save the change. Then edit the name of the account to change it back to your old email address. You can now use your current password to turn off Find My iPhone on your device, even though it prompts you for the password for your old account ID. Then go to Settings>iCloud, tap Delete Account and choose Delete from My iDevice when prompted (your iCloud data will still be in iCloud). Next, go back to https//appleid.apple.com and change your primary email address and iCloud ID name back to the way it was. Now you can go to Settings>iCloud and sign in with your current iCloud ID and password.

Issue with electronic mail address in profile

As a part of the conversion process, one of the electronic mail addresses I use was effectively 'burned in' to my profile. Clearly I can make it visible, or keep it hidden - but there is a problem. The public address I previously had listed for this purpose is not available - instead it's the private address that is displayed!
Think of it like this:
[email protected] [private address]
[email protected] [public address]
It was the public one previously visible - it's now the private one, currently set to hidden, which is the only one I can choose to display or hide. Can anything be done about this, or are we stuck with this 'converted' change to our profiles?

I appreciate the thought, and am sure that for some users this would be a sufficient tactic. Unfortunately, I have historically had issues with the interlocking but thoroughly unreliable process of changing ones basic identity at…
http://myinfo.apple.com
This is aggravated by the fact that I have four such identities - though I only use one here in Apple Discussions - with varying levels of access to ADC, GSX and other generally non-public areas at Apple. Managing them, including my .Mac ID, is at times a challenge, and I hesitate to do anything at all to upset the delicate balance. Unless the Discussions profiles revert to a primary private electronic mail address with a secondary optional 'public' address, I suppose I will just have to use the previously non-public address that became the sole available address following the conversion.
Thanks again for thinking about this, and offering a solution to the issue.

When i try to download an app and i have entered my password i am asked to add some security questions. I can add two questions and an alternative e-mail address, however it will not let me select the third security question.

when i try to download an app and i have entered my password i am asked to add three security questions. I can add two questions and an alternative e-mail address, however it will not let me select the third security question.

Thanks Liam. After the second ap download it asked me three security questions on iTunes and on my MAC it allowed me to set up these with no error on the third question. iPAD 3 now downloads apps fine.
Apple really need to sort out this issue or provide guidance on this. Two days of the unit not really being fit for purpose - what use is an IPAD without the ability to download aps.
Also NO Response from Apple via online tech support and it's now been nearly 24 hours - I was told by telephone support I would get a response within 24 hours or less, as also stated in the email response too!??
It would be good to get a formal response from Apple on this rather than radio silence.

Manage e-mail addresses - password issue

Similar Messages

Maybe you are looking for