[Bug]: SMTP issue with Oracle Cloud Email Delivery

[db509]

Issue Description

Good morning everyone,
After installing OpenSign on Docker on Oracle Cloud, I'm experiencing an issue with sending emails using Oracle Cloud's Email Delivery service.
I'm using Oracle Linux 8 as the instance operating system.
The OpenSign system is then published via an Nginx container and the load balancer is protected with a WAF.
Everything seems to be working except sending emails.
I attach an extract of the configuration files I use to deploy via a Gitlab pipeline

1. .env

Email mailgun or set SMTP_ENABLE true to use SMTP config (The app will not initialize if any of these 3 variables are not set) *********************************************************************************************************************

SMTP_ENABLE=true
SMTP_HOST=smtp.email.eu-milan-1.oci.oraclecloud.com
SMTP_PORT=587
SMTP_USER=***
SMTP_PASS="pwd"
SMTP_SECURE=true

--- Identità del Mittente ---

MAIL_FROM_ADDRESS=noreply@floora.it
SENDER_MAIL=noreply@floora.it
MAIL_FROM=noreply@floora.it
SMTP_FROM_ADDRESS=noreply@floora.it
MAIL_FROM_NAME="OpenSign Floora"
SMTP_MAIL_FROM=noreply@floora.it

--- Mailgun (Configurazione disattivata) ---

Queste non vengono usate se SMTP_ENABLE=true

#MAILGUN_API_KEY=
#MAILGUN_DOMAIN=erasoluzioni.it
#MAILGUN_SENDER=noreply@floora.it

2. floora.it.har

"queryString": [],
"cookies": [],
"headersSize": 782,
"bodySize": 1104,
"postData": {
"mimeType": "application/json",
"text": "{"replyto":"noreply@floora.it","extUserId":"ZtJ3043ezG","recipient":"dario.buso@floora.it","subject":"No reply has requested you to sign \"Fattura\"","from":"noreply@floora.it","html":"

Hi Dario,

We hope this email finds you well. No reply has requested you to review and sign "Fattura".

Your signature is crucial to proceed with the next steps as it signifies your agreement and authorization.

<a href=\"https://***.floora.it/login/SzVKNmRyQ1NBUC9kYXJpby5idXNvQGZsb29yYS5pdC9zYzFURFdybzZK\" rel=\"noopener noreferrer\" target=\"_blank\">Sign here

If you have any questions or need further clarification regarding the document or the signing process, please contact the sender.

Thanks

Team OpenSign™

 

"}"
}

3. docker-compose.yml

services:
server:
image: opensign/opensignserver:main
container_name: opensign-server
dns:
- 169.254.169.254 # DNS Interno Oracle Cloud
- 8.8.8.8 # DNS Google (Backup)
- 1.1.1.1 # DNS Cloudflare (Backup)
restart: always
volumes:
- opensign-files:/usr/src/app/files
depends_on:
- mongo
env_file: .env
environment:
- NODE_ENV=production
- TRUST_PROXY=true
networks:
- dmz-docker-net
mongo:
image: mongo:latest
container_name: opensign-mongo-db
restart: always
volumes:
- data-volume:/data/db
ports:
- "27018:27017"
networks:
- dmz-docker-net
client:
image: opensign/opensign:main
container_name: opensign
restart: always
depends_on:
- server
env_file: .env
networks:
- dmz-docker-net
caddy:
image: caddy:latest
container_name: opensign-caddy
restart: always
ports:
- "3001:3001"

- "4443:443"

- "4443:443/udp"

env_file: .env
volumes:
  - ./Caddyfile:/etc/caddy/Caddyfile
  - caddy_data:/data
  - caddy_config:/config
networks:
  - dmz-docker-net

volumes:
data-volume:
name: "opensign-data-volume"
web-root:
name: "opensign-web-root"
opensign-files:
name: "opensign-files"
caddy_data:
name: "opensign-caddy_data"
caddy_config:
name: "opensign-caddy_config"

--- RETE CONDIVISA ---

Usiamo la stessa rete di Nginx Proxy

networks:
dmz-docker-net:
external: true
name: dmz-docker-net

4. nginx.conf

events {
worker_connections 1024;
}

http {
# Impostazioni generali per i buffer (inserite nel blocco http)
large_client_header_buffers 4 64k;
client_max_body_size 1G; # This has to be larger than your largest model
# Aggiunta per OpenSign
include /etc/nginx/mime.types;
default_type application/octet-stream;
# Server per la gestione delle richieste HTTPS

# ------------------------------------------------------------
# Configurazione OPENSIGN
# ------------------------------------------------------------
 server {
        listen 443 ssl;
        server_name ***.floora.it;

        # Recommended since you are using SSL
        http2 on;

        ssl_certificate /etc/nginx/ssl/floora_it.crt;
        ssl_certificate_key /etc/nginx/ssl/floora_it.key;
        # Definisci il resolver di Docker (IP standard interno)
        resolver 127.0.0.11 valid=30s;
        #--- FRONTEND CLIENT ---
       location / {

           set $upstream_opensign http://opensign-caddy:3001;
           # Usa la variabile nel proxy_pass
           proxy_pass $upstream_opensign;
          
           # Se il contenuto è compresso (gzip), sub_filter non può leggere/modificare il testo.
           proxy_set_header Accept-Encoding "";

           proxy_set_header Host $host;
           proxy_set_header X-Real-IP $remote_addr;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
           proxy_set_header X-Forwarded-Proto $scheme;

       }
    }
  # OPZIONALE: Reindirizzamento HTTP a HTTPS
    server {
        listen 80;
        server_name _;
        return 301 https://$host$request_uri;
    }

}

5. Caddyfile

:3001 {
# Gestione delle chiamate backend (allineato con PARSE_MOUNT=/app)
reverse_proxy /app/* server:8080

# Tutto il resto va al frontend
reverse_proxy client:3000

}

The error I get is the following on the OpenSign server: Error in sendmailv3: Error: Mail command failed: 553 Invalid email address

I couldn't find anything about this in the discussions.
https://github.com/OpenSignLabs/OpenSign/discussions?discussions_q=Error+in+sendmailv3+

I found this thread open, but it doesn't solve my problem: #1857

I tried configuring both Oracle Cloud email delivery and Aruba SMTP, but to no avail.
Can anyone tell me if there are more specific logs to check, or if the variables in the env file are set incorrectly?

Thanks.
Best regards.

Dario

Expected Behavior

No response

Current Behavior

No response

Steps to reproduce

No response

Screenshots of the issue(optional)

No response

Operating System [e.g. MacOS Sonoma 14.1, Windows 11]

No response

What browsers are you seeing the problem on?

Chrome

What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6]

opensign/opensignserver:main

What environment are you seeing the problem on?

No response

Please check the boxes that apply to this issue report.

• I have searched the existing issues & discussions to make sure that this is not a duplicate.

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the existing issues & discussions to make sure that this is not a duplicate.