[GH-ISSUE #1422] does not receive verification email #401

Open
opened 2026-02-26 18:46:53 +03:00 by kerem · 18 comments
Owner

Originally created by @fred781987 on GitHub (Oct 27, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1422

Issue Description

I am trying to create an account on documenso but it does not send verification email on my email can someone help me out ?

Originally created by @fred781987 on GitHub (Oct 27, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1422 # Issue Description I am trying to create an account on documenso but it does not send verification email on my email can someone help me out ?
Author
Owner

@github-actions[bot] commented on GitHub (Oct 27, 2024):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

<!-- gh-comment-id:2439990882 --> @github-actions[bot] commented on GitHub (Oct 27, 2024): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)
Author
Owner

@dguyen commented on GitHub (Oct 28, 2024):

Hi, are you self hosting Documenso? Or is this happening on app.documenso.com?

<!-- gh-comment-id:2440659009 --> @dguyen commented on GitHub (Oct 28, 2024): Hi, are you self hosting Documenso? Or is this happening on app.documenso.com?
Author
Owner

@syedfaiqyazdani commented on GitHub (Oct 28, 2024):

i have setup documenso locally when i try to create an account i don't receive any email for verfication any solution to solve this problem

<!-- gh-comment-id:2442141954 --> @syedfaiqyazdani commented on GitHub (Oct 28, 2024): i have setup documenso locally when i try to create an account i don't receive any email for verfication any solution to solve this problem
Author
Owner

@pbmagnet4 commented on GitHub (Oct 29, 2024):

I am experiencing the same issue. Locally hosted following this tutorial:

https://mariushosting.com/how-to-install-documenso-on-your-synology-nas/

My guess is that there is an issue with setting up the STMP protocol. Any help on the matter would be greatly appreciated.

<!-- gh-comment-id:2445040260 --> @pbmagnet4 commented on GitHub (Oct 29, 2024): I am experiencing the same issue. Locally hosted following this tutorial: https://mariushosting.com/how-to-install-documenso-on-your-synology-nas/ My guess is that there is an issue with setting up the STMP protocol. Any help on the matter would be greatly appreciated.
Author
Owner

@PhatWheZ commented on GitHub (Nov 1, 2024):

@dguyen I am trying to setup a self-hosted environment and when running the logs output failed smtp messages, but if you try again after a few seconds it shows to send, but nothing comes through

I am keen to assist in providing to the community where i can, as this is a great project!

<!-- gh-comment-id:2451440179 --> @PhatWheZ commented on GitHub (Nov 1, 2024): @dguyen I am trying to setup a self-hosted environment and when running the logs output failed smtp messages, but if you try again after a few seconds it shows to send, but nothing comes through I am keen to assist in providing to the community where i can, as this is a great project!
Author
Owner

@candiepih commented on GitHub (Nov 4, 2024):

I am currently experiencing this problem. It's sending reset password emails but not email verification emails

<!-- gh-comment-id:2454416535 --> @candiepih commented on GitHub (Nov 4, 2024): I am currently experiencing this problem. It's sending reset password emails but not email verification emails
Author
Owner

@PhatWheZ commented on GitHub (Nov 4, 2024):

@candiepih sounds odd that half works and not the rest.
On my end, i have mails working no problem with the following variables declared in a .env file with only env_file: .env being listed in my docker-compose.yml file

# [[SMTP]]
NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth"
NEXT_PRIVATE_SMTP_HOST="{Host FQDN or IP}"
NEXT_PRIVATE_SMTP_PORT="25"
NEXT_PRIVATE_SMTP_USERNAME="documenso@domain.io"
NEXT_PRIVATE_SMTP_PASSWORD="app-password"
NEXT_PRIVATE_SMTP_SECURE="false"
NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="true"
NEXT_PRIVATE_SMTP_FROM_NAME="Documenso"
NEXT_PRIVATE_SMTP_FROM_ADDRESS="documenso@{yourdomain.com}"
NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=50
<!-- gh-comment-id:2454508700 --> @PhatWheZ commented on GitHub (Nov 4, 2024): @candiepih sounds odd that half works and not the rest. On my end, i have mails working no problem with the following variables declared in a `.env` file with only `env_file: .env` being listed in my `docker-compose.yml` file ``` # [[SMTP]] NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth" NEXT_PRIVATE_SMTP_HOST="{Host FQDN or IP}" NEXT_PRIVATE_SMTP_PORT="25" NEXT_PRIVATE_SMTP_USERNAME="documenso@domain.io" NEXT_PRIVATE_SMTP_PASSWORD="app-password" NEXT_PRIVATE_SMTP_SECURE="false" NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="true" NEXT_PRIVATE_SMTP_FROM_NAME="Documenso" NEXT_PRIVATE_SMTP_FROM_ADDRESS="documenso@{yourdomain.com}" NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=50 ```
Author
Owner

@candiepih commented on GitHub (Nov 4, 2024):

@candiepih sounds odd that half works and not the rest. On my end, i have mails working no problem with the following variables declared in a .env file with only env_file: .env being listed in my docker-compose.yml file

# [[SMTP]]
NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth"
NEXT_PRIVATE_SMTP_HOST="{Host FQDN or IP}"
NEXT_PRIVATE_SMTP_PORT="25"
NEXT_PRIVATE_SMTP_USERNAME="documenso@domain.io"
NEXT_PRIVATE_SMTP_PASSWORD="app-password"
NEXT_PRIVATE_SMTP_SECURE="false"
NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="true"
NEXT_PRIVATE_SMTP_FROM_NAME="Documenso"
NEXT_PRIVATE_SMTP_FROM_ADDRESS="documenso@{yourdomain.com}"
NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=50

I was using docker-compose before and had that issue, it's now working after I cloned the repo. Maybe the issue lies within the code associated with the Docker image.

<!-- gh-comment-id:2454591743 --> @candiepih commented on GitHub (Nov 4, 2024): > @candiepih sounds odd that half works and not the rest. On my end, i have mails working no problem with the following variables declared in a `.env` file with only `env_file: .env` being listed in my `docker-compose.yml` file > > ``` > # [[SMTP]] > NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth" > NEXT_PRIVATE_SMTP_HOST="{Host FQDN or IP}" > NEXT_PRIVATE_SMTP_PORT="25" > NEXT_PRIVATE_SMTP_USERNAME="documenso@domain.io" > NEXT_PRIVATE_SMTP_PASSWORD="app-password" > NEXT_PRIVATE_SMTP_SECURE="false" > NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="true" > NEXT_PRIVATE_SMTP_FROM_NAME="Documenso" > NEXT_PRIVATE_SMTP_FROM_ADDRESS="documenso@{yourdomain.com}" > NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=50 > ``` I was using docker-compose before and had that issue, it's now working after I cloned the repo. Maybe the issue lies within the code associated with the Docker image.
Author
Owner

@PhatWheZ commented on GitHub (Nov 5, 2024):

I setup my own docker-compose.yml file which works fine. I didnt copy the repo as I am trying to find the kinks.

services:
  postgres:
    image: postgres:15
    container_name: postgres
    healthcheck:
      test: ['CMD-SHELL', 'pg_isready -U ${POSTGRES_USER}']
      interval: 10s
      timeout: 5s
      retries: 5
    env_file: .env
    volumes:
      - postgres:/var/lib/postgresql/data

  documenso:
    image: documenso/documenso:latest
    container_name: documenso
    depends_on:
      postgres:
        condition: service_healthy
    env_file: .env
    environment:
      - NEXT_PRIVATE_SIGNING_PASSPHRASE=${NEXT_PRIVATE_SIGNING_PASSPRHASE}
    volumes:
      - /opt/documenso/cert.p12:/opt/documenso/cert.p12
    ports:
      - 3000:3000

volumes:
  postgres:
<!-- gh-comment-id:2456555164 --> @PhatWheZ commented on GitHub (Nov 5, 2024): I setup my own `docker-compose.yml` file which works fine. I didnt copy the repo as I am trying to find the kinks. ``` services: postgres: image: postgres:15 container_name: postgres healthcheck: test: ['CMD-SHELL', 'pg_isready -U ${POSTGRES_USER}'] interval: 10s timeout: 5s retries: 5 env_file: .env volumes: - postgres:/var/lib/postgresql/data documenso: image: documenso/documenso:latest container_name: documenso depends_on: postgres: condition: service_healthy env_file: .env environment: - NEXT_PRIVATE_SIGNING_PASSPHRASE=${NEXT_PRIVATE_SIGNING_PASSPRHASE} volumes: - /opt/documenso/cert.p12:/opt/documenso/cert.p12 ports: - 3000:3000 volumes: postgres: ```
Author
Owner

@crazyyzarc commented on GitHub (Nov 13, 2024):

Despite following the linked instructions about Docker, no mails are being sent. I use nginx as reverse proxy for my own trusted certificate.

  - PORT=3000
  - NEXTAUTH_SECRET=iLE3qPl8jJZWSrmSJGERVQt6YKIQIoUT
  - NEXT_PRIVATE_ENCRYPTION_KEY=Lzav2o6C0HBsg75bo2dUPqpOZ5k4904E
  - NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY=Q6GigBFoGF62jhqzD4ebXEow5gLiSSs7
  - NEXTAUTH_URL=https://sign.my.intranet
  - NEXT_PUBLIC_WEBAPP_URL=https://sign.my.intranet
  - NEXT_PRIVATE_INTERNAL_WEBAPP_URL=https://sign.my.intranet
  - NEXT_PUBLIC_MARKETING_URL=https://sign.my.intranet
  - NEXT_PRIVATE_DATABASE_URL=postgres://documensouser:documensopass@documenso-db:5432/documenso
  - NEXT_PRIVATE_DIRECT_DATABASE_URL=postgres://documensouser:documensopass@documenso-db:5432/documenso
  - NEXT_PUBLIC_UPLOAD_TRANSPORT=database
  - NEXT_PRIVATE_SMTP_TRANSPORT=smtp-auth
  - NEXT_PRIVATE_SMTP_HOST=email.my.intranet
  - NEXT_PRIVATE_SMTP_PORT=25
  - NEXT_PRIVATE_SMTP_USERNAME=SMTPuser
  - NEXT_PRIVATE_SMTP_PASSWORD=SMTPpassword
  - NEXT_PRIVATE_SMTP_SECURE=false
  - NEXT_PRIVATE_SMTP_FROM_NAME=Documenso
  - NEXT_PRIVATE_SMTP_FROM_ADDRESS=notification@my.intranet
  - NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS=true

image

Can I activate debugging for Documenso?

<!-- gh-comment-id:2473516977 --> @crazyyzarc commented on GitHub (Nov 13, 2024): Despite following the linked instructions about Docker, no mails are being sent. I use nginx as reverse proxy for my own trusted certificate. - PORT=3000 - NEXTAUTH_SECRET=iLE3qPl8jJZWSrmSJGERVQt6YKIQIoUT - NEXT_PRIVATE_ENCRYPTION_KEY=Lzav2o6C0HBsg75bo2dUPqpOZ5k4904E - NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY=Q6GigBFoGF62jhqzD4ebXEow5gLiSSs7 - NEXTAUTH_URL=https://sign.my.intranet - NEXT_PUBLIC_WEBAPP_URL=https://sign.my.intranet - NEXT_PRIVATE_INTERNAL_WEBAPP_URL=https://sign.my.intranet - NEXT_PUBLIC_MARKETING_URL=https://sign.my.intranet - NEXT_PRIVATE_DATABASE_URL=postgres://documensouser:documensopass@documenso-db:5432/documenso - NEXT_PRIVATE_DIRECT_DATABASE_URL=postgres://documensouser:documensopass@documenso-db:5432/documenso - NEXT_PUBLIC_UPLOAD_TRANSPORT=database - NEXT_PRIVATE_SMTP_TRANSPORT=smtp-auth - NEXT_PRIVATE_SMTP_HOST=email.my.intranet - NEXT_PRIVATE_SMTP_PORT=25 - NEXT_PRIVATE_SMTP_USERNAME=SMTPuser - NEXT_PRIVATE_SMTP_PASSWORD=SMTPpassword - NEXT_PRIVATE_SMTP_SECURE=false - NEXT_PRIVATE_SMTP_FROM_NAME=Documenso - NEXT_PRIVATE_SMTP_FROM_ADDRESS=notification@my.intranet - NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS=true ![image](https://github.com/user-attachments/assets/8bce7888-daec-4020-857a-5b682d5614dd) Can I activate debugging for Documenso?
Author
Owner

@PhatWheZ commented on GitHub (Nov 13, 2024):

Can you try put the values in ""

  - NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth"
  - NEXT_PRIVATE_SMTP_HOST="email.my.intranet"
  - NEXT_PRIVATE_SMTP_PORT="25"
  - NEXT_PRIVATE_SMTP_USERNAME="SMTPuser"
  - NEXT_PRIVATE_SMTP_PASSWORD="SMTPpassword"
  - NEXT_PRIVATE_SMTP_SECURE="false"
  - NEXT_PRIVATE_SMTP_FROM_NAME="Documenso"
  - NEXT_PRIVATE_SMTP_FROM_ADDRESS="notification@my.intranet"
  - NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="true"
<!-- gh-comment-id:2473681029 --> @PhatWheZ commented on GitHub (Nov 13, 2024): Can you try put the values in `""` ``` - NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth" - NEXT_PRIVATE_SMTP_HOST="email.my.intranet" - NEXT_PRIVATE_SMTP_PORT="25" - NEXT_PRIVATE_SMTP_USERNAME="SMTPuser" - NEXT_PRIVATE_SMTP_PASSWORD="SMTPpassword" - NEXT_PRIVATE_SMTP_SECURE="false" - NEXT_PRIVATE_SMTP_FROM_NAME="Documenso" - NEXT_PRIVATE_SMTP_FROM_ADDRESS="notification@my.intranet" - NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="true" ```
Author
Owner

@CyberB1aze commented on GitHub (Nov 14, 2024):

Having the same issue

Logs

[JOBS]: Job send.signup.confirmation.email failed Error: Failed to send the confirmation email
    at u (/app/apps/web/.next/server/chunks/9783.js:1:34900)
    at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:21019)
    at async /app/apps/web/.next/server/chunks/9783.js:1:17053
    at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853)
    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492)
    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9)
    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37)
    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17)
    at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21)
    at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24)
Submitting job to endpoint: https://personal.domain/api/jobs/send.signup.confirmation.email/cm3h0vzml0000p43480ma0ob2
[JOBS]: Triggering job send.signup.confirmation.email with payload { email: 'personal.mail.id' }
Error: queryA EBADNAME "smtp.gmail.com"
    at QueryReqWrap.onresolve [as oncomplete] (node:internal/dns/callback_resolver:45:19)
    at QueryReqWrap.callbackTrampoline (node:internal/async_hooks:128:17) {
  errno: undefined,
  code: 'EDNS',
  syscall: 'queryA',
  hostname: '"smtp.gmail.com"',
  command: 'CONN'

My env variables

      - NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="true"
      - NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth"
      - NEXT_PRIVATE_SMTP_HOST="smtp.gmail.com"
      - NEXT_PRIVATE_SMTP_PORT="25"
      - NEXT_PRIVATE_SMTP_USERNAME="email"
      - NEXT_PRIVATE_SMTP_PASSWORD="password"
      - NEXT_PRIVATE_SMTP_FROM_NAME="Documenso"

not sure whats going on here

<!-- gh-comment-id:2475674286 --> @CyberB1aze commented on GitHub (Nov 14, 2024): Having the same issue Logs ``` [JOBS]: Job send.signup.confirmation.email failed Error: Failed to send the confirmation email at u (/app/apps/web/.next/server/chunks/9783.js:1:34900) at async Object.handler (/app/apps/web/.next/server/chunks/9783.js:1:21019) at async /app/apps/web/.next/server/chunks/9783.js:1:17053 at async K (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17492) at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:600:9) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:269:37) at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/next/dist/server/lib/router-server.js:353:24) Submitting job to endpoint: https://personal.domain/api/jobs/send.signup.confirmation.email/cm3h0vzml0000p43480ma0ob2 [JOBS]: Triggering job send.signup.confirmation.email with payload { email: 'personal.mail.id' } Error: queryA EBADNAME "smtp.gmail.com" at QueryReqWrap.onresolve [as oncomplete] (node:internal/dns/callback_resolver:45:19) at QueryReqWrap.callbackTrampoline (node:internal/async_hooks:128:17) { errno: undefined, code: 'EDNS', syscall: 'queryA', hostname: '"smtp.gmail.com"', command: 'CONN' ``` My env variables ``` - NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="true" - NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth" - NEXT_PRIVATE_SMTP_HOST="smtp.gmail.com" - NEXT_PRIVATE_SMTP_PORT="25" - NEXT_PRIVATE_SMTP_USERNAME="email" - NEXT_PRIVATE_SMTP_PASSWORD="password" - NEXT_PRIVATE_SMTP_FROM_NAME="Documenso" ``` not sure whats going on here
Author
Owner

@PhatWheZ commented on GitHub (Nov 14, 2024):

Hi there,
Double check the settings necessary for you to send using Gmail.

  - NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth"
  - NEXT_PRIVATE_SMTP_HOST="email.my.intranet"
  - NEXT_PRIVATE_SMTP_PORT="587"
  - NEXT_PRIVATE_SMTP_USERNAME="SMTPuser"
  - NEXT_PRIVATE_SMTP_PASSWORD="SMTPpassword"
  - NEXT_PRIVATE_SMTP_SECURE="true"
  - NEXT_PRIVATE_SMTP_FROM_NAME="Documenso"
  - NEXT_PRIVATE_SMTP_FROM_ADDRESS="notification@my.intranet"
  - NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="false"

I am using an internal mail relay which is why i can get away using port 25

<!-- gh-comment-id:2476894950 --> @PhatWheZ commented on GitHub (Nov 14, 2024): Hi there, Double check the settings necessary for you to send using Gmail. ``` - NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth" - NEXT_PRIVATE_SMTP_HOST="email.my.intranet" - NEXT_PRIVATE_SMTP_PORT="587" - NEXT_PRIVATE_SMTP_USERNAME="SMTPuser" - NEXT_PRIVATE_SMTP_PASSWORD="SMTPpassword" - NEXT_PRIVATE_SMTP_SECURE="true" - NEXT_PRIVATE_SMTP_FROM_NAME="Documenso" - NEXT_PRIVATE_SMTP_FROM_ADDRESS="notification@my.intranet" - NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS="false" ``` I am using an internal mail relay which is why i can get away using port 25
Author
Owner

@crazyyzarc commented on GitHub (Nov 19, 2024):

My email server (Microsoft Exchange Server 2016) received no incoming mail, depite I put the variables in ""
image

I've tested with PowerShell get-messagetrackinglog Module

<!-- gh-comment-id:2485997800 --> @crazyyzarc commented on GitHub (Nov 19, 2024): My email server (Microsoft Exchange Server 2016) received no incoming mail, depite I put the variables in "" ![image](https://github.com/user-attachments/assets/4857bc1a-30e0-4489-b98f-93b8fcfaed56) I've tested with PowerShell get-messagetrackinglog Module
Author
Owner

@PhatWheZ commented on GitHub (Nov 19, 2024):

And your exchange server is allowing smtp relay connections?

Perhaps try send a mail using Powershell to validate

# Send Email
$from = "noreply@contoso.com"
$to = "yourself@contoso.com"
$smtpServer = "relay.contoso.com"
Send-MailMessage -From $from -To $to -Subject $subject -Body $body -SmtpServer $smtpServer -Port 25
<!-- gh-comment-id:2486118919 --> @PhatWheZ commented on GitHub (Nov 19, 2024): And your exchange server is allowing smtp relay connections? Perhaps try send a mail using Powershell to validate ``` # Send Email $from = "noreply@contoso.com" $to = "yourself@contoso.com" $smtpServer = "relay.contoso.com" Send-MailMessage -From $from -To $to -Subject $subject -Body $body -SmtpServer $smtpServer -Port 25 ```
Author
Owner

@crazyyzarc commented on GitHub (Nov 20, 2024):

And your exchange server is allowing smtp relay connections?

Perhaps try send a mail using Powershell to validate

# Send Email
$from = "noreply@contoso.com"
$to = "yourself@contoso.com"
$smtpServer = "relay.contoso.com"
Send-MailMessage -From $from -To $to -Subject $subject -Body $body -SmtpServer $smtpServer -Port 25

yes, the server IP is entereed in the anonymous relay of the Exchange receiving connection. A powershell docker image on documenso can mailing without auth (this is correct)

image
2024-11-20_08-14-12_QJglV135XX

<!-- gh-comment-id:2487699054 --> @crazyyzarc commented on GitHub (Nov 20, 2024): > And your exchange server is allowing smtp relay connections? > > Perhaps try send a mail using Powershell to validate > > ``` > # Send Email > $from = "noreply@contoso.com" > $to = "yourself@contoso.com" > $smtpServer = "relay.contoso.com" > Send-MailMessage -From $from -To $to -Subject $subject -Body $body -SmtpServer $smtpServer -Port 25 > ``` yes, the server IP is entereed in the anonymous relay of the Exchange receiving connection. A powershell docker image on documenso can mailing without auth (this is correct) ![image](https://github.com/user-attachments/assets/a32f89bb-9867-4a8c-8539-52fbfa054be1) ![2024-11-20_08-14-12_QJglV135XX](https://github.com/user-attachments/assets/5979aa82-c674-474f-b7e9-e87c2d9faf76)
Author
Owner

@tcheronneau commented on GitHub (Dec 23, 2024):

This one worked for me https://github.com/documenso/documenso/issues/1307

<!-- gh-comment-id:2559060087 --> @tcheronneau commented on GitHub (Dec 23, 2024): This one worked for me https://github.com/documenso/documenso/issues/1307
Author
Owner

@Novapixel1010 commented on GitHub (Apr 27, 2025):

Did you ever figure this out?

<!-- gh-comment-id:2833564782 --> @Novapixel1010 commented on GitHub (Apr 27, 2025): Did you ever figure this out?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#401
No description provided.