forum.excito.com

yes but not as admin because you'll forget to check.. Well maybe not you, but most people =)

I'm currently a bit low on coffee but if many users get this flood of PHP warning emails like you do, and most have a faulty /etc/aliases setup (as discussed elsewhere), would that mean that all those people are now seeing their HDs filled with mailqueue?

apologies, I meant logrotate. Depending om what exotic logfilename you enter in the vhost config, you may very well need to add that name in /etc/logrotate.d/apache2. If you cal the file /var/log/apache/somehostfilename.log then it is automatically included.

Yes, but if you look at past threads that deal with this same issue, those loads of emails are always because some process is misbehaving and sending tons of mails. Fixing that issue also fixes the mail flood. But you need to read the mails first right? Although admin is the logical choice for a roo...

it runs a perl script (/usr/share/perl5/Bubba/Notify.pm) that loops through files in the /var/spool/bubba-notify dir (which is empty in my case) and prints out a JSON response. My guess would be something with FTD but as there is no docs in the scripts it is no more than a guess...

ah... indeed...stupid.

should be the postcat command will show the content of a specific queued mail, identified by the queue ID from the mailq command.

of course, the answer is blatantly obvious if only the OP would run

Im sorry but you are making this up. Bounced messages that return are double-bounced and disappear. The ones that do not deliver because of DNS are also bounced after queue_lifetime is matched. The only messages that are not removed from queues are the from dthe delivery agent, as there is no place ...

Then why, according to you, is the mail stuck in the queue?

The easiest way to get rid of localhost is Cat access_log | grep -v localhost . The second bes t solution i guess is splitting your host into two separate vhosts, both with a documentroot to the same position. Then make one point to the. Internal interface <virtualhost 127.0.0.1:80> and the other to...

The whole issue here is that, with maildir, root is not permitted to receive mail at all. That i why the mail is stuck. The postfix installer is quite lear on this topic.

Your mysql remark is very cryptic. What does that mean? I can tell you already that in default mode mysql has no root pwd, and setting one stops the web-updater from functioning properly (something tht could have been easily fixed with a passwd file but alas). For the rest, id recommend you create a...

Maybe you should mention that the force option is required because hfsplus support is not considered stable in linux. Althou unstable in linux terms is still very robust, you are not allowed to complain if for some reason your partition gets corrupted.

Pleas run to clean the messages. They contain only stats and log data.
Then edit and alter the last line of that file. You need to enter a avlid mail address here, or a username that can receive mail.
Now run

Not sure, i think the lights are a little different in rescue mode. Much more important is whether you can ssh into one of the nics right?