Expiration emails being sent to bitnami@domain.com instead of administration email

I have my site hosted through Lightsail on AWS. I installed SSL on my site using the /opt/bitnami/bncert-tool command. During the configuration, I entered my admin email address. But for some reason, I am receiving bounce notifications that letsencrypt is attempting to send (what I believe are expiration emails) to bitnami@domain.com. I'm omitting the domain for my client's privacy, but the domain is mostly irrelevant because it's happening to at least 2 other sites so this seems like a larger problem. The original email header:

"headers":[{"name":"Received","value":"from domain.com (ec2-15-xxx-xxx-111.ca-central-1.compute.amazonaws.com [15.xxx.xxx.111]) by email-smtp.amazonaws.com with SMTP (SimpleEmailService-d-JNPSWR36C) id vILwu73rXmEOehuBzNvN for bitnami@domain.com; Thu, 29 Jul 2021 00:00:03 +0000 (UTC)"},{"name":"Received","value":"by domain.com (Postfix, from userid 1000) id 52BE8C0576; Thu, 29 Jul 2021 00:00:03 +0000 (UTC)"},{"name":"From","value":"root@domain.com (Cron Daemon)"},{"name":"To","value":"bitnami@domain.com"},{"name":"Subject","value":"Cron bitnami@ip-172-26-2-41 sudo /opt/bitnami/letsencrypt/lego --path /opt/bitnami/letsencrypt --email="administration@myemail.com" --http --http-timeout 30 --http.webroot /opt/bitnami/apps/letsencrypt --domains=domain.com renew && sudo /opt/bitnami/apache2/bin/httpd -f /opt/bitnami/apache2/conf/httpd.conf -k graceful # bncert-autorenew"},{"name":"MIME-Version","value":"1.0"},{"name":"Content-Type","value":"text/plain; charset=UTF-8"},{"name":"Content-Transfer-Encoding","value":"8bit"},{"name":"X-Cron-Env","value":"<SHELL=/bin/sh>"},{"name":"X-Cron-Env","value":"<HOME=/home/bitnami>"},{"name":"X-Cron-Env","value":"<PATH=/usr/bin:/bin>"},{"name":"X-Cron-Env","value":"<LOGNAME=bitnami>"},{"name":"Message-Id","value":"20210729000003.52BE8C0576@domain.com"},{"name":"Date","value":"Thu, 29 Jul 2021 00:00:03 +0000 (UTC)"}],"commonHeaders":{"from":["Cron Daemon root@domain.com"],"date":"Thu, 29 Jul 2021 00:00:03 +0000 (UTC)","to":["bitnami@domain.com"],"messageId":"20210729000003.52BE8C0576@domain.com","subject":"Cron bitnami@ip-172-26-2-41 sudo /opt/bitnami/letsencrypt/lego --path /opt/bitnami/letsencrypt --email="administration@myemail.com" --http --http-timeout 30 --http.webroot /opt/bitnami/apps/letsencrypt --domains=domain.com renew && sudo /opt/bitnami/apache2/bin/httpd -f /opt/bitnami/apache2/conf/httpd.conf -k graceful # bncert-autorenew"}}}

If anyone can shed some light on this, I would really appreciate it.

1 Like

Those are being sent by the cron daemon on your server, not by Let's Encrypt. (See the "From" header, and the Recieved headers show it coming through AWS SES which isn't the email service that Let's Encrypt uses last I knew.)

I don't know much (or really anything) about bitnami, but you should be able to set the MAILTO= variable in your cron job somewhere.


I've tried your fix and will let you know if it works. I am optimistic. Thanks for catching that header. I've pretty much gone cross-eyed from all this.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.