Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: [SOLVED] Could not send message: mail.SEND_FAILURE...Invalid Addresses

  1. #1
    thunder04 is offline Special Member
    Join Date
    Dec 2007
    Location
    Stockton, CA
    Posts
    164
    Rep Power
    7

    Default [SOLVED] Could not send message: mail.SEND_FAILURE...Invalid Addresses

    Hey Everyone,

    We just upgraded from ZCS 5.0.18 to 6.0.5 last Thursday. Ever since then, some users periodically encounter problems sending mail to outside addresses. I cannot figure out a pattern on why this is happening. It happens when creating a new message and when replying. Users receive an error message indicating invalid addresses...but (especially when clicking reply) as far as I can tell there aren't any invalid addresses.

    Here is an example:

    Example 1:

    Code:
    Could not send message: mail.SEND_FAILURE
    method:	SendMsgRequest
    msg:	SMTP server reported: Invalid Addresses
    code:	mail.SEND_FAILURE
    detail:	soap:Sender
    trace:	btpool0-4370://mail.ourserver.org/service/soap/SendMsgRequest:1266885067376:058a757e7e76eb96
    request:	
    
    Body: {
      SendMsgRequest: {
        _jsns: "urn:zimbraMail",
        m: {
          e: [
            0: {
              a: "recipient@theirserver.org",
              p: "Suzanne Recipient",
              t: "t"
             },
            1: {
              a: "sender@ourserver.org",
              p: "Jim Sender",
              t: "f"
             }
           ],
          idnt: "357bc018-9664-4e3f-841d-ab8fabfa9a4d",
          irt: {
            _content: "<17018994.5290.1266884930686.JavaMail.root@cottontail>"
           },
          mp: [
            0: {
              content: {
                _content:
    
     Content removed for privacy...I don't think it's important anyway.
    
    "
               },
              ct: "text/plain"
             }
           ],
          su: {
            _content: "Re: Subject"
           }
         },
        suid: 1266885066892
       }
     },
    Header: {
      context: {
        _jsns: "urn:zimbra",
        account: {
          _content: "sender@ourserver.org",
          by: "name"
         },
        authToken: "(removed)",
        notify: {
          seq: 27
         },
        session: {
          _content: 18777,
          id: 18777
         },
        userAgent: {
          name: "ZimbraWebClient - FF3.0 (Mac)",
          version: "6.0.5_GA_2213.DEBIAN4.0"
         }
       }
     }
    We've NEVER had this problem before, and it's happening with e-mail addresses that people have successfully been e-mailing for a long while. In some cases, if a user tries multiple times (closes e-mail, deletes draft, re-replies or re-creates e-mail), they're successful...but most of the time they are not.

    I worked with a user having this problem and couldn't find any logical reason why it was happening. Nothing stuck out as a possible reason why Zimbra was having trouble. Most of the time it wouldn't work, sometimes it would. The user who was encountering this problem could send/recieve e-mail from many other outside e-mail addresses just fine.

    The weirdest thing is that, in some cases, a user will have trouble replying to a message sent to them by the affected address, but they can compose a new message and there is a 50/50 change it'll work. Vice versa as well.

    I should mention that the upgrade also involved moving to LVM and expanding storage for Zimbra, so I had to copy Zimbra from one partition to another. I used "cp --archive" could this be an issue? Is there a way to verify all ownerships and permissions are correct?

    Where do I start to troubleshoot this?! Any help would be GREATLY appreciated!
    Last edited by thunder04; 02-22-2010 at 06:42 PM.

  2. #2
    veronica is offline Outstanding Member
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    Do you have any recipient checks enabled on MTA ?

  3. #3
    veronica is offline Outstanding Member
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    somehow it appears to me to be a problem of reject_unverified_recipient

  4. #4
    thunder04 is offline Special Member
    Join Date
    Dec 2007
    Location
    Stockton, CA
    Posts
    164
    Rep Power
    7

    Default

    Hmm. I do. Here's my postfix_recipient_restrictions.cf file:

    Code:
    reject_non_fqdn_recipient
    reject_unknown_recipient_domain
    reject_unverified_recipient
    permit_sasl_authenticated
    permit_mynetworks
    reject_unauth_destination
    reject_unlisted_recipient
    check_policy_service inet:127.0.0.1:60000
    %%contains VAR:zimbraMtaRestriction reject_invalid_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_non_fqdn_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_non_fqdn_sender%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_client%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_sender_domain%%
    %%explode reject_rbl_client VAR:zimbraMtaRestrictionRBLs%%
    %%contains VAR:zimbraMtaRestriction check_policy_service unix:private/policy%%
    permit
    I will remove "reject_unverified_recipient" to see if this helps. Does anybody know why this would suddenly be causing a problem?

  5. #5
    thunder04 is offline Special Member
    Join Date
    Dec 2007
    Location
    Stockton, CA
    Posts
    164
    Rep Power
    7

    Default

    Well, the good news is that removing "reject_unverified_recipient" from postfix_recipient_restrictions.cf has seemed to solved the problem. I've asked a few of the users who were having trouble to try again, and they all were successful. Hopefully I'm not premature in stating that it's fixed!

    I am curious, though, on why reject_unverified_recipient was causing this problem. Does anybody have any idea?

  6. #6
    veronica is offline Outstanding Member
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    Its because setting "reject_unverified_recipient" would make postfix send a verification notification to the recipient MTA server which recipient MTA needs to acknowledge. Many MTa don't do that causing mails to be deferred.

  7. #7
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    As Veronica has said that will happen so that unnecessary backscatter is stopped.

  8. #8
    thunder04 is offline Special Member
    Join Date
    Dec 2007
    Location
    Stockton, CA
    Posts
    164
    Rep Power
    7

    Default

    Aha! That makes perfect sense. Thank you for your help!!!

  9. #9
    sridharsagi is offline Intermediate Member
    Join Date
    May 2010
    Posts
    23
    Rep Power
    5

    Default

    Hi All

    I have the same error, i trying to configure RestrictPostfixRecipient

    My out put of postfix_recipient_restriction.cf is below

    check_recipient_access hash:/opt/zimbra/postfix/conf/protected_recipients
    reject_non_fqdn_recipient
    permit_sasl_authenticated
    permit_mynetworks
    reject_unauth_destination
    reject_unlisted_recipient
    %%contains VAR:zimbraMtaRestriction reject_invalid_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_non_fqdn_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_non_fqdn_sender%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_client%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_sender_domain%%
    %%explode reject_rbl_client VAR:zimbraMtaRestrictionRBLs%%
    %%contains VAR:zimbraMtaRestriction check_policy_service unixrivate/policy%%
    permit

    Please help in resolving the issues.

  10. #10
    bornsilly is offline Member
    Join Date
    Feb 2008
    Posts
    12
    Rep Power
    7

    Default

    Hi all,

    I came to this thread because i am having the same issue. Looking at my postfix_recipient_restrictions.cf config i do not have the reject_unverified_recipient entry. I have also noticed that if i retry a few times to send the message that it does get send. My postfix_recipient_restrictions.cf looks as followed:

    %%contains VAR:zimbraServiceEnabled cbpolicyd, check_policy_service inet:127.0.0.1:10031%%
    reject_non_fqdn_recipient
    permit_sasl_authenticated
    permit_mynetworks
    reject_unauth_destination
    reject_unlisted_recipient
    %%contains VAR:zimbraMtaRestriction reject_invalid_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_non_fqdn_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_non_fqdn_sender%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_client%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_hostname%%
    %%contains VAR:zimbraMtaRestriction reject_unknown_sender_domain%%
    %%explode reject_rbl_client VAR:zimbraMtaRestrictionRBLs%%
    %%contains VAR:zimbraMtaRestriction check_policy_service unixrivate/policy%%
    permit

    The problem started suddenly without a single change to the system and I have no idea were to start looking.

    I hope somebody can help me with how to troubleshoot this issue

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 0
    Last Post: 08-23-2009, 03:10 PM
  2. Replies: 2
    Last Post: 06-18-2008, 06:54 AM
  3. Send Message as Distribution List
    By akirsch in forum Administrators
    Replies: 3
    Last Post: 01-18-2007, 11:45 AM
  4. Send error on Firefox/FC3
    By rodrigoccurvo in forum Users
    Replies: 12
    Last Post: 10-22-2005, 11:31 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •