The full message (with email addresses redacted) was:
qmail-inject: fatal: unable to parse this line:
To: REDACTED;REDACTED;REDACTED
system error calling qmail-inject
The problem was probably due to the ';' used to seperate email addesses (that were NOT enclosed in <>) and that the vpopmail user had set a .qmail file to redirect all their mail.
So, the email log look something like...
qmail: 1297251062.876788 new msg 4515421
qmail: 1297251062.876812 info msg 4515421: bytes 387 from <REDACTED1> qp 7531 uid 64020
qmail: 1297251062.893855 starting delivery 286560: msg 4515421 to local skinny-jet.co.uk-REDACTED2@skinny-jet.co.uk
qmail: 1297251062.893873 status: local 1/10 remote 1/20
qmail: 1297251062.896739 delivery 286560: failure: qmail-inject:_fatal:_unable_to_parse_this_line:/To:_REDACTED;REDACTED;REDACTED/system_error_calling_qmail-inject/
qmail: 1297251062.896755 status: local 0/10 remote 1/20
qmail: 1297251062.910979 bounce msg 4515421 qp 7535
qmail: 1297251062.910996 end msg 4515421
Changing the ';' to ',' in the "To" header fixed the problem.
09 February 2011
11 June 2010
10 May 2010
Windows 7 cannot access Linux Samba Network
Oh how I hate Windows 7 and Networking. Every now and then I find I cannot access a Linux machine runing Samba on my home network.
This time the symptoms were Windows 7 asking for a username and password from the Windows 7 domain to logon to the Linux-Samba PC. of course Samba does not like the Windows 7 domain credentials!
It took hours to track down the problem and fix it. Somehow, best know to Windows 7, it had created an entry in the Windows Vault for the connection to Linux Samba. To remove it from the vault, go to Control Panel -> Credential Manager and then remove the offending entry from Windows Credentials. As soon as I did that I could connect to my Linux Samba PC and access all the shares.
This time the symptoms were Windows 7 asking for a username and password from the Windows 7 domain to logon to the Linux-Samba PC. of course Samba does not like the Windows 7 domain credentials!
It took hours to track down the problem and fix it. Somehow, best know to Windows 7, it had created an entry in the Windows Vault for the connection to Linux Samba. To remove it from the vault, go to Control Panel -> Credential Manager and then remove the offending entry from Windows Credentials. As soon as I did that I could connect to my Linux Samba PC and access all the shares.
16 November 2009
Norwich Cringleford Travelodge
A £9 room - and we got what we paid for - a room in much need of renovation!
Some idiot had set the room thermostat to 30 degrees centigrade so we had to open the windows to cool down the room - what a waste of energy!
It took a few hours to cool down in time for sleep. But what a soggy bed.
Next morning the shower controls were very delicate. A small change on the temperature control made it go from too cold to too hot!
Not our best overnight accomadation. Was it worth £9 a night? Maybe.
Some idiot had set the room thermostat to 30 degrees centigrade so we had to open the windows to cool down the room - what a waste of energy!
It took a few hours to cool down in time for sleep. But what a soggy bed.
Next morning the shower controls were very delicate. A small change on the temperature control made it go from too cold to too hot!
Not our best overnight accomadation. Was it worth £9 a night? Maybe.
20 August 2009
Problem with SEAGATE FreeAgent USB disk drive on Linux
After the sucess of two days ago, I started to have problems with the SEAGATE FreeAgent USB disk drive on my Linux system. Apparently SEAGATE do not support the FreeAgent USB disk drive on a Linux system!
The problem seems to be due to the SEAGATE FreeAgent USB disk drive going into power save mode. The symptoms on Linux are I/O errors. Often I could list the directories but not access any files. After investiagation it would appear that the symptoms were caused by the directory listing commands returning data from the Linux cache but as soon as I needed to do real I/O, I got the errors. It seems that the SEAGATE FreeAgent USB disk drive does not come out of power saving mode in a maner that was compatible with my Linux system.
There were a few suggestions on the Internet. Most identified that the SEAGATE FreeAgent USB disk drive had problems after spindown/spinup. Most needed the Linux utility sdparm in order to stop the auto spindown.
But I took a very much simpler approach. I created a CRON job with a very simple command. The CRON entry is
*/10 * * * * date > /backups/p3/stop-spin-down/last.txt
This runs the command every 10 minutes and writes to the FreeAgent USB disk. The disk had a mount point of /backups/p3 and I just made a directory (mkdir /backups/p3/stop-spin-down) - writable by all (chmod go+rwx /backups/p3/stop-spin-down) - for the file to be written to.
I hope that helps other people and I will let you know if I have any other problems.
The problem seems to be due to the SEAGATE FreeAgent USB disk drive going into power save mode. The symptoms on Linux are I/O errors. Often I could list the directories but not access any files. After investiagation it would appear that the symptoms were caused by the directory listing commands returning data from the Linux cache but as soon as I needed to do real I/O, I got the errors. It seems that the SEAGATE FreeAgent USB disk drive does not come out of power saving mode in a maner that was compatible with my Linux system.
There were a few suggestions on the Internet. Most identified that the SEAGATE FreeAgent USB disk drive had problems after spindown/spinup. Most needed the Linux utility sdparm in order to stop the auto spindown.
But I took a very much simpler approach. I created a CRON job with a very simple command. The CRON entry is
*/10 * * * * date > /backups/p3/stop-spin-down/last.txt
This runs the command every 10 minutes and writes to the FreeAgent USB disk. The disk had a mount point of /backups/p3 and I just made a directory (mkdir /backups/p3/stop-spin-down) - writable by all (chmod go+rwx /backups/p3/stop-spin-down) - for the file to be written to.
I hope that helps other people and I will let you know if I have any other problems.
18 August 2009
Installing a SEAGATE FreeAgent USB disk drive on Linux is easy
After my sucess in July 2008 of installing a USB disk drive on Linux I did it again today. This time I needed to partition the USB disk drive.
The steps were:
Plug the USB disk drive onto a Windows XP (home) PC. The USB disk drive was a Seagate FreeAgent Desk external 500GB drive USB 2.0. The PC only had USB 1 ports but it worked fine.
I then copied the files from the disk (about 90MBytes) to my PC.
Then I used the Windows Disk Manager (Settings->Control Panel->Administrative Tools->Computer Management->Storage->Disk Management) to partition the disk into 4 partitions. The first was around 90MBytes for the NTFS. The next three were deined in a logical partition. They were set as FAT32 or NTFS - at this point it does not really matter what the file system is as they will be changed in Linux.
I then unpluged the USB cable from the PC and plugged it into a USB port on my Linux machine. Then on the Linux machine:
It really was as easy as that. Considering that the version of Linux (Red Hat Linux release 7.2 Enigma ) was over 7 years old and it was running on a Pentium processor (not even a Pentium 2), that is very impressive
The steps were:
Plug the USB disk drive onto a Windows XP (home) PC. The USB disk drive was a Seagate FreeAgent Desk external 500GB drive USB 2.0. The PC only had USB 1 ports but it worked fine.
I then copied the files from the disk (about 90MBytes) to my PC.
Then I used the Windows Disk Manager (Settings->Control Panel->Administrative Tools->Computer Management->Storage->Disk Management) to partition the disk into 4 partitions. The first was around 90MBytes for the NTFS. The next three were deined in a logical partition. They were set as FAT32 or NTFS - at this point it does not really matter what the file system is as they will be changed in Linux.
I then unpluged the USB cable from the PC and plugged it into a USB port on my Linux machine. Then on the Linux machine:
- As root (su command)
- /sbin/fdisk /dev/sda
- p (to show and verify the partions)
- Changed the three logical partitions (partitions 5, 6 and 7) to have an id of 83 - Linux partition
- w (to write table to disk and exit)
- p (to show and verify the partions)
- /sbin/blockdev --rereadpt /dev/sda
- /sbin/mkfs.ext2 /dev/sda5 (being a 24 GByte partition, this took several minutes)
- /sbin/mkfs.ext2 /dev/sda6 (being a 3 GByte partition, this took a few minutes)
- /sbin/mkfs.ext2 /dev/sda7 (being a 355 GBytes disk, this took around 2 1/2 hours)
- mkdir /backups
- mkdir /backups/p1
- mkdir /backups/p2
- mkdir /backups/p3
- mount /dev/sda5 /backups/p1
- mount /dev/sda6 /backups/p2
- mount /dev/sda7 /backups/p3
- /sbin/fdisk /dev/sda
It really was as easy as that. Considering that the version of Linux (Red Hat Linux release 7.2 Enigma ) was over 7 years old and it was running on a Pentium processor (not even a Pentium 2), that is very impressive
06 January 2009
Fidge is not as cold as you think
As a purely scientific exercise, I monitored the temperatures in my under-cabinet fridge. The results were a bit surprising - if not alarming.
| Location | Temperature (C) | ||
|---|---|---|---|
| Minimum | Maximum | ||
| Door | Top Shelf | 11.5 | 11.7 |
| Middle Shelf | 8.8 | 9.6 | |
| Bottom Shelf | 5.8 | 7.1 | |
| Body of fridge | Top Shelf | 6.5 | 8.1 |
| Middle Shelf | 5.0 | 6.1 | |
| Bottom Shelf | 4.5 | 6.6 | |
| Crisper | 5.0 | 8.9 | |
Subscribe to:
Posts (Atom)