PHP Warning: mail(): SMTP server response: 452 4.3.1 Out of memory

MarkP

Hi All,

We have OSTicket (v1.6 ST) running on a Windows server using IIS as the SMTP server. Everything has been working beautifully for several weeks but today a strange issue has started to occurr.

You can browse and view tickets and everything else as normal but everytime a user attempts updates a ticket the page appears to hang indefinately. If I close the browser and log back in I can see the update has been added but no email is sent.

If I look at the php-errors.log file I see a message like the below corresponding with every update attempt:

PHP Warning: mail(): SMTP server response: 452 4.3.1 Out of memory in C:\inetpub\wwwroot\osticket\include\pear\Mail\mail.php on line 128

If I take a look at line 128 is looks as follows:

127: if (empty($this->_params) || ini_get('safe_mode')) {

128: $result = mail($recipients, $subject, $body, $text_headers);

129: } else {

130: $result = mail($recipients, $subject, $body, $text_headers,

131: $this->_params);

132: }

As far as I can tell the server is in good shape. Hundreds of gigs of disk space available, permissions haven't changed. Nothing interesting in the badmail folders. Nothing else in the logs. The SMTP server is up and running and as I said before everything has been working.

I'm not sure what to look at next so any help would be gratefully received.

equisde

Hello,

A couple of suggestions...

1. This is the simplest and most obvious method. You just edit your php.ini and change the memory_limit to whatever you need. For ex:

memory_limit = 32M

You will require access to make changes to php.ini on the system. This change is global and will be used by all php scripts running on the system. Once you change this value, you will need to restart the web server in order for it to become active.

Keep in mind that this limit has its logic and don’t increase it artificially, as poorly written php scripts might overkill your system without proper limits.

Note: if you know what you are doing and want to remove the memory limit, you would set this value to -1.

2. Changing memory_limit using .htaccess for a single folder/vhost

Changing the global memory_limit might not be a good idea, and you might be better changing this only inside one folder (normally one application or virtual host) that needs this value changed for its functionality. To do this you have to add to the respective location .htaccess something like:

php_value memory_limit 64M

This change would not require a reload and will become active immediately.

MarkP

Hello,
A couple of suggestions...
1. This is the simplest and most obvious method. You just edit your php.ini and change the memory_limit to whatever you need. For ex:
memory_limit = 32M
You will require access to make changes to php.ini on the system. This change is global and will be used by all php scripts running on the system. Once you change this value, you will need to restart the web server in order for it to become active.
Keep in mind that this limit has its logic and don’t increase it artificially, as poorly written php scripts might overkill your system without proper limits.
Note: if you know what you are doing and want to remove the memory limit, you would set this value to -1.
2. Changing memory_limit using .htaccess for a single folder/vhost
Changing the global memory_limit might not be a good idea, and you might be better changing this only inside one folder (normally one application or virtual host) that needs this value changed for its functionality. To do this you have to add to the respective location .htaccess something like:
php_value memory_limit 64M
This change would not require a reload and will become active immediately.

Thanks equisde, I appreciate the advice. :)