This will usually clear it up for me and I can then copy/paste fine on the host machine.

Further to that last post I came across a Q&A in my 2-day-old newspaper http://blogs.guardian.co.uk/askjack/2008/06/more_things_to_try_if_you_cant.html. My experience with getting into Gmail seems much the same (though I entered via simple HTML as mentioned).

My guess is during the upgrade, Google changed the filtering and I’m only now hitting the problem. It’s a pity I didn’t get the explicit message earlier – I’m not sure why I was dealt the general one first.

Just trying to send 250 monthly newsletters – who would have thought it would be this tough? I’m going to to try customisation as a defence to the filtering and see if that works. Given your VBS posting, is this something you do?

Away until Mon/Tue now – happy weekends,

Chris

I coming more and more to the conclusion that the problem is with the might forces of Google.

I had tried port 465 without luck (same message), 587 was unknown to me but it didn’t like that at all. I decided to log in to the Gmail account and see what was happening there, perhaps look for a setting similar to the ‘bulk mail’ problem above. Gmail didn’t open nicely, the small progress bar getting stuck in a 99% back to 25% loop for a while until after a few minutes, I pressed the HTML lite link and was presented with my inbox. Nothing to see there so I gave the script another go.

Voila!

It worked. For a short while. Then it stopped again, same error. I asked it politely to try again and got “error -2147220975 (80040211) [..] transport error Ox800ccc69 [..] Daily sending quota exceeded”.

That at least, but sadly, seems explicit. I guess I’ve fallen foul of some Gmail anti-spam setting. Something for the morning – perhaps.

Bike: Italy, last year, http://www.dubiouslogic.com/photos/Italy_2007-06/760/DSC02073.jpg, just after a perfect lunch overlooking Lake Maggiore, setting the navigation for Switzerland via the Simplon Pass over which I was to discover we were leaking break fluid…

Chris

http://mail.google.com/support/bin/answer.py?hl=en&answer=13287

Re Bike – Thank you, I can’t believe this thing is legal.

Drew

Thanks for the answer.

I can’t send email via CDO at all now – I’ve been drafting and testing the mail for the last few days and it’s been fine – sending to my modest list of addresses (250) stalled after 50 as mentioned – now nothing will move.

Yes, I’ve reached the same conclusions, abetted by more searching. There was (2005) a problem with McAfee that led to something similar, their trying to prevent mass-mailing worms exploiting SMTP.

I’ve checked my anti-virus (Kaspersky) and there’s nothing similar, I’ve checked the firewall (XP) and nothing there. I’ve switched off both and the problem persists. However, if I switch:

.Item(cdoSMTPUseSSL) = True

To false I _do_ appear to be getting through to the server.

I’m continuing to poke it but now a voice from downstairs wants dinner…

Nice bike by the way,

Chris