Outlook 2007 users angry over Office 2007 HTML-e-mail changes


Recommended Posts

Office 2007 to me, is great aslong as i can send and receive emails then it sure doesn't bother me. It's Quite easy to work around the HTML changes they have done anyway. If you can't live with it don't use it :) simple as pie.

Yeah, Rich text is pretty much what mails should use.

HTML that's for annoying ugly badly made greeting card mails and spam mail from gaming mailing lists.

the only peopel who use HTML over Rich text are the ones who somehow ended up with html by default and don't know any better or don't know how to change.

You must never have received an email in your life. Most websites use html emails to send our their newsletter, and businesses sends out mail formatted in html as well.

Do you not understand that you can enable proper HTML rendering from within the options? The default however is using word.

How would you do that? I just looked through all the settings, and I couldn't see anything to change the rendering engine?

..I work for the Ministry of Government Services, for the Government of Ontario, as a PKI / MyOPS support agent, and I constantly get emails from Tech Support, and higher level agency officials, and 99.9% off all email I get, even from Tech Support, is in HTML
Then they aren't power users, they just haven't switched it off (which makes them lazy users)
Most websites use html emails to send our their newsletter...

well, they shouldn't. That's what the frickin web is for. You send a mail saying "here's a link to the latest news on our site". It also saves bandwidth.

and businesses sends out mail formatted in html as well.
True. Amazon is good at that. Yet they are pretty much all offers for stuff, which could have been dealt with by plaintext links as above. There's absolutely no reason to send an invoice / purchase order / etc. as HTML because in order to receive that you must have been on the e-commerce site to begin with. You deciding not to print out an order confirmation web page if you want something with fancy formatting is your problem. Go back to the site and review your order if you need it that bad.
Do you not understand that you can enable proper HTML rendering from within the options? The default however is using word.

How would you do that? I just looked through all the settings, and I couldn't see anything to change the rendering engine?

QFT. If it isn't easy / obvious to change (and what is in Outlook, how many frickin settings to stop HTML email inbound or outbound?), there will be a lot more complaints becuase of the default of using a rendering engine that is ieven worse than Trident.

I love Outlook 2007......easier to use if you ask me.

As for the rendering engine pfft who cares........i hate HTML emails....if it cant be said in plain text emails then its probally not worth reading.

GOOD JOB MS - Security First for a change....WD

I have to side with those not caring. When signing up for online newsletters I always specify plain text and I have Outlook only using plain text. If you are taking the time to make up an elaborate CSS/HTML email to send to me it you are wasting your time. I like the way information looks when printed in courier new. I can read what I need to read and while it may not look good, but I never have to worry about phishing and other junk.

This is really a huge problem. For those who say that HTML isn't for email - HTML offers a much higher clickthrough rate over plain text. That means a lot of money to people like GAP, Microsoft, HP, Lexus, and the sort. To have their designers spending more time coding emails to ancient HTML standards is crazy. Looking forward to Office 2007 SP1. :crazy:

Everybody in this thread is missing the point:

1. You will still receive spam it has no affect on that.

2. It won't stop others from sending you HTML designed email because they will be using other types of email clients like Outlook 2003 and Thunderbird, but when Outlook 2007 receives it, it will not display properly.

3. The rendering engine is poorly designed, slow and buggy and that is in plain text mode, html mode can cause cpu spikes that last for 5 minutes.

4. Outlook 2007 cannot send out properly designed HTML emails, they are scrambled which is going to cause a lot of headaches.

I believe it is better that the end user or admin has the choice to lock down which email mode is used and not chosen for us by Microsoft. Microsoft should have just prompted people to switch to plain test mode or rich text mode or maybe default to plain text mode and make users switch to html mode.

The point being the end user should be given the choice.

and get the DoJ and the EU back in our arses again because we requiere users to install another MS app so they can render their freaking emails? no thanks! :rolleyes: :cry: :no:

The IE6 engine is already installed on xp machines, its part of windows :p

It's much more complicated than that...

And another thing, this isn't more secure simply because it is not IE. It's more secure because the Outlook/Office team has full control over the code so they can lock it down in ways specific to their uses of it, and apply greater defense-in-depth strategies.

I personally have 0 complaints and have been using Outlook 2007 beta for a while. I love it. I do not understand what all the fuss is about.

The fuss is that they removed a properly working feature and replaced it with one that doesn't work properly.

Talking to a Microsoft Office employee I was told this was not planned. I guess they couldn't get IE6 and outlook 2007 to work properly together so that would require going to ie7 but most corps have yet to upgrade to ie7 so that means they needed some other way to render the html emails so they choose word 2007 since it would be included in the office 2007 suite.

The problem is that word 2007 can't render html properly, so it's by accident and not by design. It would be nice if we were allowed to choose the rendering engine like Outlook 2003.

Edited by hardgiant
The fuss is that they removed a properly working feature and replaced it with one that doesn't work properly.

It works just fine here. I've received HTML email (invoice...) and it displayed ok to me. Outlook 2007 to Outlook 2007 will work just fine. If this is 5 year step backward, then older client will have no issues displaying emails sent by 2007 user. The only who complain are "email designers". I have yet to see any experienced computer user to send CSS email to me. The only ones I get were graciously forwarded email (read spam) from my friends who fall fall all kind of scams (get rich in 5 minutes by forwarding this email to 100 of your friends in next 30 seconds).

Talking to a Microsoft Office employee I was told this was not planned.

Hearsay.

The problem is that word 2007 can't render html properly, so it's by accident and not by design. It would be nice if we were allowed to choose the rendering engine like Outlook 2003.

Where exactly in 2003 are you allowed to choose rendering engine? I've used it for years and never saw that option. It only allows you to choose which format your emails will be composed in. You are thinking about option to compose email in World (RTF/HTML) or in Outlook (Plain text)?

Edited by richter
Gee, I've been using Outlook 2007 (full not beta) for a few days and I had no idea I was angry. I need to keep tabs on my emotions better. All this time I thought I really liked Outlook 2007.

That's priceless.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • expected when they force you by having to use TPM and secure boot for anti cheat crap, and lazy developers only test on windows 11.
    • The fact I need to use "Show more" like 99% of the time is so annoying. Or why I have 7-zip under 3 submenus when it could be in top. And Microslop keeps saying how they'll improve Start and I've not seen ANY improvement yet. In MONTHS. WTF?! I'll believe any of it when they actually deliver anything.
    • LosslessCut 3.69 by Razvan Serea LosslessCut aims to be the ultimate cross platform FFmpeg GUI for extremely fast and lossless operations on video, audio, subtitle and other related media files. The main feature is lossless trimming and cutting of video and audio files, which is great for saving space by rough-cutting your large video files taken from a video camera, GoPro, drone, etc. It lets you quickly extract the good parts from your videos and discard many gigabytes of data without doing a slow re-encode and thereby losing quality. Or you can add a music or subtitle track to your video without needing to encode. Everything is extremely fast because it does an almost direct data copy, fueled by the awesome FFmpeg which does all the grunt work. Features Lossless cutting of most video and audio formats Losslessly cut out parts of video/audio (for cutting away commercials etc.) Losslessly rearrange the order of video/audio segments Lossless merge/concatenation of arbitrary files (with identical codecs parameters, e.g. from the same camera) Lossless stream editing: Combine arbitrary tracks from multiple files (ex. add music or subtitle track to a video file) Losslessly extract all tracks from a file (extract video, audio, subtitle, attachments and other tracks from one file into separate files) Batch view for fast multi-file workflow Remux into any compatible output format Take full-resolution snapshots from videos in JPEG/PNG format Manual input of cutpoint times Apply a per-file timecode offset (and auto load timecode from file) Change rotation/orientation metadata in videos View technical data about all streams Timeline zoom and frame/keyframe jumping for accurate cutting around keyframes Saves per project cut segments to project file View FFmpeg last command log so you can modify and re-run recent commands on the command line Undo/redo Give labels to cut segments View segment details, export/import cut segments as CSV Import segments from: MP4/MKV chapters, Text file, YouTube, CSV, CUE, XML (DaVinci, Final Cut Pro) Video thumbnails and audio waveform Edit file metadata and per-stream metadata Edit per-stream disposition Cut with chapter marks Annotate segments with tags View subtitles Example lossless use cases Cut out commercials from a recorded TV show (and re-format from TS to MP4) Remove audio tracks from a file Extract music track from a video and cut it to your needs Add music to a video (or replace existing audio track) Combine audio and video tracks from separate recordings Include an external subtitle into a video Quickly change a H264/H265 MKV video to MOV or MP4 for playback on iPhone Import a list of cut times from other tool as a EDL (edit decision list, CSV) and run these cuts with LosslessCut Export a list of cut times as a CSV EDL and process these in another tool Quickly cut a file by its MP4/MKV chapters Quickly cut a YouTube video by its chapters (or music times from a comment) Change the language of a file's audio/subtitle tracks Attach cover art to videos Change author, title, GPS position, recording time of a video Fix rotation of a video that has the wrong orientation flag set Great for rotating phone videos that come out the wrong way without actually re-encoding the video. Loop a video / audio clip X times quickly without re-encoding LosslessCut 3.69.0 changelog: Add lossless cropping & aspect ratio override via bitstream and container metadata #643 Alow shifting tracks for each file (-itsoffset) #216 Add "decimate video" tool to filter away all non-keyframes #2111 Add Windows ARM 64 native build with native ffmpeg Move timecode out of timeline and make it copy-able #2592 #2691 #2800 #483 #2808 Upgrade Electron to latest Add new "opposing" align mode #2654 Add FFmpeg -hwaccel auto setting for hardware acceleration of certain operations Add API events export-start and export-complete Allow deleting track metadata #2819 Improve shift segments dialog #2839 Show keyboard shortcuts inside button tooltips in UI Warn if trying to cut with too few keyframes around cutpoint #516 #2780 #2756 (Linux) include app name in notification #2794 Pull latest translations Other notable changes: Advanced output directory selector #2101 #2115 #2755 increase max file name length to 250 (truncation) #2779 don't reset playback speed when using special playback modes #2889 preserve chapters when merging files that already have chapters don't merge adjacent segments in combineOverlappingSegments #2896 don't transfer segment name when filling gaps #2754 always scroll up to zoom in #2703 #2786 increase max keyframes to 10000 Don't bind ctrl/cmd+c by default (they interfer with copying text) Many other improvements and fixes Download: LosslessCut 3.69.0 | ARM64 | ~100.0 MB (Open Source) Links: LosslessCut Website | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Doesn't even need a UI for point 2 - use some sort of JSON/XML container - because MOST users won't even bother.
  • Recent Achievements

    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      488
    2. 2
      PsYcHoKiLLa
      263
    3. 3
      Skyfrog
      85
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      62
  • Tell a friend

    Love Neowin? Tell a friend!