Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install and configure Trac <-> email gateway #2246

Closed
mc-butler opened this issue Jun 23, 2010 · 7 comments
Closed

Install and configure Trac <-> email gateway #2246

mc-butler opened this issue Jun 23, 2010 · 7 comments
Assignees
Labels
area: adm Administrative tasks prio: medium Has the potential to affect progress

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/2246
Reporter zaytsev (@zyv)

Points to consider:

1) https://subtrac.sara.nl/oss/email2trac/wiki/Email2tracInstallation

2) We don't really need attachments, have to disable it

3) Mailing list subscribed to Trac notifications -> replies go directly into Trac

4) Problem with code review: another mailing list subscribed to all branches commits?

Comments welcome.

@mc-butler
Copy link
Author

Changed by ossi (@ossilator) on Jun 23, 2010 at 16:47 UTC (comment 1)

cool initiative. :)

i wouldn't worry about disabling attachments. it would be an effort without much use. and the feature might actually be useful in a yet unforeseen scenario.

to block *all* spam, the receiving MTA should have a filter configured which accepts only signed mails (any valid signature is ok). when using gpg-agent or dedicated low-value password-less keys, the overhead for the developers would be (almost) zero.

it needs to be verified whether the plugin deals well with the "[Midnight Commander]" prefix from the list. if not, the MTA could just rewrite the subject.

regarding the list for code reviews, i think the notifications for the "preliminary" commits should just go to mc-devel@. it's the right place to discuss development matters, irrespective of the tools around it.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 23, 2010 at 16:56 UTC (comment 2)

Well, there's not much of initiative to it yet. I didn't discuss it with others yet, one of the reasons being that I'm at a conference right know and they are blocking all IM, while circumventing this with my SSH hosts is too much of a PITA. But I definitively think that having a working Trac <-> email gateway is a worthwhile goal and it will be accepted as such.

The reason why I wouldn't want to allow attachments at least in the initial implementation is that it's a huge security risk if not properly implemented, and it seems that it's quite challenging to get it right with the Trac plugin that is available right now.

In what concerns the SPAM, I think as a first step we can just stick to filtering by the sender email which has to be one of a registered Trac user. More sophisticated filtering can be added later.

I don't think that we should direct all the commits from non-master branches to mc-devel. This is a huge influx of junk. I'd rather have a separate list for it as we have it for Trac notifications, but with reply-to set to mc-devel.

IMO.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Sep 1, 2010 at 18:00 UTC (comment 3)

  • Type changed from enhancement to task
  • Milestone Future Releases deleted

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Nov 6, 2011 at 7:24 UTC (comment 4)

  • Version version not selected deleted
  • Branch state set to no branch

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 16, 2015 at 18:03 UTC (comment 5)

Test comment, hoping to find out why posting is so slow by profiling.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jun 16, 2015 at 19:36 UTC (comment 6)

Okay, it seems that the problem was in the SMTP server settings (used domain name instead of IP address of the loopback interface).

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jan 10, 2025 at 16:25 UTC (comment 7)

  • Status changed from new to closed
  • Resolution set to wontfix

Time has come to close this ticket. Hopefully we'll rather move to GitHub at some point.

@mc-butler mc-butler closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: adm Administrative tasks prio: medium Has the potential to affect progress
Development

No branches or pull requests

2 participants