nextcloud / nextcloud/mail

Adding a new alias should retrigger autoresponder service

Open
#10,242 0 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

Steps to reproduce

The autoresponder sieve script contains a list of allowed recipients.

  1. Enable an autoresponder
  2. Add an alias
  3. The alias is not part of the generated sieve script
Expected behavior

If autoresponder enabled and an alias is added, then trigger an update for the autoresponder.

Actual behavior

Click on save autoresponder required to add the new alias

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 where the autoresponder sieve script is generated and where adding an alias is saved. Compare that flow with the save-autoresponder action to identify the missing update trigger. Done means an alias added while an autoresponder is enabled appears in the generated sieve script without requiring the autoresponder to be saved again.

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.