Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/54#issuecomment-222651106
how would you detect a "non-mailing list" address though? Surely you'd want
the system to just be interactions with lists, and not a gener
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/54#issuecomment-222651890
replying to both the list AND the original sender would be possible within
the current design. It's just replying to all 'To: ' addresses
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/54#issuecomment-222652240
that would require rewriting the archiver to also digest those headers
---
If your project is set up for it, you can reply to this email and have your
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/54#issuecomment-222653173
I'm curious whether you think it's Pony Mail's job to act as a complete
mail client, or just interact with the specific list you are on
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/54#issuecomment-222654045
I'm not _against it_, but if this was added, it should be something that
you enable on purpose (i.e. a setting that is off by default, but c
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/40#issuecomment-222654351
could you submit this in the form of a pull request instead?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/59
step 1: how would you define an admin? :)
It could be done, but would require some rewrite of the elastic library to
support DELETE operations
---
If your project is set
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/59
Pierre, this has no relevance to the subject. How the ASF decides to
utilize an implementation of this project is their business. It has no impact
on how we decide to implement
Github user Humbedooh commented on a diff in the pull request:
https://github.com/apache/incubator-ponymail/pull/36#discussion_r65303038
--- Diff: tools/archiver.py ---
@@ -282,23 +290,17 @@ def archive_message(self, mlist, msg):
body = body.encode
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/54
welp, I must admit I was wrong. Pony Mail already saves the to/cc headers
in the digest, so this is indeed possible with the current design.
---
If your project is set up for
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/46
it's _not_ a bug, it's a configuration issue. If you have a specific issue
with that service, I suggest you reach out to the people in charge of it.
---
If your proj
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/59
edit-list.py could be enhanced to do this, I suppose.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/pull/56
Please see http://ponymail.incubator.apache.org/contribute.html#gitworkflow
for instructions on how to squash/rebase your PR
---
If your project is set up for it, you can reply
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/46
See aa98961019c7c660c8c610449f5640afa1228cfb - this should be considered a
done deal now.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user Humbedooh closed the pull request at:
https://github.com/apache/incubator-ponymail/issues/46
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/53
I suppose that would technically be an ElasticSearch issue.
the mbox script downloads everything from 2016-03-01 to 2016-03-31 there,
so if that email makes it to the blob
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/14
just testing GH integration, ignore :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/14
just testing GH integration, ignore :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user Humbedooh commented on the pull request:
https://github.com/apache/incubator-ponymail/issues/14
just testing GH integration, ignore :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/14
just testing GH integration, ignore :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/46
That's hardly our fault :) If you want a specific instance to be
re-indexed, contact the appropriate people in charge of that.
---
If your project is set up for it, you can rep
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/46
But we don't run lists.apache.org :) We're a software community, not a
service provider.
---
If your project is set up for it, you can reply to this email and have your
re
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/59
Emails can be hidden by deleting the digest. This is what edit-lists.py
does currently. The original email is retained in the source index, but the
digest is removed, thus making the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/59
no, the issue can't be closed just yet. You can't delete emails by ID, only
mass-remove lists with that script.
---
If your project is set up for it, you can reply to this
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/64
This seems to be a webkit specific behavior (works as intended in Firefox).
I'm not sure we can work around that.
---
If your project is set up for it, you can reply to this
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/64
yes, both of those are webkit browsers.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/65
We'll need some javascript console output to go on, this is insufficient
data.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/66
this is not incorrect per se, it's just a conversion from the original date
to your own timezone. The TZ of an email is not saved in the digest.
---
If your project is set up f
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/66
that is to say, all timestamps are converted to UTC before they are saved.
If you wish to know the author's timezone, you need to view the source.
This is not something that
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/66
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/65
ugh, that's a nasty behavior by Opera. That line tries to assert whether
window.localStorage exists, and should just return false in this case. That it
turns into an error
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/65
a line number would be nice :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/65
yes, they are all webkit these days.
I've made a workaround, though it bugs me that these browsers behave so
poorly. They should just set the storage objects to null if th
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/65
already exists: http://crbug.com/357625
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/pull/56
I am inclined to -1 this. There is far too many unnecessary changes. The
markdown files and configuration snippets do NOT need license headers.
Documentation and examples do
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/57
which browser do you use for this?
it is supposed to escape the stuff, so it can render it as an URL - I'm not
sure where the bug lies.
---
If your project is set up for it
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/63
This was fixed in 19da4b5dd
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/63
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/44
return to? This is usually a brand new page/tab, as you get a link you need
to open.
So...just close the tab and be done with it? I'm not sure we need to
redirect back to any
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/53
Cannot reproduce. I think this is/was an old bug that has been fixed since
(maybe in Sam's rewrite?). The email is probably off by one hour because of
some daylight savings
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/53
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/67
Discussion at:
https://lists.apache.org/thread.html/7d8607ae4ba832e5d1dd3f7ef0ca14e2dde9bf377d4bed1a8aee7dab@%3Cdev.ponymail.apache.org%3E
---
If your project is set up for it, you
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/57
So here's where it gets complicated :) We're gonna need a publicly
available version of the email to test against :) Can you provide that?
---
If your project is set up f
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/68
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/68
bla bla bla
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/68
bla bla bla
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/68
aand closing this ticket ;)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/pull/56
the LICENSE file technically covers everything else, FWIW. When not
specified, the ALv2 applies to any file without an explicit license header. We
put license headers in our code for
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/44
Feel free to propose a patch (please make it a pull request if so).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/pull/56
If you can find any place that explicitly says documentation must be
licensed, then fine - but I haven't found such a policy and I don't agree that
we need this. I can reach
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/pull/56
Thank you for providing a factual link, Justin. This gives us some real
data to assess.
http://www.apache.org/legal/src-headers.html#faq-exceptions however states
that
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/pull/56
To clarify; I am not against putting license headers in a select files that
may warrant it. I am against accepting this PR and putting license headers in
ALL files, regardless of size
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/72
Can you provide any evidence that this is an issue with Pony Mail?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/72
This is an issue tracker for Pony Mail the project, not the specific
deployment on lists.apache.org.
If something is wrong with that specific instance, I'd think the first
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/78
you can set it to auto-scale to your screen height in your preferences, and
use the mouse scroll wheel to go to next/previous page. FWIW :)
---
If your project is set up for it, you
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/93
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/93
Sebastian, the AAA module bundled with Pony Mail is an example. To my
knowledge, it is not in use anywhere, nor should it be.
---
If your project is set up for it, you can reply to
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/100
Please don't conflate Pony Mail with lists.apache.org - the project is not
in charge of the installation.
---
If your project is set up for it, you can reply to this email and
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/100
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/104
Please direct that question to the Apache Infrastructure team, the Pony
Mail project can't really help with specific installations.
---
If your project is set up for it, yo
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/104
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/106
Iiiinteresting! It would appear a variable has gotten stuck somewhere.
I'll take a look when time allows :)
---
If your project is set up for it, you can reply to this emai
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/110
Not entirely true, html emails can be archived by using the html2text
converter. This is mentioned in
https://github.com/apache/incubator-ponymail/blob/master/docs/ARCHIVING.md - if
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/109
If you could point to a place in the code where it ignores 0-length bodies,
that would be helpful. As far as I can tell, it only ignores if the body cannot
be found, not simply if
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/108
This is currently by design, and thus not a bug. If you want the behavior
to change, I would suggest a discussion on the mailing list :)
---
If your project is set up for it, you
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/111
Would you say
http://95.85.36.224/list2.html?u...@accumulo.apache.org:2016-08 makes things
clearer? This is the (very early) preview of a new design branch. It's mainly
design
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/113
Pony Mail supports short URLs for this very purpose. They are disabled on
that specific installation due to the theoretical risk of duplicate short.
Since you refer to
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/113
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/113
Reopening as we're working on a better URL shortener for the
coffee-and-cake branch.
This will shorten the ID to something like 'PZ1ii9x4503us3eb04qvh3s'
---
If
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/92
Not a Pony Mail issue, that's internal to ASF
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project doe
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/92
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/85
Shouldn't this simply be a PR? :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/82
Agreed - this should be an easy PR, just have a check box and if checked,
set a cookie expiration date sometime in the future.
---
If your project is set up for it, you can reply to
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/50
This is being worked on in the coffee-and-cake branch now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/61
Closing as fixed, forgot to do that a while ago :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/61
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/114
Will be fixed in 0.10 (coffee-and-cake), thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user Humbedooh closed the issue at:
https://github.com/apache/incubator-ponymail/issues/114
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/140
I agree it should be using the same standards as in the aaa_examples dir.
However, it's not actively doing any harm as is. It is probably a file we
should just change to be m
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/155
Yes, mod_lua needs to be loaded for this to work. See
http://modlua.org/gs/installing - the module should be there already (unless
you built from source), as it's a standard
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/140
yes, that's my thinking - we make a wrapper that essentially tries to load
the _real_ AAA module, but if none is found, it just Åeturns a blank function,
so it'll work w
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/162
I think the main issue here is, elastic shouldn't error out on a 404, only
other 4xx/5xx errors.
it should be changed to uhm... something like "if code != 200 and code !
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/173
It's not so much top posting, but rather inconsistent ordering due to async
fetching gone wrong. This is slated to be fully fixed in 0.10
---
If your project is set up for it
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/178
IIRC, the chance of colliding two shortlinks with the new generator is
1:10^33.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/178
The new shortlink generator only allows shortlinks for IDs made by the
newer generators (it checks). if the old is used, it falls back to full IDs for
everything.
---
If your
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/178
old shortlinks should work, the new ones and the old ones use different
markers to denote which generator was used, and the new JS knows this.
---
If your project is set up for it
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/131
I suppose you could easily make a third option - the internals should
support it, so you just need the JS to add a *@$project.foo.bar option.
---
If your project is set up for it
Github user Humbedooh commented on the issue:
https://github.com/apache/incubator-ponymail/issues/181
Most likely a URI length issue here, various browsers only support a mailto
link of N kilobytes, the trick is figuring out when the limit has been hit and
then truncate. Obviously we
88 matches
Mail list logo
