Hi,
First off I'd like to say thanks to everyone involved with RC for their hard work. You guys have produced one of my ideal webmail clients. I love it! :)
Ok, so on to my problem. I'm running FreeBSD 6.0 with Courier-IMAPd & Postfix, and "User-Agent: RoundCube Webmail/0.1b"
For some odd reason, I'm having trouble sending e-mails with attachments. I did some investigating and found that the resulting e-mail's primary header didn't contain Content-Type. It should be something along the lines of Content-Type: multipart/mixed; boundary="..." So I browsed through the source, found where the actual mail is sent, and added some code to add that header specifically (which uses a regex to extract the boundary string as I noticed the encoding is reliant on PEAR:Mail_mime).
No dice :(. I played around with Content-Transfer-Encoding, and Content-Type to no avail. I have no idea what's causing this. I sent an almost identical email (with the same attachment) through SquirrelMail, removed the extraneous headers (time, etc.) and did a diff. Practically no difference! The base64 encoding looked fine. The only differences were in the body text charset and transfer encoding.
So as it is, I'm out of ideas. If you guys want to see the actual e-mails, I can send those if you like. Heck, give me your email address and I'll send you an e-mail with an attachment and you can see for yourself what's wrong.
My guess is either some character encoding issue(s) or a problem with perhapse PEAR:Mail_mime. I'm not sure yet. Any help would be appericiated :)
-Regards
Peeyush Singh
On Sun, 5 Feb 2006 17:24:55 -0500, Peeyush Singh psingh@peeyushsingh.com wrote:
Hi,
First off I'd like to say thanks to everyone involved with RC for their hard work. You guys have produced one of my ideal webmail clients. I love it! :)
Ok, so on to my problem. I'm running FreeBSD 6.0 with Courier-IMAPd & Postfix, and "User-Agent: RoundCube Webmail/0.1b"
For some odd reason, I'm having trouble sending e-mails with attachments. I did some investigating and found that the resulting e-mail's primary header didn't contain Content-Type. It should be something along the lines of Content-Type: multipart/mixed; boundary="..." So I browsed through the source, found where the actual mail is sent, and added some code to add that header specifically (which uses a regex to extract the boundary string as I noticed the encoding is reliant on PEAR:Mail_mime).
No dice :(. I played around with Content-Transfer-Encoding, and Content-Type to no avail. I have no idea what's causing this. I sent an almost identical email (with the same attachment) through SquirrelMail, removed the extraneous headers (time, etc.) and did a diff. Practically no difference! The base64 encoding looked fine. The only differences were in the body text charset and transfer encoding.
So as it is, I'm out of ideas. If you guys want to see the actual e-mails, I can send those if you like. Heck, give me your email address and I'll send you an e-mail with an attachment and you can see for yourself what's wrong.
My guess is either some character encoding issue(s) or a problem with perhapse PEAR:Mail_mime. I'm not sure yet. Any help would be appericiated :)
-Regards
Peeyush Singh
-
Michiel Oosterling -
Peeyush Singh