>Be honest - the email subject told you everything you wanted to know... From what I can tell by searching around, the actual subject title of this email is "C

>Be honest - the email subject told you everything you wanted to know... From what I can tell by searching around, the actual subject title of this email is "CD Baby Loves you", not "CD Baby order shipped", so one does have to read this email to find out what it means. However, let's assume that the title did say that the order shipped. One still has to look in the email to see if every ordered item shipped, or whether any of them are backordered, or arriving in multiple shipments. Maybe a person placed two orders at the same time -- which one shipped? Let's assume a person only ordered one cd. Ey still has to read the entire thing, because maybe there's some content in it that ey need to act on (e.g., the wrong shipping address, or the wrong charge amount). If that was the case, and someone didn't read the email, whose fault would it be when the mistake was found out later? Everyone laughs when people don't read a software EULA that promises the creator the user's soul, saying "well, people should have read the EULA". How much would the cd buyer be blamed if ey was charged double and didn't find out about it until a month later, when eir credit card statement came in? "Well, it was in your order confirmation; you should have read it." And arguing that the CDBaby order confirmation doesn't contain the price, and it contains the address at the top, so my argument doesn't apply is not the issue. How do you know there's no data requiring action in the text unless you read it?