Topic: Email Attachments in Ver5

[Ille DuPre]

I am running server/gateway ver 5. I tried the fix listed here in the forum for increasing attachment size and max execution time. Is there a set limit in V5 to limit attachments no matter what is set?

Thank you

[Joe]

Howdy,

Large attachments in webmail also stopped working for me after upgrading to SME 5. I followed the howto for changing php.ini and still no luck. Initially I thought it was a result of upgrading from 4.1.2 but have since done a fresh install of SME 5.0 and, after following the steps in the howto again, it doesn't work either. I noticed that the howto refers to version 5. I'm wondering if it was tried against a beta version of SME 5.0 with older/newer versions of imp/php/mysql/horde. Or is there just one more little step that I am missing to get it working in SME 5.0? Has anyone gotten large attachments to work under SME 5.0?


Using rpm -q on fresh installs I get:

4.1.2: (large attachments work after howto is applied)

mysql-3.23.32-1.7
php-4.0.3pl1-1
horde-1.2.4-3es
imp-2.2.4-4es


SME 5.0 w/ blades 2 & 3 applied: (large attachments don't work after howto is applied)

mysql-3.23.36-1
php-4.0.4pl1-9
horde-1.2.7-1es
imp-2.2.7-02es



Things I've tried without success after poking around the imp/horde list:

Delete cookies on the client so ssl doesn't get confused by new server with the same name.

Insert "set variable = max_allowed_packet = 10m"  in both [mysqld] and [safe_mysqld] sections of my.cnf (not both at the same time)

Also tried sending large attachments before blade2 update and again before blade3 update with no luck.

Thanks for any help.

Joe

[Ille DuPre]

Joe,

I tried the how to and it seems to have worked...albeit slowly. I sometimes get errors after sending but it always sends.

I did a backup then a fresh install of SME V5 when I upgraded. I then applied the backup. I have noticed a few things that did not transfer. At first I thought It could be that the backup does not work well with SME V5. But yours had probs after a fresh install and doing the how-to.

Tell me...did you go back to check whether your new setting re: the how-to actually took. I went back in to check mine and they had reverted back to default.

I'm at a loss as to why it worked.

Let me know what you find out.

Ille

[Joe]

Ille,

thanks for the feedback

> Tell me...did you go back to check whether your new setting re: the
> how-to
> actually took. I went back in to check mine and they had reverted back
> to
> default.

Just did a fresh install of SME 5.0 and update blades 2 & 3 followed by the steps in the howto. I assume that you are wondering if the changes in php.ini got overwritten somehow. The changes were still in php.ini after the restart. Your success might have to do with file size. I believe anything under ~100k works. But when I test an 800k file it sends a message from root with cc = "recipient list not shown"@, @ and no attachment. In the past root has been replaced by anonymous.

Joe

[Kyle]

I've had the same experiences consistently... I actually had to roll my production box back to 4.12 as a result.  However, I'm not entirely sure that the threshold for the problem is 100k.  I set up a plain-vanila server-only V5 installation in a VM just to do some testing with this webmail problem.  What I did notice was:

80k file:no problem.. mail sent quickly (within seconds)
500k file:sent ok.. sending the mail (uploading file) took 5 minutes (this is much slower than V4.12 was)
4000k file: mail send failed.. (after about 5 minutes of attempting to send the mail..no error on the client..message to root w/ no attachment as previously mentioned.)

The test VM was set up with V5, to which the blade updates 2+3 were immediately applied, as well as the php.ini modifications.  Unfortunately, this webmail attachment issue is the only thing keeping me from migrating to the new version.  I know that a bunch of others have reported these problems previously, and the suggestion always seems to be to make the php.ini mods to allow for a larger file size and timeout.  This does not seem to work for this particular problem.  I'll keep working on my test environment to see if I can find a reasonable workaround, but if anyone has good suggestions, let me know!

[Joe]

Kyle

I'm wondering if/how you got back to 4.1.2 while preserving webmail accounts?

Does copying the files in /var/lib/mysql/horde have a shot at working? Will it look like it's working and then break later?

Thanks

Joe

[Kyle]

Joe,

If I'm remembering correctly (I actually played with the upgrade a couple of weeks ago), I had taken a complete backup of the 4.12 server before attempting to upgrade.  Once upgraded, I ran a bunch of tests, and discovered this issue pretty quickly.  At that point, I wiped the server clean, reinstalled 4.12, did a basic reconfiguration, applied the appropriate security patches and restored all the data.  Its a pretty low-volume server, so luckily downtime wasn't much of an issue.  I suppose I should have said "reinstalled" as opposed to "rolled-back".  

At this point, I'll stick to playing with this in my test VM until I'm sure it can be worked around (or fixed)... Even though I was able to fully restore the box for the most part, it was still quite a pain in the neck (ok, so I'm whining and don't like waiting for restores).

Kyle

[Kyle]

Just a bit of added info for anyone that is interested:

I did retry this experiment using V5.1beta3 in a VM, and it works correctly in that version.  (and the performance is much more normal than what I saw with 5.0)

[Joe]

Kyle

Thanks for the feedback and encouraging news about 5.1. I will be falling back to 4.1.2 soon myself.

Joe