Closed GoogleCodeExporter closed 9 years ago
Hello Larry,
You're correct, date.js seems to parse that date ok. As well as the 'test
parser' on gmail delay send's configuration page.
Could you follow the debug steps
(https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendDebugging_8) and
attach the logs when trying to send an email with that date?
Thanks,
-Blair
Original comment by blairk...@gmail.com
on 30 Dec 2014 at 2:47
Attached is a copy of the e-mail I'm trying to send & the logs. I was unable to
view the headers presumably because the e-mail wasn't sent.
I hope this is the needed info.
Original comment by larry.h...@gmail.com
on 30 Dec 2014 at 3:18
Attachments:
Any luck with this issue?
Original comment by larry.h...@gmail.com
on 4 Jan 2015 at 12:09
Hello Larry,
I checked the logs that were uploaded. It doesn't appear that there were any
emails to send when you ran the script.
Could you follow all the steps that you did to create the logs, but before you
'run now' make sure you have an email with the date/time you're having trouble
with ready to send.
Then we can get a debug log with the failing output.
Thanks!
Original comment by blairk...@gmail.com
on 4 Jan 2015 at 12:19
Here are new logs and a screenshot of the test e-mail.
Original comment by larry.h...@gmail.com
on 4 Jan 2015 at 2:15
Attachments:
Blair --
I tested the date issue in a new e-mail - and it worked as expected. Then I
retyped my problem message into a new one and tested the date by sending it to
myself. It worked, too. So, for now, I think the errors were caused by
something in the body of the problem message and not the script or jdate.
Original comment by larry.h...@gmail.com
on 4 Jan 2015 at 5:28
Hey Larry,
Ah I see.. I'm working on the next version of the script now which will not try
to parse the date out of the email itself. Currently stange HTML formatting or
anything else can cause problems when trying to pull the date out.
I'm going to close out this bug, but thanks for all the help debugging.
-Blair
Original comment by blairk...@gmail.com
on 5 Jan 2015 at 12:49
Blair --
I had another somewhat similar problem. It appears to have been an embedded
JPEG . When I deleted it the error message didn't come back.
Original comment by larry.h...@gmail.com
on 7 Jan 2015 at 8:15
ohh.. interesting.. Good debugging Larry.
If it's not too much trouble, could you forward me directly the problem email?
Id' like to figure out how to avoid that..
Original comment by blairk...@gmail.com
on 9 Jan 2015 at 1:41
I no longer have the message as it was when the error occurred. I had to delete
the apparently offending JPEG to complete my test and send the message at the
scheduled time.
Original comment by larry.h...@gmail.com
on 9 Jan 2015 at 3:29
I see, if you do encounter this again, if you could forward me the message
manually (not using gmail delay send) I would be most appreciative!
-Blair
Original comment by blairk...@gmail.com
on 9 Jan 2015 at 4:40
Original issue reported on code.google.com by
larry.h...@gmail.com
on 30 Dec 2014 at 1:26