-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account Deletion AND smtp without authentication (port 25/tcp) #1167
Comments
Thank you for opening your first issue and for being a part of the open signing revolution! |
Do this instead |
I was able to send myself an e-mail via Curl without SMTP Auth. However, it did not send me an e-mail via the registration process. The Exchange had not received any from the system either. Documenso Server Log@documenso/web:start: { @documenso/web:start: jobDefinitions: { @documenso/web:start: 'send.signing.requested.email': { @documenso/web:start: id: 'send.signing.requested.email', @documenso/web:start: name: 'Send Signing Email', @documenso/web:start: version: '1.0.0', @documenso/web:start: trigger: [Object], @documenso/web:start: handler: [AsyncFunction: handler], @documenso/web:start: enabled: true @documenso/web:start: }, @documenso/web:start: 'send.signup.confirmation.email': { @documenso/web:start: id: 'send.signup.confirmation.email', @documenso/web:start: name: 'Send Confirmation Email', @documenso/web:start: version: '1.0.0', @documenso/web:start: trigger: [Object], @documenso/web:start: handler: [AsyncFunction: handler], @documenso/web:start: enabled: true @documenso/web:start: }, @documenso/web:start: 'send.team-member-joined.email': { @documenso/web:start: id: 'send.team-member-joined.email', @documenso/web:start: name: 'Send Team Member Joined Email', @documenso/web:start: version: '1.0.0', @documenso/web:start: trigger: [Object], @documenso/web:start: handler: [AsyncFunction: handler], @documenso/web:start: enabled: true @documenso/web:start: }, @documenso/web:start: 'send.team-member-left.email': { @documenso/web:start: id: 'send.team-member-left.email', @documenso/web:start: name: 'Send Team Member Left Email', @documenso/web:start: version: '1.0.0', @documenso/web:start: trigger: [Object], @documenso/web:start: handler: [AsyncFunction: handler], @documenso/web:start: enabled: true @documenso/web:start: }, @documenso/web:start: 'send.team-deleted.email': { @documenso/web:start: id: 'send.team-deleted.email', @documenso/web:start: name: 'Send Team Deleted Email', @documenso/web:start: version: '1.0.0', @documenso/web:start: trigger: [Object], @documenso/web:start: handler: [AsyncFunction: handler], @documenso/web:start: enabled: true @documenso/web:start: } @documenso/web:start: } @documenso/web:start: } @documenso/web:start: { @documenso/web:start: options: { @documenso/web:start: name: 'send.signup.confirmation.email', @documenso/web:start: payload: { email: 'me@example.org' } @documenso/web:start: } @documenso/web:start: } @documenso/web:start: Eligible jobs: [ 'Send Confirmation Email' ] @documenso/web:start: Submitting job to endpoint: https://sign.example.org/api/jobs/send.signup.confirmation.email/blub .env SMTP# [[SMTP]] # OPTIONAL: Defines the transport to use for sending emails. Available options: smtp-auth (default) | smtp-api | mailchannels NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth" # OPTIONAL: Defines the host to use for sending emails. NEXT_PRIVATE_SMTP_HOST="192.168.178.8" # OPTIONAL: Defines the port to use for sending emails. NEXT_PRIVATE_SMTP_PORT=25 # OPTIONAL: Defines the username to use with the SMTP server. NEXT_PRIVATE_SMTP_USERNAME= # OPTIONAL: Defines the password to use with the SMTP server. NEXT_PRIVATE_SMTP_PASSWORD= # OPTIONAL: Defines the API key user to use with the SMTP server. NEXT_PRIVATE_SMTP_APIKEY_USER= # OPTIONAL: Defines the API key to use with the SMTP server. NEXT_PRIVATE_SMTP_APIKEY= # OPTIONAL: Defines whether to force the use of TLS. NEXT_PRIVATE_SMTP_SECURE= # OPTIONAL: if this is true and NEXT_PRIVATE_SMTP_SECURE is false then TLS is not used even if the server supports STARTTLS extension NEXT_PRIVATE_SMTP_UNSAFE_IGNORE_TLS=false # REQUIRED: Defines the sender name to use for the from address. NEXT_PRIVATE_SMTP_FROM_NAME="Documenso" # REQUIRED: Defines the email address to use as the from address. NEXT_PRIVATE_SMTP_FROM_ADDRESS="me@example.org" # OPTIONAL: The API key to use for Resend.com NEXT_PRIVATE_RESEND_API_KEY= # OPTIONAL: The API key to use for MailChannels. NEXT_PRIVATE_MAILCHANNELS_API_KEY= # OPTIONAL: The endpoint to use for the MailChannels API if using a proxy. NEXT_PRIVATE_MAILCHANNELS_ENDPOINT= # OPTIONAL: The domain to use for DKIM signing. NEXT_PRIVATE_MAILCHANNELS_DKIM_DOMAIN= # OPTIONAL: The selector to use for DKIM signing. NEXT_PRIVATE_MAILCHANNELS_DKIM_SELECTOR= # OPTIONAL: The private key to use for DKIM signing. NEXT_PRIVATE_MAILCHANNELS_DKIM_PRIVATE_KEY= # OPTIONAL: Displays the maximum document upload limit to the user in MBs NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=5 |
Issue Description
Hello everyone,
I have registered several users and have not yet received any emails because it always went wrong.
How do I delete the old users? My internal mail server can only be reached via port 25 without authentication.
How do I make it possible to send mail without smtp-auth or others?
I have secured the web server via an NGINX reverse proxy.
Steps to Reproduce
When completing the registration process, the following message appears.
And when I log in again with the same e-mail, I get this. So I can't try it again with my e-mail
Expected Behavior
Mail confirmation can also be done internally via insecure non-authentication (port 25).
Current Behavior
The DB table should not exist according to the error message, so I can't delete users from my Documenso instance
The table Account in documenso-db exists
Many thanks in advance! Maybe I'm just missing something
Screenshots (optional)
No response
Operating System [e.g., Windows 10]
Windows 10
Browser [e.g., Chrome, Firefox]
Firefox
Version [e.g., 2.0.1]
126
Please check the boxes that apply to this issue report.
The text was updated successfully, but these errors were encountered: