[GitHub] dimidd opened a new issue #447: Import from a local json file

2018-05-07 Thread GitBox
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

[GitHub] sebbASF commented on issue #448: edit-list: handle config consistently

2018-05-14 Thread GitBox
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

[GitHub] dimidd commented on issue #448: edit-list: handle config consistently

2018-05-14 Thread GitBox
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 : >

[GitHub] sebbASF commented on issue #447: Import from a local json file

2018-05-14 Thread GitBox
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

[GitHub] sebbASF closed issue #430: Enh: Add option to search all lists in the domain (project) in Advanced Search

2018-05-14 Thread GitBox
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

[GitHub] sebbASF commented on issue #430: Enh: Add option to search all lists in the domain (project) in Advanced Search

2018-05-14 Thread GitBox
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

[GitHub] sebbASF commented on issue #448: edit-list: handle config consistently

2018-05-14 Thread GitBox
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

[GitHub] sebbASF commented on issue #447: Import from a local json file

2018-05-14 Thread GitBox
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

[GitHub] sebbASF closed issue #423: Dump documents to disk on ES failure

2018-05-14 Thread GitBox
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

[GitHub] sebbASF opened a new issue #449: Bug: archiver ignores failures if dumponfail is not defined

2018-05-14 Thread GitBox
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

[GitHub] Humbedooh opened a new issue #423: Dump documents to disk on ES failure

2018-05-14 Thread GitBox
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

[GitHub] sebbASF commented on issue #447: Import from a local json file

2018-05-14 Thread GitBox
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

[GitHub] sebbASF commented on issue #423: Dump documents to disk on ES failure

2018-05-14 Thread GitBox
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

[GitHub] sebbASF commented on issue #449: Bug: archiver ignores failures if dumponfail is not defined

2018-05-14 Thread GitBox
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:

[GitHub] dimidd commented on issue #447: Import from a local json file

2018-05-14 Thread GitBox
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.

[GitHub] Humbedooh commented on issue #447: Import from a local json file

2018-05-14 Thread GitBox
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

[GitHub] dimidd commented on issue #447: Import from a local json file

2018-05-14 Thread GitBox
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.

[GitHub] dimidd commented on issue #447: Import from a local json file

2018-05-14 Thread GitBox
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

[GitHub] dimidd commented on issue #447: Import from a local json file

2018-05-14 Thread GitBox
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

[GitHub] asfgit closed issue #449: Bug: archiver ignores failures if dumponfail is not defined

2018-05-14 Thread GitBox
asfgit closed issue #449: Bug: archiver ignores failures if dumponfail is not defined URL: https://github.com/apache/incubator-ponymail/issues/449 This is an automated message from the Apache Git Service. To respond to the

[GitHub] dimidd opened a new pull request #448: edit-list: handle config consistently

2018-05-09 Thread GitBox
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

[GitHub] Humbedooh commented on issue #448: edit-list: handle config consistently

2018-05-09 Thread GitBox
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

[GitHub] dimidd commented on issue #447: Import from a local json file

2018-05-09 Thread GitBox
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

[GitHub] dimidd commented on issue #448: edit-list: handle config consistently

2018-05-09 Thread GitBox
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.

[GitHub] Humbedooh commented on issue #448: edit-list: handle config consistently

2018-05-09 Thread GitBox
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

[GitHub] sebbASF commented on issue #448: edit-list: handle config consistently

2018-05-09 Thread GitBox
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

[GitHub] sebbASF closed issue #447: Import from a local json file

2018-05-18 Thread GitBox
sebbASF closed issue #447: Import from a local json file URL: https://github.com/apache/incubator-ponymail/issues/447 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub

[GitHub] sebbASF commented on issue #447: Import from a local json file

2018-05-18 Thread GitBox
sebbASF commented on issue #447: Import from a local json file URL: https://github.com/apache/incubator-ponymail/issues/447#issuecomment-390189619 Seems to me this has reached a natural close This is an automated message

[GitHub] asfgit closed issue #450: Bug: copy-list.py does not work

2018-05-17 Thread GitBox
asfgit closed issue #450: Bug: copy-list.py does not work URL: https://github.com/apache/incubator-ponymail/issues/450 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub

[GitHub] sebbASF opened a new issue #451: Bug: unnecessary test (will always succeed) in copy-list.py

2018-05-17 Thread GitBox
sebbASF opened a new issue #451: Bug: unnecessary test (will always succeed) in copy-list.py URL: https://github.com/apache/incubator-ponymail/issues/451 The code at https://github.com/apache/incubator-ponymail/blob/master/tools/copy-list.py#L121 says: if targetLID or newdb:

[GitHub] asfgit closed issue #451: Bug: unnecessary test (will always succeed) in copy-list.py

2018-05-17 Thread GitBox
asfgit closed issue #451: Bug: unnecessary test (will always succeed) in copy-list.py URL: https://github.com/apache/incubator-ponymail/issues/451 This is an automated message from the Apache Git Service. To respond to the

[GitHub] sebbASF commented on issue #450: Bug: copy-list.py does not work

2018-05-17 Thread GitBox
sebbASF commented on issue #450: Bug: copy-list.py does not work URL: https://github.com/apache/incubator-ponymail/issues/450#issuecomment-389847056 Another bug: if the --newdb option is present the code ignores the --target name, yet it allows both to be specified. Either the

[GitHub] asfgit closed issue #452: Bug: setup.py --default should not prompt for urlPrefix

2018-05-17 Thread GitBox
asfgit closed issue #452: Bug: setup.py --default should not prompt for urlPrefix URL: https://github.com/apache/incubator-ponymail/issues/452 This is an automated message from the Apache Git Service. To respond to the

[GitHub] sebbASF opened a new issue #452: Bug: setup.py --default should not prompt for urlPrefix

2018-05-17 Thread GitBox
sebbASF opened a new issue #452: Bug: setup.py --default should not prompt for urlPrefix URL: https://github.com/apache/incubator-ponymail/issues/452 If the --default option is used, setup.py should not prompt for optional parameters such as urlPrefix

[GitHub] sebbASF opened a new issue #450: Bug: copy-list.py does not work

2018-05-16 Thread GitBox
sebbASF opened a new issue #450: Bug: copy-list.py does not work URL: https://github.com/apache/incubator-ponymail/issues/450 The copy-list.py tool does not work when copying source to target within a database. This is partly because it updates the wrong field: if targetLID:

[GitHub] sebbASF opened a new issue #457: Bug: install.py uses deprecated method and Python2 - is it needed?

2018-05-23 Thread GitBox
sebbASF opened a new issue #457: Bug: install.py uses deprecated method and Python2 - is it needed? URL: https://github.com/apache/incubator-ponymail/issues/457 install.py uses the deprecated method platform.linux_distribution() There does not appear to be a built-in replacement.

[GitHub] sebbASF opened a new issue #459: Bug: variable 'mid' used before assignment in archiver.py

2018-05-23 Thread GitBox
sebbASF opened a new issue #459: Bug: variable 'mid' used before assignment in archiver.py URL: https://github.com/apache/incubator-ponymail/issues/459 pylint reports: E:481,71: Using variable 'mid' before assignment [1] [1]

[GitHub] sebbASF commented on issue #448: edit-list: handle config consistently

2018-05-23 Thread GitBox
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

[GitHub] asfgit closed issue #459: Bug: variable 'mid' used before assignment in archiver.py

2018-05-23 Thread GitBox
asfgit closed issue #459: Bug: variable 'mid' used before assignment in archiver.py URL: https://github.com/apache/incubator-ponymail/issues/459 This is an automated message from the Apache Git Service. To respond to the

[GitHub] sebbASF opened a new issue #458: Bug: tmpname used before it has been set up in import-mbox

2018-05-23 Thread GitBox
sebbASF opened a new issue #458: Bug: tmpname used before it has been set up in import-mbox URL: https://github.com/apache/incubator-ponymail/issues/458 pylint reports that the code at line 178 [1] uses tmpname, but it has not yet been set up. It looks like this was caused by

[GitHub] dimidd commented on issue #448: edit-list: handle config consistently

2018-05-23 Thread GitBox
dimidd commented on issue #448: edit-list: handle config consistently URL: https://github.com/apache/incubator-ponymail/pull/448#issuecomment-391308477 OK, then this PR is redundant. This is an automated message from the

[GitHub] asfgit closed issue #458: Bug: tmpname used before it has been set up in import-mbox

2018-05-24 Thread GitBox
asfgit closed issue #458: Bug: tmpname used before it has been set up in import-mbox URL: https://github.com/apache/incubator-ponymail/issues/458 This is an automated message from the Apache Git Service. To respond to the

[GitHub] sebbASF opened a new issue #463: Bug: Archiver#msgbody: poor handling of conversion to string

2018-05-25 Thread GitBox
sebbASF opened a new issue #463: Bug: Archiver#msgbody: poor handling of conversion to string URL: https://github.com/apache/incubator-ponymail/issues/463 The method msgbody returns a string. This is converted here:

[GitHub] sebbASF opened a new issue #461: Bug: archiver.py can never detect content-type: flowed

2018-05-25 Thread GitBox
sebbASF opened a new issue #461: Bug: archiver.py can never detect content-type: flowed URL: https://github.com/apache/incubator-ponymail/issues/461 The code to detect content-type: flowed is here:

[GitHub] sebbASF opened a new issue #462: Bug: archiver.py: convertToWrapped expects bytes

2018-05-25 Thread GitBox
sebbASF opened a new issue #462: Bug: archiver.py: convertToWrapped expects bytes URL: https://github.com/apache/incubator-ponymail/issues/462 convertToWrapped is being called incorrectly; it expects bytes.

[GitHub] asfgit closed issue #461: Bug: archiver.py can never detect content-type: flowed

2018-05-25 Thread GitBox
asfgit closed issue #461: Bug: archiver.py can never detect content-type: flowed URL: https://github.com/apache/incubator-ponymail/issues/461 This is an automated message from the Apache Git Service. To respond to the

[GitHub] sebbASF commented on issue #463: Bug: Archiver#msgbody: poor handling of conversion to string

2018-05-25 Thread GitBox
sebbASF commented on issue #463: Bug: Archiver#msgbody: poor handling of conversion to string URL: https://github.com/apache/incubator-ponymail/issues/463#issuecomment-392104749 Note that a successful decode will change type(body) to str, so the first charset will be used if it succeeds.

[GitHub] sebbASF commented on issue #462: Bug: archiver.py: convertToWrapped expects bytes

2018-05-25 Thread GitBox
sebbASF commented on issue #462: Bug: archiver.py: convertToWrapped expects bytes URL: https://github.com/apache/incubator-ponymail/issues/462#issuecomment-392098583 Fixing this changes the generated message ids for the applicable messages. Also, the reformatted result has line breaks

[GitHub] sebbASF commented on issue #463: Bug: Archiver#msgbody: poor handling of conversion to string

2018-05-25 Thread GitBox
sebbASF commented on issue #463: Bug: Archiver#msgbody: poor handling of conversion to string URL: https://github.com/apache/incubator-ponymail/issues/463#issuecomment-392104749 If the code is fixed to apply only a single charset, this may affect the output and thus the generated message

[GitHub] asfgit closed issue #460: Bug: import-mbox.py: imap code should not reset ES instance

2018-05-24 Thread GitBox
asfgit closed issue #460: Bug: import-mbox.py: imap code should not reset ES instance URL: https://github.com/apache/incubator-ponymail/issues/460 This is an automated message from the Apache Git Service. To respond to the

[GitHub] sebbASF opened a new issue #460: Bug: import-mbox.py: imap code should not reset ES instance

2018-05-24 Thread GitBox
sebbASF opened a new issue #460: Bug: import-mbox.py: imap code should not reset ES instance URL: https://github.com/apache/incubator-ponymail/issues/460 If the source has an imap(s) URL, the code overwrites the ES instance:

[GitHub] sebbASF opened a new issue #454: Bug: push-failures.py expects to find non-existent 'id' key in json file

2018-05-18 Thread GitBox
sebbASF opened a new issue #454: Bug: push-failures.py expects to find non-existent 'id' key in json file URL: https://github.com/apache/incubator-ponymail/issues/454 The push-failures script reads the .json files created by the archiver if it cannot write a message to the database.

[GitHub] asfgit closed issue #454: Bug: push-failures.py expects to find non-existent 'id' key in json file

2018-05-18 Thread GitBox
asfgit closed issue #454: Bug: push-failures.py expects to find non-existent 'id' key in json file URL: https://github.com/apache/incubator-ponymail/issues/454 This is an automated message from the Apache Git Service. To

[GitHub] sebbASF opened a new issue #453: Bug: setup.py fails with ES2 - fielddata

2018-05-17 Thread GitBox
sebbASF opened a new issue #453: Bug: setup.py fails with ES2 - fielddata URL: https://github.com/apache/incubator-ponymail/issues/453 The way fielddata is handled changed in ES 5; it's now a boolean. It's not needed in ES2 because the default is OK, so drop the setting if creating ES2

[GitHub] asfgit closed issue #453: Bug: setup.py fails with ES2 - fielddata

2018-05-17 Thread GitBox
asfgit closed issue #453: Bug: setup.py fails with ES2 - fielddata URL: https://github.com/apache/incubator-ponymail/issues/453 This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] asfgit closed issue #456: Enh: remove duplicated code in tools scripts by using elastic.py module

2018-05-23 Thread GitBox
asfgit closed issue #456: Enh: remove duplicated code in tools scripts by using elastic.py module URL: https://github.com/apache/incubator-ponymail/issues/456 This is an automated message from the Apache Git Service. To

[GitHub] asfgit closed issue #345: Bug: ES 5.x does not support word-cloud (stats.lua)

2018-05-17 Thread GitBox
asfgit closed issue #345: Bug: ES 5.x does not support word-cloud (stats.lua) URL: https://github.com/apache/incubator-ponymail/issues/345 This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] sebbASF commented on issue #242: Website Fix - security issue reporting

2018-05-17 Thread GitBox
sebbASF commented on issue #242: Website Fix - security issue reporting URL: https://github.com/apache/incubator-ponymail/issues/242#issuecomment-390047308 The normal procedure is to inform security@apache; they will then inform the (P)PMC.

[GitHub] sebbASF closed issue #242: Website Fix - security issue reporting

2018-05-17 Thread GitBox
sebbASF closed issue #242: Website Fix - security issue reporting URL: https://github.com/apache/incubator-ponymail/issues/242 This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] BigBlueHat opened a new issue #468: Working on *just* the UX?

2018-06-12 Thread GitBox
BigBlueHat opened a new issue #468: Working on *just* the UX? URL: https://github.com/apache/incubator-ponymail/issues/468 I'd love to contribute to the UX, but setting up Elastic Search, Python3, Lua, and Apache or NGINX is a bit much to tweak some HTML and JS which gets it's "meaning"

[GitHub] sebbASF commented on issue #465: setup.py tries to install Python modules

2018-05-27 Thread GitBox
sebbASF commented on issue #465: setup.py tries to install Python modules URL: https://github.com/apache/incubator-ponymail/issues/465#issuecomment-392324822 It looks as though this processing was originally done in the install.py script.

[GitHub] asfgit closed issue #464: Bug: setup.py uses ES library version to decide what features the database supports

2018-05-27 Thread GitBox
asfgit closed issue #464: Bug: setup.py uses ES library version to decide what features the database supports URL: https://github.com/apache/incubator-ponymail/issues/464 This is an automated message from the Apache Git

[GitHub] sebbASF opened a new issue #464: Bug: setup.py uses ES library version to decide what features the database supports

2018-05-26 Thread GitBox
sebbASF opened a new issue #464: Bug: setup.py uses ES library version to decide what features the database supports URL: https://github.com/apache/incubator-ponymail/issues/464 The setup.py code includes some setup that depends on the database version. Currently it checks the version

[GitHub] sebbASF opened a new issue #465: setup.py tries to install Python modules

2018-05-27 Thread GitBox
sebbASF opened a new issue #465: setup.py tries to install Python modules URL: https://github.com/apache/incubator-ponymail/issues/465 If the import of elasticsearch fails, setup.py tries to install some Python modules. This uses pip3 and is unconditionally tried if the current user is

[GitHub] sebbASF commented on issue #466: Bug: thread.lua fetches replies from other lists

2018-05-30 Thread GitBox
sebbASF commented on issue #466: Bug: thread.lua fetches replies from other lists URL: https://github.com/apache/incubator-ponymail/issues/466#issuecomment-393081539 If the same mbox file is present on multiple lists, then it's not surprising that PonyMail shows the mails from both.

[GitHub] dimidd opened a new issue #466: Bug: thread.lua fetches replies from other lists

2018-05-30 Thread GitBox
dimidd opened a new issue #466: Bug: thread.lua fetches replies from other lists URL: https://github.com/apache/incubator-ponymail/issues/466 How to reproduce: import the same mbox file to two different lists. Open a thread of list1, replies which belong to list2 will be shown as well.

[GitHub] dimidd closed issue #466: Bug: thread.lua fetches replies from other lists

2018-05-30 Thread GitBox
dimidd closed issue #466: Bug: thread.lua fetches replies from other lists URL: https://github.com/apache/incubator-ponymail/issues/466 This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] dimidd commented on issue #466: Bug: thread.lua fetches replies from other lists

2018-05-30 Thread GitBox
dimidd commented on issue #466: Bug: thread.lua fetches replies from other lists URL: https://github.com/apache/incubator-ponymail/issues/466#issuecomment-39308 I see, thanks. This is an automated message from the

[GitHub] dimidd opened a new pull request #467: setup: move mappings to a separate file

2018-05-31 Thread GitBox
dimidd opened a new pull request #467: setup: move mappings to a separate file URL: https://github.com/apache/incubator-ponymail/pull/467 * This will allow to easily customize the mappings, implements #455. * Strip whitespace Signed-off-by: Dimid Duchovny

[GitHub] dimidd commented on issue #467: setup: move mappings to a separate file

2018-06-03 Thread GitBox
dimidd commented on issue #467: setup: move mappings to a separate file URL: https://github.com/apache/incubator-ponymail/pull/467#issuecomment-394145258 OK, I'll make a separate PR for whitespace fixes. Regarding comments, how about using YAML which does support one-line comments?

[GitHub] sebbASF commented on issue #467: setup: move mappings to a separate file

2018-06-03 Thread GitBox
sebbASF commented on issue #467: setup: move mappings to a separate file URL: https://github.com/apache/incubator-ponymail/pull/467#issuecomment-394152476 I'm still not convinced that there is a general use case for a separate mappings file. What are the changes you want to make?

[GitHub] dimidd closed pull request #467: setup: move mappings to a separate file

2018-06-03 Thread GitBox
dimidd closed pull request #467: setup: move mappings to a separate file URL: https://github.com/apache/incubator-ponymail/pull/467 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

[GitHub] sebbASF commented on issue #467: setup: move mappings to a separate file

2018-05-31 Thread GitBox
sebbASF commented on issue #467: setup: move mappings to a separate file URL: https://github.com/apache/incubator-ponymail/pull/467#issuecomment-393665350 Please don't mix changes in a single PR; this makes it harder to review. Also, I'm not convinced that there is a need for the

[GitHub] Humbedooh opened a new pull request #429: Do less aggressive subject nesting

2018-01-07 Thread GitBox
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.

[GitHub] sebbASF commented on issue #427: Bug: GUI gets threading wrong if mail happens to have same subject

2018-01-07 Thread GitBox
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

[GitHub] sebbASF commented on issue #426: Bug: GUI squashes deeply nested conversations

2018-01-07 Thread GitBox
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

[GitHub] sebbASF commented on issue #429: Do less aggressive subject nesting

2018-01-07 Thread GitBox
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

[GitHub] sebbASF commented on issue #428: Initial stab at fixing #426

2018-01-07 Thread GitBox
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

[GitHub] sebbASF commented on issue #429: Do less aggressive subject nesting

2018-01-07 Thread GitBox
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,

[GitHub] sebbASF commented on issue #431: Use correct dependency order to fix OAuth login problem

2018-02-02 Thread GitBox
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

[GitHub] sbp opened a new pull request #431: Use correct dependency order to fix OAuth login problem

2018-02-02 Thread GitBox
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

[GitHub] sebbASF commented on issue #431: Use correct dependency order to fix OAuth login problem

2018-02-02 Thread GitBox
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

[GitHub] sebbASF commented on issue #431: Use correct dependency order to fix OAuth login problem

2018-02-02 Thread GitBox
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

[GitHub] sebbASF closed issue #418: unable to access pony mail

2018-02-02 Thread GitBox
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

[GitHub] sebbASF commented on issue #418: unable to access pony mail

2018-02-02 Thread GitBox
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

[GitHub] ddekany opened a new issue #432: Indentation (leading white-space) not shown

2018-02-12 Thread GitBox
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

[GitHub] sebbASF commented on issue #432: Indentation in mail content (leading white-space) not shown

2018-02-12 Thread GitBox
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?

[GitHub] sebbASF commented on issue #432: Indentation in mail content (leading white-space) not shown

2018-02-12 Thread GitBox
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.

[GitHub] dimidd commented on issue #433: Emails not showing after importing from archive

2018-02-21 Thread GitBox
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

[GitHub] dimidd closed issue #433: Emails not showing after importing from archive

2018-02-21 Thread GitBox
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,

[GitHub] dimidd opened a new pull request #435: import-mbox: Clarify List-ID format

2018-02-22 Thread GitBox
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.

[GitHub] sebbASF closed pull request #435: import-mbox: Clarify List-ID format

2018-02-22 Thread GitBox
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

[GitHub] dimidd commented on issue #435: import-mbox: Clarify List-ID format

2018-02-22 Thread GitBox
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.

[GitHub] sebbASF commented on issue #435: import-mbox: Clarify List-ID format

2018-02-22 Thread GitBox
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

[GitHub] dimidd opened a new issue #433: Emails not showing after importing from archive

2018-02-19 Thread GitBox
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

[GitHub] sebbASF commented on issue #433: Emails not showing after importing from archive

2018-02-19 Thread GitBox
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?

[GitHub] Humbedooh commented on issue #433: Emails not showing after importing from archive

2018-02-20 Thread GitBox
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

[GitHub] sebbASF commented on issue #433: Emails not showing after importing from archive

2018-02-20 Thread GitBox
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

[GitHub] dimidd commented on issue #433: Emails not showing after importing from archive

2018-02-20 Thread GitBox
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.

[GitHub] dimidd commented on issue #433: Emails not showing after importing from archive

2018-02-20 Thread GitBox
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: ![](https://i.imgur.com/4BL6vU2.png)

  1   2   >