For a while, I had a problem with Googlebot being unable to crawl my site (and in fact I was having this problem for so long that my site was actually de-listed from Google).
Testing my site in Google Webmaster Tools with Fetch As Googlebot actually returned a blank page: Googlebot was unable to reach my site, and could provide no diagnostic message that could explain the lack of reachability.
What’s up with that?
I’m using nginx with PHP-FPM (APC is installed).
I need PHP’s flush() to work. Is this possible?
Things I’ve tried so far:
php.ini, as well as output compression.gzip in nginx’s configuration.fastcgi_* buffering settings and fastcgi_max_temp_file_size to zero.I’m sure I must be missing something, since I’ve run across many posts here and elsewhere where people claimed they’ve got it working, but I’m having no luck, it would seem.
I’ve noticed this for a while, and it’s never made any sense to me:
Why does ntpd need to listen on so many addresses?
For example, a Debian machine:
$ netstat Proto Local Address Foreign Address Program name udp 0.0.0.0:123 0.0.0.0:* ntpd udp 127.0.0.1:123 0.0.0.0:* ntpd udp [LAN]:123 0.0.0.0:* ntpd udp [IPv4]:123 0.0.0.0:* ntpd udp6 :::123 :::* ntpd udp6 ::1:123 :::* ntpd udp6 [link-local] :::* ntpd udp6 [IPv6] :::* ntpd
This (redacted) netstat listing shows nptd listening on the broadcast, local, LAN, and global addresses, for IPv4 and IPv6.
Why is ntpd so promiscuous?
Linode offers nice big /116 (4096) IPv6 address blocks for no additional cost, in addition to the included single IPv4 and IPv6 address per VPS.
Normally, with a run-of-the-mill website not needing SSL, I can point many A records to a single IPv4 address, and configure Apache (or equivalent) to do the right thing, with the Host header getting a browser where it needs to go.
With a site needing SSL, I provision and configure a separate IPv4 address, and point the DNS appropriately, since (assuming no SNI) the web server doesn’t know what certificate to use before the SSL handshake.
All well and good.
I would like to make use of the addresses provided by Linode to make some, and eventually all of these sites IPv6-native, and I’m unsure of the best practices to use for that. Should I follow the same approach for non-SSL hosts? Should I always allocate a separate IPv6 address per host? I haven’t read anything that tells me to take either approach. Maybe there’s an RFC I missed.
However, my plain and simple (hehe) question is this: Given Linode’s only offering a single “physical” interface (eth0), and all additional IPv4/v6 addresses needing to be virtual interfaces on top of it (eth0:0, eth0:1, …), is there a point where I would be better advised to not add any more virtual addresses? Or, assuming the interface hasn’t been saturated by that point, is there no downside to having many (hundreds) of IPv6 addresses as virtual interfaces?
(I may be asking the wrong question [or possibly even multiple wrong questions] here if I’m misunderstanding Linode’s offerings and/or IPv6 in general, but hopefully that’s not the case. ;)
I have Postfix configured with a few domains, delivering to Dovecot locally.
I’ve noticed some interesting spam that comes in, purporting to be from an address at one of those domains, but that address does not exist.
How can I configure Postfix to drop those emails? Real email from this domain a. originates from the same server it is being delivered to, and b. is DKIM signed.
By default, Munin (I’m using 1.4.5) shows graphs for the day, week, month, and year.
Can I configure it to additionally display an hourly graph?
As with all mail servers, mine frequently receives spam for invalid recipient addresses.
What configuration values will force Postfix to immediately reject these messages? Furthermore, if Postfix is rejecting them and tries to bounce them back to the origin, how do I force Postfix not to bother deferring the bounce message if it isn’t immediately accepted by the origin?
I currently have a server running Debian 6, with postfix and dovecot handling email. This server hosts email for a number of domains and users, so I use MySQL as my backing store for users and forwardings and everything related.
Currently, this server is the only server listed in an MX record for all of the domains it serves. I would like to create a secondary server that would be listed in the DNS with a lower priority (e.g. current primary server is priority 5, secondary would be priority 10), so that in the event that I need to reboot the primary server, or otherwise make it unavailable, the secondary server would receive email, and hold it until the primary server came back up, at which point it would deliver any held email to the primary server.
I do not need the secondary server to function as a backup sending server. Users would never need to see the secondary server, they would simply not lose incoming emails if the primary server is down, and they would be unable to send or receive until the primary came back up.
How would I go about doing this? I would like to use the same software if they can handle this task, because I’m already familiar with managing them.
For new accounts, dovecot only has a single default folder, the inbox.
Is there a way to specify a default set of subfolders, preferably immutable, that exist for each inbox?
Ideally, I want each account to have a Sent, Trash, and Drafts folder, which can all be read/written to, but not renamed or deleted.
In case it is relevant, my dovecot configuration specifies no subfolder prefix, so all user-created subfolders exist at the "root" level of the Maildir, which is the mailbox format I’m using.
Is there a way to configure Postfix to accept any mail for a domain (catch-all), and then forward that email to the same recipient at a different domain, ignorant of whether the recipient actually exists?
I use Postfix with a MySQL backing for virtual accounts.
FINAL RESULT
I fixed this problem by resizing my xvda partition from 700MB to 10GB. I used Linode’s control panel to do that, which involved shutting down the VPS, running the resize operation, and then booting it back up. Many thanks to everyone who provided insights and solutions; they were all instrumental and helpful.
ORIGINAL QUESTION
I’m running Postfix as my MTA, and it has randomly decided to stop accepting incoming email:
Sep 14 07:50:26 zulu postfix/smtpd[27946]: warning: not enough free space in mail queue: 6832128 bytes < 1.5*message size limit
In my postconf:
message_size_limit = 10240000
queue_minfree = 25000000
All mail to my system is being rejected with 452 4.3.1 Insufficient system storage.
I know little to nothing about partitions and related magic, I only know that Postfix is seemingly telling me that it has no space, when in fact my system has plenty of space:
Finally, Postfix is still delivering the failure notices to my postmaster@ account, so I’m really quite at a loss.
EDIT
root@zulu:/# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda 679M 644M 6.9M 99% /
tmpfs 249M 0 249M 0% /lib/init/rw
udev 10M 112K 9.9M 2% /dev
tmpfs 249M 0 249M 0% /dev/shm
As far as I know, the mail queue is stored in /var/spool/postfix. I’m not entirely sure how to determine if that is correct, but it seems correct:
root@zulu:/var/spool/postfix# ls -al
total 84
drwxr-xr-x 21 root root 4096 Sep 6 13:58 .
drwxr-xr-x 4 root root 4096 Sep 6 06:55 ..
drwx------ 2 postfix root 4096 Sep 14 08:37 active
drwx------ 2 postfix root 4096 Sep 13 13:19 bounce
drwx------ 2 postfix root 4096 Sep 6 06:55 corrupt
drwx------ 3 postfix root 4096 Sep 12 06:13 defer
drwx------ 3 postfix root 4096 Sep 12 06:13 deferred
drwxr-xr-x 2 root root 4096 May 4 17:30 dev
drwxr-xr-x 3 root root 4096 Sep 14 07:37 etc
drwx------ 2 postfix root 4096 Sep 6 06:55 flush
drwx------ 2 postfix root 4096 Sep 6 06:55 hold
drwx------ 2 postfix root 4096 Sep 14 08:37 incoming
drwxr-xr-x 2 root root 4096 Sep 14 07:37 lib
drwx-wx--T 2 postfix postdrop 4096 Sep 8 21:41 maildrop
drwxr-xr-x 2 root root 4096 Sep 12 06:13 pid
drwx------ 2 postfix root 4096 Sep 14 07:37 private
drwx--s--- 2 postfix postdrop 4096 Sep 14 07:37 public
drwx------ 2 postfix root 4096 Sep 6 06:55 saved
drwx------ 2 postfix root 4096 Sep 6 06:55 trace
drwxr-xr-x 3 root root 4096 Sep 6 06:55 usr
drwxr-xr-x 3 root root 4096 Sep 6 13:58 var
fdisk:
root@zulu:/# fdisk -l /dev/xvda
Disk /dev/xvda: 734 MB, 734003200 bytes
255 heads, 63 sectors/track, 89 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/xvda doesn't contain a valid partition table
I should probably note that this is a Linode VPS.
I have a server with Debian 6 (Squeeze), running Postfix, Dovecot, and using MySQL as the backing store for virtual email accounts.
For my domain example.com, I have a ‘catch-all’ @example.com that forwards to [email protected].
I want to allow an authenticated user to log in as [email protected] to use SMTP (and thus take advantage of SPF validation and DKIM signing), but not allow Postfix to deliver mail sent to [email protected] to Dovecot. Configuring a ‘full’ account in the MySQL database causes this to happen, so far as I can tell.
How can I do this? Am I approaching this in the wrong way?
I’m running an email server using qmail.
I want to transparently add a BCC to each email that is sent through the server, for particular accounts. This would have the effect of saving every sent email to a separate mailbox for archival and legal purposes.
What’s the best way to go about doing this?
I’m running a Rackspace Cloud CentOS 5.5 instance.
It shipped with:
[root@server ~]# php -v
PHP 5.1.6 (cli) (built: Nov 29 2010 16:47:46)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies
and
[root@server ~]# mysql --version
mysql Ver 14.12 Distrib 5.0.77, for redhat-linux-gnu (x86_64) using readline 5.1
I want to upgrade it to at least PHP 5.2, and 5.3 if possible.
What are the proper steps for ensuring a smooth upgrade (with no data loss in MySQL, dependencies upgraded accordingly, etc.), and how would that upgrade actually be performed?
Apologies if the question title is nonsensical, but this has me quite confused.
Here’s what I want to do:
Domain xyz.com is the FQDN for webserver xyz-1.
xyz-1 has Plesk installed.
I want xyz-1 to be able to serve the DNS for xyz.com, so that the nameservers for xyz.com are set to ns1.xyz.com and ns2.xyz.com.
I’m probably wording this incorrectly, but that’s essentially what I’m trying to do.
Additionally, any domains added to Plesk, with their nameservers set to ns1 and ns2.xyz.com would also have their DNS served correctly (duh?).
I'm setting up a server with Plesk, and we'd like to be able to provide a publicly-accessible copy of phpMyAdmin.
I was able to determine where it could go:
/var/www/vhosts/default/httpsdocs
However, it's serving phpMyAdmin as the actual PHP files, not as executed PHP.
What's the best/correct way to enable PHP execution on that directory?
Is there any way to take an image of a "cloud" server (the server in question is on the Rackspace Cloud/Mosso) and store it so that the server instance can be shut down/destroyed, and if I decide I want the server back, I can just restore this backed up image of the filesystem onto a new server instance?
Will adding a second SPF record mess up my DNS, or will it be like adding an extra nameserver?
(i.e. it only helps, not hurts)