No SMSs being delivered on Nokia 1650

Hi,
I have two friends in India in the same city, both of them use mobile connection with the same IDEA network. One of them is able to receive my sms messages which I'm sending from the UK and the other one is not able to receive any messages and the delivery report I receive is 'Failed', the friend who can't receive SMSs is using Nokia model 1650.
Hence I'm wondering if there is any setting in the handset which may prevent the messages from being delivered??
Any help around this will really be appreciated and welcome.
Regards,

Hi,
it cud be possible by ur service provider as i faced the same pb in the same country.. use 00 before country code before sending any msgs.. instead of using +
e.g. when u reply to any msg the number will be like
+9133333333(dun use this)
use this 0091333333
try ths.. it mite be helpful f0r u .. and comments..

Similar Messages

Emails are only being delivered to the WebOutlook inbox and not my desktop outlook

1. Big Problem: How do I get emails sent to my primary email address (name @ wealthblush dot com hosted by Go Daddy) to go to both the
Outlook Web App inbox AND the inbox of my desktop Outlook 2013? They only go to
Outlook Web App and not my desktop Outlook 2013.
How is the email account configured in Outlook (POP3, IMAP or Exchange):
POP/SMTP is for the user @ wealthblush dot com - this is the one where the email ONLY goes to the Outlook Web App, but not into Desktop Outlook 2013.
IMAP/SMTP is for the user @ charter dot net email. Emails go to both clients, but if I delete on one client it is not deleted on the other.
Exchange/ActiveSync is the outlook.com email and it only goes to my desktop Outlook.
I'm not getting any error messages. Mail is being delivered to the user @ wealthblush dot com, but only to Outlook Web App and NOT my desktop Outlook.
2. How can I change the inbox an email account puts incoming emails into? I read somewhere the way to do this is to create a search folder? This question is actually in advance of fixing
question number 1 above.
3. I don't know how I should configure my emails with the new Outlook 2013 now being in the cloud:
- I have an @ outlook dot com email I setup when MS came out with the free outlook dot com (hotmail), but I never used it because the reminders didn't work the same as in desktop outlook (not being able to snooze for a few hours
or days or weeks if I remember right and the way we get the alerts too).
- I also have an email with my ISP (@ charter dot net) which is a mix of personal and business emails. I've had this account for over 10 years.
- Finally, I have a business website (www dot wealthblush dot com) hosted by GoDaddy with one real email @ wealthblush dot com. I've already setup the aliases for several other emails in my new office 365 account (support,
sales, webmaster at wealthblush dot com) which are configured to pass into specific folders using Outlook 2013 Rules in my desktop outlook. I'm not sure if those rules are replicated into the office 365 account.
I still want the aliases to go into those folders like before.
4. In the case of my outlook.com email, they do go to both inboxes (on the web and desktop), but when I delete an email from one place, shouldn't it get deleted in the other place as well? How do I get them to synch?
5. And then there's my existing .pst files. I have 4 of them with old emails I've saved over the years that takes up just over one GB. I save these .pst files to DVD everyday so I can go back to look at something if I need to (and for hard drive
crashes). Does MS want me to import all that stuff to their servers and get rid of my .pst files? Does MS want me to put everything into one .pst file? It seems like it? If I do then I assume things need to be synchronized all the time between my file and
your .pst file? The synchronization process is as close as you can get to real-time, right? Or does each individual change get sent as it happens?
6. I also have a skydrive account from a while ago too. Is this where I should put my documents so they're accessible when I'm not at my desk? Now, that would be a LOT of data (probably close to 80 GB). Or, is the intention for us users
to only put certain current docs in this area. I assume these files can be synced with my desktop too, right? But I don't know how to. Do you keep old versions of the files in skydrive so we can recover them? I want to know if I can use your service to hold
my files (they would ONLY exist on your system and you'll back them up and I can get old versions back when needed).
7. Is an option to keep everything on my desktop 2013 like I did in 2010 of Outlook, bypassing the cloud and MS mail servers all together?
Sorry about all the questions, but I'm just getting the feel for your approach and need to decide how this all should fit together, do it, then go back to my business. I'm by myself at my company right now, but I'm planning on hiring a few people
real soon too so I need to keep this in mind. I've worked with Outlook since it came out, and I've configured it, but mainly only for myself and my family.

R1: Seems you didn't configure you email account in your Outlook client properly. please refer to the following KB article and try to create a new mail profile to configure your email account again:
http://support.microsoft.com/kb/2758902
R2: Do you want create subfolders under Inbox to category your emails? If so, we can just right click on Inbox > select New Folder... After that, we need to create rules to move or copy your emails to each subfoler. See:
http://office.microsoft.com/en-us/outlook-help/manage-email-messages-by-using-rules-HA010355682.aspx
Besides, in order to avoid confusion and keep track of troubleshooting steps, we usually troubleshoot one issue per thread in order to find a resolution efficiently. Concerning your other question, I suggest we create new posts for your other questions via:
http://social.technet.microsoft.com/Forums/en-US/home?forum=outlook
Thanks for the understanding.
Steve Fan
TechNet Community Support

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see 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,
#       mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in
#   the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

My 4S has stopped ringing. Voicemail's disabled but if you call me, you'll hear it ring your end but it does nothing at mine and freezes if I make a call. Texts are not being delivered or coming through delayed. Ringer is on, tone enabled - help!

My iPhone 4S has stopped ringing altogether. Voicemail is disabled but if you call me, you'll hear it ringing at your end but it does nothing my end and freezes in the phone app if I make a call (doesn't ring or connect and doesn't freeze the phone, just the calling part). Texts are not being delivered or coming through delayed. Ringer is on, tone enabled - help!
I've disabled roaming so it only runs on wifi (this after getting a £4k phone bill...) and I can use Skype, Viber and WhatsApp with no problem at all.
Would really appreciate any help at all!
Many thanks.

Hi there - am with Orange and they said nothing wrong with account and service running normally. They said if they had cut me off I would've received a text (debatable with current message receiving situation!) and when I called out it would say 'calls from this number are barred'. Also if you called me it would say something similar. But it doesn't, it will ring and ring until it rings off but nothing happens at all on my handset. Not even a missed call notification. If I call out, it will display that it is calling the number but that's it. If I cancel the call it will constantly display 'ending call'. If I come out of the phone and go to another app then revist phone it will start calling that last dialled number - without ever getting as far as ringing or connecting.

Pictures are not being delivered after saying delivered on iMessage.

Pictures are not being delivered after saying delivered on iMessage.
Txting through iMessage works fine. Pic's won't send.
I turned on and off everything and did all the necessary trouble shooting.
I'm on a Verizon 4S. and I'm sure Verizon has nothing to do with iMessage system, since it's on its on server.

bump

When I send a message using iMessage to a contact's email, the message (whether independent or to a group) is being delivered in their email inbox instead of their iMessage application.

When I send a message using iMessage to a contact's email, the message (whether independent or to a group) is being delivered in their email inbox instead of their iMessage application.
Is there any resolution to this issue?

Yes, they are registered for iMessage and IOS 5.0.1 update. A few days ago (10-12 days) the group messaging was working fine, but now the messages are being delivered to the email inox instead of iMessage app.

E-mail not being delivered - AGAIN!!!

This *****!!! You guys are really ruining my e-mail ability...since I do pay for this service!!! Stop blocking my e-mail! I'm really ******!!!!
This is the second week my e-mail has been rejected by the server and I've not been able to finish sending out my mail to people. I organize a class reunion. I e-mail about 200 people once a week. For some reason there was a change to a setting somewhere along the line and 2 weeks ago my mail stopped being delivered. I stated in my last contact that I would switch to a free service that would allow me to send my mail. I don't use all the .Mac services and I can get web space much cheaper.
Either fix this or consider me (a member for 4+ years) cancelled. I don't have time to write to you guys every week about this. Did I mention I was ******?
[email protected]
It's not like I am sending out huge files or something like that. See below.
This is what I am sending.
Hello Class of 1992,
Okay, you can stop waiting now. You've got to make your move and send in your money for tickets. Get them before the May 15 deadline and save yourself $40 dollars!
I've heard from so many of you over the past 5 years of working on this project and there has been a great deal of interest over this period of time. So...here we are...it's almost happening and you need a ticket to get in the door.
We had a meeting this weekend in the space rented for the 15 year reunion and we've got such a great location chosen for you guys. We'll be right on the beach which we have access to during the day for those who want to show up with coolers and beach chairs to relax, meet and greet. Bring your kids, spouses and spirit of fun to the afternoon beach time.
You are going to have a great time during the evening. We've got plenty of food available, drinks, music and how many reunions do you know of that have a tower to overlook the entire beach at their disposal?
It's gonna be awesome! And guess what...YOU ARE INVITED!!!
Get your ticket ordered early....save some $$$ and start off your summer right with old friends, fantastic times and new memories.
For a single person it's only $85.00 dollars. If you bring your spouse or date; only $125.00 per couple. And heck, if you've got anyone else you'd like to bring it's only $45.00 for each additional person. You can't beat it for an awesome time.
Make your check payable to Bill (Billy) Owens (Reunion Treasurer).
Mail to:
3765 Silina Drive
Virginia Beach, VA 23452
See you on June 16!
www.kempsville1992.com

Parsing through your rant which isn't directed at Apple, it seems you might be exceeding the sending limits included with a .Mac account which are not extreme by any means so take a deep breath and calm down.
All internet service providers and email account providers (even free ones) have sending limits or restrictions for non-business/personal email accounts.
These restrictions are in place as part of an overall effort to prevent spam emanating from an ISP's or email account provider's domain. In case you aren't aware, spammers make use of bulk spam mailings and these restrictions make it more difficult for a spammer to do his thing.
It makes no difference that you aren't a spammer or the content of your message is not spam since there is no way an ISP or email account provider can make this determination when you send a message but they can impose sending limits or restrictions.
Copied from the following link.
http://docs.info.apple.com/article.html?artnum=25301
.Mac has several safeguards in place to ensure that only .Mac members send messages with the Mac.com outgoing mail server. Among them are reasonable limitations on:
* The number of messages that can be sent each day (200 messages)
* The number of recipients that can be sent to each day (400 recipients)
* The number of recipients a message can be addressed to at one time (100 recipients)
* The size of outgoing messages
There is also a 10 MB maximum size for messages sent or received using the .Mac mail system.
.Mac Email has been designed primarily for personal use. Sending unsolicited bulk email messages through the .Mac email server is prohibited.
If your message is being rejected by a recipient's incoming mail server, what is the return email error message provided which is sent by the recipient's incoming mail server?
Regardless, this problem is with the recipient's email account provider. If the return email error message from the recipient's incoming mail server indicates the recipient has exceeded their allocated server storage space, this the recipient's problem.
So instead of ranting, how about providing more detailed information about the error message provided so someone here can help narrow down where the problem lies so you can direct your efforts there.
IMO - since you use your .Mac account for email only, you should cancel your account but keep in mind that even a "free" service includes sending restrictions which may not be identical to .Mac account restrictions but none are restriction free.

Messages with zip files or multiple attachments are not being delivered

Has anyone else come across this? I've discovered that files sent from my .mac account are not being delivered if they contain zip files or multiple attachment. A single .docx file goes through, but multiple doc files or a single zip file do not.
I get no error message, and neither does the recipient. The message sends on my end but simply doesn't show up on their end.
Any thoughts on what might be causing this?

Another follow-up: Now, for whatever reason, even attachments of a single document aren't going through.
Again, I'm receiving no error message, and it shows up in my sent folder. It just never makes it to the recipient.
This is very frustrating, and makes my iCloud mail account all but useless. Does anyone have any idea at all what might be happening?

HT3728 my broadband speed has all of a sudden been reduced dramatically over the weekend. the isp asked me to eliminate my apple airport express base station to make sure that my 20mb band is being delivered which i did and confirmed so.

MY BROADBAND HAS BEEN REDUCED DRAMATICALLY IN MY HOME NETWORK USING MY AIRPORT EXTREME BASE STATION.
THIS HAPPENED SO UNEXPECTEDLY OVER THE WEEKEND. I CALL MY ISP AND THEY SIMPLY TOLD ME TO ELIMINATE THE AIRPORT
EXTREME BASE STATION TO CONFIRM THAT WHAT I HAVE PURCHASED IS BEING DELIVERED WHICH I DID AND CONFIRMED.
MEANWHILE USING MY NETWORK UNTIL LAST FRIDAY EVERYTHING LOOKED JUST GREAT.
I WONDER WHETHER I WOULD HAVE TO RESET MY AIRPORT EXTREME TO FACTORY SETTINGS TO RECONFIGURE IT.

Hmm. Your ISP is incorrect in telling you that removing any of your routers on the local area network will have anything to do with the bandwidth performance that they provide you at the Internet modem. On the other hand, changing/removing networking equipment on your local network DOES affect bandwidth performance on that local network.
Most likely what the ISP is asking you to do is verify that you are getting their promised download/upload bandwidth at the modem. It appears that you did that and verified that you are getting the stated bandwidth.
So, we should take a look at why, when adding the AirPort Extreme, you are getting less.
First off, which AirPort Extreme model do you have? What is the make & model of the broadband modem that your ISP is providing you?
It is always a good idea to perform a complete power recycle of your networking equipment when introducing new hardware. Please check out the following AirPort User Tip for details.
(p.s. Please don't use all capital letters when you post. It appears to readers that you are shouting. Thx!)

Messages in queue not being delivered

Hi
I am using IMS 5.2. After a recent migration of user accounts to an new login ID, some user's emails are not being delivered to thier accounts and are accumulating in the ims-ms queue. When I did the migration, I copied the user's email to thier new account. I did reconstruct -f -r a couple of times, and emails appeared to be delivered to the new login accounts.
There were a few emails left in the queue but now there are close to 6000 and users are not getting emails delivered. When I look at the message in the queue, they state the user is overquota. I checked the user's account and they are not overquota.
Any suggestions on how to correct the problem or get the message to be delivered?
Thanks
Randy

Jay,
iPlanet Messaging Server 5.2 (built Feb 21 2002)
libimta.so 5.2 (built 15:07:23, Feb 21 2002)
SunOS cpmail 5.8 Generic_108528-27 sun4u sparc
SUNW,Ultra-60
This is the original release. There have been over thirty patch/hotfix releases, and hundreds of fixes. I URGE you to go to Sun's download site, and get 5.2p2, and install it immediately.Thanks for the advice Jay. The product is installed as part of the portal we are using(which I upgraded last June). I was unaware of the versioning and patches that are associated with the version of IMS that was installed. I will move forward with confirming with our portal vendor that the latest sp and patches will support the integrated IMS.
>>
>>
How did you "migrate" your users to new login id?When you "copied" the files, did you re-set
ownership/permisions of the files?
I used the following process in a script to migrate
the users from old login to new login:
1. created the new login mailbox with mboxutil -c
2. moved new mailbox to different partitions
There is a utility/command that does all of this for you.
mboxutil -r
When you "moved" the mailbox, I assume you use unix cp, right? Bad Idea.
current versions of mboxutil do this all for you, and don't need reconstruct afterwards.
I suspect that you have either not properly "moved" your user in LDAP, folder database, or have gotten file ownership or permissions wrong after the move.
Unix files are owned by a user and group, and have various read/write permissions set by the OS. YOu're on a Unix system, so you should know about such.I tried using the mboxutil -r initially but was getting a lot of errors with it in my test environment. In hindsight, I am thinking this had to do with the version of IMS I have installed. The unix file move was done with the IMS admin so would also own all the the messages etc on the OS side. I have obviously made a mess of things! So again, I will put in a support call to our portal vendor about how to proceed on this. I really appreciate your input into this.
3. retrieved hashed directory information for old and
new mailbox for user
4. copied files from old to new mailbox with cp -R
oldmailbox/* newmailbox/
5. after all users were migrated, I did a reconstruct
-f -r, and a reconstruct -f -m
I am not sure what you mean by re-set
ownership/permissions.
Have you looked at the "default" log for an errormessage?
I found the following errors in the default log:
default.60.1093908097:[31/Aug/2004:04:15:01 -0600]
cpmail stored[28697]: Store Critical: Error checking
mailbox database: Ignoring log file:
/usr/iplanet/ims52/msg-cpmail/store/mboxlist/log.00000
00543: magic number 0, not 40988
default.62.1094084554:[02/Sep/2004:04:15:02 -0600]
cpmail stored[20883]: Store Critical: Error checking
mailbox database: Ignoring log file:
/usr/iplanet/ims52/msg-cpmail/store/mboxlist/log.00000
00543: magic number 0, not 40988
Your reconstruct command may have been wrong, too. That's what the errors are telling you.
Also, there are other problems in your system. Permission problems, most likely.
I would do a reconstruct -m, first. and see if the above goes away.I will proceed with what you suggested, and let you know the results. Again, thank you very much for your time and input for this.
>>
>>
AS well, when I do a mboxutil -u on an affected user,
the quota information says the user is well under
quota. For example:
$ mboxutil -u xxxxxxxxx
diskquota size(K) %use msgquota msgs %use user
25600 2604 10% no quota 19
19 xxxxxxxxxxx
The error message doesn't really have anything todo with quota.>>
>>
In imta/queue/ims-ms, the user has 183 messages
waiting to be delivered. All of the messages say the
user is over quota.
Any suggestions?
Randy, you need to re-think how you're moving users. You have somewhat messed up your mailstore. . . I will in re-think things. In fact, I have a number of users to migrate. I will stop what I am doing and get this right before I proceed! There is no sense compounding the problem when there is a better alternative. One thing for sure, I will continue using this forum before I proceed with messing with a production system!
You may need to contact tech support for the immediate help you will need to straighten this all out.>>
>>
RandyThanks Jay.
Randy

Outgoing mails are either being rejected or not being delivered - Exchange 2010

Mails sent out to some domains not being delivered or being rejected;
Receiving different errors as below:
1.
B6.7host.com rejected your message to the following e-mail addresses:
'[email protected]' ([email protected]) <mailto:[email protected]>
B6.7host.com gave this error:
unknown user <[email protected]>
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: exchsrv.mydomain.com
[email protected]
B6.7host.com #550 unknown user <[email protected]> ##
====================================================================================
2.
Diagnostic information for administrators:
Generating server: exchsrv.mydomain.com
[email protected]
#554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##
[email protected]
#554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##
[email protected]
#554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##
======================================================================================
3. --9B095B5ADSN=_01CF0B73B41F3F480004B263dub0?omc1?s26.du
Content-Type: message/delivery-status
Reporting-MTA: dns;dub0-omc1-s26.dub0.hotmail.com
Received-From-MTA: dns;DUB127-W1
Arrival-Date: Mon, 27 Jan 2014 03:18:13 -0800
Final-Recipient: rfc822;[email protected]
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;550 #5.1.0 Address rejected.
==========================================================
For No. 2, I m seeing that the DNS name is not resolving. How can I be sure this issue is not from my side ?
For No. 3, It seems to be some problem from that domain itself, and even mails from outlook.com are being rejected.
Is there any best practice that I am missing out on ?
How can these issues be resolved ?

MX record of ju.ahg.com.sa seems to work via SMTP testing.
This was useing the MXtoolbox site.
Connecting to 78.93.11.251
220 [874 ms]
EHLO MXTB-PWS3.mxtoolbox.com
250-S-34-8.AHGJU.COM.SA Hello [64.20.227.133]
250-SIZE
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-XXXXXXXA
250-XXXXXXXXXXXXXB
250-AUTH NTLM
250-XXXXXXXXXXXXXXXXXC
250-8BITMIME
250-BINARYMIME
250-XXXXXXXD
250-XXXXXXE
250-XXXXF
250 XXXXXXG [858 ms]
MAIL FROM: <[email protected]>
250 2.1.0 Sender OK [858 ms]
RCPT TO: <[email protected]>
550 5.7.1 Unable to relay [5897 ms]
MXTB-PWS3v2 10390ms
Seems to be ok, sent a test message to [email protected]
and it seems to have gone through from were I am.
Check your Exchange Servers DNS settings.
Also, please let me know if you have a Edge server setup OR have your SMTP connect setup to use Smart Hosting.

My text messages are not being delivered

MY text messages are not being delivered. Keep coming back with the red saying "Not Delivered". Anyone know why this all of a sudden started happening and how to fix it?

Thank You Meg St._Clair contacted my carrier and fixed the problem on my iPhone 6 but still an issue on my iPad mini
Carrier could not fix the problem so said I would have to plug my iPad into my Mac and back it up and then restore factory settings
Havent done any of that yet!

IMessage saying messages are not being delivered... but they are...

This past week I have been sending out texts on imessage, but about 80% of them are coming back saying they aren't being delivered. But everyone seems to be getting them and responding. They also have said the same thing happens to them. I thought it might be a wifi issue and that I'm going through a work wifi, but it happens even when I'm on LTE. Any ideas as to why this is happening?

I've been having the same issue for the past couple of days too. It first says "Delivered" then changes to "Not Delivered", even though (at least most of the time) the messages seem to be going through. Only started happening to me on the weekend. Doesn't seem to make a difference if I'm using wifi or the 3G network. iMessage is only enabled on my iPhone. I've tried switching iMessage off and then on again as per some suggestions. Nothing seems to help.

Text messages are not being delivered from iPhone 4s

Why aren't my messages being delivered from my iPhone 4S?

Thank You Meg St._Clair contacted my carrier and fixed the problem on my iPhone 6 but still an issue on my iPad mini
Carrier could not fix the problem so said I would have to plug my iPad into my Mac and back it up and then restore factory settings
Havent done any of that yet!

Nokia 1650 troubleshooting help needed

I have a Nokia 1650. I turned my phone off as usual when I went to bed last night and this morning it would not turn on again. The screen wont light up but I can see ' Local mode' written on the screen. I have tried usual stuff like taking out the battery and the sim card and re -introducing them but it doesn't make any difference! Any ideas?

I will suggest you a quick and easy fix for you mate.
1. Back up you important stuff on the nokia suite
2. Hard reset , wipe everything off your nokia e7
3. Run it a few days without any third party apps and see how it goes.
4. Symbian belle is available now, you should check with your latest nokia suite. If its not then maybe your country is not ready for the update.
HOPE THIS HELPS
Join my movement to bring a change in NOKIA for good by supporting my FORUM
http://discussions.europe.nokia.com/t5/Eseries-and-Communicators/NOKIA-MODERATORS-ONLY/td-p/1318965

No SMSs being delivered on Nokia 1650

Similar Messages

Maybe you are looking for