suse, sendmail, linksys router, mailman architecture is getting some mail sent to spam/junk mail folders

I have setup mailman on a suse box using sendmail behind a linksys router.  I have a domain and mx record setup at register.com.  The functionality is working; however, the mail sent through mailman/sendmail/linksys router is getting sent to my junk folder at my yahoo.com account, the mail does not make it to my msn.com account, and everything works fine with my various gmail.com accounts, meaning the mail doesn't get sent to my spam folder for may gmail.com accounts.  It goes to my inbox.  One thought is that yahoo and msn are somehow identifying where the mail is sent from asside from the domain name.  The from address used my mailman is the correct domain.  For example, the confirmation notice below is sent from mailman.  Notice the reference to the 192.168.1.1 IP which is my linksys router.  Any insight is greatly appreciated.


Mailing list subscription confirmation notice for mailing list
Maytest2list

We have received a request from 192.168.1.1 for subscription of your
email address, "test@xxxxxxx.com", to the maytest2list@xxxxxxx.com
mailing list.  To confirm that you want to be added to this mailing
list, simply reply to this message, keeping the Subject: header
intact.  Or visit this web page:

jdzemkeAsked:
Who is Participating?
 
ridConnect With a Mentor Commented:
I still think that some domains (e.g. yahoo in this case) identifies your IP as belonging to a "suspicious" range of IP's. If your setup with your ISP gives you a dynamic IP (the router is a DHCP client on the WAN side), you may have a problem there. If you have a static, public IP (on the router WAN side), it doesn't matter what happens on the inside of that router, although I would personally prefer to have my servers on static IP on my LAN.

Anyway, since things work OK with Gmail, I suppose you may have a good IP and that a working reverse DNS lookup can be made, so the fact that the messages end up in the "bad mail" depot may have other reasons. Yahoo and others may use some kind of adaptive filter that happens to look for some particular detail in the incoming messages, one detail that happens to be present in your outgoing mail. Perhaps the "localhost(127.0.0.1)" thing, or something else. Are you running your server on your workstation?
/RID
0
 
ridCommented:
Some clarification:
Mail doesn't get sent to a specific folder - it is transmitted to a receiving end server, which acceps the mail or doesn't accept the mail. If it is accepted, it can be processed by internal goings-on to place it in your SPAM folder in your web access page, but that is another story. On the server, everything ends up in the inbox, so to speak.

If  your messages aren't accepted, you must look at your credentials. Is your server/domain blacklisted (you have been discovered as an open relay or something); does your domain name stand up to a reverse DNS lookup?

Some big outfits do block certain IP address ranges, because they are (or are suspected to be) in a dynamic IP range, which is a bit suspicious in the mail business. You may have to contact the recipients to get you off the list...
/RID
0
 
UstasConnect With a Mentor Commented:
So..

If I understood correctly, mail coming out from your server gets marked as spam, by most well known e-mail providers, like MSN or Yahoo...

1. If you have a fixed IP, check if this ip is black listed. I normally check it here:
http://www.robtex.com/rbls.html

2. If your IP is dynamic, and you use some DNS updating client such as no-ip, you should consider having your setup changed to a one with a fixed IP. Other mail servers and their spam checking tools will trust you more.

3. Consider asking your ISP to put reverse dns entry to the fixed IP you have on your linksys router to match with the MX record. i.e. if your mail server listed in mx record is mail.somedomain.com, make sure your fixed IP on the router resolves to mail.somedomain.com. That too will help you prove that you are not a spammer.

4. Can you post the full headers of your messages, that end-up in Junk mail folder. I.e. go to the yahoo account that recieved your mail and put it to the spam folder, and enable full header views. Some mail servers may actually put the spam checking results into the headers, that will help you locate the problem.

5. Lastly, consider having a real-ip on your linux server, if you really need to run a proper e-mail server.

Hope this helps.

Stas
0
 
jdzemkeAuthor Commented:
Stats - Below is the full header view from the yahoo account I am using.  Are you able to recognize anything in the message below that would force this mail into the "bulk"/spam folder?  The Received: from linux.local 127.0.0.1 is suspect.

Bear with me on this.  Even if I get a static IP from my ISP (which would get assigned to my linksys router) and I do port forwarding through my linksys router, wouldn't I experience the same problem?  I am trying to get a clarification on the "real-ip" comment.  Maybe you are referring to my linux box being setup as a dhcp client.

I really appreciate the insight.


full header view from yahoo ---------------------------------------
X-Apparently-To: user@xxxxx.com via 68.142.207.221; Sat, 03 Jun 2006 11:52:02 -0700
X-YahooFilteredBulk: 8X.4X.5X.7X
X-Originating-IP: [8X.4X.5X.7X]
Return-Path: <maytest2list-bounces@xxxxx.com>
Authentication-Results: mta237.mail.re4.yahoo.com from=xxxxx.com; domainkeys=neutral (no sig)
Received: from 8X.4X.5X.7X (EHLO xxxxx.com) (8X.4X.5X.7X) by mta237.mail.re4.yahoo.com with SMTP; Sat, 03 Jun 2006 11:52:02 -0700
Received: from linux.local (localhost [127.0.0.1]) by xxxxx.com (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id k53Dk5f6001250 for <user@xxxxx.com>; Sat, 3 Jun 2006 08:46:05 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
From: maytest2list-request@xxxxx.com  Add to Address Book  Add Mobile Alert  
To: user@xxxxx.com
Subject: confirm a9701efa6def7d33c3bb4974c107b9688d1d1c9b
Reply-to: maytest2list-request@xxxxx.com
Message-ID: <mailman.0.1149342364.1249.maytest2list@xxxxx.com>
Date: Sat, 03 Jun 2006 08:46:04 -0500
Precedence: bulk
X-BeenThere: maytest2list@xxxxx.com
X-Mailman-Version: 2.1.6
List-Id: <maytest2list.xxxxx.com>
X-List-Administrivia: yes
Sender: maytest2list-bounces@xxxxx.com
Errors-To: maytest2list-bounces@xxxxx.com
Content-Length: 563
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.