=======================================
=== PLEASE READ BEFORE FILING ISSUE:
https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendDebugging_8
=======================================
What steps will reproduce the problem?
1.n/a
2.n/a
3.n/a
What is the expected output? What do you see instead?
There are 2 Issues:
1) I am using the date convention as follows: @2015/08/02 8am
Using this convention, some of my emails are being automatically sent, and for
others they are not. The only difference in the ones that aren't being
automatically sent is that they were all drafted on the same day (June 16th).
I am putting this text in front of an HTML email, does that affect it? (the
successful sends and the failures both have the HTML just after the @2015/08/02
8am). I am copying the "@2015/08/02 8am" from an excel s/s that generates this
date/time for me, I wonder if that has anything to do with it? (i.e. if it is
pasted in a "paste as text only" does that make a difference?
2) For the successful sends, I no longer see the email addresses in the BCC
field in my sent folder. The emails are sent, but I can only confirm that from
the receipt and that is very manual given the full email address isn't shown on
some of the receipts. Below is a sample receipt, notice Steve Batz name is
there but not his email address. I use the search function in Gmail all the
time to confirm that a coach has been sent all of the emails they were supposed
to receive so this is a problem not to be able to search on the coaches email
address and see all of the emails they have been sent.
Date Sent To CC BCC From Subject Body Snippit (first 500 chars) Attachments
Thu Jul 09 2015 16:03 ddeboer@bgccw.org, Steve Batz ,
Victor.Martin@cityofdoral.com alphabasketball@gmail.com A Great Shooting Game
that also helps develop Clutch Free Throw Shooters: "Validation"
What version of the product are you using?
I can't see where this is identified???
Please provide any additional information below.
Original issue reported on code.google.com by john.lam...@gmail.com on 10 Jul 2015 at 3:27
Original issue reported on code.google.com by
john.lam...@gmail.com
on 10 Jul 2015 at 3:27