Tim Young [Elevate Software] <timyoung@elevatesoft.com> wrote:
> Matthew,
>
> Hmm, still didn't see anything yet...checking the admin logs for Google
> mail, yep, it got marked as spam.
>

Resent without zip and added download for it.

--
Matthew Jones

Tim Young [Elevate Software] wrote:

> .checking the admin logs for Google mail, yep, it got marked as spam.

Interesting - didn't know that was available - Google Apps I presume?
Spam just gets put in folders for me. That said, I'm quite surprised as
I'm using Google apps and I have no idea why it would be put into spam
and deleted too. Do they not trust themselves? Perhaps it is the
encrypted zip. Third attempt sent from another system, in case you
didn't get it.

--

Matthew Jones

Matthew,

<< Interesting - didn't know that was available - Google Apps I presume? >>

Yep, admin.google.com.

We switched to using Google Mail earlier this year when I finally got tired of dealing with admin'ing the email. We still use our own server for outbound bulk emails, though.

Anyways, I did receive it finally, thanks.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Anyways, I did receive it finally, thanks.

Are you able to get anywhere with it? I will be picking up the project
again soon after being pulled onto something else, and it would be good
to know that 2.05 release will not have this issue. I realise it is
probably not simple though.

--

Matthew Jones

Matthew,

<< Are you able to get anywhere with it? I will be picking up the project again soon after being pulled onto something else, and it would be good to know that 2.05 release will not have this issue. I realise it is probably not simple  though. >>

I didn't fix it yet, but I know where the issue is and I'm holding up the last 2.05 beta until I can fix it today.  I just need to do some regression tests to make sure that it doesn't break anything else.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> I didn't fix it yet, but I know where the issue is and I'm holding up
> the last 2.05 beta until I can fix it today.  I just need to do some
> regression tests to make sure that it doesn't break anything else.

Did this make it into 2.05? I just did a quick test on my code, and I
see a similar failure. Take out the problem routine and it works fine.
I will dig deeper tomorrow...

--

Matthew Jones

Matthew Jones wrote:

> Did this make it into 2.05? I just did a quick test on my code, and I
> see a similar failure. Take out the problem routine and it works fine.
> I will dig deeper tomorrow...

A proper test shows it is working as expected - brilliant.

--

Matthew Jones

Matthew,

<< A proper test shows it is working as expected - brilliant. >>

Yeah, it got fixed, but I think I missed adding an incident report for it.  I will do so.

Tim Young
Elevate Software
www.elevatesoft.com