Exim4 550-Verification failed - how to allow any sender?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












Mail sent from a daemon on my server connecting to exim4 daemon light using SMTP seems to be being frozen. In the exim4 log:



2014-10-01 09:52:19 1XZKKJ-00049R-8p <= noreply@example.com H=localhost (server.example.com) [127.0.0.1] P=esmtp S=9492
014-10-01 09:52:22 1XZKKJ-00049R-8p ** someone@somewhere.com R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<someone@somewhere.com>: host somewhere.com [203.170.86.177]: 550-Verification failed for <noreply@example.com>
550-No Such User Here
550 Sender verify failed


I think this is saying exim4 rejected the sender's, i.e. the from email address? Exim4 is running on server.example.com and I am using noreply@example.com as the sender which does not exist - it worked in the past. I had to recently re-do domain records on example.com but they are all OK now and have percolated out (they were done days ago).



I think I have the same issue as here: http://help.directadmin.com/item.php?id=59, but cannot try the solution as cannot find exim4 configuration file is - there are many under /etc/exim4/conf.d (I just ran dpkg-reconfigure exim4-config when I installed exim) and the documentation says there is just one? Also how was it working before?



I am prepared to allow any sender - the firewall blocks external access to exim and I am only using it to send mail from my own daemon.



UPDATE Sending to other email addresses works, just to particular one (that is certainly valid) does not - which is weird because exim says it is problem with sender not recipient?!










share|improve this question
















bumped to the homepage by Community♦ yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















    up vote
    0
    down vote

    favorite












    Mail sent from a daemon on my server connecting to exim4 daemon light using SMTP seems to be being frozen. In the exim4 log:



    2014-10-01 09:52:19 1XZKKJ-00049R-8p <= noreply@example.com H=localhost (server.example.com) [127.0.0.1] P=esmtp S=9492
    014-10-01 09:52:22 1XZKKJ-00049R-8p ** someone@somewhere.com R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<someone@somewhere.com>: host somewhere.com [203.170.86.177]: 550-Verification failed for <noreply@example.com>
    550-No Such User Here
    550 Sender verify failed


    I think this is saying exim4 rejected the sender's, i.e. the from email address? Exim4 is running on server.example.com and I am using noreply@example.com as the sender which does not exist - it worked in the past. I had to recently re-do domain records on example.com but they are all OK now and have percolated out (they were done days ago).



    I think I have the same issue as here: http://help.directadmin.com/item.php?id=59, but cannot try the solution as cannot find exim4 configuration file is - there are many under /etc/exim4/conf.d (I just ran dpkg-reconfigure exim4-config when I installed exim) and the documentation says there is just one? Also how was it working before?



    I am prepared to allow any sender - the firewall blocks external access to exim and I am only using it to send mail from my own daemon.



    UPDATE Sending to other email addresses works, just to particular one (that is certainly valid) does not - which is weird because exim says it is problem with sender not recipient?!










    share|improve this question
















    bumped to the homepage by Community♦ yesterday


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Mail sent from a daemon on my server connecting to exim4 daemon light using SMTP seems to be being frozen. In the exim4 log:



      2014-10-01 09:52:19 1XZKKJ-00049R-8p <= noreply@example.com H=localhost (server.example.com) [127.0.0.1] P=esmtp S=9492
      014-10-01 09:52:22 1XZKKJ-00049R-8p ** someone@somewhere.com R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<someone@somewhere.com>: host somewhere.com [203.170.86.177]: 550-Verification failed for <noreply@example.com>
      550-No Such User Here
      550 Sender verify failed


      I think this is saying exim4 rejected the sender's, i.e. the from email address? Exim4 is running on server.example.com and I am using noreply@example.com as the sender which does not exist - it worked in the past. I had to recently re-do domain records on example.com but they are all OK now and have percolated out (they were done days ago).



      I think I have the same issue as here: http://help.directadmin.com/item.php?id=59, but cannot try the solution as cannot find exim4 configuration file is - there are many under /etc/exim4/conf.d (I just ran dpkg-reconfigure exim4-config when I installed exim) and the documentation says there is just one? Also how was it working before?



      I am prepared to allow any sender - the firewall blocks external access to exim and I am only using it to send mail from my own daemon.



      UPDATE Sending to other email addresses works, just to particular one (that is certainly valid) does not - which is weird because exim says it is problem with sender not recipient?!










      share|improve this question















      Mail sent from a daemon on my server connecting to exim4 daemon light using SMTP seems to be being frozen. In the exim4 log:



      2014-10-01 09:52:19 1XZKKJ-00049R-8p <= noreply@example.com H=localhost (server.example.com) [127.0.0.1] P=esmtp S=9492
      014-10-01 09:52:22 1XZKKJ-00049R-8p ** someone@somewhere.com R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<someone@somewhere.com>: host somewhere.com [203.170.86.177]: 550-Verification failed for <noreply@example.com>
      550-No Such User Here
      550 Sender verify failed


      I think this is saying exim4 rejected the sender's, i.e. the from email address? Exim4 is running on server.example.com and I am using noreply@example.com as the sender which does not exist - it worked in the past. I had to recently re-do domain records on example.com but they are all OK now and have percolated out (they were done days ago).



      I think I have the same issue as here: http://help.directadmin.com/item.php?id=59, but cannot try the solution as cannot find exim4 configuration file is - there are many under /etc/exim4/conf.d (I just ran dpkg-reconfigure exim4-config when I installed exim) and the documentation says there is just one? Also how was it working before?



      I am prepared to allow any sender - the firewall blocks external access to exim and I am only using it to send mail from my own daemon.



      UPDATE Sending to other email addresses works, just to particular one (that is certainly valid) does not - which is weird because exim says it is problem with sender not recipient?!







      debian smtp exim






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 31 at 22:08









      roaima

      40.4k547110




      40.4k547110










      asked Oct 1 '14 at 16:17









      markmnl

      3361512




      3361512





      bumped to the homepage by Community♦ yesterday


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community♦ yesterday


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          It is the receiving MTA that is rejecting the non-existent sender; there is nothing that you can do about that on your end about that (besides simply using a real sender).



          I also reject envelope senders that do not exist, as that means that NDRs also can't be delivered to the sender, and in 99.5% of the cases a non-existent envelope sender is spam or phishing or similar. There's no good reason not to use a working envelope sender.






          share|improve this answer




















          • The sending MTA. Fair enough but doesn't explain why works to other recipients.
            – markmnl
            Oct 2 '14 at 16:22










          • What do you mean, "The sending MTA"? The receiving MTA is the one rejecting the sender. It works for other recipients because the receiving MTA for those other recipients is not checking the sender.
            – wurtel
            Oct 6 '14 at 9:41

















          up vote
          0
          down vote













          Check for a "verify = sender" in your Exim acl's, such as the one that executes for the RCPT TO: command (look for acl_smtp_rcpt=xxxxx). That Exim option in an acl checks to make sure the sender is a "valid" (see exim docs for exactly what that means), and you may need to remove it since this is an internal server only sending from fake senders. In a production server, there are better ways to do the same.



          If your acl's are checking the sender when processing the RCPT TO:, like some configurations do, then you can get this message where it looks like the problem is in the recipient when it is actually the sender verify causing the rejection.



          Try running a command-line exim in address verification mode to see which acl's are executing:



          exim4 -d -bvs noreply@example.com
          exim4 -d -bv someone@somewhere.com





          share|improve this answer






















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            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',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f158660%2fexim4-550-verification-failed-how-to-allow-any-sender%23new-answer', 'question_page');

            );

            Post as a guest






























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            It is the receiving MTA that is rejecting the non-existent sender; there is nothing that you can do about that on your end about that (besides simply using a real sender).



            I also reject envelope senders that do not exist, as that means that NDRs also can't be delivered to the sender, and in 99.5% of the cases a non-existent envelope sender is spam or phishing or similar. There's no good reason not to use a working envelope sender.






            share|improve this answer




















            • The sending MTA. Fair enough but doesn't explain why works to other recipients.
              – markmnl
              Oct 2 '14 at 16:22










            • What do you mean, "The sending MTA"? The receiving MTA is the one rejecting the sender. It works for other recipients because the receiving MTA for those other recipients is not checking the sender.
              – wurtel
              Oct 6 '14 at 9:41














            up vote
            0
            down vote













            It is the receiving MTA that is rejecting the non-existent sender; there is nothing that you can do about that on your end about that (besides simply using a real sender).



            I also reject envelope senders that do not exist, as that means that NDRs also can't be delivered to the sender, and in 99.5% of the cases a non-existent envelope sender is spam or phishing or similar. There's no good reason not to use a working envelope sender.






            share|improve this answer




















            • The sending MTA. Fair enough but doesn't explain why works to other recipients.
              – markmnl
              Oct 2 '14 at 16:22










            • What do you mean, "The sending MTA"? The receiving MTA is the one rejecting the sender. It works for other recipients because the receiving MTA for those other recipients is not checking the sender.
              – wurtel
              Oct 6 '14 at 9:41












            up vote
            0
            down vote










            up vote
            0
            down vote









            It is the receiving MTA that is rejecting the non-existent sender; there is nothing that you can do about that on your end about that (besides simply using a real sender).



            I also reject envelope senders that do not exist, as that means that NDRs also can't be delivered to the sender, and in 99.5% of the cases a non-existent envelope sender is spam or phishing or similar. There's no good reason not to use a working envelope sender.






            share|improve this answer












            It is the receiving MTA that is rejecting the non-existent sender; there is nothing that you can do about that on your end about that (besides simply using a real sender).



            I also reject envelope senders that do not exist, as that means that NDRs also can't be delivered to the sender, and in 99.5% of the cases a non-existent envelope sender is spam or phishing or similar. There's no good reason not to use a working envelope sender.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Oct 2 '14 at 7:12









            wurtel

            9,37511324




            9,37511324











            • The sending MTA. Fair enough but doesn't explain why works to other recipients.
              – markmnl
              Oct 2 '14 at 16:22










            • What do you mean, "The sending MTA"? The receiving MTA is the one rejecting the sender. It works for other recipients because the receiving MTA for those other recipients is not checking the sender.
              – wurtel
              Oct 6 '14 at 9:41
















            • The sending MTA. Fair enough but doesn't explain why works to other recipients.
              – markmnl
              Oct 2 '14 at 16:22










            • What do you mean, "The sending MTA"? The receiving MTA is the one rejecting the sender. It works for other recipients because the receiving MTA for those other recipients is not checking the sender.
              – wurtel
              Oct 6 '14 at 9:41















            The sending MTA. Fair enough but doesn't explain why works to other recipients.
            – markmnl
            Oct 2 '14 at 16:22




            The sending MTA. Fair enough but doesn't explain why works to other recipients.
            – markmnl
            Oct 2 '14 at 16:22












            What do you mean, "The sending MTA"? The receiving MTA is the one rejecting the sender. It works for other recipients because the receiving MTA for those other recipients is not checking the sender.
            – wurtel
            Oct 6 '14 at 9:41




            What do you mean, "The sending MTA"? The receiving MTA is the one rejecting the sender. It works for other recipients because the receiving MTA for those other recipients is not checking the sender.
            – wurtel
            Oct 6 '14 at 9:41












            up vote
            0
            down vote













            Check for a "verify = sender" in your Exim acl's, such as the one that executes for the RCPT TO: command (look for acl_smtp_rcpt=xxxxx). That Exim option in an acl checks to make sure the sender is a "valid" (see exim docs for exactly what that means), and you may need to remove it since this is an internal server only sending from fake senders. In a production server, there are better ways to do the same.



            If your acl's are checking the sender when processing the RCPT TO:, like some configurations do, then you can get this message where it looks like the problem is in the recipient when it is actually the sender verify causing the rejection.



            Try running a command-line exim in address verification mode to see which acl's are executing:



            exim4 -d -bvs noreply@example.com
            exim4 -d -bv someone@somewhere.com





            share|improve this answer


























              up vote
              0
              down vote













              Check for a "verify = sender" in your Exim acl's, such as the one that executes for the RCPT TO: command (look for acl_smtp_rcpt=xxxxx). That Exim option in an acl checks to make sure the sender is a "valid" (see exim docs for exactly what that means), and you may need to remove it since this is an internal server only sending from fake senders. In a production server, there are better ways to do the same.



              If your acl's are checking the sender when processing the RCPT TO:, like some configurations do, then you can get this message where it looks like the problem is in the recipient when it is actually the sender verify causing the rejection.



              Try running a command-line exim in address verification mode to see which acl's are executing:



              exim4 -d -bvs noreply@example.com
              exim4 -d -bv someone@somewhere.com





              share|improve this answer
























                up vote
                0
                down vote










                up vote
                0
                down vote









                Check for a "verify = sender" in your Exim acl's, such as the one that executes for the RCPT TO: command (look for acl_smtp_rcpt=xxxxx). That Exim option in an acl checks to make sure the sender is a "valid" (see exim docs for exactly what that means), and you may need to remove it since this is an internal server only sending from fake senders. In a production server, there are better ways to do the same.



                If your acl's are checking the sender when processing the RCPT TO:, like some configurations do, then you can get this message where it looks like the problem is in the recipient when it is actually the sender verify causing the rejection.



                Try running a command-line exim in address verification mode to see which acl's are executing:



                exim4 -d -bvs noreply@example.com
                exim4 -d -bv someone@somewhere.com





                share|improve this answer














                Check for a "verify = sender" in your Exim acl's, such as the one that executes for the RCPT TO: command (look for acl_smtp_rcpt=xxxxx). That Exim option in an acl checks to make sure the sender is a "valid" (see exim docs for exactly what that means), and you may need to remove it since this is an internal server only sending from fake senders. In a production server, there are better ways to do the same.



                If your acl's are checking the sender when processing the RCPT TO:, like some configurations do, then you can get this message where it looks like the problem is in the recipient when it is actually the sender verify causing the rejection.



                Try running a command-line exim in address verification mode to see which acl's are executing:



                exim4 -d -bvs noreply@example.com
                exim4 -d -bv someone@somewhere.com






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Oct 23 '15 at 4:40

























                answered Oct 23 '15 at 2:38









                simpleuser

                17512




                17512



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f158660%2fexim4-550-verification-failed-how-to-allow-any-sender%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?