nextcloud / nextcloud/mail

Connections without authentication

Open
#3,145 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Expected behavior

It should be possible to configure localhost:25 for outbound email - without TLS, without username, without password.

Actual behavior

Whenever I try to specify localhost:25 for outbound email (TLS none, no username, no password) the settings are not accepted. I've already configured DEBUG log output. In horde_smtp.log I see

>> Thu, 21 May 2020 21:51:00 +0000
>> Connection to: smtp://localhost:25
S: 220 xxx.xxxxxx.xx ESMTP Postfix
C: EHLO xx.xxxxxx.xx
S: 250-xxx.xxxxxx.xx
S: 250-PIPELINING
S: 250-SIZE 10240000
S: 250-VRFY
S: 250-ETRN
S: 250-STARTTLS
S: 250-ENHANCEDSTATUSCODES
S: 250-8BITMIME
S: 250-DSN
S: 250-SMTPUTF8
S: 250 CHUNKING
C: STARTTLS
S: 220 2.0.0 Ready to start TLS
C: QUIT
>> ERROR: Server read/timeout error.

IMHO the mail app should not try to switch to TLS with STARTTLS here.

Mail app

Mail app version: 1.3.5

Mailserver or service: SMTP is served by local Postfix, IMAP and submission (authenticated SMTP with STARTTLS via port 587) are served by local dovecot.

BTW:

I have configured plain text IMAP on localhost:110 and secured IMAP (port 993) an all other interfaces. The email app happily connects to IMAP (localhost:110). But it refuses to use local plain SMTP (localhost:25).) The email app successfully connects to the FQDN of my server to submission (port 587) with STARTTLS.

Server configuration

Operating system: Arch Linux

Web server: Apache 2.4.43

Database: mariadb 10.4.13

PHP version: 7.4.6

Nextcloud Version: 18.0.4

Client configuration

Browser: Firefox 76.0.1

Operating system: Manjaro Linux

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the SMTP settings and the horde_smtp.log output for a localhost:25 connection with TLS disabled, username omitted, and password omitted. Reproduce the connection and confirm it completes without issuing STARTTLS when TLS is set to none.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.