hi,
I have setup virtualmin to work as my email server. I have also setup outlook 2007 to serve as my email client. I am able to receive emails but when sending emails, sometimes it arrives at destination and sometimes it doesn’t. In mail.log it shows that the email was sent
yeah all the emails that i sent out i sent them to my external email addresses to test them. only once (the 2nd or 3rd try but not the first, first was in inbox) they ended up in spam. I am using my ISP’s SMTP server, which should deliver it to inbox.
since when was hotmail and yahoo proven to be reliable addresses to test email on?
Yahoo often bounces emails first round and may deliver few days later. I have seen this time after time when sending mails to yahoo accounts.
So the first one from root to administrator was delivered successfully. The second one from bilal was detected as spam for some reason. You’ll want to look in the .spam folder and look at the headers for why spamassassin called it spam. I always suspect DNS misconfiguration, but there are other possibilities.
i dont know why it classified it as spam, since its local from same domain, and its also in the spamassasin’s whitelist. As for DNS, i’m not using BIND, infact I unchecked it from the module list. I’m using the Domainpeople.com (where i got the domain from) DNS.
Anything else that I can check?
maybe since its https(secure) it could be causing problems? (noob guesses)
but DNS shouldnt have any affect on the out going emails or any local emails right?
Wrong. As I mentioned previously, misconfigured DNS is a very spammy characteristic. Your message was classified as spam. DNS misconfiguration is a very common cause of that. How else can I say it, so you’ll believe me and provide the information we need to help you fix things?
If you just look in the headers of the message marked as spam, as I explained above, we won’t have to guess.
Or, you can continue to theorize and have no idea what’s going on. But, I’m running out of ways to ask for the information we need to actually troubleshoot your problem…so, I’m gonna have to give up at some point.
Please just look in the spam mailbox of that user, and look at the headers of that message. SpamAssassin explains exactly why it marked something spam. You just have to look at it.
here is the information in the header of the email marked as spam
Received: from localhost by eServer with SpamAssassin (version 3.2.4); Tue, 17 Mar 2009 14:15:45 -0500
From: "bilal.genvion" <bilal@genvion.ca>
To: <test@genvion.ca>
Subject: test
Date: Tue, 17 Mar 2009 14:15:32 -0500
Message-Id: <83b545db8cf4a700835b154df0b9b5b7@192.168.1.103>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on eServer
X-Spam-Level: *****
X-Spam-Status: Yes, score=5.4 required=5.0 tests=LOCALPART_IN_SUBJECT, NO_RELAYS,TVD_SPACE_RATIO autolearn=no version=3.2.4
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_49BFF6E1.6488D12D"
and this was in the body of the email
Spam detection software, running on the system "eServer", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
-0.0 NO_RELAYS Informational: message was not relayed via SMTP
2.5 LOCALPART_IN_SUBJECT Local part of To: address appears in Subject
2.9 TVD_SPACE_RATIO BODY: TVD_SPACE_RATIO
You have a broken hostname. It is “localhost”. This is never right. If you installed with the install.sh automated install script, it shouldn’t have let you proceed until you set a valid fully qualified domain name…but I guess it failed to detect this problem somehow.
So, you need to fix that. In Webmin->Networking->Hostname and DNS Client you can set the hostname. It needs to be a sane fully qualified domain name, and it needs to resolve via DNS.
If you are running Debian 5 or Ubuntu you might have to update /etc/mailname (I hate this new convention; this is a really stupid idea that I think the Ubuntu folks came up with…the seem to be full of stupid ideas on the server-side…they broke the Apache configuration in really stupid ways last year, too) to also include this new name. On most systems, Postfix gets the name from the system hostname, so it only needs to be set in one location.
I’m not actually sure what “TVD_SPACE_RATIO” is, but if your hostname were sane, it wouldn’t have been enough to push this into being ranked spam and it would have been delivered correctly.
ERROR: Some of your MX records returned by your nameservers are IP addresses. This is not ok per the RFCs and you should change them.
The problem records are:
205.200.9.230
This can cause problems !
ERROR: I could not get any A records for www.genvion.ca!
Looking for A record through squish:
50.0% of queries will end in failure at 204.174.223.72 (ns1.domainpeople.com) - no such record
50.0% of queries will end in failure at 64.40.96.140 (ns2.domainpeople.com) - no such record
