These variables weren't working as expected. Need to figure out why.

Open
#1,471 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
tooling

Research direction

Start with email/customer-satisfaction-spam.sieve around lines 165-175, using the linked revision as the reference. Reproduce the behavior with the shown allowlist, bodyPatterns, subjectPatterns, and immediateMatch values, then determine why the variables are not taking effect; completion would require a confirmed cause and working variable behavior.

Written by the indexing model from the issue text.

Description

Define any allowlist items (email addresses, domains, words) here
set "allowlist_emails" "allowedcontact1@example.com,allowedcontact2@example.com";
Define any phrases that should be considered likely to be customer satisfaction surveys
set "bodyPatterns" "TODO!"
This time for the subject
set "subjectPatterns" "TODO!"
set "allowlist_domains" "@alloweddomain.com";
set "allowlist_words" "allowedword";
Define any phrases that should trigger immediate filing into the "Customer Satisfaction Spam" folder
set "immediateMatch" "[How likely are you to recommend us to a friend or colleague,How would you rate the support you received,What do you think about your store experience,What do you think about your purchase products,Take a few minutes to share your feedback]";
end TODO ###

Line: 168
https://github.com/sammcj/scripts/blob/301d45c2f40bb3e1d953451b6dd7d06b6b61d890//email/customer-satisfaction-spam.sieve#L165-L175

Dominant language
Python
Stars
17
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from sammcj/scripts

All issues in sammcj/scripts

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.