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

Issue for testing github-sf mailing list integration #74

Closed
jwpeterson opened this issue Apr 4, 2013 · 6 comments
Closed

Issue for testing github-sf mailing list integration #74

jwpeterson opened this issue Apr 4, 2013 · 6 comments

Comments

@jwpeterson
Copy link
Member

Feel free to post random philosophical musings...

@jwpeterson
Copy link
Member Author

res ipsa loquitur

@roystgnr
Copy link
Member

roystgnr commented Apr 4, 2013

I only seem to be getting these messages from github; are they making
it to libmesh-devel?

On Thu, 4 Apr 2013, jwpeterson wrote:

Feel free to post random philosophical musings...

Anyone short on musing ideas, feel free to submit your answers to the
survey here:

http://philpapers.org/philpapers/raw/survey.pdf

@jwpeterson
Copy link
Member Author

On Thu, Apr 4, 2013 at 10:40 AM, roystgnr notifications@github.com wrote:

I only seem to be getting these messages from github; are they making
it to libmesh-devel?

Negative. They are all being trapped under the "implicit destination"
rule. I tried to set up a forwarding filter from
libmesh.devel@gmail.comas well, but it looks like forwarding also
counts as an implicit
destination.

At least now that the emails are going to the gmail account I created, the
libmesh-devel mailman page isn't getting blown up with pending moderator
requests any more.

On Thu, 4 Apr 2013, jwpeterson wrote:

Feel free to post random philosophical musings...

Anyone short on musing ideas, feel free to submit your answers to the
survey here:

http://philpapers.org/philpapers/raw/survey.pdf

Hmm... I don't even know how to answer the first question without looking
up definitions of terms.

John

@jwpeterson
Copy link
Member Author

BTW, I did find this thread:

http://mail.python.org/pipermail/mailman-users/2006-September/053495.html

that would probably allow us to automatically accept the bcc'd/forwarded posts. But do we really want to do that after all? It would most likely force everyone to have to create a mail filter to avoid seeing two copies of everything posted to a github issue. On the other hand, this will effectively be the end of the libmesh-devel mailing list (and its archives, which I've found to be useful in the past) as we know it. You can already see the drop-off in the last month's data...

@roystgnr
Copy link
Member

roystgnr commented Apr 4, 2013

I'm already in the habit of unthinkingly deleting the second copy of
messages that get sent both directly to my email address and
indirectly via libmesh mailing lists. Deleting the third copy will be
a mild annoyance but not a strain.

@roystgnr
Copy link
Member

roystgnr commented Apr 4, 2013

Let me try another email to an on-topic ticket and let's see if I get
another "Undelivered Mail Returned to Sender"...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants