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

Similar Messages

  • 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.

  • 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.

  • Relay access denied error

    Guys/gals,
    I have this problem on my newly installed SLS. Here is the output of 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
    mapsrbldomains =
    messagesizelimit = 209715200
    mydestination = $myhostname, localhost.$mydomain, localhost,
    mydomain = caradimas.org
    mydomain_fallback = localhost
    myhostname = mail.caradimas.org
    mynetworks = 127.0.0.0/8
    myorigin = $mydomain
    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 rejectrblclient zen.spamhaus.org permit
    smtpdenforcetls = no
    smtpdhelorequired = yes
    smtpdhelorestrictions = rejectinvalid_helohostname rejectnon_fqdn_helohostname
    smtpdpw_server_securityoptions = login,gssapi,cram-md5
    smtpdrecipientrestrictions = permitsaslauthenticated permit_mynetworks rejectunauthdestination checkpolicyservice unix:private/policy permit
    smtpdsasl_authenable = yes
    smtpdtlsCAfile = /etc/certificates/family.caradimas.org.33E94047AFE79CA6E6513B0DD8E2DE4AE822F25B .chain.pem
    smtpdtls_certfile = /etc/certificates/family.caradimas.org.33E94047AFE79CA6E6513B0DD8E2DE4AE822F25B .cert.pem
    smtpdtls_excludeciphers = SSLv2, aNULL, ADH, eNULL
    smtpdtls_keyfile = /etc/certificates/family.caradimas.org.33E94047AFE79CA6E6513B0DD8E2DE4AE822F25B .key.pem
    smtpdtlsloglevel = 0
    smtpduse_pwserver = yes
    smtpdusetls = yes
    tlsrandomsource = dev:/dev/urandom
    unknownlocal_recipient_rejectcode = 550
    virtualaliasmaps = $virtual_maps
    Any help in solving this issue will be greatly appreciated.

    It isn't possible to answer your question since you haven't really given enough information.
    OK, sure, you've given the server config, but not explained the problem.
    For example - where are you trying to send mail from? The server itself? a machine on your network?
    Since my_networks is set to 127.0.0.0/8 then only the machine itself can send unauthenticated emails - all other users will need to authenticate.
    So the next question is whether your mail client is authenticating against the server or not?
    A copy of the logs (/var/log/mail.log and/or /var/log/system.log) showing a client trying (and failing) to send a message would help.

  • 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.

  • 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.

  • SquirrelMail - Relay access denied

    I've got problem using SquirrelMail (OS X Sever 10.4) keep getting the following message when trying to send mail:
    Message not sent. Server replied:
    Transaction failed
    554 <[email protected]>: Relay access denied
    Is there something to do in the server setup?

    It's mail to an external mail. Works to domain hosted on same server. But the from address looks like this:
    [email protected]
    When it should look like:
    [email protected]
    Could it be that I allowed webmail for both my_domain.com and www.my_domain.com?

  • Problems with MX record - Relay access denied

    Hello there,
    I'm just having some issues with my mails on a business catalyst website.
    We want to use an external server to handle mail, so I created an MX record accordingly in the business catalyst control center, pointing to the external mx server.
    However, when I lookup the mx entry with mxtoolbox it shows me something like mx.mydomain.ch.cust.b.hostedmail.com
    I guess this is originated from businesscatalyst, since the name server entries should be up to date by name (ns1.worldsecuresystems.com, ns2.worldsecuresystems.com).
    When I try to send an email to my domain hosted on business catalyst, I get an
    554 5.7.1 <[email protected]>: Relay access denied
    Why is the mx entry resolved to *.cust.b.hostedmail.com ?
    Thanks in advance

    Hi there, If you want to keep mail and other services off BC your better off actually just pointing the domain A-record to BC and leave everything else in tact.
    What you have setup is kind of if you posted a letter in the normal post for your next door neigbour. The letter has to do a round trip and come back again.
    Pointing the A-record just points your web traffic to BC and your emails stay at their source.
    Less hassle.

  • One particular user can't send to outside domains. "Relay access denied"

    I'm having a problem whereby one particular user of a mail domain I'm hosting can't send to external addresses. She can send to internal addresses, and other users can send to external addresses, but when she tries to send to an external address, this is what appears in the postfix log:
    Oct 30 12:49:21 mail1 postfix/smtpd[81724]: NOQUEUE: reject: RCPT from c-98-207-79-238.hsd1.ca.comcast.net[98.207.79.238]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.1.103]>
    Currently, I'm set to accept relays from all IP addresses, but only from authenticated users (which she is).
    Here's the relevant portion of /etc/postfix/main.cf:
    myhostname = mail1.tajimacreative.com
    mailbox_transport = cyrus
    mydomain = tajimacreative.com
    mailboxsizelimit = 0
    enableserveroptions = yes
    inet_interfaces = all
    relayhost =
    mydestination = $myhostname,localhost.$mydomain,localhost,tajimacreative.com,etajima.com
    smtpdsasl_authenable = yes
    smtpduse_pwserver = yes
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdpw_server_securityoptions = login,gssapi,cram-md5
    content_filter = smtp-amavis:[127.0.0.1]:10024
    smtpdusetls = yes
    smtpdenforcetls = no
    smtpdclientrestrictions = permit_mynetworks permit
    mapsrbldomains =
    smtpdtls_keyfile = /etc/certificates/*.tajimacreative.com.key
    localrecipientmaps = proxy:unix:passwd.byname $alias_maps
    luser_relay = support
    mynetworks = 127.0.0.0/8
    virtual_transport = lmtp:unix:/var/imap/socket/lmtp
    virtualmailboxdomains = hash:/etc/postfix/virtual_domains
    smtpdtls_certfile = /etc/certificates/*.tajimacreative.com.crt
    ownerrequestspecial = no
    recipient_delimiter = +
    alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
    smtpdtlsloglevel = 0
    smtpdtlsCAfile = /etc/certificates/*.tajimacreative.com.chcrt
    Any help would be greatly appreciated!

    If others can send then most likely the mail client is not authenticating properly. Either it is trying to use a non supported authentication method or simply a wrong password.

  • SMTP Relay Access Denied Problem

    Hi,
    While trying to Send Mail from SAP WEBAS 6.40 Short Message to External Mail domain like <uname>@yahoo.com or <uname>@gmail.com. i am getting Relay Access Deny Error.
    but,
    The Mails are delivering to those users in my own mail domain which is configured in the SCOT.
    The SMTP,SICF & SCOT are configured as per SAP.
    Our mail domain is hosted by Intermedia.net mail.
    I am doubting about Mail Domain Intermedia.net  route permission for Relay the mail to the mail server which is POP3 QMAIL Server.
    Pls tell me the Setting required to Change in the Mail server for Relay Access Permission.
    My Environment is ECC5.0 - WIN - MSSQL.
    Thanks & Regards,
    R.Shiva

    I´m with the same problem. The theme is that is problem of the configuration of smtp.
    1496168 - Error XS802 / XS829 - relay problem while sending mails through SAPconnect using SMTP plug-in

  • 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

  • Email relay access denied

    anyone knows how to solve this problem
    when sending massages this pops up!
    email relay access denied
    there are no support info from Apple

    Check your outgoing server settings. Consult with your e-mail provider.

  • 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 /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.

  • 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

Maybe you are looking for