On 05May2008 17:28, Dan Espen <[EMAIL PROTECTED]> wrote: | > > I'm behind a corporate Exchange Server which seems to have | > > changed recently to converting everything it sees to HTML. | > > How embarrassing.
Oh please may I add this to my sig quote collection? | > I'm also behind a corporate Exchange Server, which I access using | > fetchmail (via ssl/imap) for incoming and nail (via smtp) for | > outgoing. It does not currently convert anything, but I seem to | > recall having had a similar problem a few years ago, following an | > "upgrade". It can be fixed, provided the server administrators | > are sufficiently motivated, but I have no clue what they had to | > do to get it to behave itself. | | I was using fetchmail until they cut off imap and pop. "until they cut off imap and pop". For why? | Now it's Perl via OWA/WEBDAV. I feel ill. | I'm sure our administrators are motivated. | Just not in the way I'd like. It's weird isn't it? It took me months to get a M$ fan boy in a former life to turn _on_ the exchange POP service (we only had exchange as a drop in calendar system while we looked for something decent after our previous one succumbed to terminal bitrot - there was much wailing and gnashing of teeth while exchange was in). They seem to have a mindset for _disabling_ system features, and forcing everyone to use whatever bogus Windows app they seem to think is cool. Somehow this whole "supply a service and let the user's use their preferred tool" thing escapes them. In sympathy, -- Cameron Simpson <[EMAIL PROTECTED]> DoD#743 http://www.cskk.ezoshosting.com/cs/ () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
