[GH-ISSUE #167] Enhancement: Mailing list To: address in folder metadata #134

Open
opened 2026-02-25 21:34:15 +03:00 by kerem · 4 comments
Owner

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 the To: box if one clicks on the Compose button from the current view showing a folder with a predefined To: address.

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 the `To:` box if one clicks on the *Compose* button from the current view showing a folder with a predefined `To:` address.
Author
Owner

@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).

<!-- gh-comment-id:282582332 --> @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).
Author
Owner

@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.

<!-- gh-comment-id:424155761 --> @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.
Author
Owner

@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).

<!-- gh-comment-id:424500292 --> @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).
Author
Owner

@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.

<!-- gh-comment-id:424521812 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#134
No description provided.