sebbASF commented on issue #449: Bug: archiver ignores failures if dumponfail
is not defined
URL:
https://github.com/apache/incubator-ponymail/issues/449#issuecomment-388808124
The code catches Exception, but does nothing unless dumponfail is defined:
https://github.com/apache/incu
sebbASF commented on issue #423: Dump documents to disk on ES failure
URL:
https://github.com/apache/incubator-ponymail/issues/423#issuecomment-388807388
Created new bug #449
This is an automated message from the Apache Git S
sebbASF closed issue #423: Dump documents to disk on ES failure
URL: https://github.com/apache/incubator-ponymail/issues/423
This is an automated message from the Apache Git Service.
To respond to the message, please log on G
sebbASF opened a new issue #449: Bug: archiver ignores failures if dumponfail
is not defined
URL: https://github.com/apache/incubator-ponymail/issues/449
See #423
This is an automated message from the Apache Git Service.
To
sebbASF commented on issue #423: Dump documents to disk on ES failure
URL:
https://github.com/apache/incubator-ponymail/issues/423#issuecomment-388805578
Code causes archiver to ignore failures if dumponfail is not defined
Th
Humbedooh opened a new issue #423: Dump documents to disk on ES failure
URL: https://github.com/apache/incubator-ponymail/issues/423
Currently, when PM fails to archive to ES for whatever reason (typically
because the DB is unavailable), it just breaks and emails are in risk of ending
up n
sebbASF commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-388792467
No; it does not work like that. There is not a simple JSON interface that
can be exposed externally.
Whilst the JSON format can be captu
dimidd commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-388775302
I see, instead, would it be possible somehow to infer it from the existing
code
automagically? E.g. add an optional flag `--dump-json` to `im
dimidd commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-388775302
I see, would it be possible somehow to infer it from the existing code
automagically? E.g. add an optional flag `--dump-json` to `import-mbox.
sebbASF commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-388774425
As I noted earlier, the JSON format depends on ES and the schema (and
possibly other aspects of how PonyMail uses ES). It's not guaranteed stab
dimidd commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-388771950
Nothing, I just don't know what should be the exact format of the JSON.
E.g. how to set the list-id that the emails belong to.
2018-05-
sebbASF commented on issue #448: edit-list: handle config consistently
URL:
https://github.com/apache/incubator-ponymail/pull/448#issuecomment-388771339
elastic.py was an attempt to extract some of the common processing into a
separate module.
However perhaps it should be split further.
Humbedooh commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-388769182
What's preventing you from using the JSON format archiver.py pushes to ES?
You should be able to just push documents manually
--
dimidd commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-388768756
In my use case, I load a PST file, convert to json, do some processing, and
would love to have an option to load a json directly.
2018-
dimidd commented on issue #448: edit-list: handle config consistently
URL:
https://github.com/apache/incubator-ponymail/pull/448#issuecomment-388767700
Then perhaps we should abstract it into its own module?
2018-05-14 13:04 GMT+03:00 sebbASF :
> I've had a look at how the oth
sebbASF commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-388767750
ElasticSearch (ES) requires JSON for its API.
The JSON format is based on the requirements of ES and the database schema.
Both may change.
sebbASF commented on issue #448: edit-list: handle config consistently
URL:
https://github.com/apache/incubator-ponymail/pull/448#issuecomment-388764527
I've had a look at how the other tools behave.
Currently, archiver.py and import-mbox.py both read ponymail.cfg from the
parent di
sebbASF commented on issue #430: Enh: Add option to search all lists in the
domain (project) in Advanced Search
URL:
https://github.com/apache/incubator-ponymail/issues/430#issuecomment-388759343
This is a duplicate of #131
sebbASF closed issue #430: Enh: Add option to search all lists in the domain
(project) in Advanced Search
URL: https://github.com/apache/incubator-ponymail/issues/430
This is an automated message from the Apache Git Service.
Humbedooh commented on issue #448: edit-list: handle config consistently
URL:
https://github.com/apache/incubator-ponymail/pull/448#issuecomment-387810229
I think that's a very good compromise :)
This is an automated message
sebbASF commented on issue #448: edit-list: handle config consistently
URL:
https://github.com/apache/incubator-ponymail/pull/448#issuecomment-387803654
Agreed: only check tools/ if cannot find config in PWD.
I don't see how that can break anything except a test that expects to fail
be
dimidd commented on issue #448: edit-list: handle config consistently
URL:
https://github.com/apache/incubator-ponymail/pull/448#issuecomment-387714508
Perhaps to prevent breaking existing code we can check if the PWD has
`ponymail.cfg` and perefer it over the one in the `tools` dir.
Humbedooh commented on issue #448: edit-list: handle config consistently
URL:
https://github.com/apache/incubator-ponymail/pull/448#issuecomment-387701031
I'm generally in favor of this change, but it may be breaking existing
behavior, so it should at the very least be noted in the changel
dimidd opened a new pull request #448: edit-list: handle config consistently
URL: https://github.com/apache/incubator-ponymail/pull/448
Read the config file regardless of what dir the script was called.
Signed-off-by: Dimid Duchovny
--
dimidd commented on issue #447: Import from a local json file
URL:
https://github.com/apache/incubator-ponymail/issues/447#issuecomment-387685478
I've thought about something like this, but not sure how to set the list id.
```import sys
import os
import configparser
import a
dimidd opened a new issue #447: Import from a local json file
URL: https://github.com/apache/incubator-ponymail/issues/447
Hello,
Looks like `import-mbox.py` is already using json as an intermediate format
to store messages, before uploading to elasticsearch. Is it possible to impor
Humbedooh closed issue #446: Testing unicode subjects via PRs, ignore: 🍔 🍔 🍔
URL: https://github.com/apache/incubator-ponymail/issues/446
This is an automated message from the Apache Git Service.
To respond to the message, pl
Humbedooh commented on issue #446: Testing unicode subjects via PRs, ignore: 🍔
🍔 🍔
URL:
https://github.com/apache/incubator-ponymail/issues/446#issuecomment-379737278
time for obvious fix...
This is an automated message from
Humbedooh commented on issue #446: Testing unicode subjects via PRs, ignore: 🍔
🍔 🍔
URL:
https://github.com/apache/incubator-ponymail/issues/446#issuecomment-379736064
might be gitbox that's broken..
This is an auto
Humbedooh commented on issue #446: Testing unicode subjects via PRs, ignore: 🍔
🍔 🍔
URL:
https://github.com/apache/incubator-ponymail/issues/446#issuecomment-379735214
bla bla
This is an automated message from the Apache Git
Humbedooh commented on issue #446: Testing unicode subjects via PRs, ignore: 🍔
🍔 🍔
URL:
https://github.com/apache/incubator-ponymail/issues/446#issuecomment-379734643
flood flood :)
This is an automated message from the Apac
Humbedooh commented on issue #446: Testing unicode subjects via PRs, ignore: 🍔
🍔 🍔
URL:
https://github.com/apache/incubator-ponymail/issues/446#issuecomment-379734349
ignore still :)
This is an automated message from the Apa
Humbedooh opened a new issue #446: Testing unicode subjects via PRs, ignore: 🍔
🍔 🍔
URL: https://github.com/apache/incubator-ponymail/issues/446
we like 🍔🍔🍔
This is an automated message from the Apache Git Service.
To respond
Humbedooh commented on issue #446: Testing unicode subjects via PRs, ignore: 🍔
🍔 🍔
URL:
https://github.com/apache/incubator-ponymail/issues/446#issuecomment-379734192
of course this renders poorly on lists
This is an automat
Humbedooh closed issue #446: Testing unicode subjects via PRs, ignore: 🍔 🍔 🍔
URL: https://github.com/apache/incubator-ponymail/issues/446
This is an automated message from the Apache Git Service.
To respond to the message, pl
Humbedooh opened a new issue #446: Testing unicode subjects via PRs, ignore: 🍔
🍔 🍔
URL: https://github.com/apache/incubator-ponymail/issues/446
we like 🍔🍔🍔
This is an automated message from the Apache Git Service.
To respond
ctubbsii commented on issue #365: Log In with Google creates extra account
URL:
https://github.com/apache/incubator-ponymail/issues/365#issuecomment-378773892
I ran into this again today. I logged in using ASF credentials, and it lists
my apache.org email as primary, and my gmail as second
Humbedooh opened a new issue #445: Composer should use unicode as encoding
URL: https://github.com/apache/incubator-ponymail/issues/445
The composer script should use unicode for replies/topics, at the very least
in the body of the email.
---
asfgit closed issue #444: thread.lua should take References header into account
URL: https://github.com/apache/incubator-ponymail/issues/444
This is an automated message from the Apache Git Service.
To respond to the message,
Humbedooh opened a new issue #444: thread.lua should take References header
into account
URL: https://github.com/apache/incubator-ponymail/issues/444
Currently, threading is done by looking at the in-reply-to headers only. As
this will vary from client to client (which header they use), we
sebbASF commented on issue #443: Enh: does not handle non-ASCII subjects well
URL:
https://github.com/apache/incubator-ponymail/issues/443#issuecomment-377541196
See also INFRA-16268
This is an automated message from the Apac
Humbedooh commented on issue #443: Bug: does not handle non-ASCII subjects well
URL:
https://github.com/apache/incubator-ponymail/issues/443#issuecomment-377521992
That is true - doesn't mean pony mail has a bug just because mod_mbox is
more lenient with faulty emails :). PM tries to decod
sebbASF commented on issue #443: Bug: does not handle non-ASCII subjects well
URL:
https://github.com/apache/incubator-ponymail/issues/443#issuecomment-377521312
However mod_mbox copes fine with the mail.
This is an automated
Humbedooh commented on issue #443: Bug: does not handle non-ASCII subjects well
URL:
https://github.com/apache/incubator-ponymail/issues/443#issuecomment-377520027
I believe this isn't to do with Pony Mail, but rather that the subject
hasn't been base64-encoded properly in the email. Sound
sebbASF opened a new issue #443: Bug: does not handle non-ASCII subjects well
URL: https://github.com/apache/incubator-ponymail/issues/443
For example, the following mail has a mangled subject display:
https://lists.apache.org/thread.html/caf3f3f78c478020f0c0069715bd303f3ecb67bf16948
sebbASF commented on issue #441: Bug: generator should not rely on parsed data,
in particular dates
URL:
https://github.com/apache/incubator-ponymail/issues/441#issuecomment-371247877
Another difference is how >From_ lines are treated when importing.
This will depend on the parser and i
asfgit closed issue #442: Enh: make MboxoFactory optional
URL: https://github.com/apache/incubator-ponymail/issues/442
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub
sebbASF opened a new issue #442: Enh: make MboxoFactory optional
URL: https://github.com/apache/incubator-ponymail/issues/442
import-mbox.py currently unconditionally uses MboxoFactory.
It would be useful to make this optional
-
sebbASF opened a new issue #441: Bug: generator should not rely on parsed data,
in particular dates
URL: https://github.com/apache/incubator-ponymail/issues/441
The generator methods currently rely on the parsed message to create the
hash.
This is subject to change if the parsing should
asfgit closed issue #440: Bug: duplication of data in response from thread.lua
URL: https://github.com/apache/incubator-ponymail/issues/440
This is an automated message from the Apache Git Service.
To respond to the message,
sebbASF opened a new issue #440: Bug: duplication of data in response from
thread.lua
URL: https://github.com/apache/incubator-ponymail/issues/440
The contents of the JSON "thread" attribute is also present as the first
entry in the "emails" attribute.
This is wasteful.
---
sebbASF commented on issue #439: Bug: stats.lua cannot handle deep nesting
URL:
https://github.com/apache/incubator-ponymail/issues/439#issuecomment-369756431
It appears that Jenkins links multiple runs of the same job together; each
run references the previous one.
--
sebbASF commented on issue #427: Bug: GUI gets threading wrong if mail happens
to have same subject
URL:
https://github.com/apache/incubator-ponymail/issues/427#issuecomment-369431232
AFAIK, the subject line can change in a thread.
For example, JIRA messages include a [Created], [Update
sebbASF commented on issue #427: Bug: GUI gets threading wrong if mail happens
to have same subject
URL:
https://github.com/apache/incubator-ponymail/issues/427#issuecomment-369431232
AFAIK, the subject line can change in a thread.
For example, JIRA messages include a [Created], [Update
sebbASF opened a new issue #439: Bug: stats.lua cannot handle deep nesting
URL: https://github.com/apache/incubator-ponymail/issues/439
stats.lua tries to calculate message threading.
However if too many messages reference each other, the code crashes with an
error:
site/api/s
wrowe commented on issue #427: Bug: GUI gets threading wrong if mail happens to
have same subject
URL:
https://github.com/apache/incubator-ponymail/issues/427#issuecomment-368958122
Is the converse also true? Noticed that the threaded browse is not forking
off messages with changed subjec
asfgit closed issue #438: Enh: option to reduce stats.lua output
URL: https://github.com/apache/incubator-ponymail/issues/438
This is an automated message from the Apache Git Service.
To respond to the message, please log on
sebbASF opened a new issue #438: Enh: option to reduce stats.lua output
URL: https://github.com/apache/incubator-ponymail/issues/438
The stats.lua output includes lists of emails, threads and participants.
Only the emails are really required as the threads and participants can be
dir
sebbASF opened a new issue #437: Bug: importer should not store mails that
don't have a Date: header
URL: https://github.com/apache/incubator-ponymail/issues/437
Related to #436, at present the importer uses the current timestamp if the
mail has no Date: header.
Any such mail will be fi
sebbASF opened a new issue #436: Enh: option to use timestamp from headers if
there is no Date: header
URL: https://github.com/apache/incubator-ponymail/issues/436
Some messages don't have a Date: header.
The importer generally runs a long while after the messages were sent, so
usin
sebbASF commented on issue #435: import-mbox: Clarify List-ID format
URL:
https://github.com/apache/incubator-ponymail/pull/435#issuecomment-367616956
Thanks; good idea
This is an automated message from the Apache Git Service
sebbASF closed pull request #435: import-mbox: Clarify List-ID format
URL: https://github.com/apache/incubator-ponymail/pull/435
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign
dimidd commented on issue #435: import-mbox: Clarify List-ID format
URL:
https://github.com/apache/incubator-ponymail/pull/435#issuecomment-367616506
This should prevent issues such as
https://github.com/apache/incubator-ponymail/issues/433.
---
dimidd opened a new pull request #435: import-mbox: Clarify List-ID format
URL: https://github.com/apache/incubator-ponymail/pull/435
The List-ID parameter must have a format of @ .
E.g. myl...@example.com
Make the user aware of that by clarifying the parameter's description.
dimidd closed issue #433: Emails not showing after importing from archive
URL: https://github.com/apache/incubator-ponymail/issues/433
This is an automated message from the Apache Git Service.
To respond to the message, pleas
dimidd commented on issue #433: Emails not showing after importing from archive
URL:
https://github.com/apache/incubator-ponymail/issues/433#issuecomment-367333637
`/api/preferences.lua` showed that `lists` is empty. Anyhow, I re-imported,
this time using `--lid myl...@example.com`, and ev
asfgit closed issue #356: Inconsistent LID validation
URL: https://github.com/apache/incubator-ponymail/issues/356
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and
sebbASF commented on issue #356: Inconsistent LID validation
URL:
https://github.com/apache/incubator-ponymail/issues/356#issuecomment-367080855
There seems no point in requiring the domain to be at least 3 chars long.
The rest of the code works OK with shorter domains.
asfgit closed issue #434: Bug: does not make sense to allow empty domain name
in LID
URL: https://github.com/apache/incubator-ponymail/issues/434
This is an automated message from the Apache Git Service.
To respond to the me
sebbASF opened a new issue #434: Bug: does not make sense to allow empty domain
name in LID
URL: https://github.com/apache/incubator-ponymail/issues/434
The parseLid function in lib/aaa.lua currently matches a LID of the form
An empty domain part does not make sense
sebbASF commented on issue #356: Inconsistent LID validation
URL:
https://github.com/apache/incubator-ponymail/issues/356#issuecomment-367037406
Further, preferences.lua requires a lid to contain both a list and a domain.
This is not checked by the importer or archiver.
sebbASF commented on issue #433: Emails not showing after importing from archive
URL:
https://github.com/apache/incubator-ponymail/issues/433#issuecomment-367006182
I think the problem might be the list-id.
If you used
--lid 'mylist'
as per the description it looks like this
sebbASF commented on issue #433: Emails not showing after importing from archive
URL:
https://github.com/apache/incubator-ponymail/issues/433#issuecomment-367007248
The following path should show what mailing lists are available:
http://your.host/api/preferences.lua
sebbASF commented on issue #433: Emails not showing after importing from archive
URL:
https://github.com/apache/incubator-ponymail/issues/433#issuecomment-367006182
I think the problem might be the list-id.
If you used
--lid 'mylist'
as per the description it looks like this
dimidd commented on issue #433: Emails not showing after importing from archive
URL:
https://github.com/apache/incubator-ponymail/issues/433#issuecomment-366973436
Thanks, the former. `list.html?mylist` is also empty.
screenshot: 
Humbedooh commented on issue #433: Emails not showing after importing from
archive
URL:
https://github.com/apache/incubator-ponymail/issues/433#issuecomment-366965096
When you say 'emails not showing', do you mean the list names are not
showing on the index page, or do you have the lists
dimidd commented on issue #433: Emails not showing after importing from archive
URL:
https://github.com/apache/incubator-ponymail/issues/433#issuecomment-366964661
Unfortunately, I didn't save the log, but it said all messages were imported
successfully but a few.
sebbASF commented on issue #433: Emails not showing after importing from archive
URL:
https://github.com/apache/incubator-ponymail/issues/433#issuecomment-366713366
Were there any messages reported when you did the import?
Th
dimidd opened a new issue #433: Emails not showing after importing from archive
URL: https://github.com/apache/incubator-ponymail/issues/433
Hello,
I might be missing something trivial, but after installing ponymail, and
importing emails from an mbox file, I don't see any lists in po
asfgit closed issue #432: Indentation in mail content (leading white-space) not
shown
URL: https://github.com/apache/incubator-ponymail/issues/432
This is an automated message from the Apache Git Service.
To respond to the m
sebbASF commented on issue #432: Indentation in mail content (leading
white-space) not shown
URL:
https://github.com/apache/incubator-ponymail/issues/432#issuecomment-365124828
Thanks for the sample.
Please file a separate issue for a separate bug.
-
ddekany commented on issue #432: Indentation in mail content (leading
white-space) not shown
URL:
https://github.com/apache/incubator-ponymail/issues/432#issuecomment-365065557
Sure:
[https://lists.apache.org/thread.html/0bc90b453f106adfdb6ba1fc91cbbb63daa386be3fe7e2463362a2bd@](https://l
sebbASF commented on issue #432: Indentation in mail content (leading
white-space) not shown
URL:
https://github.com/apache/incubator-ponymail/issues/432#issuecomment-364989820
Can you please provide some sample links to show the problem?
--
ddekany opened a new issue #432: Indentation (leading white-space) not shown
URL: https://github.com/apache/incubator-ponymail/issues/432
Currently you are using `white-space: pre-line` on the `pre` that holds the
mail body (for text/plain mail content). This un-indents the lines of the mai
sebbASF commented on issue #418: unable to access pony mail
URL:
https://github.com/apache/incubator-ponymail/issues/418#issuecomment-362668801
Cannot reproduce
This is an automated message from the Apache Git Service.
To res
sebbASF closed issue #418: unable to access pony mail
URL: https://github.com/apache/incubator-ponymail/issues/418
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and
sebbASF commented on issue #431: Use correct dependency order to fix OAuth
login problem
URL:
https://github.com/apache/incubator-ponymail/pull/431#issuecomment-362663000
Thanks for the report and the PR
This is an automated
sebbASF commented on issue #431: Use correct dependency order to fix OAuth
login problem
URL:
https://github.com/apache/incubator-ponymail/pull/431#issuecomment-362662871
Note: checked the other html files -config.js is loaded just after
bootstrap, so OK
-
asfgit closed pull request #431: Use correct dependency order to fix OAuth
login problem
URL: https://github.com/apache/incubator-ponymail/pull/431
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
sebbASF commented on issue #431: Use correct dependency order to fix OAuth
login problem
URL:
https://github.com/apache/incubator-ponymail/pull/431#issuecomment-362660581
It looks like there's another dependency order problem:
ponymail.js references pm_config which is defined on config.
sbp opened a new pull request #431: Use correct dependency order to fix OAuth
login problem
URL: https://github.com/apache/incubator-ponymail/pull/431
OAuth login does not presently work if configured in `config.js`. The issue
is that constructing OAuth login URLs in `oauth.html` requires
bindul opened a new issue #430: Enh: Add option to search all lists in the
domain (project) in Advanced Search
URL: https://github.com/apache/incubator-ponymail/issues/430
On lists.apache.org , when using the regular search (top menu), you can
choose to search _This list_ or _All tlp.apach
sebbASF commented on issue #429: Do less aggressive subject nesting
URL:
https://github.com/apache/incubator-ponymail/pull/429#issuecomment-355861618
There will only be 100 unconnected threads if the mailers are broken and
don't provide Reference headers. Are there many such broken clients
sebbASF commented on issue #428: Initial stab at fixing #426
URL:
https://github.com/apache/incubator-ponymail/pull/428#issuecomment-355861136
As per my comment on #426, there should be no padding at all.
Having a maximum is a separate feature, and a sensible value will depend on
th
Humbedooh commented on issue #429: Do less aggressive subject nesting
URL:
https://github.com/apache/incubator-ponymail/pull/429#issuecomment-355861021
That will only be true if there is no IRT or References header.
It's by no means perfect, but would you prefer the alternative that we c
sebbASF commented on issue #429: Do less aggressive subject nesting
URL:
https://github.com/apache/incubator-ponymail/pull/429#issuecomment-355860932
I don't think it makes sense to match by subject even if there is a reply
prefix indicator.
If there are two identical subjects, they
Humbedooh commented on issue #427: Bug: GUI gets threading wrong if mail
happens to have same subject
URL:
https://github.com/apache/incubator-ponymail/issues/427#issuecomment-355860563
It is primarily driven by that yes - sometimes those headers are missing
from replies, and we improvise
sebbASF commented on issue #426: Bug: GUI squashes deeply nested conversations
URL:
https://github.com/apache/incubator-ponymail/issues/426#issuecomment-355860543
IMO the nested bodies should all have the same RH margins; only the LH
margin needs to change in order to support the nesting m
sebbASF commented on issue #427: Bug: GUI gets threading wrong if mail happens
to have same subject
URL:
https://github.com/apache/incubator-ponymail/issues/427#issuecomment-355860198
Surely the nesting needs to be driven by the Reference headers instead of
the subject?
Looking for
Humbedooh opened a new pull request #429: Do less aggressive subject nesting
URL: https://github.com/apache/incubator-ponymail/pull/429
This addresses #427 by only allowing sort-by-subject to
happen if we can establish that an email is a reply.
---
201 - 300 of 301 matches
Mail list logo
