Forwarding Email in Leopard Server, part 2

I’ve previously written about problems with Leopard server and forwarding of virtual hosted domain email. My solution was somewhat inelegant and errors were written into the mail.log. Since that time I’ve found a solution that works and generates no errors. It also has the added benefit of being entirely within Server Admin.

Here’s what to do.

In Server Admin > Mail > Settings > Advanced > Hosting the following items are needed.

  1. Obviously, in the lower panel Virtual Domain Hosting needs to be checked and the domains entered.

  2. In the upper panel I have the following entries.

    • localhost
    • server.mydomain.private (this is the entry under Server Admin > Mail > Settings > General > Domain Name.
    • virtual1.com
    • virtual2.com
    • virtual3.com

virtual1.com and the others are the hosted virtual domains for which users have email accounts. That’s it. When I check my mail logs, mail is forwarded, I get no errors regarding accounts not being set up, and there are no other errors in mail.log.

Mean People Suck

Mean people suck. It has always seemed to me that it’s much easier to be nice to people than to be mean.

  • It takes more effort to exclude someone than to include them.
  • It’s easier to smile than to frown.
  • It’s easier to tell the truth than to lie.

Unfortunately hurt feelings last a long time and saying your sorry sometimes just doesn’t make it better. Regrettably the world is full of people who choose to be mean. Yes, I believe it is a choice. Life’s lesson is that when people are mean to you it’s best to let it run off you like water off a duck. Real friends aren’t mean. They’re either not really your friend or they’re trying to impress someone else at your expense. In either case it sucks. Hurt takes time to heal and sometimes “I’m sorry” just doesn’t cut it. Don’t sweat the small stuff. You probably cause yourself more angst by thinking about it that blowing it off.

Almost everyone should get a second chance, especially those you’ve known for a long time.

I hope my son learns this lesson.

AT&T WiFi

It’s real. I’m here in McDonalds and I decided for the fun of it to see what WiFi was around. I saw attwifi and selected. I opened up a web page it redirected me to an iPhone AT&T page where I entered my phone number and viola. High speed access.

QuickClot

Boy I’d really like to try some of this QuickClot stuff in the OR. I think it would be great to use for a planned second look.

Ambulance Chaser

Yes Virginia, they really do exist.

So here’s the story. The family of a trauma victim, a motor vehicle collision, is met outside the ICU by a lawyer saying that the particular vehicle in which they were traveling has a defect and he and his firm would be happy to represent them. The family never contacted this lawyer, or any lawyer for that matter. He just showed up out of thin air.

Does it really matter if the driver of the vehicle is intoxicated and the vehicle is traveling at over 100 mph?

Apparently not to this attorney.

Minh T. Nguyen
Jeffrey S. PoP & Associates
Beverly Hills, CA
minhnguyen@poplawyer.com

By all means, send him and email and let him know what you think if his ethics and behavior.

Never Events

In October, 2007 CMS (Medicare) proposed a list of eight preventable conditions that result in a prolongation and increase in cost of care to the hospitalized patient. These are what CMS terms **never events**. CMS is trying to couch this in terms of patient safety but if you look at the list, there are only a few of these items that are 100% preventable. It’s really less about patient safety and more about how CMS can cut reimbursement. Medicine isn’t an exact science and expecting it to act as one is irrational.

On April, 14 2008 CMS proposed additions to their **never event** list

The HAC provisions in Medicare regulations required hospitals to begin reporting on their Medicare claims on October 1, 2007, whether certain specified diagnoses were present when the patient was admitted. The first eight conditions, which were selected last year because they greatly complicate the treatment of the illness or injury that caused the hospitalization, resulting in higher payments to the hospital for the patient’s care by both Medicare and the patient, were:

  • Object inadvertently left in after surgery
  • Air embolism
  • Blood incompatibility
  • Catheter associated urinary tract infection
  • Pressure ulcer (decubitus ulcer)
  • Vascular catheter associated infection
  • Surgical site infection- Mediastinitis (infection in the chest) after coronary artery bypass graft surgery
  • Certain types of falls and trauma

CMS is proposing to expand the list of conditions that need to be reported if present when a patient is first admitted and is seeking public comment on whether they should be added to the list in the final rule to be announced later this year. The list in the proposed rule includes:

  • Surgical site infections following certain elective procedures
  • Legionnaires’ disease (a type of pneumonia caused by a specific bacterium)
  • Extreme blood sugar derangement
  • Iatrogenic pneumothorax (collapse of the lung)
  • Delirium
  • Ventilator-associated pneumonia
  • Deep vein thrombosis/Pulmonary Embolism (formation/movement of a blood clot)
  • Staphylococcus aureus septicemia (bloodstream infection)
  • Clostridium difficile associated disease (a bacterium that causes severe diarrhea and more serious intestinal conditions such as colitis)

Some of the biggest problems in this list are twofold.

  1. Who’s to define things like derangement and what constitutes delirium?
  2. If these are **never events** can someone please tell me how to avoid them 100% of the time?

All invasive procedures, and I include having a foley and being on a ventilator as invasive, carry risk. The risk is small but it exists and it is not zero. I seems what CMS is seeking to do is to transfer the risk from the receivers of medical care to the providers of medical care.

Personally, I think this list will ever expand and eventually hospitals and physicians will cease to be paid for any care arising out of these **never events**. When that starts happening, watch out. All of a sudden it will not make financial sense for hospitals and doctors to participate with Medicare.

iCal - Exchange Time Zone Fix

As any Mac user who deals with Microsoft Exchange invites will tell you Exchange screws up the time zone information. What this means is that you will likely miss your meetings. Not a good thing.

Justin Hartman has recently given you his solution to this problem. I haven’t tested it but in looking at it I’m certain it works just fine. I say this because he’s fixing the problem is a similar manner. It’s just that he’s using a combination of shell scripts and AppleScripts. I’ve got it down to a single AppleScript.

There is one property at the head of the script that needs to be fixed depending upon the location of your Exchange server. What you need to do is copy in the correct property from what iCal expects to see as time zone information.

ical-tzid.png

You can find this information by selecting the time zone drop down menu in the upper right corner of your iCal window and select Other....

Once there find the location of your Exchange server and see what the resultant time zone information looks like in iCal. In my case, I live in California and my time zone is US/Pacific or America/Los_Angeles but the Exchange server in question lives in Dallas. So I set the property to US/Central.

Note: The ical_TZID property cannot have any spaces. Replace all spaces with underscores “_”. In iCal America/Los_Angeles will look like America/Los Angeles in the iCal dropdown menu.

I think I’ve built in the enough logic to grab any twisted time zone information out of the Exchange invite that Exchange can produce. If I’m wrong let me know.

Save the script and either set it up to run from a mail rule or as I do call it from the System AppleScript menu. You will need to save the script in ~/Library/Scripts/Applications/Mail/ folder. Create this folder if it doesn’t exist.

You can download the MailExchange2iCal-TZ-fix script here.

The script was not entirely my creation and credit also goes to others. I’m quite certain any errors are likely mine. ;-)

If it works for you let me know. If it doesn’t work let me know that too and I’ll see if it can be fixed.

You will likely need a different copy of the script for each Exchange server that send you invites.

Update - 5 August 2008

To set the script up to run automatically you will need to create a new Mail rule as follows.

  1. Mail -> Preferences -> Rules -> Add Rule
  2. Description “Fix Exchange Invites”
  3. If “any” of the following conditions are met:
    • “Content-Class” “Contains” “urn:content-classes:calendarmessage”
      Note that the Content-Class header is not in the default list of headers on which you can set a rule action, but you can add it. This hint originally here.
    • “Any Attachment Name” “ends with” “.ics”
  4. Perform the following actions:
    • “Run AppleScript” “~/Library/Scripts/Applications/Mail/MailExchange2iCal-TZ-fix.scpt”
  5. Click “OK” and then “Apply”

Update - 11 August 2008

I found a glaring problem that I believe I’ve fixed. Apparently if the invite is only sent as an attachment the previous version of the script wouldn’t parse out the .ics attachment. This new version will. Please download it.

Update - 18 August 2008

I re-wrote the script making it better and more versatile. Please go to it’s new post home.

Immediate Breast Reconstruction and CMS

OK, first off this part of my practice is over and I’ve moved on. But let me relay a story of how CMS (that’s Medicare for the uninitiated) works.

I was asked by one of my local breast surgeons if I would see a patient for immediate breast reconstruction with implants. The patient was to undergo bilateral mastectomies. No problem. I see the patient. Surgery scheduled and goes fine.

I submit my claim forms to CMS and I only get paid for the consult. They say the surgery (immediate reconstruction with implants) is only billable as an add-on to a procedure done by me. This is absurd. I didn’t do the mastectomies. It seems that CMS can write their own rules along the way. My coder followed all the proper rules according to the CPT Code books.

It’s now over 6 months later and it looks like I’m going to have to write off the $400 that Medicare is usually willing to pay for this procedure. Yep, you read that correctly. No offense to all those women with breast cancer needing and wanting this combination of procedures but I can tell you now that at this fee schedule and with this ease of reimbursement I surprised that anyone is willing to do immediate breast reconstruction. This clearly has not been worth my time and energy, even to get paid.

Side note: If you think the solution to healthcare is to let the government run it; I wish you luck in getting any doctors to care for you.

Ivory Towers

An Ivory Tower is supposed to be the tertiary referral center where they know everything and can take care of all difficult patients. So why is it when I have a specific need for a higher level of care that one of my local Level 1 trauma centers, University of California, San Diego, balked.

I had a difficult patient. Suffice it to say that I needed someone capable of performing endovascular thoracic stent grafts. I was given contact by the patient’s insurer. I spoke with the Trauma fellow and the classic response was..

Don’t you have a closer Level 1 Trauma Center?

Now I later did speak with a Cardiac Surgeon at Cedar’s who was willing and able but in the end the patient’s concomitant injuries were enough to have family withdraw supportive care. Back to the real problem.

When I was a resident our Attending Staff only wanted to know the answer to one question.

Do you want to send the patient by ground or by air?

As he explained one day. We were here at the university, the ivory tower. We were expected to provide support and assistance to the surrounding communities’ surgeons. It was never a question of whether or not someone had insurance or that they were beyond salvage. We were there the help. In this case, help our fellow surgeons.

I guess in the 11 years since I’ve finished residency a lot has changed. Unfortunately, not for the better.

Fixing cyrus

Yeah, I did something stupid and had to reinstall my server OS — again. I thought I’d be OK but my mail backup was about a day old. I’ve used mailbfr before and it worked great but this time I kept getting errors. It seemed that mailbfr wasn’t copying over the skipstamp file.

What I did was to copy this file manually then run some of the commands that system.log reported as not being run properly.

sudo cp /mailbfrBackups/mailbackup/cyrus_config_DIR/imap/db/skipstamp /var/imap/db
sudo /usr/bin/cyrus/bin/reconstruct -p default -i
sudo su _cyrus /usr/bin/cyrus/bin/reconstruct -i
sudo -u _cyrus /usr/bin/cyrus/bin/cyrus-quota -f

So far I think I’ve got all my users and mailboxes back. Of course all the email is now listed as unread, but I expected that.

Of course Alex came back with the real answer which was the following in mailbfr.

sudo mailbfr -f
sudo mailbfr -o

And all is well. I think.

Of course, it didn’t work as expected. I ended up reinstalling the OS and then fixing only specific users mailstores. Once everything was working I then updated the OS to 10.5.2 and now everything works.