Microsoft error message "452 4.3.1 Out of memory"

I'm troubleshooting a Microsoft mail server. I go through the logical process of realizing that unless Crazy Monkey Man has put some sort of voodoo magic on my server box there must be a good reason why a Microsoft product isn't working. *cough*.

Right, I telnet onto the server, authenticate myself and try sending a "mail from:" command. I get the error message "452 4.3.1 Out of memory" which I assume means I'm out of memory. So I check my server memory to see that it still has 2 gig free and is under no heavy load right now.

Hmm, how could an SMTP service demand 2gig of RAM I wonder? Not even Microsoft would be so daring to put a hardware requirement like that.
Microsoft should choose a new mascot

The truth is that when Microsoft says that you're "Out of memory" what they actually mean is that you don't have write privileges to a particular folder (click here if you don't believe me). They just say you're out of memory to trick you. Sort of like Microsoft's idea of a friendly joke.

Only problem is that I *do* have write privileges on the folder in question.

Further investigation reveals that Microsoft has two seperate documents on this issue and the error message "Out of memory" can actually mean one of three things. None of which involve memory. Click here if you don't believe me.

Haha, good one Microsoft. I bet you're laughing all the way to the bank with your little prank.

Comments

Using Fail2Ban to protect a Varnished site from scrapers

I'm using Varnish to cache a fairly busy property site. Varnish works like a bomb for normal users and has greatly improved our page load speed. For bots that are scraping the site, presumably to add the property listings to their own site, though the cache is next to useless since the bots are sequentially trawling through the whole site. I decided to use fail2ban to block IP's who hit the site too often. The first step in doing so was to enable a disk based access log for Varnish so that fail2ban will have something to work with. This means setting up varnishncsa. Add this to your /etc/rc.local file: varnishncsa -a -w /var/log/varnish/access.log -D -P /var/run/varnishncsa.pid This starts up varnishncsa in daemon mode and appends Varnish access attempts to /var/log/varnish/access.log Now edit or create /etc/logrotate.d/varnish and make an entry to rotate this access log: /var/log/varnish/*log { create 640 http log compress ...

Translating a bit of the idea behind domain driven design into code architecture

I've often participated in arguments discussions about whether thin models or thin controllers should be preferred. The wisdom of a thin controller is that if you need to test your controller in isolation then you need to stub the dependencies of your request and response. It also violates the single responsibility principal because the controller could have multiple reasons to change. Seemingly, the alternative is to settle on having fat models. This results in having domain logic right next to your persistence logic. If you ever want to change your persistence layer you're going to be in for a painful time. That's a bit of a cargo cult argument because honestly who does that, but it's also a violation of the single responsibility principal. One way to decouple your domain logic from both persistence and controller is to use the "repository pattern". Here we encapsulate domain logic into a data service. This layer deals exclusively with imple...

Separating business logic from persistence layer in Laravel

There are several reasons to separate business logic from your persistence layer. Perhaps the biggest advantage is that the parts of your application which are unique are not coupled to how data are persisted. This makes the code easier to port and maintain. I'm going to use Doctrine to replace the Eloquent ORM in Laravel. A thorough comparison of the patterns is available here . By using Doctrine I am also hoping to mitigate the risk of a major version upgrade on the underlying framework. It can be expected for the ORM to change between major versions of a framework and upgrading to a new release can be quite costly. Another advantage to this approach is to limit the access that objects have to the database. Unless a developer is aware of the business rules in place on an Eloquent model there is a chance they will mistakenly ignore them by calling the ActiveRecord save method directly. I'm not implementing the repository pattern in all its ...

Adventures in IT

Search This Blog