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

[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:
   
   
https://github.com/apache/incubator-ponymail/blob/master/tools/archiver.py#L451
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 nowhere.
   
   I propose we add a --dumponfail directive that spits out a JSON object to a 
directory with the various documents that _need_ to be stored. A process can 
then later scoop up those json files and push them to ES when the DB is back in 
working condition.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 captured for a given message by dumping the 
parameters to the ES methods, that is not the whole story. e.g. the message ID 
also needs to be generated; attachments scanned etc.
   
   PonyMail requires the original source message so that will need to be part 
of your input data.
   This can just be fed as input to the archiver. Or the source can be written 
to a file and parsed by import-mbox.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 `import-mbox.py`.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 `import-mbox.py`.
   
   2018-05-14 13:43 GMT+03:00 sebbASF :
   
   > 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 
stable.
   >
   > I think it would be quite a lot of work to define a format that is
   > guaranteed not to change.
   >
   > —
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > 
,
   > or mute the thread
   > 

   > .
   >
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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.
   
   2018-05-14 13:22 GMT+03:00 Daniel Gruno :
   
   > What's preventing you from using the JSON format archiver.py pushes to ES?
   > You should be able to just push documents manually
   >
   > —
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > 
,
   > or mute the thread
   > 

   > .
   >
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 further.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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.
   
   2018-05-14 13:15 GMT+03:00 sebbASF :
   
   > ElasticSearch (ES) requires JSON for its API.
   > The JSON format is based on the requirements of ES and the database schema.
   > Both may change.
   >
   > import-mbox already supports various standard mailbox formats (mbox, IMAP
   > etc)
   >
   > Personally, I don't see a use case for defining another mail input format.
   >
   > —
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > 
,
   > or mute the thread
   > 

   > .
   >
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 :
   
   > 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 directory.
   > Whereas the other tools/ scripts read from the CWD.
   >
   > I think the current situation is confusing: I would expect all the tools
   > to behave the same way.
   >
   > So although this will change the behaviour, I now think it might be best
   > for all the tools to work the same as archiver and import-mbox.
   >
   > —
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > 
,
   > or mute the thread
   > 

   > .
   >
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 change.
   
   import-mbox already supports various standard mailbox formats (mbox, IMAP 
etc)
   
   Personally, I don't see a use case for defining another mail input format.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 directory.
   Whereas the other tools/ scripts read from the CWD.
   
   I think the current situation is confusing: I would expect all the tools to 
behave the same way.
   
   So although this will change the behaviour, I now think it might be best for 
all the tools to work the same as archiver and import-mbox.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[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 Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services