What does “550 550 5.4.1 Relay Access Denied (state 14).” mean?












4















I am getting this message when I send an email to a corporate email address from my google-apps account:




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: 550 550 5.4.1 Relay Access Denied (state
14).




Maybe it just means the address is bad, but if I try a definite bad email I get:




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: 550 550 5.4.1 @.com: Recipient
address rejected: Access Denied (state 14).




Can anyone suggest why the slightly different responses?










share|improve this question























  • A relay error means that the destination domain is not on the permitted relay list on the SMTP server you are sending through. Were both emails in the same domain?

    – Paul
    Oct 19 '11 at 21:09
















4















I am getting this message when I send an email to a corporate email address from my google-apps account:




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: 550 550 5.4.1 Relay Access Denied (state
14).




Maybe it just means the address is bad, but if I try a definite bad email I get:




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: 550 550 5.4.1 @.com: Recipient
address rejected: Access Denied (state 14).




Can anyone suggest why the slightly different responses?










share|improve this question























  • A relay error means that the destination domain is not on the permitted relay list on the SMTP server you are sending through. Were both emails in the same domain?

    – Paul
    Oct 19 '11 at 21:09














4












4








4








I am getting this message when I send an email to a corporate email address from my google-apps account:




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: 550 550 5.4.1 Relay Access Denied (state
14).




Maybe it just means the address is bad, but if I try a definite bad email I get:




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: 550 550 5.4.1 @.com: Recipient
address rejected: Access Denied (state 14).




Can anyone suggest why the slightly different responses?










share|improve this question














I am getting this message when I send an email to a corporate email address from my google-apps account:




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: 550 550 5.4.1 Relay Access Denied (state
14).




Maybe it just means the address is bad, but if I try a definite bad email I get:




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: 550 550 5.4.1 @.com: Recipient
address rejected: Access Denied (state 14).




Can anyone suggest why the slightly different responses?







email






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 19 '11 at 21:03









Mr. BoyMr. Boy

1,737164667




1,737164667













  • A relay error means that the destination domain is not on the permitted relay list on the SMTP server you are sending through. Were both emails in the same domain?

    – Paul
    Oct 19 '11 at 21:09



















  • A relay error means that the destination domain is not on the permitted relay list on the SMTP server you are sending through. Were both emails in the same domain?

    – Paul
    Oct 19 '11 at 21:09

















A relay error means that the destination domain is not on the permitted relay list on the SMTP server you are sending through. Were both emails in the same domain?

– Paul
Oct 19 '11 at 21:09





A relay error means that the destination domain is not on the permitted relay list on the SMTP server you are sending through. Were both emails in the same domain?

– Paul
Oct 19 '11 at 21:09










4 Answers
4






active

oldest

votes


















4














550 Relay Access Denied is often a catch-all response for when mail is rejected, commonly due to falling into a spam filter.



Reasons could include actual spam detection (bulk mailing, or perhaps an overzealous spam filter setting), or a misconfiguration on your Google Apps domain settings where your domain's MX records don't match what IP the server is connecting from (seems unlikely).



I would definitely mention it to the mail administrator of your corporation. You may have uncovered a configuration issue that is also preventing a bunch of other people's email from arriving properly, possibly losing your company business.






share|improve this answer































    1














    This could also happen if your exchange server happens to fill up with logs that have not truncated. If you have an application that does your back ups of Microsoft Exchange and those back ups fail then they won't truncate. Your server well essentially fill up with logs and you'll run out of Disc space and then your server will stop receiving / sending emails. Careful though: The reaction on our exchange server is not always the same; sometimes it will allow intra-emails and other times not. Sometimes after four attempts we can send an outbound but we cannot receive an inbound or vice versa.






    share|improve this answer

































      0














      I can see the thread is quite old, but a simple Google search sent me here, so I hope it can help other people.



      I saw this error message today (a mail sent from a gmail address to an office 365 enterprise address).



      The error was just the person tried to send the mail to a.name@entreprise.com instead of aname@enterprise.com :)



      So, if you get this message, you can double-check the recipient's address you typed.



      PS: sorry if my English is basic, I'm a French user!






      share|improve this answer































        -1














        I'm afraid, I don't know what's the generic reason but I've seen that this error may occur if you type a erroneous email address like spelling mistake.






        share|improve this answer



















        • 2





          This seems to duplicate Slain's more detailed answer from October.

          – tripleee
          Jan 4 at 12:16











        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "3"
        };
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function() {
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled) {
        StackExchange.using("snippets", function() {
        createEditor();
        });
        }
        else {
        createEditor();
        }
        });

        function createEditor() {
        StackExchange.prepareEditor({
        heartbeatType: 'answer',
        autoActivateHeartbeat: false,
        convertImagesToLinks: true,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: 10,
        bindNavPrevention: true,
        postfix: "",
        imageUploader: {
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        },
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        });


        }
        });














        draft saved

        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f348512%2fwhat-does-550-550-5-4-1-relay-access-denied-state-14-mean%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        4 Answers
        4






        active

        oldest

        votes








        4 Answers
        4






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        4














        550 Relay Access Denied is often a catch-all response for when mail is rejected, commonly due to falling into a spam filter.



        Reasons could include actual spam detection (bulk mailing, or perhaps an overzealous spam filter setting), or a misconfiguration on your Google Apps domain settings where your domain's MX records don't match what IP the server is connecting from (seems unlikely).



        I would definitely mention it to the mail administrator of your corporation. You may have uncovered a configuration issue that is also preventing a bunch of other people's email from arriving properly, possibly losing your company business.






        share|improve this answer




























          4














          550 Relay Access Denied is often a catch-all response for when mail is rejected, commonly due to falling into a spam filter.



          Reasons could include actual spam detection (bulk mailing, or perhaps an overzealous spam filter setting), or a misconfiguration on your Google Apps domain settings where your domain's MX records don't match what IP the server is connecting from (seems unlikely).



          I would definitely mention it to the mail administrator of your corporation. You may have uncovered a configuration issue that is also preventing a bunch of other people's email from arriving properly, possibly losing your company business.






          share|improve this answer


























            4












            4








            4







            550 Relay Access Denied is often a catch-all response for when mail is rejected, commonly due to falling into a spam filter.



            Reasons could include actual spam detection (bulk mailing, or perhaps an overzealous spam filter setting), or a misconfiguration on your Google Apps domain settings where your domain's MX records don't match what IP the server is connecting from (seems unlikely).



            I would definitely mention it to the mail administrator of your corporation. You may have uncovered a configuration issue that is also preventing a bunch of other people's email from arriving properly, possibly losing your company business.






            share|improve this answer













            550 Relay Access Denied is often a catch-all response for when mail is rejected, commonly due to falling into a spam filter.



            Reasons could include actual spam detection (bulk mailing, or perhaps an overzealous spam filter setting), or a misconfiguration on your Google Apps domain settings where your domain's MX records don't match what IP the server is connecting from (seems unlikely).



            I would definitely mention it to the mail administrator of your corporation. You may have uncovered a configuration issue that is also preventing a bunch of other people's email from arriving properly, possibly losing your company business.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Oct 19 '11 at 21:45









            Syclone0044Syclone0044

            1,127819




            1,127819

























                1














                This could also happen if your exchange server happens to fill up with logs that have not truncated. If you have an application that does your back ups of Microsoft Exchange and those back ups fail then they won't truncate. Your server well essentially fill up with logs and you'll run out of Disc space and then your server will stop receiving / sending emails. Careful though: The reaction on our exchange server is not always the same; sometimes it will allow intra-emails and other times not. Sometimes after four attempts we can send an outbound but we cannot receive an inbound or vice versa.






                share|improve this answer






























                  1














                  This could also happen if your exchange server happens to fill up with logs that have not truncated. If you have an application that does your back ups of Microsoft Exchange and those back ups fail then they won't truncate. Your server well essentially fill up with logs and you'll run out of Disc space and then your server will stop receiving / sending emails. Careful though: The reaction on our exchange server is not always the same; sometimes it will allow intra-emails and other times not. Sometimes after four attempts we can send an outbound but we cannot receive an inbound or vice versa.






                  share|improve this answer




























                    1












                    1








                    1







                    This could also happen if your exchange server happens to fill up with logs that have not truncated. If you have an application that does your back ups of Microsoft Exchange and those back ups fail then they won't truncate. Your server well essentially fill up with logs and you'll run out of Disc space and then your server will stop receiving / sending emails. Careful though: The reaction on our exchange server is not always the same; sometimes it will allow intra-emails and other times not. Sometimes after four attempts we can send an outbound but we cannot receive an inbound or vice versa.






                    share|improve this answer















                    This could also happen if your exchange server happens to fill up with logs that have not truncated. If you have an application that does your back ups of Microsoft Exchange and those back ups fail then they won't truncate. Your server well essentially fill up with logs and you'll run out of Disc space and then your server will stop receiving / sending emails. Careful though: The reaction on our exchange server is not always the same; sometimes it will allow intra-emails and other times not. Sometimes after four attempts we can send an outbound but we cannot receive an inbound or vice versa.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited May 2 '16 at 22:57









                    jhaagsma

                    1,4481813




                    1,4481813










                    answered Apr 27 '16 at 22:50









                    JloJlo

                    111




                    111























                        0














                        I can see the thread is quite old, but a simple Google search sent me here, so I hope it can help other people.



                        I saw this error message today (a mail sent from a gmail address to an office 365 enterprise address).



                        The error was just the person tried to send the mail to a.name@entreprise.com instead of aname@enterprise.com :)



                        So, if you get this message, you can double-check the recipient's address you typed.



                        PS: sorry if my English is basic, I'm a French user!






                        share|improve this answer




























                          0














                          I can see the thread is quite old, but a simple Google search sent me here, so I hope it can help other people.



                          I saw this error message today (a mail sent from a gmail address to an office 365 enterprise address).



                          The error was just the person tried to send the mail to a.name@entreprise.com instead of aname@enterprise.com :)



                          So, if you get this message, you can double-check the recipient's address you typed.



                          PS: sorry if my English is basic, I'm a French user!






                          share|improve this answer


























                            0












                            0








                            0







                            I can see the thread is quite old, but a simple Google search sent me here, so I hope it can help other people.



                            I saw this error message today (a mail sent from a gmail address to an office 365 enterprise address).



                            The error was just the person tried to send the mail to a.name@entreprise.com instead of aname@enterprise.com :)



                            So, if you get this message, you can double-check the recipient's address you typed.



                            PS: sorry if my English is basic, I'm a French user!






                            share|improve this answer













                            I can see the thread is quite old, but a simple Google search sent me here, so I hope it can help other people.



                            I saw this error message today (a mail sent from a gmail address to an office 365 enterprise address).



                            The error was just the person tried to send the mail to a.name@entreprise.com instead of aname@enterprise.com :)



                            So, if you get this message, you can double-check the recipient's address you typed.



                            PS: sorry if my English is basic, I'm a French user!







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Oct 17 '18 at 14:33









                            SlainSlain

                            1




                            1























                                -1














                                I'm afraid, I don't know what's the generic reason but I've seen that this error may occur if you type a erroneous email address like spelling mistake.






                                share|improve this answer



















                                • 2





                                  This seems to duplicate Slain's more detailed answer from October.

                                  – tripleee
                                  Jan 4 at 12:16
















                                -1














                                I'm afraid, I don't know what's the generic reason but I've seen that this error may occur if you type a erroneous email address like spelling mistake.






                                share|improve this answer



















                                • 2





                                  This seems to duplicate Slain's more detailed answer from October.

                                  – tripleee
                                  Jan 4 at 12:16














                                -1












                                -1








                                -1







                                I'm afraid, I don't know what's the generic reason but I've seen that this error may occur if you type a erroneous email address like spelling mistake.






                                share|improve this answer













                                I'm afraid, I don't know what's the generic reason but I've seen that this error may occur if you type a erroneous email address like spelling mistake.







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Jan 4 at 12:15









                                user980892user980892

                                1




                                1








                                • 2





                                  This seems to duplicate Slain's more detailed answer from October.

                                  – tripleee
                                  Jan 4 at 12:16














                                • 2





                                  This seems to duplicate Slain's more detailed answer from October.

                                  – tripleee
                                  Jan 4 at 12:16








                                2




                                2





                                This seems to duplicate Slain's more detailed answer from October.

                                – tripleee
                                Jan 4 at 12:16





                                This seems to duplicate Slain's more detailed answer from October.

                                – tripleee
                                Jan 4 at 12:16


















                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Super User!


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid



                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.


                                To learn more, see our tips on writing great answers.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f348512%2fwhat-does-550-550-5-4-1-relay-access-denied-state-14-mean%23new-answer', 'question_page');
                                }
                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown







                                Popular posts from this blog

                                flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                                Mangá

                                 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕