-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot send mail via SMTP #4253
Comments
You'll need to figure it out by investigating the interaction between FreeScout and you mail server. |
Mail server logs the following:
I cannot identify any other helpful logs within FreeScout. The mail server logs indicate to me that the issues lies within FreeScout: The
|
Not sure if this will be helpful or not as I've never used Dovecot for email submission - always postfix before it. Dovecot uses the BURL protocol to enable the submission process. BURL uploads the message to the Sent folder and then submits it. The process can be problematic with different clients - yet Thunderbird does support it. I haven't found a lot in relation to support in the SwiftMailer client that FreeScout uses. The 'clue' in your errors though could be "0 authentication methods". Check the Dovecot auth methods in its conf file. You may want to ensure it includes CRAM-MD5 - eg: auth_mechanisms = plain login cram-md5 hope that at least points you in the right direction. |
@KlausdB 💯 You were right on the money! I hardcoded the authentication method Specifically I added Immediately the testmail ist sent and received. Our dovecot was not configured to accept the default auth mode Changing this config to @freescout-help Maybe make the login mechanism configurable as well? |
Hello, we have encountered a similar problem. Our support is currently working on version 1.8.140.
App log:
Our administrator tried to make changes to the files described above, but this did not help to solve the problem. Perhaps you can suggest some other options for resolving this situation? PHP version: 8.2.22 |
@SergeyMi88 |
@KlausdB
Restrictions:
I would like to draw your attention to the fact that FreeScout and our mail server worked perfectly for a long time. The problems started after the release of version 1.8.141. We tried to install several more subsequent releases that mentioned changes in the mail operation, but the problem remained unresolved. As a result, we had to roll back to version 1.8.140, which is what our main project is currently running on. |
@SergeyMi88 There was no changes made in the emails sending subsystem - it was using Swiftmail library to send emails before and it's using it now. |
OK @SergeyMi88 I can see that you are telling Postfix to use Dovecot for authentication, so the issue appears the same as the previous user who resolved theirs in the freescout code instead of the server. Their instance was talking to Dovecot direct however. If not that, check the dovecot configuration for auth. Is it listening and responding correctly to postfix. Is there a: If that is problematic, you could look at setting up postfix to auth smtp such as here: Note that I have nothing to do with Freescout, just a user trying to help. I'm on version 1.8.153 and looking back through the changelog suggests there were some encryption method changes made at your release level. It's not specifically for smtp, but can effect it. |
@freescout-help I have identified three changes between 1.8.140 and 1.8.153 that could cause changes in behaviour.
My guess is that one of these changes also changed the default authentication methods that Swiftmailer will use to try and establish a connection -- in particular setting the authentication methods to |
@sr-fias You are right. @SergeyMi88 Try to change this line https://github.com/freescout-help-desk/freescout/blob/dist/overrides/swiftmailer/swiftmailer/lib/classes/Swift/SmtpTransport.php#L42 to the following:
|
We made this change on our test and main server and it helped, mail works without errors. Thanks to everyone for the help. |
@SergeyMi88 should be fixed in 0280e4f |
PHP version: 8.2.22
FreeScout version: 1.8.153
Database: MySQL
Are you using CloudFlare: No
Are you using non-official modules: No
We are currently testing FreeScout via the Docker Container provided by tiredofit.
The system is up and running and IMAP connection to the mailbox is working fine and fetching mail.
But we have an issue with sending mail. Testing the settings always leads to a generic error in a red box:
Server, username and password are the same between SMTP and IMAP. SMTP port is 587.
One thing that may be uncommon in our setup: The authentication username differs from the email address.
Additionally below the test field a yellow box shows the following SMTP connection log:
If we leave the username field empty we get a longer error in a red box:
followed by a long string of connection logs with multiple retries of sending a mail and authentication errors inbetween. This was done to verify that the connection to the SMTP server is actually working.
So the connection to the SMTP server is functioning but somehow the authentication using username/password is failing. Same username/password works for IMAP and in Thunderbird, which is why we expect some sort of bug with FreeScout.
Can anyone help us out?
Thanks!
The text was updated successfully, but these errors were encountered: