Skip to main content

Outlook 2003 is beginning to wear on me

I'm having a particular problem that only recently started happening in Outlook 2003 and it's beginning to really bug me.
 
Whenever I send an email, it goes into my Outbox before sending. No problem there, right?
 
Well, if I go back INTO my Outbox just to look at the messages, the messages no longer get sent. It's like they think they are "DRAFT" messages. This never used to happen (and I can't think of what's changed unless it was a service pack or something). I have to actually re-open the message, cut and paste it and then resend it as a brand new email.
 
But now, it's even worse. If I am in the Outbox folder, and try to open the email to create a new one (so it will actually send), it automatically looks as though I'm reading it and so it won't send.
 
I'm going to post this to a forum somewhere but if someone off hand knows the solution, please advise. I'm currently running a few add-ons in my Outlook including Lookout, Newsgator and OnFolio (wonder if that's the culprit).
 
I'll keep you posted.

Comments

Game Geek said…
That's been the Outlook behavior for sometime. If you look at a message in the outbox, don't close it. Click the Send button instead. Another option is to setup Outlook so that it send immediately.

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...