Skip to main content

GSuite Delivery Problem

The Emperor
I am having an issue by using GSuite split delivery and having the latest version [76.0.11] of WHM/cPanel did not help Sender (somesender@gmail.com) who sends to my non-GSuite mailbox user (nonGSuiteuser@example.com) who is set to split to my Local Mail Exchanger gets: [quote] Message not delivered Your message couldn't be delivered to nonGSuiteuser@example.com because the remote server is misconfigured. See technical details below for more information. The response from the remote server was: 550 Please turn on SMTP Authentication in your mail client. mail-ua1-f72.google.com [209.85.222.72]:48632 is not permitted to relay through this server without authentication.
exim_mainlog of my Local Mail Exchanger [quote] 2018-12-19 17:05:50 H=mail-ua1-f72.google.com [209.85.222.72]:48632 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F= rejected RCPT : Rejected relay attempt: '209.85.222.72' From: 'somesender@gmail.com' To: 'nonGSuiteuser@example.com'
  • Non-GSuite user email address (nonGSuiteuser@example.com) does have mailbox created on my Local Mail Exchanger
  • Routings are all correct set in the GSuite Advanced settings
  • All other GSuite users have no problems on receiving emails, like the last 6 years do.
None of solutions on old threads did help,

Comments

8 comments

Date Votes
  • GOT
    What's the setting in the dns zone under mail exchanger? If its set to remote, then it is going to always reject the emails for that domain regardless if the account exists or not.
    0
  • The Emperor
    What's the setting in the dns zone under mail exchanger? If its set to remote, then it is going to always reject the emails for that domain regardless if the account exists or not.

    Yes it is in remote because it is required to setup the Gmail MX Servers, however if that is what it blocks the whole process, it shouldn't be any record or footprint to the exim_mainlog
    0
  • GOT
    If its set to remote, then exim is going to reject it regardless. I'm not clear how you are expecting to split the mail delivery exactly. Can you elaborate on how you are expecting that to work?
    0
  • The Emperor
    If its set to remote, then exim is going to reject it regardless. I'm not clear how you are expecting to split the mail delivery exactly. Can you elaborate on how you are expecting that to work?

    The concept is simple I have 10 GSuite mailbox addresses for @example.com and now I want to have 5 more mailbox addresses for @example.com that they will not be registered as GSuite users, hence the mails that are sent to these addresses will be routed and fully managed in their mailboxes on my server. and by fully I mean by not using practices like creating forwarding filters on GSuite alias addresses for those mail addresses.
    0
  • GOT
    I'm not aware of any way to do what you are wanting, honestly. Perhaps someone else will weigh in with a solution. The MX records have to point to a single place, the internet as a whole does not look up mx records based on the name portion of an email address.
    0
  • The Emperor
    I'm not aware of any way to do what you are wanting, honestly. Perhaps someone else will weigh in with a solution. The MX records have to point to a single place, the internet as a whole does not look up mx records based on the name portion of an email address.

    @GOT I appreciate your honesty. I hope someone else will figure out a solution for this issue.
    0
  • The Emperor
    Ok the following partially worked for me and I am going to share; I added into /etc/localdomains the domain that I was trying to make GSuite Split Delivery to work. Apparently the domain for whatever reason was not in localdomain and it has to be both in /etc/localdomains & /etc/remotedomains Now, with the correct
    0
  • cPanelLauren
    This is definitely configurable, you need to point the MX records to Gsuite as you would normally though, then configure split delivery in their interface. This is discussed in the threads here:
    Apparently the domain for whatever reason was not in localdomain and it has to be both in /etc/localdomains & /etc/remotedomains

    This should be set to one or the other local or remote, if the domain is present in localdomains mail sent from the server to the same domain will ONLY be delivered locally as the routing indicates as such. This might be a solution for you but you may want to read it over     the backup mx selection should be what you want
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post