Smtp not working

[lament sedge]

Human support please

[lament sedge]

@slate flame maybe i can send a screenshot in here?

[slate flame]

Yes, please upload a screenshot of the error.

[slate flame]

@lament sedge are you self hosting locally, or is it cloud hosted?

[lament sedge]

self hostet. and the email comunication is working with a normal python script on the server

[lament sedge]

port is open

[slate flame]

<@&725604214666952714> @woven kernel @fallow tendon any ideas what the issue could be here?

@lament sedge could you send a copy of your server logs to [email protected] please?
https://docs.appsmith.com/getting-started/setup/instance-management/how-to-get-container-logs

[lament sedge]

the complete?

[slate flame]

either the full logs, or try connecting SMTP again so it's recent, then copy the related logs.

[lament sedge]

its done. and its a really big .txt file 1.7mb

hope u got something

[woven kernel]

@lament sedge Can you please try to use port 587 instead of 465?

[lament sedge]

my email hoster dont use 587

[woven kernel]

Does your email provider have TLS support? Can you try to use port 587 with TLS enabled?

[lament sedge]

Same issue

[woven kernel]

Ok, our team is checking the logs you sent per email and will get back to you

[lament sedge]

thx

[lament sedge]

Some News?

[lament sedge]

👀

[lament sedge]

@slate flame are there some news? Cause I want to continue

[woven kernel]

Our team still needs some time to check this

[lament sedge]

ok

[woven kernel]

Thank you for your patience while I consulted our team.
Please follow the below steps to telnet to the host:

• enter the container:
  docker exec -it -u root appsmith bash
• install telnet:
  apt update; apt-get install -y telnet

telnet host port
and check if you can connect to the host via the port

Or you can do this after exec into the container:

• apt update; apt-get install inetutils-ping
• ping <smtp-host>

Let us know if the above steps work or if you get any errors.
Additionally, check if inbound and outbound rules are set to allow traffic on 465.

[lament sedge]

👀

[lament sedge]

btw, telnet is blocked by datalix. but the ping was successfully

[woven kernel]

@lament sedge The port 465 is the default port for implicit TLS, which we do not support. Appsmith only supports explicit TLS (STARTTLS) at this juncture. Can you please confirm with the admin of your SMTP server if explicit TLS (or STARTTLS) is supported? If yes, then on which port?

[lament sedge]

my hoster uses explicit tls on port 465

[lament sedge]

👀

[lament sedge]

Some News?

Cause i need the Mail settings

[woven kernel]

Sorry for the delay. Our team still needs some time to look into this.

[lament sedge]

Ok

[lament sedge]

Some news?

[trim tundra]

Sync internally,

[rare mica]

Hello! I'm AppySmith, your support bot for Appsmith queries. I see you're experiencing difficulties with SMTP configuration on Appsmith.

The error message "Bad request: Exception reading response" suggests that Appsmith is having trouble connecting to your SMTP server. Given that the SMTP settings are working with a PHP script, this appears to be related to how Appsmith interacts with your email provider.

To assist you better, please provide me with the following information:

1. Which email provider are you using?
2. Can you confirm that the SMTP settings (host, port, username, and password) are correctly entered in Appsmith?
3. Is SSL/TLS correctly configured for the SMTP server on Appsmith?
4. Have you checked your Appsmith server logs for more specific error messages regarding the SMTP connection failure?
5. Are there any network policies or firewalls that might be blocking traffic from your Appsmith instance to the SMTP server?

This information will help in narrowing down the cause of the issue.

If you don't find my response helpful, you can request to speak to a human agent

[lament sedge]

I use datalix.de. the mail in on their host system under plesk. username password and so on is 100% correct.

What exactly is meant by point 3? I entered everything in the interface and yes. I sent you the logs by email. No, nothing is blocked. I also have a Python script with the same data on the server where Appsmith is running and the email was sent out with it.

[lament sedge]

Hm ok

[rare mica]

Thank you for providing additional details. Given that you're sure the credentials are correct and no network blockages are present, let's review the TLS/SSL settings.

By point 3, I was referring to the encryption method used while sending emails. Since you mentioned that your email host uses explicit TLS on port 465, it's important to ensure Appsmith is set up to use STARTTLS with the correct port.

However, typically port 465 is used for implicit SSL/TLS, and Appsmith supports explicit TLS (STARTTLS). This might be causing the issue. Usually, STARTTLS is used with port 587 or sometimes port 25.

Here's what we can try:

1. Verify that your email provider supports STARTTLS and find out the correct port for STARTTLS.
2. Make sure you have chosen the STARTTLS option in the Appsmith email configuration.
3. Check the Appsmith configuration to use the correct port provided by your email host for STARTTLS.

If you have already sent the logs via email as mentioned previously, the Appsmith team will be checking for specific error messages to help diagnose the issue.

If you could check with your email provider about the support for explicit TLS (STARTTLS) and the correct port, and confirm that information here, that would be the next step in troubleshooting this issue.

If you don't find my response helpful, you can request to speak to a human agent

[lament sedge]

It's not the port or TLS or anything like that. As I said, it works with a normal Python script

[rare mica]

I understand that the SMTP configuration works with a Python script on the same server, which does suggest that the SMTP settings and network are correctly configured outside of Appsmith. There may be something specific to Appsmith that is causing the SMTP connection to fail.

Could you please confirm the following for me?

• The Appsmith version you are using.
• Do you have the correct SMTP settings configured within Appsmith, and are they identical to the ones used by your Python script?
• Have you ensured the SMTP plugin/module is enabled and configured correctly in Appsmith?
• Have you checked the advanced settings for any relevant options that might need to be adjusted for the SMTP connection?

I will need only the Appsmith version you are using to proceed with troubleshooting further, as it will help me provide you with version-specific guidance.

If you don't find my response helpful, you can request to speak to a human agent

[lament sedge]

the settings are all correct. the version should be the latest. I don't know what is meant by SMTP plugin

[rare mica]

If you are running the latest version of Appsmith and have confirmed that the settings are correct, we should check the Appsmith application logs for any errors related to SMTP that could help identify the issue.

Regarding the SMTP plugin/module, Appsmith has integrations (similar to plugins) for different functionalities, including email, and I was referring to the email configuration settings on your Appsmith instance where you set up SMTP.

Since you've already sent the logs via email, the Appsmith team will likely be reviewing those for any specific errors. However, I can help you identify potential issues if you can share the error messages related to SMTP from the Appsmith server logs. If you have access to the logs on your server, please check them for any recent error messages that pertain to SMTP or email sending failures.

If that's not feasible or you would prefer the assistance of the Appsmith support team, let me know, and I will advise on the next steps. If you can share the Appsmith server logs here (please make sure there's no sensitive information in what you share), I can help analyze them directly.

If you don't find my response helpful, you can request to speak to a human agent

[lament sedge]

I think the team can help better. because the ai somehow repeats a lot

[rare mica]

Someone from our team will reach out to you on this thread. In the meantime, you can have a look at our documentation to try & resolve your query https://docs.appsmith.com?utm=bot

[rare mica]

Hello! I'm Amelia with Appsmith Support. ?
To further troubleshoot this issue, please run the following command and send us the entire output:

echo 'From: [email protected]
To: [email protected]
Subject: Test from LittleTools.app
Date: '"$(date +'%a, %d %b %Y %H:%m:%S')"'

hello' | curl -v smtps://hostname:465 --mail-from '[email protected]' --mail-rcpt '[email protected]' --user 'username:password' --upload-file -

Please ensure you replace the from and to addresses, SMTP host, username, and password, and run the final command from inside your container.

[lament sedge]

Thats what i got back

[lament sedge]

Is This helpful?

[rare mica]

Thank you for sending the output. Our team is checking it and will get back to you.

[lament sedge]

Ok

[rare mica]

The curl command failed to send the email because you are using a self-signed certificate. This is not secure and Appsmith does not support it. Our team's recommendation is to get a proper signed TLS certificate for the server as a solution.

[lament sedge]

for the myappsmith.mydomain.de domain?

[rare mica]

No, the issue is that your email provider uses a self-signed certificate. This is an issue with the SMTP server.

[lament sedge]

I have now tried again with webmail.mydomain.de. same problem. but there is a lets encrypt cert installed

or it is mydomain.de but there is the same issue

[rare mica]

Can you share the output of the command for the other email server as well?

[lament sedge]

its working

[lament sedge]

with this script

i got the mail

but this isnt working

[rare mica]

Can you please confirm if explicit TLS (or STARTTLS) is supported by this other email service provider, and if yes, on which port?

[lament sedge]

I already said above. port 465 and explicit TLS

[lament sedge]

👀

[lament sedge]

<@&725605013220622356> ?

[fallow tendon]

@lament sedge We are still actively looking into the cause of this issue. Thank you for your patience. We will provide an update here when we have a resolution for you.

[rare mica]

@lament sedge Can you please try to run this other command and let us know if it works:

echo 'From: [email protected]
To: [email protected]
Subject: Test from Appsmith
Date: '"$(date +'%a, %d %b %Y %H:%m:%S')"'

hey' | curl smtp://hostname:587 --mail-from '[email protected]' --mail-rcpt '[email protected]' --user 'username:password' --ssl-reqd --upload-file -

[lament sedge]

connection refused

[rare mica]

Is it possible to get port 587 opened with explicit TLS support, then try the command again? If the curl command is able to send the email, then so should Appsmith.

[lament sedge]

I asked the owner. He said it is not possible.

[rare mica]

If it is not possible to get a port opened with explicit TLS support, then it won't work in Appsmith and you will have to use another email service provider that supports it.

[lament sedge]

Ok