user199421's questions

As part of the product we offer we send emails on behalf of our clients. Because the emails don't come from an IP associated with the client they are sometimes flagged as spam.

We advised some of our clients to add an SPF record approving us to send emails on their behalf. We saw immediate improvement in deliverability rates after making the change however one of our clients was notified by his hosting provider that the SPF record we suggested to add would "slightly restrict" all emails that don't come from our servers (including our client's own servers).

The record we use is this:

v=spf1 a mx include:ourdomain.com ~all

So my question is if the warning we received about this is correct and if so why and what can be done to solve this (allow sending email both from original domain and by ourselves).

I have a 3 - 4 year old 250GB WD hard drive that has shown abnormally high temperature readings ever since I bought it. The temperatures were so much higher than expected that I ended up attributing them to a bad sensor. For example, the other drive I have on the my system at the moment is a WD 640GB and it is currently at 40C. While the 250GB drive is at 62C. Typically, when the system boots up the temperature for that drive will quickly clime to 50C - 58C (today's a bit hotter). These drives are right next to each other in the case so that there is no other source of heat that could affect the temperatures.

All in all I never had any problems with that drive (except for the alarming temp readings) but in a recent S.M.A.R.T data check I noticed some CRC errors. These errors are usually attributed to bad cables bad just to be on the safe side I am planning on retiring this drive soon.

In the early days, when the 250GB drive was my main drive I was quite worried so I bought a hard drive cooler for that drive. It manages to to lower the temperature by about 5C. The problem is that it really makes a lot of noise. What I am interested in knowing is if my assumption that it's more than likely a bad sensor is logical so that I can disconnect the hard drive cooler and get some peace and quiet.

Host is Windows 7 Guest is Ubuntu 11.04

Network adapter is wireless

I can ping other computers on the network but not the host. No firewall are involved.

Sniffing the traffic with wireshark it looks like both the host and the guest are using the same MAC address. My guest simply doesn't receive a reply when asking for 192.168.1.101 (the host) My router has no problem giving both of them different IP addresses but maybe duplicate MAC address is the problem?

It seems logical that both will have the same MAC address (from the host point of view) but it strange that there is no work around for this because otherwise I don't see how the host and guess are supposed to communicate.