CL_SMTP_RESPONSE error in CRM mail delivery

Hi,
We have problems with mail delivery in our CRM .
The error is:
Error interno: CL_SMTP_RESPONSE Código de error ESMTP desconocido 554
554 SPAM-Relay detected
Nº mensaje: XS829
Please, what to do?
Manuel

Hi,
Error "554 SPAM-Relay detected" comes from your mailserver, hence please check your mail server configuration.
"Error interno: CL_SMTP_RESPONSE Código de error ESMTP desconocido 554"
This comes because 554 is not expected as a status for this problem, so the SAP processing gives "Código de error desconocido", that is "code unknown".
Br,
Javier

Similar Messages

TS4002 Hello, icloud receive messages from gilly hicks, but does not receive messages from another personal account... this is happening me since one week and i dont know how to solve this.... error in the mail delivery system says not valid IPv4 SMTP err

Hello, icloud receive messages from gilly hicks, but does not receive messages from another personal account... this is happening me since one week and i dont know how to solve this.... error in the mail delivery system says not valid IPv4
SMTP error from remote mail server after RCPT TO:<[email protected]>:
host mx6.me.com.akadns.net [17.158.8.114]: 550 5.7.0 Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=184.173.9.56:
[email protected]
i do alse receive from gmail....
please help... what is happening!!!!

Just to recap, this is a collection of ports I have collected over time for people who needed this information when setting up the HP ePrint app so that they could view their email from within the app. I am certain other applications also need this information. Although lengthy, I could not find a more comprehensive place to retrieve this information. Feel free to post additional information, faulty information, or other related topics below as this is simply a collection of data and it would be practically impossible to test all of them. Thank you!
Don't forgot to say thanks by giving "Kudos" if I helped solve your problem.
When a solution is found please mark the post that solves your issue.
Every problem has a solution!

Mail Delivery System Errors and Securing/Protecting agains spam

Good morning all.
This morning I started recieving these:
          From: Mail Delivery System <[email protected]>
          Subject: [It] Postfix SMTP server: errors from imr-mb02.mx.aol.com[64.12.207.163]
          Date: November 18, 2011 8:51:23 AM EST
          To: Postmaster <[email protected]>
Transcript of session follows.
Out: 220 mail.cotaoil.com ESMTP Postfix
In: EHLO imr-mb02.mx.aol.com
Out: 250-mail.cotaoil.com
Out: 250-PIPELINING
Out: 250-SIZE
Out: 250-VRFY
Out: 250-ETRN
Out: 250-AUTH LOGIN PLAIN CRAM-MD5 GSSAPI
Out: 250-AUTH=LOGIN PLAIN CRAM-MD5 GSSAPI
Out: 250-STARTTLS
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL From:<[email protected]> SIZE=3485
Out: 250 2.1.0 Ok
In: RCPT To:<[email protected]> ORCPT=rfc822;[email protected]
Out: 451 4.3.5 Server configuration error
In: DATA
Out: 554 5.5.1 Error: no valid recipients
In: RSET
Out: 250 2.0.0 Ok
In: QUIT
Out: 221 2.0.0 Bye
How this started:
Over the past couple of days to approx a week, I have seen a massive influx of Spam on our server. Spam coming in on random ex employee names that no longer work for the company.
Previous to the spam, I turned on "forward un-deliverable mail to" and set to me. The CEO was missing emails because people were not spelling his name correctly. I have actually been able tyo catch a lot of employee emails some important, others not.
In trying to make the mail server more secure, one of the features I tried to turn on was SMTP Client Restrictions, Which broke SMTP for my users. Obviously the error is mine and I need to do more research, but love some feedback on what needs to be set on the server and clients for SMTP client restrictions to work.
I know THE HOFF (mr hoffman) had information at some point to help users secure postfix, can anyone point me in the right direction, as well as any tips here on how to stop the influx of spam?
pstconf -n is here:
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
biff = no
body_checks = regexp:/etc/postfix/body_checks
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
enable_server_options = yes
header_checks = pcre:/etc/postfix/custom_header_checks
html_directory = /usr/share/doc/postfix/html
inet_interfaces = all
local_recipient_maps =
mail_owner = _postfix
mailbox_size_limit = 0
mailbox_transport = dovecot
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maps_rbl_domains =
maximal_queue_lifetime = 2d
message_size_limit = 0
mydestination = $myhostname, localhost.$mydomain, localhost, mail.cotaoil.com, cotaoil.com, $mydomain
mydomain = mail.cotaoil.com
mydomain_fallback = localhost
myhostname = mail.cotaoil.com
mynetworks = 127.0.0.0/8,192.1.1.10,192.1.1.11
newaliases_path = /usr/bin/newaliases
owner_request_special = no
queue_directory = /private/var/spool/imap/dovecot/mail
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtp_sasl_password_maps =
smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated hash:/etc/postfix/smtpdreject cidr:/etc/postfix/smtpdreject.cidr reject_rbl_client zen.spamhaus.org permit
smtpd_enforce_tls = no
smtpd_helo_required = yes
smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
smtpd_pw_server_security_options = cram-md5,gssapi,login,plain
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks   reject_unknown_recipient_domain reject_unknown_sender_domain reject_invalid_hostname reject_unauth_destination check_policy_service unix:private/policy permit
smtpd_sasl_auth_enable = yes
smtpd_tls_CAfile = /etc/certificates/mail.cotaoil.com.8F44026B8E7E908CEDAAD718F486D91C8FCD693E.cha in.pem
smtpd_tls_cert_file = /etc/certificates/mail.cotaoil.com.8F44026B8E7E908CEDAAD718F486D91C8FCD693E.cer t.pem
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
smtpd_tls_key_file = /etc/certificates/mail.cotaoil.com.8F44026B8E7E908CEDAAD718F486D91C8FCD693E.key .pem
smtpd_tls_loglevel = 0
smtpd_use_pw_server = yes
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
virtual_alias_maps =
mail:~ administrator$

I am not certain what you mean by immediately removing the 192.1.1.10 and 192.1.1.11, AIX servers that I use to relay admin emails to an IT address here. Some sort of a gateway implemented on a pair of IBM boxes, I might presume.
192.1.1.0/24 is in a public address space that you don't have assigned (unless you're BBN). If that IP routing leaks out, then some folks can get cranky. Or should you eventially need to contact hosts within the address space of the "real" occupants of 192.1.1.0/24, routing won't necessarilt play nice. There may well be a static IP route here, depending on the details of the router configuration, as otherwise that IP traffic would be going to BBN and not to those servers. The Internet works because folks play by the rules, when working with IP routing and DNS services. And if your predecessor used this address space (and not the likely 192.168.0.0/16 block), I'd look around to see if there were other unusual network configuration choices.
TCP port 25 is the server-to-server mail port. That's the main connection used among mail servers. Blocking that has the effect that you've discovered.
It's the clients that can also use that port that need to be relocated off the port, as the clients don't have the reverse DNS and related tests that would allow them access to that port, with various common server security configurations.
Open TCP 587 at the firewall and ensure that this port is active at the mail server host, as a starting point. You can test that with (among other tools) with a remote "telnet your.mail.server.host.name 587" command or similar; that's a primitive (but effective) (common) port test.
With the Apple Mail client, make sure the SMTP server is configured to use the default SMTP ports. Mail > Preferences > Account > Account Information > Edit SMTP Server > select the target SMTP server > Advanced > select "use the default ports (25, 465, 587)" and consider using SSL and authentication. (Apple Mail tries a few ports automatically, so the set-up can be different than other clients.)
I don't have enough space here for a full write-up on how mail or IP works, and setting up an arbitrary mail client or an IP network can be an adventure; I assumed the Apple mail client in the above. See the user collaboration services disscussion of mail services in the Mac OS X Server Advanced Administration manual as some background. (And if this stuff all looks a little cryptic, that's understandable, and you might want to consider getting some set-up help or consider moving to hosted mail services and making this stuff somebody else's problem.)

How can I stop getting 30 - 50 "Mail Administrator" or "Mail Delivery Errors" from occorring in my e-mail on a daily basis

Every time I log in to my e-mail I see 30 to 50 "mail delivery" errors. This is very frustrating to each time having to delete those items. I have blocked and clicked on spam, but there is no change.

For goodness sake, it is most likely [http://en.wikipedia.org/wiki/Backscatter_%28email%29 backscatter], changing your mail password probably will not help but is a prudent thing to do, but it is actually quite unlikely that anyone is trying to use your mail account.
There is basically nothing that can be done about backscatter, as the article I linked to advises.

Mail delivery errors

Hi, recently I'm getting tons of Mail Delivery System errors. 69 today alone. When I delete them, they come right back. Many are the same email and sometimes the page is blank. Very weird. The only thing i did differently was to try and set up a rule for people to know I was on vacation. Did not work, and had hundreds of MDS errors upon my return. Have deleted the rule but still not working properly. I also have to force quit on mail often to get it to shut down. Any ideas how to clean this up?
Cheers

I've got the same problem. One thing that helped was to clean out my inbox on my ISP's server. That stopped the force quit problem, at least for now, and also stopped a problem where mail received after that Mail delivery error message wouldn't come into my Mail application. BUT I'm still getting the tons of Mail Delivery System error messages, and yes, even when I delete them, they come right back. The message, which seems blank until I double click on it to open it in a new window, was correct. One address I'd sent an email to is no longer good, which is why one of those messages would have made sense. I see that there is a Windows virus that does this, and am wondering if there might be a Mac one also???

Mail delivery error with 5510 e-print. updates and connection are ok. friend has same problem.

I have checked all of the updates and connections for my new printer. As far as I can tell, I've checked everything that needs to be checked and all is good. But, I still get the Mail Delivery error when e-printing. And my friend has the same problem with her new 5510 b111a. What could possibly be the problem? Regular printing, scanning and so on work fine with my wireless connection.
This question was solved.
View Solution.

So it sounds like it may be an Issue with the provided Email Address from your internet service provider, you are sending from ,
What i would suggest as a test is to create a Email account either with g mail and or yahoo, and try to send the email to your eprint account/Email, and see if it accepts the email also, make sure you have your printer set to Accept email from all users you can do this by logging into Eprint Center and then going into these settings and selecting that option
I am an HP employee.
__ if this Solution has helped Please Mark as Resolved and feel free to Provide a Kudos__

No delivery if order has error in CRM

Hi All,
I want to restrict delivery if system has any error in CRM Order.
Requirement,
(1) Created orders are successfully replicated in ECC
(2) After making some changes in existing order changes are not replicated.
(3) I want to restrict delivery if order has an any error in CRM.
Regards
Jay

Hi Jay,
For your Requirement to restrict delivery in CRM System
SAP CRM has preset Functionality for Orders with Error Status in SAP CRM they do not Replicate to ECC System, So if your Order has an Error Status then it shall not Replicate to ECC System.
For Achieving your Required Details you may Follow the Steps as mentioned below
(1) Created orders are successfully replicated in ECC
For Replication of the Order you need to Configure the Middleware Parameters and Subscription and Publication for Particular System Status for the Order to Replicate to ECC System
(2) After making some changes in existing order changes are not replicated.
For Replication of the Order after Changes,Check the Status Profile there is a option for "Business Transaction Control" which should be set to To be Distributed which then allows the Order to Flow to the ECC System after changes have been Made.
(3) I want to restrict delivery if order has an any error in CRM.
For this Process you shall require to Configure the System as to Distribute the Order at a Particular status which is the Final status in CRM and you shall have to Configure the Processing of Outbound Delivery on the Same status,due to which if Errors are Present in the Order the Order with Errors doesnt flow to ECC and you shall be able to Stop Processing of the Orders with Errors.
Hope it Answers your Queries...
Revert Back for Further Queries..
Thanks and Regards
RK.

Mail delivery error when trying to send document to hpeprint. I know the email address is correct

I just got the HP8600. I set up eprint according to the instructions. When I email a document to the printer, I get a Mail Delivery error:
This message was created automatically by the mail system (ecelerity).
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
>>> [email protected] (reading confirmation): 550 5.7.1 Command
>>> rejected
I know the email address is correct. I don't know what to do to get this to work.

The Q.com provider seems to have issues sending to our servers for some reason. Other email providers will work fine like you've found with your gmail account. The best workaround at this time is to send from your gmail account if possible.
Jon-W
I work on behalf of HP
Please click “Accept as Solution ” on the post that solves your issue to help others find the solution.
Click the KUDOS STAR on the left to say “Thanks” for helping!

Mail Delivery error with every incoming mail

For every incoming mail I get a Mail Delivery from [email protected] since this morning.
I'm reading more and more posts from people with the same problem.
Apple, HELP!!!

This has been widely reported, and Apple have said that it is under investigation.

Mail delivery system error - won't delete, replicates

I have a problem with a 'mail delivery system' email, following an email that I sent out to an incorrect address. I deleted the email, and it promptly reappeared - with exactly the same time as the original, but no content. When I checked in trash, it was there too, but the more I try to empty trash, the more it appears again in the inbox again. A couple of days later, I had two more 'mail delivery system' emails, this time unprovoked, and these have replicated, ie each time I delete them, TWO emails appear in the inbox. I have carried out a disk repair, but the problem still exists. It isn't a huge problem; I continue to receive other mail, but it is a bit irritating - my trash box is huge, and won't empty.
Any advice gratefully received, thanks!

Okay, so here is what appears to be going on.
You sent an email to a group of people and at least one of the addresses was incorrect, so you deleted it, perhaps thinking that would stop the mail from being sent, but I'm just speculating on that. So it goes to your Trash in Mail, but also reappears in the Sent mailbox.
Later you get an email telling you that your message wasn't delivered, and possibly that it would keep trying for a few days. After that time, you seem to have received a message telling you that delivery of your message failed for a different reason, in that the email address didn't exist in the directory of the mail domain you sent the message to. But it also says that it wasn't delivered because it or another message was too old, and even more strange, that the mail server doesn't accept messages from users on it's own system, which makes no sense whatsoever. Adding more intrigue is the fact that it seems to have had a problem identifying you on it's own mail system for a bit, since it claimed you had no email address there.
As for the emails replicating when you delete them from the Sent mailbox, I'm guessing (because I've never had this problem myself or heard of anyone else having it) that because the message was CCed to multiple recipients, each time you delete the Sent message, you're only deleting a reference to the message for one of the recipients. So, again I'm guessing, if you were to keep deleting that original Sent message enough times, it would eventually reach the end of the actual recipient list and then disappear. Only a guess.
If you're using a POP account, there's no reason why you can't empty the Trash in Mail, as well as set the account preferences to delete files from the server when you retrieve them. Have you tried that, or do you not know how to do it?
Mulder

[Solved] postfix local mail delivery fails

Hi Guys,
on my home pc i use postfix (gmail as a smtp relay) and fetchmail for sending/receiving mails, this works very well, however sending a mail to a local user fails, I'm lost here and need your help guys.
if i send a mail like :
$>echo "Test" | mail -s "Test : local mail delivery" "andy"
The mail stays in the queue for ever...
$>mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
CC82513BCA* 455 Sun Aug 3 09:53:09 [email protected]
[email protected]
Sending to external addresses works without any problems.
Here some important info/config files :
$>whoami
andy
$>hostname
box
$>cat /etc/host.conf
# /etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost box
::1 localhost.localdomain localhost
192.168.1.3 lbox.localdomain lbox
$>cat /etc/postfix/main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/bin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /var/lib/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
#myhostname = mail.example.com
myhostname = localhost.localdomain
# 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
mydomain = localdomain
# 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
inet_interfaces = 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
#mydestination = localhost, localhost.localdomain
# 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 $pr/oxy_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]
relayhost = [smtp.gmail.com]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
alias_maps = hash:/etc/postfix/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
alias_database = $alias_maps
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
mailbox_command = /usr/bin/procmail
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
# Enable smtp auth
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/saslpass
smtp_sasl_security_options = noanonymous
# Enable tls
smtp_use_tls = yes
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
# Max message size limit
message_size_limit = 0
Please help
Last edited by Rumcajs (2014-08-05 06:16:11)

I have solved it, and this was the problem (main.cf) message_size_limit = 0 i have set this to unlimited "0" so bigger mails not get rejected by postfix, the defualt value was 10240000 (~10 Mb) after finally checking the postfix log with journalctl -u postfix (because /var/log/mail.log) is not used anymore i found this line : "fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit" after setting mailbox_size_limit to unlimited "0" postfix starts to delivery local mail.
Last edited by Rumcajs (2014-08-05 06:17:23)

TS3276 problem with mail delivery

has anyone else gotten a "problem during delivery processing" message with each outgoing message? it just randomly started happening to me this morning. it says my message was sent but the reason: Error in sieve filter: Notify mailto: recipient is not a valid address
one comes from postmaster@mac and one comes from Internet Mail Delivery....

My Wife and I both have an Ipad and an iPhone, I use an iMac and my wife a MacBook Pro.
I have this problem with all my devices.
My wife has NOT got this problem.
We both use a [email protected] email acount.
Just compared the settings:
For "Incoming server" I have p03-imap.mail.me.com
My Wife has p02-imap.mail.me.com .... and has not got this problem.
I have setup a new rule for incoming mails (for the meantime):
move all incoming emails from [email protected] to trash and delete it.
Works fine for now,......until APPLE deals with the problem.
Message was edited by: RTONLINE

SMTP error from remote mail server after initial connection:

Hello folks. I having some serious issues sending email to clients with .mac accounts. I keep on getting the following error. Can someone help? I have replaced email address names with "Blank@...) for obvious reasons.
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
SMTP error from remote mail server after initial connection:
host smtp-mx1.mac.com [17.148.20.64]: 452 try later:
retry timeout exceeded
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from ip72-207-229-240.br.br.cox.net ([72.207.229.240] helo=[192.168.0.102])
by srv3.purenrg.com with esmtp (Exim 4.68)
(envelope-from <[email protected]>)
id 1JFeOb-0001FZ-5F
for [email protected]; Thu, 17 Jan 2008 18:43:41 -0500
Message-Id: <[email protected]>
From: "[email protected]" <[email protected]>
To: Cindy Barnes <[email protected]>
Content-Type: multipart/alternative; boundary=Apple-Mail-3--1032078955
Mime-Version: 1.0 (Apple Message framework v915)
Subject: invoice 520 is overdue
Date: Thu, 17 Jan 2008 17:43:40 -0600
X-Mailer: Apple Mail (2.915)
X-PopBeforeSMTPSenders: [email protected]{
--Apple-Mail-3--1032078955
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit

I'm sure someone will give more detail, but it looks like the server blocked your address because it thinks it's a spam source. If you're not spamming, then it might be someone on the same network spamming, or malware on your computer doing it. Or it could just be a mistake. try calling whoever runs your mail server and see if they can give you more information.

My account sending hidden SPAM e-mails, i receive only mail delivery failure for e-mails that i didn't send

My account sending SPAM e-mails but i can't find it in sent folder, i receive only undelivered message response for messages which i didn't send and problem is not on provider server i checked it out.
Examples of server response:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
SMTP error from remote mail server after end of data:
host mx1.optonline.net [167.206.4.77]: 554 5.7.1 Spam detected by Cloudmark content scanner. Message rejected.
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from [181.64.16.205] (helo=kiwqdljpf)
by smtp2.neobee.net with esmtpa (Exim 4.74)
(envelope-from <[email protected]>)
id 1WPiCY-0004IY-2G
for [email protected]; Tue, 18 Mar 2014 01:48:20 +0100
Subject: FirmViagra
Date: Mon, 17 Mar 2014 18:41:36 -0700
To: <[email protected]>
From: "Sleb Icap" <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-7
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 05e778587fdac215ad5fe7047e8f78ed
http://holzstark.at/opportune.htm?la
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
SMTP error from remote mail server after RCPT TO:<[email protected]>:
host mx.coxmail.com [68.99.120.4]: 550 5.1.1 <[email protected]> recipient rejected
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from [181.64.16.205] (helo=kiwqdljpf)
by smtp2.neobee.net with esmtpa (Exim 4.74)
(envelope-from <[email protected]>)
id 1WPiCk-0004IY-B6
for [email protected]; Tue, 18 Mar 2014 01:48:32 +0100
Subject: SweetDrugs
Date: Mon, 17 Mar 2014 18:41:48 -0700
To: <[email protected]>
From: [email protected]
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 05e778587fdac215ad5fe7047e8f78ed
http://selapak-cambodia.com/chic.html?zogyzeno
My configuration of Thunderbird is:
Application Basics
Name Thunderbird
Version 24.3.0
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
Profile Folder
Show Folder
(Local drive)
Application Build ID 20140131124303
Enabled Plugins about:plugins
Build Configuration about:buildconfig
Crash Reports about:crashes
Memory Use about:memory
Mail and News Accounts
ID Incoming server Outgoing servers
Name Connection security Authentication method Name Connection security Authentication method Default?
account1 (pop3) pop3.neobee.net:110 plain passwordCleartext smtp.neobee.net:25 alwaysSTARTTLS passwordCleartext true
account2 (none) Local Folders plain passwordCleartext
account3 (pop3) pop.mail.yahoo.com:995 SSL passwordCleartext smtp.mail.yahoo.com:465 SSL passwordCleartext true
account4 (pop3) pop.mail.yahoo.com:995 SSL passwordCleartext smtp.mail.yahoo.com:465 SSL passwordCleartext true
account5 (pop3) pop.mail.yahoo.com:995 SSL passwordCleartext smtp.mail.yahoo.com:465 SSL passwordCleartext true
Extensions
Name Version Enabled ID
Test Pilot for Thunderbird 1.3.9 false [email protected]
Important Modified Preferences
Name Value
browser.cache.disk.capacity 358400
browser.cache.disk.smart_size.first_run false
browser.cache.disk.smart_size.use_old_max false
browser.cache.disk.smart_size_cached_value 358400
dom.max_chrome_script_run_time 0
extensions.lastAppVersion 24.3.0
font.internaluseonly.changed true
font.name.monospace.el Consolas
font.name.monospace.tr Consolas
font.name.monospace.x-baltic Consolas
font.name.monospace.x-central-euro Consolas
font.name.monospace.x-cyrillic Consolas
font.name.monospace.x-unicode Consolas
font.name.monospace.x-western Consolas
font.name.sans-serif.el Calibri
font.name.sans-serif.tr Calibri
font.name.sans-serif.x-baltic Calibri
font.name.sans-serif.x-central-euro Calibri
font.name.sans-serif.x-cyrillic Calibri
font.name.sans-serif.x-unicode Calibri
font.name.sans-serif.x-western Calibri
font.name.serif.el Cambria
font.name.serif.tr Cambria
font.name.serif.x-baltic Cambria
font.name.serif.x-central-euro Cambria
font.name.serif.x-cyrillic Cambria
font.name.serif.x-unicode Cambria
font.name.serif.x-western Cambria
font.size.fixed.el 14
font.size.fixed.tr 14
font.size.fixed.x-baltic 14
font.size.fixed.x-central-euro 14
font.size.fixed.x-cyrillic 14
font.size.fixed.x-unicode 14
font.size.fixed.x-western 14
font.size.variable.el 17
font.size.variable.tr 17
font.size.variable.x-baltic 17
font.size.variable.x-central-euro 17
font.size.variable.x-cyrillic 17
font.size.variable.x-unicode 17
font.size.variable.x-western 17
mail.openMessageBehavior.version 1
mail.winsearch.firstRunDone true
mailnews.database.global.datastore.id d3f7cbbc-ff7c-49f8-8265-081ff16f23e
network.cookie.prefsMigrated true
places.database.lastMaintenance 1394703331
places.history.expiration.transient_current_max_pages 104858
plugin.importedState true
plugin.state.flash 0
plugin.state.java 0
plugin.state.npauthz 0
plugin.state.npbrowserplugin 0
plugin.state.npctrl 0
plugin.state.npdeployjava 0
plugin.state.npgeplugin 0
plugin.state.npgoogleupdate 0
plugin.state.npnokiasuiteenabler 0
plugin.state.nppdf 0
plugin.state.npspwrap 0
plugin.state.npvlc 0
security.default_personal_cert Select Automatically
security.disable_button.openCertManager false
security.disable_button.openDeviceManager false
security.OCSP.require true
Graphics
Adapter Description Intel(R) HD Graphics Family
Vendor ID 0x8086
Device ID 0x0116
Adapter RAM Unknown
Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32
Driver Version 8.15.10.2462
Driver Date 7-26-2011
Adapter Description (GPU #2) NVIDIA GeForce GT 630M
Vendor ID (GPU #2) 0x10de
Device ID (GPU #2) 0x0de9
Adapter RAM (GPU #2) 2048
Adapter Drivers (GPU #2) nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Driver Version (GPU #2) 9.18.13.3165
Driver Date (GPU #2) 10-23-2013
Direct2D Enabled false
DirectWrite Enabled false (6.2.9200.16571)
ClearType Parameters ClearType parameters not found
WebGL Renderer false
GPU Accelerated Windows 0
AzureCanvasBackend skia
AzureFallbackCanvasBackend cairo
AzureContentBackend none
JavaScript
Incremental GC 1
Accessibility
Activated 0
Prevent Accessibility 0
Library Versions
Expected minimum version Version in use
NSPR 4.10.2 4.10.2
NSS 3.15.4 Basic ECC 3.15.4 Basic ECC
NSS Util 3.15.4 3.15.4
NSS SSL 3.15.4 Basic ECC 3.15.4 Basic ECC
NSS S/MIME 3.15.4 Basic ECC 3.15.4 Basic ECC
Please help me to solve this problem.

By the way, some non-delivery receipts (NDRs) are themselves spam messages with malicious attachments designed to infect your computer, so be cautious about opening any of those.

Receiving "Mail Delivery System" when Email is sent...why?

Every time I send an email via my mac mail, I always get a Mail Delivery System email containing different content such as: [Return Code 554] sid: d61F1m00P408TaZ01 or [Return Code 550] sid: d61F1m00P408TaZ01. It was also brought to my attention that those receiving my emails are getting them but they are also getting an extra email with a crazy unknown link. Help! How do I correct this? I need this email for my start-up. thanks...

Hi
No, ive not changed anything, ill include some of the error reports:
The mail system
<[email protected]>: host mx.bt.lon5.cpcloud.co.uk[65.20.0.49] said:
522 IP FOUND IN DNSRBL (please check for IP address listing on common DNS
RBL services) (in reply to MAIL FROM command)
Reporting-MTA: dns; s3.trafficplanethosting.com
X-Postfix-Queue-ID: A04751B4A808
X-Postfix-Sender: rfc822; info@...
Arrival-Date: Thu, 25 Sep 2014 07:47:54 -0500 (CDT)
Final-Recipient: rfc822;
Original-Recipient:
Action: failed
Status: 5.0.0
Remote-MTA: dns; mx.bt.lon5.cpcloud.co.uk
Diagnostic-Code: smtp; 522 IP FOUND IN DNSRBL (please check for IP address
listing on common DNS RBL services)
this message was sent to my own email address and did arrive even though it says it didnt:
The mail system
<[email protected]>: host mta5.am0.yahoodns.net[98.138.112.35] said: 553
5.7.1 [BL21] Connections will not be accepted from 208.100.3.208, because
the ip is in Spamhaus's list; see http://postmaster.yahoo.com/550-bl23.html
(in reply to MAIL FROM command)
Reporting-MTA: dns; s3.trafficplanethosting.com
X-Postfix-Queue-ID: CB7EA1B4A09D
X-Postfix-Sender: rfc822; [email protected]
Arrival-Date: Thu, 25 Sep 2014 04:53:02 -0500 (CDT)
Final-Recipient: rfc822; [email protected]
Action: failed
Status: 5.7.1
Remote-MTA: dns; mta5.am0.yahoodns.net
Diagnostic-Code: smtp; 553 5.7.1 [BL21] Connections will not be accepted from
208.100.3.208, because the ip is in Spamhaus's list; see
http://postmaster.yahoo.com/550-bl23.html
thanks

CL_SMTP_RESPONSE error in CRM mail delivery

Similar Messages

Maybe you are looking for