mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #167] Enhancement: Mailing list To: address in folder metadata #134
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#134
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dumblob on GitHub (Feb 16, 2017).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/167
Originally assigned to: @jasonmunro on GitHub.
When posting a new topic to mailing lists, I noticed I'm always searching through piles of information (mail headers, my own notes, etc.) to find out what is the correct
To:address to post to.Would it be possible to store this information in some metadata for a folder? I can imagine something like Address for
To:prefilling: option in each folder settings. This content would be then prefilled to theTo:box if one clicks on the Compose button from the current view showing a folder with a predefinedTo:address.@jasonmunro commented on GitHub (Feb 26, 2017):
This is an interesting concept, an "imap folder meta" module that allows you to set a variety of different properties (default to: address, sort order, filtering etc).
@jasonmunro commented on GitHub (Sep 24, 2018):
Correct me if I'm wrong, but I think implementing this issue:
https://github.com/jasonmunro/cypht/issues/169
Would go a long way here. Most (all?) mailing lists provide headers to let you know where to post back to the list.
@dumblob commented on GitHub (Sep 25, 2018):
The issue https://github.com/jasonmunro/cypht/issues/169 looks quite similar. The main thing seems to be missing though - I'm starting mailing list threads more frequently than commenting on existing ones. In other words, I have no email with any such mailing list header to use as a starting reference "where to post to".
Still, I have the feeling having settings for metadata (including the
To:field) for each folder is generally easier to implement and gives the user a guarantee. I'm also not sure whether there is a standard for email headers for mailing lists, so I'm curious how it'll turn with the issue https://github.com/jasonmunro/cypht/issues/169 .With regards to the
To:prefill folder setting, I wouldn't let it overwrite things, but rather add the content at the end of an existing one if any (e.g. there will be some autoextracted content from mailing list headers, so the prefill folder setting content wouldn't overwrite anything, but add it to the end).@jasonmunro commented on GitHub (Sep 25, 2018):
Excellent points - as always :) I think an "imap folder meta" plugin is in order for this. Mailing list headers are not consistent, because it's E-mail so of course not. However I have built a mailing list plugin for past projects and it worked pretty well. I will keep this open as a separate issue.