Re: Mime bug?

[<ty...@bo...>]

> Fatal error: Maximum execution time of 30 seconds exceeded in 
> ./functions/mime.php on line 160

(Long lines are due to SquirrelMail and Opera, I'm guessing ... Apologizing in advance)

I get this same error when I try to view a message with two attachments, but it dies on line 164 for me.  All I am doing is trying to view my message about the new ABook_Take plugin with .zip and .tar.gz versions attached.  I use Opera, so that might be the thing throwing the wrench in your machine.  The mail is extremely tiny, but apparently unviewable with SquirrelMail.  I also sent this file with SquirrelMail, so I really don't know what the problem could be.

I tried to alter the structure below to mirror what I have:

---=[ BEGIN ]=------=[ BEGIN ]=------=[ BEGIN ]=------=[ BEGIN ]=---
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="============_-1244970129==_============"
To: .........
From: .........
Subject: .........

--============_-1244970129==_============
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Body of e-mail in plain text.  There is no blank line between this
section and the boundary
--============_-1244970129==_============
Content-Type: application/octet-stream; name=\"\"abook_take-1.0.tar.gz\"\"
Content-Disposition: attachment; filename="abook_take-1.0.tar.gz"
Content-Transfer-Encoding: base64

Encoded data here -- notice that the name is \"\"file\"\".  Again, no
blank line
--============_-1244970129==_============
Content-Type: application/zip
Content-Disposition: attachment; filename="abook_take-1.0.zip"
Content-Transfer-Encoding: base64

Lookie here -- the filename looks correct.  I used SquirrelMail to compose this one message and it does different things to the file names...  Strange, no?  This section has a blank line after it.

--============_-1244970129==_============

--
SquirrelMail list signature

---=[ END ]=------=[ END ]=------=[ END ]=------=[ END ]=---