Closed MaikeruJon closed 7 years ago
Dear @MaikeruJon
You are right, the intention of the command co2dice tstamp recv
is to fetch tstamps from the email and to derive the OK/SAMPLE decision.
In case it does not work properly some options can be added to the command to facilitate finding the proper dice response:
co2dice tstamp recv --mailbox "Spam"
will search messages in a particular folder of the email (Spam in the example). The default is Inbox.co2dice tstamp recv "IP-10-AAA-2017-1003"
will search messages containing the specified familiy-id in the subject/body of the message.co2dice tstamp recv TstampReceiver.rfc-criteria=['SUBJECT "Proof of Posting Certificate 0973449:[dice test hotmail] dices/IP-10-AAA-2017-1001/0" ']
will search messages containing the specified subject.co2dice tstamp recv --before "08/01/17"
will search messages sent before the specified day (1 st August 2017).co2dice tstamp recv --after "08/01/17"
will search messages sent after the specified day (1 st August 2017).co2dice tstamp recv --on "08/01/17"
will search messages sent on the specified day (1 st August 2017).In case none of this additional options work, could you please send us in an e-mail the following command?
co2dice tstamp recv -v
Kind regards.
To clarify further the situation, first some definitions:
1) I assume that with "acknowledgement" you mean the reply-email you receive back From:
tstamper-address, with subject "Proof of posting <subject-prefix> <dice-id>"
, correct?
2) And the "actual reply" are the stamped-emails that appear as sent From:
your email-address to the tstamp_recepient
addresses, with subject containing just "<subject-prefix> <dice-id>"
, correct?
Dice comes pre-populated with some default criteria so that (t)recv
commands fetch ONLY "acknowledgement" emails (1) above, because that's the typical use-case. In the end, the resulting criteria are those printed as logging statement shown below:
15:28:28 : INFO:co2mpas.sampling.tstamp.TstampReceiver:Searching: (FROM:maXXX@YYYY) (SUBJECT "[dice test]")
The parameters controlling those default criteria to are the following (for v1.5.7
):
TstampReceiver.subject_prefix
TstampReceiver.email_criteria ## This param will be renamed as `rfc_criteria` in forthcoming release 1.6.x
Tip: you may view them with co2dice config desc criteria
command. And in 1.5.x you view the actual values with co2dice config show TstampReceiver
.
In order to fetch emails received from the tstamp_recipient
addresses you have to override these defaults.
To summarize things up:
co2dice_config.py
file to our email, and specify from which account you want intend to parse tstamps, so that we can modify them appropriately.Many thanks to the team for your typically prompt and helpful replies. I have had success and I now feed back as follows:
1) "I assume that with "acknowledgement" you mean..." Yes, that is what I meant.
2) "And the "actual reply" are the stamped-emails..." Yes, that is what I meant
3) "co2dice tstamp recv "IP-10-AAA-2017-1003" will search messages containing the specified familiy-id in the subject/body of the message." Thank you. This worked for me.
tstamp recv history.txt
(hidden)
Please refer to the uploaded file that shows the history.
co2dice_config.py.txt
(hidden)
I think that there is noting so confidential in it, so I am uploading my configuration file for reference.
Thanks again.
[edit: ankostis] anyway, i've hidden the files, expect in a couple of days to disappear completely.
How long does it take before my project shows up in the response from
co2dice tstamp recv
? I received the e-mail reply from the time stamper and thought that I could get the result of my latest submission by the commandco2dice tstamp recv
instead ofco2dice project tparse
and then copying and inserting. But half-an-hour after I received the reply (not the acknowledgement, the actual reply) from timestamper, I am just receiving a list of old timestamper mails. Am I misunderstanding this command?