1

Topic: SMTP error 454

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.5.1 MARIADB edition.
- Deployed with iRedMail Easy or the downloadable installer? Downloadable installer.
- Linux/BSD distribution name and version: Debian 10.11
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

When I try to send an email from Roundcube I get SMTP error 454, I tried checking other topics on the matter but I can't seem to fix it. I'll attach related log files below.

Post's attachments

dovecot.log 2.97 kb, 1 downloads since 2022-02-09 

mail.log 925.71 kb, 2 downloads since 2022-02-09 

php-fpm.log 294.16 kb, 1 downloads since 2022-02-09 

php7.3-fpm.log 9.43 kb, 1 downloads since 2022-02-09 

You don't have the permssions to download the attachments of this post.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: SMTP error 454

Your maillog contains many messages about being unable to allocate memory, did you already restart the server?

Also, I see in the same log that you have certificate issues which might be the probable cause for error 454.

3 (edited by FranGamer1892 2022-02-10 05:58:28)

Re: SMTP error 454

alm wrote:

Your maillog contains many messages about being unable to allocate memory, did you already restart the server?

Also, I see in the same log that you have certificate issues which might be the probable cause for error 454.

I restarted the server and the problem persists. What could I do about my certificates? Here's some config files just in case. Thanks.

PS: These certificates were generated automatically by another program a few days ago. I didn't generate them for iRedMail particuarly, but since when I was going to certbot said they were the same, I just used the old ones:

"You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry."

Post's attachments

dovecot.conf 12.95 kb, 1 downloads since 2022-02-09 

main.cf 12.22 kb, 1 downloads since 2022-02-09 

You don't have the permssions to download the attachments of this post.

4 (edited by alm 2022-02-10 06:40:10)

Re: SMTP error 454

Did you follow all the steps in https://docs.iredmail.org/letsencrypt.html ?

Did it fail directly after changing the certificate? If so, I think you need to re-check everything you did.

I see the certificate is created February 8th (yesterday) and is a valid certificate when I connect to your servers' webpage. This means that NGINX works and the certificate itself should be correct.

PS. I see that you changed the paths to the certificate files in main.cf and dovecot.conf files, that is different from the advised steps. The advise is to use symbolic links so that the files don't have to change and you will stay with the default setup. Not that it can't work that way but is more prone to errors because you have to change more files.

5

Re: SMTP error 454

Thanks! I got the messages working. Now time to fix this :-/ https://www.mail-tester.com/test-kiyui5ff8
(I think I got this though)