RocketChat / RocketChat/Rocket.Chat

Direct reply via email never seems to log in to check for email

Open
#14,628 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

rocket chat never checks for emails. When I direct message a user it does send an email out to that user, and I've test sending emails back for direct replies, but RocketChat never actually attempts to connect via POP and get those emails. I enabled debugging and watched the rocket chat log, let the check time to 2 minutes and it does not ever even attempt to log into the email server to check for new mail. I've also configured it for IMAP, and seem thing... neither rocketchat, nor the email server logs a connection attempt.

Expected behavior:

The rocketchat server should periodically check for emails and post the direct replies.

Actual behavior:

The server does not ever check for replies.

Server Setup Information:
  • Version of Rocket.Chat Server: 1.0.2
  • Operating System: Ubuntu 18.04.2
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog: yes
  • NodeJS Version: 8.11.3
  • MongoDB Version: 3.16.12
Additional context
Relevant logs:

May 24 19:33:16 rcchat001 rocketchat[11448]: Starting Email Intercepter...
May 24 19:33:16 rcchat001 rocketchat[11448]: Disconnecting already running POP instance...
May 24 19:33:16 rcchat001 rocketchat[11448]: Starting new POP instance......

Then nothing else happens.

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 tracing the server's "Email Intercepter" startup messages and the POP/IMAP email-checking path described in the issue, using the provided logs to determine why no connection attempt occurs. Done means the server periodically connects to the configured mailbox and posts direct email replies as messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.