Codeberg/Community
54
325
Fork
You've already forked Community
12

Please enable Reply via Email for Codeberg accounts #1562

Open
opened 2024年05月08日 16:07:02 +02:00 by xinnix · 23 comments

Feature Description

The main thing im missing from github is the ability to reply to reply to a post via email.

When receiving an email notification about a comment an Issue I would love to be able to reply to the email and have it post as a comment in the codeberg issue.

This is an existing feature

see the documentation on sending and receiving e-mail in the Admin guide. Once configured it works as described.

for sending e.mails: https://forgejo.org/docs/latest/admin/email-setup/

for handling incoming emails:
https://forgejo.org/docs/latest/admin/incoming-email/

### Feature Description The main thing im missing from github is the ability to reply to reply to a post via email. When receiving an email notification about a comment an Issue I would love to be able to reply to the email and have it post as a comment in the codeberg issue. ### This is an existing feature see the documentation on sending and receiving e-mail in the Admin guide. Once configured it works as described. for sending e.mails: https://forgejo.org/docs/latest/admin/email-setup/ for handling incoming emails: https://forgejo.org/docs/latest/admin/incoming-email/
Owner
Copy link

We are well aware of this feature. There were some bugs with the implementation found and fixed recently that would end up in support overhead for Codeberg.

Finally, it requires human power to do the setup and test it accordingly.

We are well aware of this feature. There were some bugs with the implementation found and fixed recently that would end up in support overhead for Codeberg. Finally, it requires human power to do the setup and test it accordingly.
Author
Copy link

Could you share the where the bugs are listed so I can share it with the Forgejo repo?

Could you share the where the bugs are listed so I can share it with the Forgejo repo?
Owner
Copy link

forgejo/forgejo#3496 is the most recent issue I am aware of. I don't have a complete list, though.

https://codeberg.org/forgejo/forgejo/issues/3496 is the most recent issue I am aware of. I don't have a complete list, though.

I'm also eagerly waiting for this feature 😇 I want people to easily contribute to changes via email without having an account.

I'm also eagerly waiting for this feature 😇 I want people to easily contribute to changes via email _without_ having an account.
Owner
Copy link

via email without having an account.

This is a separate discussion and not planned here.

> via email without having an account. This is a separate discussion and not planned here.
n0toose changed title from (削除) Please enable Reply via Email (削除ここまで) to Please enable Reply via Email for Codeberg accounts 2024年05月10日 15:45:22 +02:00

This is a separate discussion and not planned here.

i know, i was just going to "exploit" this email feature in a different way ;)

> This is a separate discussion and not planned here. i know, i was just going to "exploit" this email feature in a different way ;)

Duplicate of #372

Duplicate of #372
fnetX added this to the Fall 2024 milestone 2024年08月18日 14:38:26 +02:00
Author
Copy link

Any update on this?

Any update on this?

This feature is a big deal, I am surprised it's not available yet.

This feature is a big deal, I am surprised it's not available yet.
Author
Copy link

@tusharhero wrote in #1562 (comment):

This feature is a big deal, I am surprised it's not available yet.

It is available its just not enabled by Codeberg and i dont know who to contact to enable it considering this issue has been open for almost a year with no reply from anyone in charge

@tusharhero wrote in https://codeberg.org/Codeberg/Community/issues/1562#issuecomment-3087067: > This feature is a big deal, I am surprised it's not available yet. It is available its just not enabled by Codeberg and i dont know who to contact to enable it considering this issue has been open for almost a year with no reply from anyone in charge
Owner
Copy link

with no reply from anyone in charge

What? #1562 (comment) is the reply from me ("someone in charge").

> with no reply from anyone in charge What? https://codeberg.org/Codeberg/Community/issues/1562#issuecomment-1813198 is the reply from me ("someone in charge").

@fnetX wrote in #1562 (comment):

with no reply from anyone in charge

What? #1562 (comment) is the reply from me ("someone in charge").

Could you tell us what the current status is?

@fnetX wrote in https://codeberg.org/Codeberg/Community/issues/1562#issuecomment-3103015: > > with no reply from anyone in charge > > What? #1562 (comment) is the reply from me ("someone in charge"). Could you tell us what the current status is?

What?

almost a year with no reply from anyone in charge.

They didn't say at all.

> What? *__almost a year__ with no reply from anyone in charge*. They didn't say *at all*.
Owner
Copy link

The status didn't change.

The status didn't change.
Author
Copy link

Hi, sorry about the perceived rudeness. Im just curious about the progress of this being tested and wasnt aware you’re on the Codeberg team. Im really grateful for the amazing work y’all do and would like to see it continue adding features like these that let us completely ditch GitHub

Hi, sorry about the perceived rudeness. Im just curious about the progress of this being tested and wasnt aware you’re on the Codeberg team. Im really grateful for the amazing work y’all do and would like to see it continue adding features like these that let us completely ditch GitHub

Completely agree with @xinnix, you all are doing amazing work bringing this alternative together, and I am super grateful for all the time and effort poured into this. Sorry about the perceived rudeness, indeed, just a friendly bump is all all of this is 😇

Completely agree with @xinnix, you all are doing amazing work bringing this alternative together, and I am super grateful for all the time and effort poured into this. Sorry about the perceived rudeness, indeed, just a friendly bump is all all of this is 😇

Actually replying to issues via email is one thing I very much dislike on GitHub, because some people always use the top-posting (TOFU) style, which is annoying enough when reading the message in an email client, but it really is a nightmare when viewing longer disussions on the issue's page in the browser.

Actually replying to issues via email is one thing I very much dislike on GitHub, because some people always use the top-posting (TOFU) style, which is annoying enough when reading the message in an email client, but it really is a nightmare when viewing longer disussions on the issue's page in the browser.

@tumirnix wrote in #1562 (comment):

Actually replying to issues via email is one thing I very much dislike on GitHub, because some people always use the top-posting (TOFU) style, which is annoying enough when reading the message in an email client, but it really is a nightmare when viewing longer disussions on the issue's page in the browser.

What makes you believe they can't do without replying from email?

@tumirnix wrote in https://codeberg.org/Codeberg/Community/issues/1562#issuecomment-3971705: > Actually replying to issues via email is one thing I very much dislike on GitHub, because some people always use the top-posting (TOFU) style, which is annoying enough when reading the message in an email client, but it really is a nightmare when viewing longer disussions on the issue's page in the browser. What makes you believe they can't do without replying from email?

some people always use the top-posting (TOFU) style

That's not people's choice, but email clients'.

It should be GitHub's job to ignore that part.

Actually, I think Forgejo does, cause I've never encountered that issue on my helpdesk, while I do see that issue on GitHub.

> some people always use the top-posting (TOFU) style That's not people's choice, but email clients'. It should be GitHub's job to ignore that part. Actually, I think Forgejo does, cause I've never encountered that issue on my helpdesk, while I do see that issue on GitHub.

FWIW, there's not really a discussion if it should be enabled or not. It will be enabled at some point; the current status is that getting it to work with our current mail server setup requires a bit more attention to ensure it handles incoming mail in a safely and expected manner.

FWIW, there's not really a discussion if it should be enabled or not. It will be enabled at some point; the current status is that getting it to work with our current mail server setup requires a bit more attention to ensure it handles incoming mail in a safely and expected manner.
Author
Copy link

Ah okay thank you for clarification!! I love codeberg so much!

Reply via email helps me and others so much because with unstable internet when we read a github issue with new comment we can reply without logging in via a web browser which would use more data than we might have access to in the moment.

Ah okay thank you for clarification!! I love codeberg so much! Reply via email helps me and others so much because with unstable internet when we read a github issue with new comment we can reply without logging in via a web browser which would use more data than we might have access to in the moment.

New to codeberg, but getting a noreply@codeberg and then having to "find" another place on your computer where you /are/ allowed to reply, e.g., from fj.el, that's just terrible!

So, very happy to hear you're working on it! #1562 (comment)

New to codeberg, but getting a noreply@codeberg and then having to "find" another place on your computer where you /are/ allowed to reply, e.g., from fj.el, that's just terrible! So, very happy to hear you're working on it! https://codeberg.org/Codeberg/Community/issues/1562#issuecomment-3972866
fnetX locked as Off-topic and limited conversation to collaborators 2025年05月28日 19:14:00 +02:00
Owner
Copy link

Locking this as I see no use in regularly receiving pings about this.

Locking this as I see no use in regularly receiving pings about this.
This discussion has been locked. Commenting is limited to contributors.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
8 participants
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
Codeberg/Community#1562
Reference in a new issue
Codeberg/Community
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?