NDR not being delivered for oversized mail

I work for a company that offers filtering and archiving services. One of our clients tried to send a mail internally which was over their mail size limit. The issue is that it is delivered to us (the external service), travels successfully through our filtering
system, and fails to be delivered back to the client's mail server. Logs show that our delivery servers attempted to transfer the mail, but the OutboundConnectionCommand sequence is EHLO, RSET, QUIT, with no reason for the transmission failure.
The mail item is not in our queue anymore and the sender received no NDR.
Do Exchange or IIS have some sort of function that would just remove the mail to prevent an indefinite replication of NDR's as a result of this mail being sent externally to and from the same mail server and being rejected repeatedly?

If you're not seeing a DATA or BDAT then the message wasn't sent.
If you're not seeing a MAIL FROM then Exchange (or any MTA) has no way of knowing the size of the message before receiving it (see DATA/BDAT above).
Given the absence of MAIL FROM/DATA/BDAT I think the message size is a red herring.
Why your MTA would think the message was delivered, in the absence of any evidence the message was sent, bears examination.
--- Rich Matheisen MCSE&I, Exchange MVP

Similar Messages

HT4061 Emails not being delivered via mac mail - recipients claim not receiving

A colleague and I have discovered over last 2 weeks issues with mac mail.
Emails are not being received - but it appears to be RANDOM.
We both use mac mail and have .me accounts.
He sent a group email that I never received until 3 days later when another colleague NOT on mac mail replied to all and I saw that I never received original note.
This colleague sent email to his attorney weeks ago -- and it was just delivered to his attorney's inbox YESTERDAY.
The colleague has also send me a several SENSITIVE correspondences that he confirmed via phone last night that I have still NOT received.
What is going on? is is a mac mail issue or an iCloud issue?
Need some help to get this reported and resolved.
thank you!

bingo123 wrote:
sorry gg30340 , Yes webmail works fine and I can receive from Outlook fine, just sent emails seems to disappear into a black hole from Outlook
Hi. Welcome to the forums.
For info, CP (Critical Path) has been in use for a few months now for the conversion from using Yahoo! mail servers.
What version of Outlook are you using ?
In the smtp setting, try removing @btinternet.com or @btopenworld.com from the username - despite what the online help might say.
You might like to try port 25, with No security or SSL/TLS setting.
Is it all emails that are failing to send ?
If emails have been fine for years, do you know what the previous settings were ?
As for disabling firewalls - this doesn't always help - as they can still block emails! What security package are you using, and have you checked the settings within that package ?
Sorry for the extra questions.
http://www.andyweb.co.uk/shortcuts
http://www.andyweb.co.uk/pictures

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.

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.

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?

Is anyone having issues with imessages disappearing or not being delivered?

Is anyone having issues with imessages disappearing or not being delivered?

I too am experiencing this on my iPhone 4 after upgrading to 4.3.3. I am fairly convinced that it is a software issue. The last update seems jumpy. There appear to be more pauses and stuttering with screen changes too. Sometime the button operates perfectely (even with repeated light touches). Other times, it doesn't matter how hard I press; it takes several presses. I notice it more when i am using a battery case or connected to an AT&T MicroCell. I am having a hard time pinpointing problematic apps, although i suspect that mail with my work Exchange account may be a culprit. I suggest posting your issues on Apple's iPhone feedback page, www.apple.com/feedback/iPhone.html, to ensure that they are looking into this problem. If it is a hardware issue, I'll be pretty upset as I received my iPhone 4 on day 1 of availability and it is out of warranty. Hoping for a fix with an update. Please post on the feedback page.

Sent emails not being delivered from Outlook

For the past week emails sent from Outlook although appearing in my Sent mailbox are not being delivered. This is not a problem where emails are sent from my iphone. I have made no settings changes. This seems to be a familiar problem but research has not produced a solution as most people give up.
I am using a Windows 8 laptop with Outlook 2013. I have set up numerous new accounts with automated settings with no success.
Please help!!

I too knowingly have had this problem since at least 19/1/2015.
I have Windows 7 with Outlook 2013 and two BT accounts plus Sky and Google accounts (for fallback). All have functioned well for the past three years.
No changes to my PC have been made for at least 6 months (apart from MS updates).
My wife's laptop runs Windows 7 with Outlook 2010 and has found the same issue. At a Womens Instutute meeting last night in the village it became apparent (without my wife initiating the issue) that a number of other BT eMail account customers have the same problem too.
I spent about an hour yesterday trying various combinations of operation to confirm the issues. I have found:
1 - eMails sent from either BT account self addressed will bounce back the eMails (presumably from the BT Server)
2 - eMails sent from either BT account to BT accounts will not forward (send/deliver)
3 - eMails sent from either BT account to non BT addresses will not forward (but will bounce back if the self address is included in the addresses showing that at least the eMail is reaching the BT mail server).
4 - eMails sent from Outlook through Sky and Google systems are being received by the BT system and recieved into the Outlook BT accounts.
5 - All eMails sent in Outlook appear in the Sent box
6 - eMails sent from Webmail accounts all work normally
All these tests can be replicated on my wife's laptop with other BT and non-BT addresses.
I then spent about an hour whilst a BT Technician (ABHISHEK SEN) through CHAT accessed my PC, checked all settings and declared no fault found.
Later I spent another hour on the phone to the BT Help Desk (with VIKRAM) who did much of the same, declared that there was a problem and that I would have to hire a local PC expert technician to come and sort out the problem on my PC. He would not acknowledge that there just might be a problem with the BT eMail Server system.
Finally the only common thread is that the BT accounts are sub-accounts of my main account and that I pay the bills - and of course the router and copper lines to the exchange.
HOW OR WHERE DO I/WE RAISE THIS ISSUE WITH A HIGHER AUTHORITY TO GET IT RESOLVED?
Oh! And then there is the rest of the village and gwood's machine also need to have their similar issue resolved too.
To use gwood's last paragraph: PLEASE HELP!!

Unity 9.1.2 - VM not being delivered to Outlook

Hello All,
VM is not being delivered to user's Outlook, when anyone tries to leave a message it disappears in a couple of minutes and does not get delivered to Outlook, message count from Unity Admin page shows 0. If Unified Messaging is disabled the messages don’t disappear.
Unity Connection version 9, if anyone encountered this issue or has any ideas please let me know.
Thanks,
AK

If they don't disappear when UM is disabled I would suspect that the outlook client is deleting them or sending them to junk mail. I had a situation once where I had to change the default smtp domain from @ to @company.com in order for the Exchange/Outlook powers NOT to junk the voicemail. I also has the side effect of allowing the users to reply to the VM messages using the Outlook client, so it was a win-win.
you could also change the Exchange policy, never tried this.
http://www.cisco.com/c/en/us/products/collateral/unified-communications/unity-connection/guide_c07-728014.pdf
disclaimer to consider though
https://supportforums.cisco.com/docs/DOC-16892
Kasey

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

Text send to email address not being delivered

Can anyone tell me why texts sent from my iphone 4 to my home email address are not being delivered? I like to send reminders of things I need to do from my phone to my email address. Have always been able to do this from other phones I've had but not now with this iphone 4. It saying they were sent but they never show up in my inbox or any other box.

longlostname wrote:
If my reply is being sent as an SMS, what is to prevent the new message from being sent as an SMS?
What prevents the new message being sent as an SMS is that your actually sending an email -- not an SMS, when you initiate a [email protected], that is an email, not an SMS.
longlostname wrote:
And are you aware of a way to send messages of any type to an email address from this model phone without having to have a data plan
Nope, you don't have the data plan. Sorta like refusing to install a trailer hitch on your truck, and then wondering why you can't pull a trailer behind.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Email not being delivered

I am trying to send email from the icloud web mail. all email is not being delivered. When I send from iphone or ipad all works fine. Icloud webmail can receive mail normally. Email does show up in the sent mail folder but is not being delivered.

I repeatedly and randomly have the same problem:
1.   I send mail to another icloud user or to some other recipient (e.g., yahoo mail).
2.   The sent message appears in my iCloud.com Sent folder signifying that it was transmitted successfully.
3.   The message is never delivered.
4.   It does not appear in the recipient's Spam folder (or any other filter).
5.   I never receive followup email from any server's postmaster indicating an error in transmission or reception.
6.   The whole experience is purely silent -- "went to the bit bucket."
There is no rhyme or reason to this.   The phenomenon is random but has repeated over a series of many months.   I could say that I am running 10.8.5, but it is an iCloud server event, not a local OS event.   The recipient might be running OS X, Linux, or Windows (etc).

After 1.1.1 update, image emails not being delivered

just upgraded to the latest patch (1.1.1). Sending images) as email are not being delivered. I am using Yahoo for email. Anyone else see this?

I've just switched SIM cards with someone else who is on P&G o2 and has an IPhone 5 running 6.1.2. My sim in their phone still won't send texts to the problem number yet their sim in my phone will? Think it might be a network issue?

All of a sudden my emails are not being delivered to my ...

all of a sudden my emails are not being delivered to my cell phone

Hi there!
There is an outage for some BIS users...see this article:
http://www.dataoutagenews.com/2009/09/22/bis-down-in-north-america-again/
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

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

NDR not being delivered for oversized mail

Similar Messages

Maybe you are looking for