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

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 glory in this demo.

Fixing puppet "Exiting; no certificate found and waitforcert is disabled" error

While debugging and setting up Puppet I am still running the agent and master from CLI in --no-daemonize mode. I kept getting an error on my agent - ""Exiting; no certificate found and waitforcert is disabled". The fix was quite simple and a little embarrassing. Firstly I forgot to run my puppet master with root privileges which meant that it was unable to write incoming certificate requests to disk. That's the embarrassing part and after I looked at my shell prompt and noticed this issue fixing it was quite simple. Firstly I got the puppet ssl path by running the command puppet agent --configprint ssldir Then I removed that directory so that my agent no longer had any certificates or requests. On my master side I cleaned the old certificate by running puppet cert clean --all (this would remove all my agent certificates but for now I have just the one so its quicker than tagging it). I started my agent up with the command puppet agent --test whi

Redirecting non-www urls to www and http to https in Nginx web server

Image: Pixabay Although I'm currently playing with Elixir and its HTTP servers like Cowboy at the moment Nginx is still my go-to server for production PHP. If you haven't already swapped your web-server from Apache then you really should consider installing Nginx on a test server and running some stress tests on it. I wrote about stress testing in my book on scaling PHP . Redirecting non-www traffic to www in nginx is best accomplished by using the "return" verb. You could use a rewrite but the Nginx manual suggests that a return is better in the section on " Taxing Rewrites ". Server blocks are cheap in Nginx and I find it's simplest to have two redirects for the person who arrives on the non-secure non-canonical form of my link. I wouldn't expect many people to reach this link because obviously every link that I create will be properly formatted so being redirected twice will only affect a small minority of people. Anyway, here's

Adventures in IT

Search This Blog