• Resolved eWallz

    (@archonic08)


    Hi, i’m just trying out the SMTP features under the Utilities section today, but could not get it to work. The send test email taking too long. The error_log showing as below. When i disable it, then install other smtp plugin and use the same smtp settings, email sending worked without issues. Same smtp setting using another popular smtp plugin also working. Just that the same settings does not work with ASE…if the smtp function in ASE can be use, I don’t need to add extra plugin to get the same purpose.

    [04-Aug-2024 14:13:28 UTC] Connection: opening to mail.domain.com:465, timeout=300, options=array()
    [04-Aug-2024 14:13:29 UTC] Connection: opened
    [04-Aug-2024 14:15:16 UTC] CLIENT -> SERVER: QUIT

    [04-Aug-2024 14:15:16 UTC] SMTP INBOUND: “”
    [04-Aug-2024 14:15:16 UTC] SERVER -> CLIENT:
    [04-Aug-2024 14:15:16 UTC] SMTP ERROR: QUIT command failed:
    [04-Aug-2024 14:15:16 UTC] Connection: closed

    • This topic was modified 3 months, 3 weeks ago by eWallz.
Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author Bowo

    (@qriouslad)

    @archonic08 thanks for reporting this. May I know which email hosting is this configured for? Which other plugins were you able to use the same settings in? It’s OK to mention the plugin name.

    Thread Starter eWallz

    (@archonic08)

    I use regular cpanel hosting. Create an email acc using the same domain and use the smtp setting.

    the 2 smtp plugin that’s working with the same setting are fluentsmtp and post smtp.

    Having the same issue here. I’m using a Microsoft Exchange account with an application password for SMTP authentication. Works just fine under FluentSMTP, but under ASE with the same settings, the test email just spins endlessly. I’ve left it running for a solid 15 minutes but still nothing, and no debug output in my debug.log either. Attempting to send emails from elsewhere on the site does nothing too.

    I’m suspecting STARTTLS, but that’s just a hypothesis.

    • This reply was modified 3 months, 1 week ago by lulech23.
    Plugin Author Bowo

    (@qriouslad)

    @archonic08 do you mind sharing which hosting provider company and which hosting package you are seeing this issue on? I may need to diagnose the issue directly on that same environment.

    @lulech23 thanks for reporting. This is a known issue with MS Exchange account. I suggest continue using FluentSMTP for now until this is resolved in ASE.

    Thread Starter eWallz

    (@archonic08)

    @qriouslad I’m using linux cpanel hosting on verpex.com. Reseller pro plan. I will test this on my other cpanel on different provider and update you the results.

    @qriouslad Figured something out. Turns out that if I enable “Force the usage of the sender name/email defined above” I’m able to send over Exchange SMTP. I suspect either $phpmailer->From or $phpmailer->FromName is not being set in some conditions if $smtp_force_from is not enabled.

    In my case, it’s no problem to force the sender name/email, so I will go with this for now!

    Thread Starter eWallz

    (@archonic08)

    @qriouslad i tested the smtp features on a different cpanel hosting provider and its working fine. So I think it’s hosting specific issue.

    Plugin Author Bowo

    (@qriouslad)

    @lulech23 thanks for testing further. That is useful debugging info. I’ll be sure to keep this in mind when I have a chance to test with a Microsoft Exchange account.

    @archonic08 thanks for testing further. Would be useful if you can figure out what might be different with the reseller pro hosting. Maybe try a different port number and security settings there? Sometimes cpanel hosting provides a couple of routes. e.g. Non-SSL via port 587, and SSL via port 465.

    Plugin Author Bowo

    (@qriouslad)

    Marking this resolved for now.

    Just chiming in to say that I tried the SMTP setup with Google Workspace using their app password (specified here: https://www.wpase.com/documentation/gmail-google-workplace-email-smtp-host-delivery/) and test emails are not being sent and errors aren’t being logged in debug.log. I know that Google depricated “less secure apps” this past summer, and I wonder if that has something to do with it.

    I can get emails to send using a cPanel email account. But I sure need to send email via my Google Workspace account.

    Thanks.

    Plugin Author Bowo

    (@qriouslad)

    @blatka apologies for the belated response. Maybe. I’m using @gmail for SMTP and it is working fine. It’s possible Google Workspace has limitations in using an app password. I’ll need to test this when I have the chance.

    I am experiencing a failure with Gmail. My site was sending emails fine with fluentSMTP, but when I use the same settings in ASE, I get this in my PHP error log:

    [15-Nov-2024 21:14:37 UTC] SMTP INBOUND: “534-5.7.9 Application-specific password required. For more information, go to”
    [15-Nov-2024 21:14:37 UTC] SMTP INBOUND: “534 5.7.9 https://support.google.com/mail/?p=InvalidSecondFactor d75a77b69052e-4635ab5d1f5sm23964201cf.74 – gsmtp”
    [15-Nov-2024 21:14:37 UTC] SERVER -> CLIENT: 534-5.7.9 Application-specific password required. For more information, go to
    534 5.7.9 https://support.google.com/mail/?p=InvalidSecondFactor d75a77b69052e-4635ab5d1f5sm23964201cf.74 – gsmtp

    [15-Nov-2024 21:14:37 UTC] SMTP ERROR: Password command failed: 534-5.7.9 Application-specific password required. For more information, go to
    534 5.7.9 https://support.google.com/mail/?p=InvalidSecondFactor d75a77b69052e-4635ab5d1f5sm23964201cf.74 – gsmtp

    Plugin Author Bowo

    (@qriouslad)

    @nitrospectide my setup wtih a gmail application password is working well. Perhaps you were authenticating differently in FluentSMTP? Using Application Client ID & Application Client Secret? With ASE, you’ll need to use an app password.

    Plugin Author Bowo

    (@qriouslad)

    @blatka I just tested with a google workplace email, and the steps outlined in https://www.wpase.com/documentation/gmail-google-workplace-email-smtp-host-delivery/ still works. Please make sure your app password is up to date or new. There’s a chance you’re using an old app password google revoked because you changed your email password at some point. In that case, you need to create a new app password to use in ASE.

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