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

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

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

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

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

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

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

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 closed issue #423: Dump documents to disk on ES failure

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

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

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

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

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

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

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

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

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

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

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] dimidd opened a new pull request #448: edit-list: handle config consistently

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

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 #448: edit-list: handle config consistently

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

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

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

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] asfgit closed issue #450: Bug: copy-list.py does not work

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

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

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

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

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 #450: Bug: copy-list.py does not work

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?

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

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

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

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] asfgit closed issue #458: Bug: tmpname used before it has been set up in import-mbox

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

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

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

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

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

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

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

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

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 #453: Bug: setup.py fails with ES2 - fielddata

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

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

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)

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 closed issue #242: Website Fix - security issue reporting

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?

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

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] sebbASF opened a new issue #464: Bug: setup.py uses ES library version to decide what features the database supports

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

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

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

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

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

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] sebbASF commented on issue #467: setup: move mappings to a separate file

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

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

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

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

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

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

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

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] sbp opened a new pull request #431: Use correct dependency order to fix OAuth login problem

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

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

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

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

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

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 closed issue #433: Emails not showing after importing from archive

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

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

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

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

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

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

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

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] sebbASF commented on issue #356: Inconsistent LID validation

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.

[GitHub] sebbASF commented on issue #356: Inconsistent LID validation

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.

[GitHub] asfgit closed issue #434: Bug: does not make sense to allow empty domain name in LID

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

[GitHub] sebbASF opened a new issue #438: Enh: option to reduce stats.lua output

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

[GitHub] sebbASF opened a new issue #436: Enh: option to use timestamp from headers if there is no Date: header

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

[GitHub] asfgit closed issue #356: Inconsistent LID validation

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

[GitHub] sharanf opened a new issue #473: Bug: Blank subject line defaulted when replying to an existing thread

sharanf opened a new issue #473: Bug: Blank subject line defaulted when replying to an existing thread URL: https://github.com/apache/incubator-ponymail/issues/473 I've have experienced and am still experiencing intermittent problems posting a message using Ponymail interface. I have

[GitHub] sharanf opened a new issue #471: Flagging Active and Inactive Mailing Lists

sharanf opened a new issue #471: Flagging Active and Inactive Mailing Lists URL: https://github.com/apache/incubator-ponymail/issues/471 Some of the older ASF mailing lists are no longer in use and are only there for display purposes. In theory would we not want to allow users to start any

[GitHub] sebbASF opened a new issue #472: Bug: mailinglists mapping - private property handling is inconsistent

sebbASF opened a new issue #472: Bug: mailinglists mapping - private property handling is inconsistent URL: https://github.com/apache/incubator-ponymail/issues/472 setup.py creates the mailinglists mapping with the properties: description, list, name However archiver.py creates

[GitHub] sebbASF opened a new issue #470: Enh: display buttons even if no mails are found in a month

sebbASF opened a new issue #470: Enh: display buttons even if no mails are found in a month URL: https://github.com/apache/incubator-ponymail/issues/470 PM should display Subscribe/Unsubscribe etc buttons even if no emails are found

[GitHub] bindul opened a new issue #430: Enh: Add option to search all lists in the domain (project) in Advanced Search

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

[GitHub] sebbASF commented on issue #441: Bug: generator should not rely on parsed data, in particular dates

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

[GitHub] sebbASF opened a new issue #442: Enh: make MboxoFactory optional

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

[GitHub] asfgit closed issue #442: Enh: make MboxoFactory optional

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

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

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

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

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],

[GitHub] sebbASF opened a new issue #439: Bug: stats.lua cannot handle deep nesting

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:

[GitHub] asfgit closed issue #444: thread.lua should take References header into account

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

[GitHub] Humbedooh opened a new issue #445: Composer should use unicode as encoding

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.

[GitHub] Humbedooh opened a new issue #444: thread.lua should take References header into account

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),

[GitHub] ctubbsii commented on issue #365: Log In with Google creates extra account

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

[GitHub] Humbedooh opened a new issue #446: Testing unicode subjects via PRs, ignore:   

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

  1   2   3   >