Mail relay access error

Hi, I recently set up my Server to host my domain, and also my email. everytime someone sends an email to the email that is hosted on my server it comes up with the following message...
"This is an automatically generated Delivery Status Notification
Delivery to the following recipient failed permanently:
[email protected]
Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 9): 554 <[email protected]>: Relay access denied"
Can anyone point me in the right direction of what I am doing wrong? I went over all settings in Server Admin and Workgroup Manager. Also, the above user, say "[email protected]" can send email to anyone with no problem, just can't receive it. The sender will get the above message if they attempt to send to that address.
Thanks!
MacBook Pro 2GHz 1.5GB RAM, 80GB HD; MDD G4 Dual 1GHz, 1.62GB RAM, 1TB Mac OS X (10.4.8)

here is the output of the terminal command your requested, unmodified of coarse...
G4-Server:~ jason$ postconf -n
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
mail_owner = postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 0
mydestination = $myhostname,localhost.$mydomain,mail,localhost
mydomain = x970.com
mydomain_fallback = localhost
myhostname = mail.x970.com
mynetworks = 127.0.0.0/8
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdpw_server_securityoptions = login,plain,cram-md5
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_certfile = /etc/certificates/Default.crt
smtpdtls_keyfile = /etc/certificates/Default.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550

Similar Messages

Can't receive mail, Relay access denied

Hello all,
I am new to Ma c OS Server, so i apologize if this topic has already been covered before. However, I have spent several hours browsing through different discussions and still couldn't figure out where my problem is.
I have set up a new Mac OS X Snow Leopard server with Mail services enabled. I have went through routine of configuring DNS, Open Directory and adding users. I could eventually run Mail services for the client for the outgoing mail, but I can't receive any incoming mail. Mail logs keep telling me that relay access is denied. Here is the example of this:
Jun 28 12:13:15 paulmacserver postfix/smtpd[5895]: NOQUEUE: reject: RCPT from va3ehsobe006.messaging.microsoft.com[216.32.180.16]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<VA3EHSOBE007.bigfish.com>
Jun 28 12:13:15 paulmacserver postfix/smtpd[5895]: disconnect from va3ehsobe006.messaging.microsoft.com[216.32.180.16]
Here is the log from postconf -n command:
paulmacserver:~ administrator$ postconf -n
biff = no
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 =
html_directory = /usr/share/doc/postfix/html
inet_interfaces = all
mail_owner = _postfix
mailbox_size_limit = 0
mailbox_transport = dovecot
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
message_size_limit = 10485760
mydestination = $myhostname, localhost.$mydomain, localhost, mail.lifefor.net
mydomain = lifefor.net
mydomain_fallback = localhost
myhostname = paulmacserver.lifefor.net
mynetworks = 127.0.0.0/8
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated permit
smtpd_enforce_tls = no
smtpd_helo_required = no
smtpd_helo_restrictions =
smtpd_pw_server_security_options = gssapi,cram-md5
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination permit
smtpd_sasl_auth_enable = yes
smtpd_tls_CAfile = /etc/certificates/paulmacserver.lifefor.net.6067B0918DA5FE13DDE10C3696E054EF3D3 29F34.chain.pem
smtpd_tls_cert_file = /etc/certificates/paulmacserver.lifefor.net.6067B0918DA5FE13DDE10C3696E054EF3D3 29F34.cert.pem
smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
smtpd_tls_key_file = /etc/certificates/paulmacserver.lifefor.net.6067B0918DA5FE13DDE10C3696E054EF3D3 29F34.key.pem
smtpd_use_pw_server = yes
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
virtual_alias_maps = $virtual_maps
paulmacserver:~ administrator$
The server sits behind firewall and has NAT routing of port 25 to the local network address of the server. Local network address range - 192.168.10.0/24, server address - 192.168.10.5, gateway address - 192.168.10.1.
paulmacserver:~ administrator$ dig lifefor.net
; <<>> DiG 9.6.0-APPLE-P2 <<>> lifefor.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29752
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;lifefor.net.                              IN          A
;; AUTHORITY SECTION:
lifefor.net.                    10800          IN          SOA          paulmacserver.lifefor.net. administrator.lifefor.net.lifefor.net. 2011062801 86400 3600 604800 345600
;; Query time: 1 msec
;; SERVER: 192.168.10.5#53(192.168.10.5)
;; WHEN: Tue Jun 28 11:21:16 2011
;; MSG SIZE rcvd: 105
paulmacserver:~ administrator$ sudo changeip -checkhostname
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
Primary address     = 192.168.10.5
Current HostName    = paulmacserver.lifefor.net
DNS HostName        = paulmacserver.lifefor.net
The names match. There is nothing to change.
dirserv:success = "success"
All appears to be OK... But I still couldn't make incoming e-mail to work. What do I have wrong?
Thanks in advance!

I dislike split-horizon DNS configurations, and that looks to be what you are trying here.
Based on changeip, your private DNS looks OK, but your public DNS is incorrect.
In particular, you have no reverse DNS for your public IP address 80.244.227.174. Work with your ISP to get that to mail.lifefor.net. This misconfiguration will usually cause issues with outbound mail; many remote servers won't accept mail arriving from this server.
This entry mydestination = $myhostname, localhost.$mydomain, localhost, mail.lifefor.net does not include your domain name. You'll want to add $mydomain into the list you'll accept mail for within Server Admin. This is likely the central trigger for the relay error.
Additionally, you will probably want to have your mail server host configured to use the internet host name mail.lifefor.net within the mail setup (or switch your public name to paulmacserver); you're running split-horizon DNS, and you've chosen to use two different host names for this box. It's both mail.lifefor.net and paulmacserver.lifefor.net. It's possible to do that, but it tends to confuse things.
As for errata, you'll want to enable anti-spam and add zen.spamhaus.org or analogous within Server Admin to fix your current accept-from-everywhere setup. With those changes, you'll see smtpd_recipient_restrictions add check_policy_service unix:private/policy and smtpd_client_restrictions will add reject_rbl_client zen.spamhaus.org

Error 550 5.7.0 Relay Access Denied in Server 2013 Enterprise

Good evening everyone.
When emails are sent from outside of our domain, to our domain; the following message is returned:
Delivery to the following recipient failed permanently:
email
Technical details of permanent failure
Google tried to deliver your message, but it was rejected by the server for the recipient domain by mail messaging microsoft
The error that the other server returned was:
550 5.7.0 Relay Access Denied
It is affecting all users.
I have scoured the net and tried many solutions. I have disabled both the anti-spam software and Symantec.
I am at a loss. I am willing to try a reconfigure that doesn't require an outside relay or try and fix this issue but the system has been down for the organization for too long.
Any advice is appreciated!
Thank you

Hi ,
1.On the exchange cas server please check the option anonymous users is checked on the receive connectors under permissions groups.
Connector name : Default front end connector
Note : Anonymous users needs to be checked on the above mentioned connector in all the cas servers to accept the anonymous connections coming from internet.
2.However please tell me ,For you exchange organisation where you have pointed your MX records ?
3.Did you done any recent change on the receive connectors ?
4.Please do the inbound email test from EXRCA tool and share me the results .
Thanks & Regards S.Nithyanandham

Weird "relay access denied" error when using "%" in email address

Hi, I've written a solution that allows emails to be processed and redirected through my mail server. First, we receive mail at user%[email protected]. Then, we do some checks to make sure its legit, alter its content and re-send it to [email protected]. I posted another topic in this forum getting some advice as to how to build it, but it's all built and working well... or so I thought...
I initially had trouble with using the % symbol as the delimiter because of a default postfix behavior (postfix by default treats the % as my custom application is, which of course can be dangerous). However, I added "allowpercenthack = no" to main.cf and that seemed to allow postfix to not attempt to process it itself and let my application do the work.
However, if I now send mail now to my server (from another server) destined to user%[email protected], I (and my log) gets:
<user%[email protected]>: Relay access denied (in reply to RCPT TO command)
However, if I send to an address WITHOUT the %, like something [email protected], the whole thing works correctly.
HOWEVER, if I send messages WITH and WITHOUT the % from the command line while ON the server, I don't get these errors.
My main.cf has the following restrictions(s):
<pre>smtpdrecipientrestrictions = rejectnon_fqdnrecipient, checkrecipientaccess hash:/etc/postfix/access,
permit_mynetworks, rejectunauthdestination, rejectnon_fqdnsender,
rejectnon_fqdnhostname, rejectinvalidhostname, checkheloaccess hash:/etc/postfix/helo_access,
rejectrblclient zen.spamhaus.org, rejectrblclient bl.spamcop.net, rejectrblclient relays.ordb.org,
permit</pre>
I'm assuming that permit_mynetworks is allowing this to work from my server's command line, and therefore I'm suspecting rejectunauthdestination is what's killing my ability to use the % symbol. As a test, I removed rejectunauthdestination temporarily and reload postix. The next mail received triggered this error in the log:
Mar 16 12:24:28 server postfix/smtpd[1368]: fatal: parameter "smtpdrecipientrestrictions": specify at least one working instance of: checkrelaydomains, rejectunauthdestination, reject, defer or deferifpermit
Of course. I needed one of those directives. I didn't want reject, defer or deferifpermit, and documentation on checkrelaydomains was not available at http://www.postfix.org/postconf.5.html. However, I tried checkrelaydomains, and it seemed to work as expected permitting my % emails and rejecting stuff it should, but of course the 'gotcha' was that postfix's log now reflected:
Mar 16 12:33:08 server postfix/smtpd[1579]: warning: support for restriction "checkrelaydomains" will be removed from Postfix; use "rejectunauthdestination" instead
Mar 16 12:33:08 server postfix/smtpd[1579]: warning: restriction `rejectnon_fqdnsender' after `checkrelaydomains' is ignored
So, can anyone recommend a way I can polish up my restrictions to allow these % addresses without opening myself up for anything dangerous?
Side question: I placed `rejectnon_fqdnsender' after rejectunauthdestination destination because I didn't want to bother checking the sender unless I confirmed the recipient was at my server. Does that comment that it doesn't work after checkrelaydomains, mean that it also doesn't get processed after rejectunauthdestination?
MacBook Mac OS X (10.4.8)

However, I added "allowpercenthack = no" to main.cf
and that seemed to allow postfix to not attempt to
process it itself and let my application do the
work.
However, if I now send mail now to my server (from
another server) destined to
user%[email protected], I (and my
log) gets:
Hardly ever had a need for this, but if I remember correctly you will need to set:
allowuntrustedrouting = yes
in main.cf
(No need for allowpercenthack (I think))
or you could create a hash table before rejectunauthdestination to return OK based on your needed patterns.
I think the first method will work though.
Side question: I placed `rejectnon_fqdnsender'
after rejectunauthdestination destination because I
didn't want to bother checking the sender unless I
confirmed the recipient was at my server. Does that
comment that it doesn't work after
checkrelaydomains, mean that it also doesn't get
processed after
checkrelaydomains is deprecated
You can place rejectnon_fqdnsender anywhere you like or even omit it, but I don't see why you would have to.

When sending an email to all our members under a group email I get a fatal error relay access denied. Very important I get these emails out to all our members.

Trying to email a group of all our members and I keep getting an error message.
he original message was received at Tue, 18 Nov 2014 13:50:51 -0500
from d154-20-241-245.bchsia.telus.net [154.20.241.245]
----- The following addresses had permanent fatal errors -----
<[email protected]>
(reason: 554 5.7.1 <[email protected]>: Relay access denied)
----- Transcript of session follows -----
... while talking to scariboochamber.org.:
>>> RCPT To:<[email protected]>
<<< 554 5.7.1 <[email protected]>: Relay access denied
554 5.0.0 Service unavailable

However, I added "allowpercenthack = no" to main.cf
and that seemed to allow postfix to not attempt to
process it itself and let my application do the
work.
However, if I now send mail now to my server (from
another server) destined to
user%[email protected], I (and my
log) gets:
Hardly ever had a need for this, but if I remember correctly you will need to set:
allowuntrustedrouting = yes
in main.cf
(No need for allowpercenthack (I think))
or you could create a hash table before rejectunauthdestination to return OK based on your needed patterns.
I think the first method will work though.
Side question: I placed `rejectnon_fqdnsender'
after rejectunauthdestination destination because I
didn't want to bother checking the sender unless I
confirmed the recipient was at my server. Does that
comment that it doesn't work after
checkrelaydomains, mean that it also doesn't get
processed after
checkrelaydomains is deprecated
You can place rejectnon_fqdnsender anywhere you like or even omit it, but I don't see why you would have to.

Receiving Relay Access Denied message when trying to send mail

Hello,
I have a client who getting the following error when sending a message:
domainname-com.mail.protection.outlook.com[207.46.163.215] said: 550 5.7.0 Relay Access Denied (in reply to RCPT TO command)
I think this is a Microsoft/outlook.com issue.
Please advise.
Have a great day,
Don

Hi,
Please send emails to different addresses, check if the message will always return.
What is the user's account type? If it's Outlook.com via Exchange ActiveSync, then we should check the service status on
www.live.com. If the there's trouble sending from Web as well, it should be somthing related to the recipient's side, contact them via a possible portal and let them know that they seem to have rejected your emails.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

OEM Email Notification:: "Relay access denied " Error

Hello all,
The IP address of the OEM grid server was changed very recently.
Though everythin works perfectly after that, 'am not getting any mail notifications that i used to get before.
The Outgoing Mail (SMTP) Server ip is the same as it was previously
In OEM, Setup => Notification Methods =>Test Mail Servers ::gives the below errors.
<smtp ip addr>: Test failed with message: "Sending failed; nested exception is: javax.mail.SendFailedException: Invalid Addresses; nested exception is: javax.mail.SendFailedException: 554 <[email protected]>: Relay access denied "
Is there anywhere i need to make any change??
TIA,
J J

Well, This was coz dat the "relaying" for the new ip address was not enabled in the mail server.
J J

Hello, relay access denied error

Hello, can someone help me with such thing: need to configure c170 as mail gateway for postfix. the thing is, i've done all the initial setup, set RAT to accept all emails for my domain and for other domains, as i use one interface deployment solution. I've put my postfix as relay host in HAT. Also i've put my host in smtp routes as for my domain and for all other domains too, so c170 must redirect outgoing messages to my postfix, but postfix tells Relay access denied. Did i miss something? or i just don't understand something? it would be great if postfix will send outgoing messages, rather than c170. Need advise. Thanks in advance.

HERE IS WHAT MY ESA SAYS:
Received Time:           17 Dec 2013 09:28:42 (GMT +02:00)
MID:           74842, 74841
Message Size:           856 (Bytes)
Subject:           123
Envelope Sender:           [email protected]
Envelope Recipients:           [email protected]
Message ID Header:           <[email protected]>
SMTP Auth User ID:           N/A
Attachment Attachments:           N/A
Sending Host Summary
Reverse DNS Hostname:           (unverified)
IP Address:           xx.xxx.xx.146
SBRS Score:           not enabled
Processing Details
           MAIL POLICY "OutgoingMail" MATCHED THESE RECIPIENTS: [email protected]
17 Dec 2013 09:28:42 (GMT +02:00)           Protocol SMTP interface Data 2 (IP xx.xxx.xx.147) on incoming connection (ICID 363238) from sender IP xx.xxx.xx.146. Reverse DNS host None verified no.
17 Dec 2013 09:28:42 (GMT +02:00)           (ICID 363238) RELAY sender group Incoming Relay match xx.xxx.xx.146 SBRS not enabled
17 Dec 2013 09:28:42 (GMT +02:00)           Start message 74841 on incoming connection (ICID 363238).
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 enqueued on incoming connection (ICID 363238) from [email protected].
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 on incoming connection (ICID 363238) added recipient ([email protected]).
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 on incoming relay (Postfix) missing header Received.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 contains message ID header '<[email protected]>'.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 original subject on injection: 123
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 (856 bytes) from [email protected] ready.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 matched per-recipient policy OutgoingMail for outbound mail policies.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 queued for delivery.
17 Dec 2013 09:28:42 (GMT +02:00)           SMTP delivery connection (DCID 41909) opened from Cisco IronPort interface xx.xxx.xx.147 to IP address xx.xxx.xx.146. on port 25.
17 Dec 2013 09:28:42 (GMT +02:00)           (DCID 41909) Delivery started for message 74841 to [email protected].
17 Dec 2013 09:28:42 (GMT +02:00)           (DCID 41909) Message 74841 bounce verification rewriting sender [email protected] to [email protected].
17 Dec 2013 09:28:42 (GMT +02:00)           (DCID 41909) Message 74841 to [email protected] bounced by destination server. Reason: 5.1.0 - Unknown address error ('554', ['5.7.1 <[email protected]>: Relay access denied'])
17 Dec 2013 09:28:42 (GMT +02:00)           Start message 74842 on incoming connection (ICID 0).
17 Dec 2013 09:28:42 (GMT +02:00)           A new message 74842 was generated to handle bounce of message 74841.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74842 enqueued on incoming connection (ICID 0) from .
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74842 on incoming connection (ICID 0) added recipient ([email protected]).
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74842 (1971 bytes) from ready.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74842 queued for delivery.
17 Dec 2013 09:28:42 (GMT +02:00)           SMTP delivery connection (DCID 41910) opened from Cisco IronPort interface xx.xxx.xx.147 to IP address xx.xxx.xx.146 on port 25.
17 Dec 2013 09:28:42 (GMT +02:00)           (DCID 41910) Delivery started for message 74842 to [email protected].
17 Dec 2013 09:28:43 (GMT +02:00)           (DCID 41910) Delivery details: Message 74842 sent to [email protected]
17 Dec 2013 09:28:43 (GMT +02:00)          Message 74842 to [email protected] received remote SMTP response '2.0.0 Ok: queued as E39B43807DF'.
HERE IS WHAT MY POSTFIX SAYS:
Dec 17 09:06:51 mail postfix/smtpd[18564]: connect from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:06:51 mail postfix/smtpd[18564]: NOQUEUE: reject: RCPT from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=
Dec 17 09:06:51 mail postfix/smtpd[18568]: connect from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:06:51 mail postfix/smtpd[18568]: 8A90D3807E5: client=smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:06:51 mail postfix/cleanup[18569]: 8A90D3807E5: message-id=<[email protected]>
Dec 17 09:06:51 mail postfix/qmgr[2383]: 8A90D3807E5: from=<>, size=2553, nrcpt=1 (queue active)
Dec 17 09:06:51 mail postfix/local[18570]: 8A90D3807E5: to=<[email protected]>, relay=local, delay=0.08, delays=0.05/0.01/0/0.02, dsn=2.0.0, status=sent (delivered to mailbox)
Dec 17 09:06:51 mail postfix/qmgr[2383]: 8A90D3807E5: removed
Dec 17 09:06:56 mail postfix/smtpd[18564]: disconnect from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:06:56 mail postfix/smtpd[18568]: disconnect from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:07:01 mail dovecot: pop3-login: Login: user=, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.146, mpid=18578, TLS
Dec 17 09:07:01 mail dovecot: pop3(test): Disconnected: Logged out top=0/0, retr=1/2651, del=0/17, size=34346
xx.xxx.xx.146 is ip of my postfix server. it is listed in relaylist. also it is listed in smtp routes for All other domains.

Mail system access module error

I have vista 64 and I installed Desktop manager 4.7 with media and every time it stats up I get this message "The mail system access module found at C:\programs Files (x86)\Research In Motion\Blaskberry\MailDerver.DLL is incompatible with this version of the desktop Tools. Please reinstall the Desktop tools." I removed and re-installed it like 4 times now and I still get the same thing. How do I fix this??
Thank you for any and all help I can get.

If found something on another form that talked about this error, but it was from 2005. It mentioned happening with the Desktop Manager 3.6. The resolution was to perform a clean uninstall of the Desktop Manager, rather than just uninstalling it.
Here are the steps to perform the clean uninstall steps
http://www.blackberry.com/btsc/KB02206
Also if that doesn't work try installing Desktop Manager 4.6, or 4.7 without Media Manager to see if it makes a difference.
If someone has been helpful please consider giving them kudos by clicking the star to the left of their post.
Remember to resolve your thread by clicking Accepted Solution.

Relay access denied (state 14).

I'm running a OS X Server (10.4) with some domains. It's been working fine untill now. I've added a new domain and pointed it to the server.
When I'm trying to mail someone on the domain, from outside the server it just jumps back with an error message as bellow:
Technical details of permanent failure:
PERM_FAILURE: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 554 554 <test@my_domain.se>:
Relay access denied (state 14).
What could be wrong? I can post to all other domains on the server.

No, turned out that I hadn't. I added them under Hostings in the Mail service setup. So now it works.
Thanks!

Relay access denied

I'm regularly getting an error while i send email outside to my organisation on either I use sun.net.smtp or javamail api to send emails.
It's working fine withing my organisation but for outside organisation let say to::: [email protected]
code is showing following error:
Exception in thread "main" sun.net.smtp.SmtpProtocolException: 554 5.7.1 <[email protected]>: Relay access denied
at sun.net.smtp.SmtpClient.issueCommand(SmtpClient.java:48)
at sun.net.smtp.SmtpClient.toCanonical(SmtpClient.java:56)
at sun.net.smtp.SmtpClient.to(SmtpClient.java:98)
at SmtpClientExample.main(SmtpClientExample.java:22)
Java Result: 1
Please help me out, I've stucked due to this.

ariser3107 wrote:
The JavaMail FAQ says that my mail server is not configured to send mail out of organisation. So, I should first configure it.
But I actually don't know about the mail server configuration.
My Organisation has taken this domain to some third party owner.
So, please tell me the way to configure it to allow sending emails out of the organisation.You might want to get better at reading the FAQ entry. I have highlighted the relevant part of the FAQ:
Q: When I try to send a message, why do I get javax.mail.SendFailedException: 550 Unable to relay for my-address?
A: This is not a JavaMail problem. This is an error reply from your SMTP mail server. It indicates that your mail server is not configured to allow you to send mail through it. Typically, mail servers for an organization will be configured to allow mail from within the organization to be sent to other addresses within the organization, or to addresses external to the organization. It will also typically allow mail coming from an address external to an organization to be sent to addresses within the orgnaization. What it will typically not allow is mail coming from an address external to the organization to be sent (relayed) to another address also external to the organization. The configuration of the mail server determines whether such relaying is allowed, and which addresses are considered internal vs. external. Often mail servers will require you to authenticate before they will relay messages.

Relay Access denied /fully-qualified hostname

hello guys,
I have made an application that sends emails (with attachments) to different users. It works fine when I use an email account (smtp server) from my network but not otherwise.... For example if i use it from my university then uni's smtp server must be used. But when i run it from my job, my uni's server does not work (vice versa).
I get the following exceptions:
Thu Feb 05 12:46:40 CET 2004
ERROR MESSAGE: javax.mail.SendFailedException: Sending failed;
nested exception is:
     class javax.mail.SendFailedException: Invalid Addresses;
nested exception is:
     class javax.mail.SendFailedException: 554 <[email protected]>: Recipient address rejected: Relay access denied
     at javax.mail.Transport.send0(Transport.java:218)
     at javax.mail.Transport.send(Transport.java:80)
     at MailUtil.testOutgoingSmtp(Main.java:692)
     at EmailConfigDialog.testBtActionPerformed(Main.java:1578)....
Thu Feb 05 12:30:58 CET 2004
ERROR MESSAGE: javax.mail.SendFailedException: Sending failed;
nested exception is:
     class javax.mail.SendFailedException: Invalid Addresses;
nested exception is:
     class javax.mail.SendFailedException: 504 <cube>: Helo command rejected: need fully-qualified hostname
     at javax.mail.Transport.send0(Transport.java:218)
     at javax.mail.Transport.send(Transport.java:80)
     at MailUtil.testOutgoingSmtp(Main.java:692)
     at EmailConfigDialog.testBtActionPerformed(Main.java:1578)
my hostname is cube. Can someone please help? It is driving me crazy :::(.
I am using windows xp
cheers
Awan

Sorry, hit the post button before addressing the other problem. While your getting the DNS problem solved find the guy that is administering the SMTP server and tell him it is not relaying messages for you. He'll probably want to know the address so bring the stack trace with you and show him the 500 series error.

Mail relay issue since lion server install

I upgraded (or not) my Mac Mini Server with Snow Leopard, to Lion Server.
I'm now getting mail relay errors when sending email to an account on my server from gmail.
"Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 554 554 5.7.1 <[email protected]>: Relay access denied (state 14)."
I'll post postconf -n if required.
voigtstr.com has an A name at the domain name registrar
mail.voigtstr.com has an mx record.
dig +short MX voigtstr.com returns
1 mail.voigtstr.com.
voigtstr.com and mail.voigtstr.com both point to my external ip address
any pointers?

LincNesh,
Seems the problem has been solved by Peter Rauen.
See this discussion: Mail relay SASL problem / postconf -n
I checked on my server and Peter is right. Although there are configs in /etc/postfix there is another path with postfix conf files: /Library/Server/Mail/Config/postfix
I actually only had to insert this line to main.cf there: smtp_sasl_security_options =
After a postfix reload my mails are being delivered via dyndns again.
Cheers!

554 5.7.1: Relay access denied

hi
I have configured a mail server on a SLS xserve but I have some problems with incoming emails: using any email account to send a test mail to [email protected] (which is a valid account I can use to send messages), I receive the following error:
----- The following addresses had permanent fatal errors -----
<[email protected]>
(reason: 554 5.7.1 <[email protected]>: Relay access denied)
----- Transcript of session follows -----
... while talking to mail.mydomain.com.:
DATA
<<< 554 5.7.1 <[email protected]>: Relay access denied
554 5.0.0 Service unavailable
<<< 554 5.5.1 Error: no valid recipients
I have read some topics on this forum with similar issues but I couldn't solve mine, I'll post my postconf -n
biff = no
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
header_checks = pcre:/etc/postfix/customheaderchecks
html_directory = /usr/share/doc/postfix/html
inet_interfaces = all
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = dovecot
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 10485760
mydomain = mydomain.com
mydomain_fallback = localhost
mynetworks = 127.0.0.0/8
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permit_mynetworks permitsaslauthenticated permit
smtpdenforcetls = no
smtpdhelorequired = yes
smtpdhelorestrictions = rejectinvalid_helohostname rejectnon_fqdn_helohostname
smtpdpw_server_securityoptions = cram-md5
smtpdrecipientrestrictions = permitsaslauthenticated permit_mynetworks rejectunauthdestination checkpolicyservice unix:private/policy permit
smtpdsasl_authenable = yes
smtpdtlsCAfile = /etc/certificates/mydomain.347A9DC2B6519982A6C3D71607EB9E0A466636CB.chain.pem
smtpdtls_certfile = /etc/certificates/mydomain.347A9DC2B6519982A6C3D71607EB9E0A466636CB.cert.pem
smtpdtls_excludeciphers = SSLv2, aNULL, ADH, eNULL
smtpdtls_keyfile = /etc/certificates/mydomain.347A9DC2B6519982A6C3D71607EB9E0A466636CB.key.pem
smtpdtlsloglevel = 0
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
virtualaliasmaps =
is there any error?
any help is greatly greatly appreciated
thanks in advance
Message was edited by: novantadue
Message was edited by: novantadue

thanks, I had already set it at "Debug" level, I have slightly different log messages when sending from gmail.com or from pippo.it but reason is the same
gmail.com
Jan 19 10:50:59 mail postfix/smtpd[1833]: connect from mail-ew0-f211.google.com[209.85.219.211]
Jan 19 10:50:59 mail postfix/smtpd[1833]: NOQUEUE: reject: RCPT from mail-ew0-f211.google.com[209.85.219.211]: 450 4.7.1 <[email protected]>: *Recipient address rejected: Service is unavailable*; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail-ew0-f211.google.com>
Jan 19 10:50:59 mail postfix/smtpd[1833]: disconnect from mail-ew0-f211.google.com[209.85.219.211]
pippo.it (80.253.x.x is public IP address)
Jan 19 10:55:44 mail postfix/smtpd[1941]: warning: 80.253.x.x : address not listed for hostname mail.pippo.it
Jan 19 10:55:44 mail postfix/smtpd[1941]: connect from unknown[80.253.x.x]
Jan 19 10:55:44 mail postfix/smtpd[1941]: NOQUEUE: reject: RCPT from unknown[80.253.x.x]: 550 5.1.1 <[email protected]>: *Recipient address rejected: User unknown in local recipient table*; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail.pippo.it>
Jan 19 10:55:44 mail postfix/smtpd[1941]: disconnect from unknown[80.253.x.x]

Configure LAMP stack to use internal mail relay without....

Does anybody know of a way i can configure my new LAMP stack to use the companys internal mail relay without having to implement postfix, or sendmail? I did already try to implement send mail recently, and its very confusing to me since i have never set up a mail server, and i tried to implement postfix, SOHO i think was the wiki i used, and that never got done either. It seems incredibly cryptic to someone who even has tons of server experience, just not the email portion. Maybe the wikis are just written for those who have more experience in making SSL certs, and being more versed in MX records, and DNS for email specific things. etc...
Since i have not successfully set up a mail server thus far, i dont have enough general mailer / experience to understand the wikis on setting up Sendmail, etc...
My company asked me if i could just use their internal mail relay instead. I would like to know if i still need to set up sendmail to allow PHP mail() function to send out mail, or if theres some configuration somewhere that i can adjust so it can use the existing internal mail relays.
Note, the only thing im trying to achieve here is to get my apps to send out emails for login password management, and error logs.

In my experience an SMTP server is preferable to sendmail/postfix as it is far more portable and robust... (in a web environment) many webhosts, for example, pay no heed to the configuration of sendmail - so code that runs on one host fails on another. PHP mail() can be leveraged to use any backend you like but this typically requires root access (or at least permissions beyond those offered on typical hosting services), and, as said above, does not allow for any useful level of error reporting.
Swiftmailer is (generally) my weapon of choice - unless the particular project has additional PEAR dependencies/requirements that mean it makes sense to stay within the same codebase... not that it (PEAR) is always that consistent anyhow
I can't really offer much in the way of help with cron integration as that is not a route I have taken - it should think it would be pretty trivial (sic )to implement as you build your script... swiftmailer has some pretty neat "live address" checking routines - have a dig through the docs
Last edited by satanselbow (2013-12-17 09:49:13)

Mail relay access error

Similar Messages

Maybe you are looking for