• Resolved BooMeranGz

    (@boomerangz)


    Hi,

    We have configured WorkSpace to be able to use its SMTP with our mail IP, due to SPAM list problems.

    Our system is working fine with Google WorkSpace, but we have not been able to get ASE to allow us to use the default Google SMTP server “smtp-relay.gmail.com” (SMTP Port 587, TLS) without username and password, which is the way WorkSpace uses it (since the IP automatically goes to the whitelist)

    We have tested this with fluentSMTP and it does allow us to do so.

    Could you please check this?

    Thanks.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Bowo

    (@qriouslad)

    Thread Starter BooMeranGz

    (@boomerangz)

    That documentation is correct, but not for this case.

    Google Workspace allows you to use the account without 2FA, and has the option to use the smtp relay without credentials (neither username nor password), and I always use it in business accounts where I have already linked the MX dedicated IPs with their DNSs for each client.

    I understand that ASE should have the option to do an SMTP relay when the “smtp-relay.gmail.com” is entered, since it will only work if it is linked to the correct IP on the user’s side.

    Otherwise ASE forces me to create a 2FA authentication factor, which complicates the existence of the same clients.

    Greetings.

    Plugin Author Bowo

    (@qriouslad)

    @boomerangz it’s not a scenario that’s been tested and implemented in ASE. I suggest using FluentSMTP for your current requirement.

    Feel free to share how you’re setting it up on FluentSMTP (screenshots perhaps?) for future reference.

    Thread Starter BooMeranGz

    (@boomerangz)

    Hi,

    Yes, for the moment I will use Fluent. But I would like you to solve that issue in ASE, it would be useful for me and for many users who need that specific SMTP configuration for Google Workspace without 2FA.a

    Also, I have bought the lifetime license of “ASE” 1 year ago, and I prefer to use the options of this add-on before installing something repetitive, it is the idea that ASE promotes…

    Some screenshots:
    image1.png
    image2.png
    image4.png

    Regards.

    Plugin Author Bowo

    (@qriouslad)

    Thanks for sharing the screenshots. They are useful when and if this issue is revisited in the future.

    FYI, so far, you’re the first ASE user reporting this issue, i.e. using this specific configuration with ASE.

    Thread Starter BooMeranGz

    (@boomerangz)

    Ok, it’s strange, since it’s a workspace option to make forwarding more comfortable or easier (although surely less secure, depending on how you look at it)

    Saludos.

    Plugin Author Bowo

    (@qriouslad)

    @boomerangz can you try modifying the following line in ASE Free / Pro?… it’s inside the /classes/class-email-delivery.php file. Line 57 in ASE Free and line 84 in ASE Pro:

    $phpmailer->SMTPAuth = true;

    into

    $phpmailer->SMTPAuth = false;

    and check whether that allows you to deliver email using workspace’s relay configuration.

    • This reply was modified 1 week, 2 days ago by Bowo.
    Thread Starter BooMeranGz

    (@boomerangz)

    Thanks for taking care of it.

    I made the change in ASE Pro.
    ASE now allows sending. But they don’t reach their destination.

    It’s probably because it doesn’t allow saving the screen without a password (it can’t be blank), deleting this field should probably work.

    image 1
    image 2

    • This reply was modified 1 week, 1 day ago by BooMeranGz.
    Plugin Author Bowo

    (@qriouslad)

    @boomerangz if so, try deleting or commenting out the following lines, which is several lines below the $phpmailer->SMTPAuth = false; line:

    $phpmailer->Username = trim( $smtp_username );
    $phpmailer->Password = trim( $smtp_password );

    Then try sending a test email again.

    Plugin Author Bowo

    (@qriouslad)

    Additionally, above the $phpmailer->SMTPAuth = false; line, try changing this line

    if ( ! empty( $smtp_host ) && ! empty( $smtp_port ) && ! empty( $smtp_security ) && ! empty( $smtp_username ) && ! empty( $smtp_password ) ) {

    into:

    if ( ! empty( $smtp_host ) && ! empty( $smtp_port ) && ! empty( $smtp_security ) ) {

    and try sending a test email.

    Thread Starter BooMeranGz

    (@boomerangz)

    Perfect!, I have modified those fragments and it works very well, even sending to Gmail, Hotmail/Outlook/Live and Yahoo.

    Then you will only have to add an option (chekbox) to cancel the authentication in cases where it is required?

    Do you want me to attach the modified code in some way?

    Plugin Author Bowo

    (@qriouslad)

    @boomerangz that’s great! I should be able to provide an additional option whether to use authentication or not, and it should work for your situation. Let me add this on a to-do list. Hopefully can implement in the near future, ideally the release after the next one.

    Thread Starter BooMeranGz

    (@boomerangz)

    Thank you very much @qriouslad

    I will be waiting for the next updates.

    Saludos.

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.