#emc-devel | Logs for 2010-04-20

[04:26:58] <steve_stallings> steve_stallings is now known as steves_logging
[18:00:02] <alex_joni> fsck it.. has anyone had reliability issues with email attachements?
[18:01:20] <cradek> what do you mean?
[18:01:53] <alex_joni> keep having issues with files getting corrupted on the way
[18:02:00] <alex_joni> mostly jpeg's and pdf's
[18:02:17] <cradek> oh you mean in general, not just at sourceforge or something? certainly no, I've never seen that.
[18:02:30] <alex_joni> in general..
[18:02:35] <cradek> nope
[18:02:39] <alex_joni> no idea how to even attempt to debug it :/
[18:02:47] <seb_kuzminsky> alex_joni: memtest ;-)
[18:02:48] <alex_joni> tried switching antivir programs, switch them off
[18:02:50] <alex_joni> changed pc's
[18:02:56] <alex_joni> seb_kuzminsky: ^^
[18:02:59] <cradek> are you using microsoft products for mail client or server?
[18:03:15] <SWPadnos> look at the SMTP headers and see if you can find a pattern based on routing
[18:03:18] <alex_joni> client, but recently changed to thunderbird
[18:03:26] <SWPadnos> unless you suspect the MUA, in which case you could try changing it
[18:03:29] <alex_joni> SWPadnos: those are emails going to various customers
[18:03:44] <alex_joni> some with yahoo addies, some with proprietary, etc
[18:03:47] <cradek> so the customer might be screwing it up? or do they all report the same problem?
[18:03:48] <SWPadnos> hmmm
[18:04:03] <alex_joni> cradek: some of them report they can't open files
[18:04:11] <cradek> put a url in the email - image attachments are obnoxious anyway
[18:04:12] <SWPadnos> all sent through your exchange server?
[18:04:16] <alex_joni> one reported today he can't open one of the two jpegs
[18:04:18] <cradek> (really, I'm serious)
[18:04:22] <alex_joni> SWPadnos: no exchange server
[18:04:26] <SWPadnos> ok
[18:05:44] <cradek> most people I interact with don't use yahoo/hotmail/etc so there might be a general problem - I might not know about it
[18:06:08] <cradek> are you sure you are sending the right content-type?
[18:09:55] <alex_joni> cradek: nope
[18:10:14] <alex_joni> I mean I did find a problem related to encoding
[18:10:33] <alex_joni> for some files (pdf and word) the MUA decided to encode them as charset-printable instead of base64
[18:10:54] <SWPadnos> send as attachments rather than inline
[18:11:04] <alex_joni> and charset-printable then got 0D 0A conversions to 0A (line ending conversion)
[18:11:11] <cradek> but you can't send a pdf or word document inline...
[18:11:13] <alex_joni> which fscked the file..
[18:11:22] <alex_joni> cradek is right, this only happens to attachements
[18:11:24] <cradek> yeah quoted-printable is bad news for binary files (duh)
[18:11:38] <cradek> what MUA did that?
[18:11:39] <alex_joni> cradek: yeah, tell that MSOE
[18:11:50] <alex_joni> Outlook Express ;)
[18:11:58] <cradek> huh
[18:12:13] <alex_joni> it supposedly looks at the file content, and decides based on chars it's mostly text
[18:13:39] <alex_joni> if the destination MUA is also Outlook Express/Outlook it's no problem
[18:13:53] <alex_joni> but yahoo and gmail decide they want to be smart and do line-ending conversions
[18:14:02] <cradek> heh, but that's not how email works...
[18:14:16] <SWPadnos> zip the attachments first :)
[18:14:47] <alex_joni> cradek: supposedly that's how it works nowadays
[18:14:48] <alex_joni> :/
[18:15:13] <alex_joni> but today I sent two almost identical images, both scanned using GIMP
[18:15:22] <alex_joni> one got through ok, the other one didn't