Re: Spam Assassin Detecting our emails as spam
Here is a complete header without the report_safe 1. Below the header is the result of my MXLookup and NSLookup. You will notice that I put my score down to 5 from my previous 8 in order to get this to report as spam. My question is what do I have to do in order to stop SA from reporting that there is no MX from our emails. I want our emails to get past: 3.2 NO_DNS_FOR_FROMDNS: Envelope sender has no MX or A DNS records Thanks, Wayne Return-Path: [EMAIL PROTECTED] Tue May 23 21:51:46 2006 Received: from UnknownHost [68.56.253.77] by worldfamousgiftbaskets.net with SMTP; Tue, 23 May 2006 21:51:46 -0500 X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on DEDE143 X-Spam-Level: *** X-Spam-Status: Yes, score=7.9 required=5.0 tests=AWL,EXTRA_MPART_TYPE,HTML_IMAGE_ONLY_24,HTML_MESSAGE,HTML_TAG_EXIST_TBODY,NO_DNS_FOR_FROM,RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=disabled version=3.1.1 X-Spam-Report: * 0.8 EXTRA_MPART_TYPE Header has extraneous Content-type:...type= entry * 0.1 HTML_TAG_EXIST_TBODY BODY: HTML has tbody tag * 0.9 HTML_IMAGE_ONLY_24 BODY: HTML: images with 2000-2400 bytes of words * 0.0 HTML_MESSAGE BODY: HTML included in message * 2.6 NO_DNS_FOR_FROM DNS: Envelope sender has no MX or A DNS records * 2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address * [68.56.253.77 listed in dnsbl.sorbs.net] * 1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP * [68.56.253.77 listed in combined.njabl.org] * -0.2 AWL AWL: From: address is in the auto white-list MIME-Version: 1.0 Message-Id: [EMAIL PROTECTED] Date: Tue, 23 May 2006 22:51:39 -0400 (Eastern Daylight Time) Content-Type: Multipart/related; type=multipart/alternative; boundary=Boundary-00=_3A1RG6G0 X-Mailer: IncrediMail (5002253) From: WFGB Team [EMAIL PROTECTED] X-FID: BA285063-5BCE-11D4-AF8D-0050DAC67E11 X-Priority: 3 To: Kammi Iungano [EMAIL PROTECTED] Subject: SPAM-LOW: SPAM: Kammi: Testing the email Disposition-Notification-To: WFGB Team [EMAIL PROTECTED] X-Spam-Prev-Subject: Kammi: Testing the email X-SmarterMail-Spam: REVERSE DNS LOOKUP, SPF_None nslookup -type=mx spectacularstuff.com Server: mail.spectacularstuff.com Address: 209.200.82.144 spectacularstuff.comMX preference = 21, mail exchanger = mail.worldfamousgiftbaskets.net mail.worldfamousgiftbaskets.net internet address = 209.200.82.144 nslookup -type=a spectacularstuff.com Server: mail.spectacularstuff.com Address: 209.200.82.144 Name:spectacularstuff.com Address: 63.134.208.125 -- View this message in context: http://www.nabble.com/Spam+Assassin+Detecting+our+emails+as+spam-t1653798.html#a4534763 Sent from the SpamAssassin - Users forum at Nabble.com.
Vouching for mail from a dynamic IP (was: SPAM-LOW: Re: Spam Assassin Detecting our emails as spam)
--On Saturday, May 20, 2006 4:54 PM -0700 jdow [EMAIL PROTECTED] wrote: Looking at your own email it comes from a COMCAST cable connection in Palmer Ranch Florida through the WFGB mailer. The WFGB mailer is not in SORBS anywhere. YOUR address most certainly is a dialup. So it WILL get tagged unless your mail goes through a machine that properly vouches for it. 68.32.0.0/11 (68.32.0.0-68.63.255.255) is a dynamic IP netblock. How does another machine properly vouch for it? If I route my mail to a colocated host under my control, how do I make that host vouch for the mail from my house?
Re: Vouching for mail from a dynamic IP (was: SPAM-LOW: Re: Spam Assassin Detecting our emails as spam)
On Mon, 22 May 2006, Kenneth Porter wrote: How does another machine properly vouch for it? If I route my mail to a colocated host under my control, how do I make that host vouch for the mail from my house? Send it over an ssh tunnel so that to the MTA it appears to be coming from 127.0.0.1. That's how I do it. -- John Hardin KA7OHZICQ#15735746http://www.impsec.org/~jhardin/ [EMAIL PROTECTED]FALaholic #11174pgpk -a [EMAIL PROTECTED] key: 0xB8732E79 - 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- The problem is when people look at Yahoo, slashdot, or groklaw and jump from obvious and correct observations like Oh my God, this place is teeming with utter morons to incorrect conclusions like there's nothing of value here.-- Al Petrofsky, in Y! SCOX ---
Re: Vouching for mail from a dynamic IP (was: SPAM-LOW: Re: Spam Assassin Detecting our emails as spam)
On Monday, May 22, 2006 12:28 PM -0700 John D. Hardin [EMAIL PROTECTED] wrote: Send it over an ssh tunnel so that to the MTA it appears to be coming from 127.0.0.1. That's how I do it. Any way to do that with sendmail at both ends? Currently I use an AuthInfo entry in the sending MTA's access DB, and a mailertable entry (or smarthost in sendmail.mc) to direct mail to the receiving MTA for domains that don't like dynamic senders. So the dynamic IP in the Received headers should show up as authenticated for the host with static IP.
Re: Spam Assassin Detecting our emails as spam
*small note to everyone. Thank you very much for your patience and willingness to help teach me on this subject\ Daryl, There is 1 issue with not hitting the spectacularstuff.com Someone is spoofing our emails and sending out SPAM as if it were us. I have gotten tons of spam from emails that look like they are from us but they are not. Could that be why we are in SORBS or we are being picked up by SORBS? We have not gotten any in a long time however. How do I tell SA not to hit @spectacularstuff.com when it comes through? Thanks, Wayne -- View this message in context: http://www.nabble.com/Spam+Assassin+Detecting+our+emails+as+spam-t1653798.html#a4493702 Sent from the SpamAssassin - Users forum at Nabble.com.
Spam Assassin Detecting our emails as spam
I have just set up Spam Assassin on our server. It is working very nicely however whenever we try to send an email from our own server to someone else on the same server, it gets picked up as spam. I am wondering if anyone here has experience with Spam Assassin and can help me fix the issues below as I don't know what they mean exactly. I have spam assassin set to detect at 8 points whether or not an email is spam. We are way over that because of the following reasons. What do I have to fix on our server to fix the 4 issues below? 1. We are losing 3.4 points because of HELO_DYNAMIC_IPADDR. 2. We are losing 2.6 points because of NO_DNS_FOR_FROM. 3. We are losing 2.0 points because of RCVD_IN_SORBS_DUL. 4. We are losing 1.7 points because of RCVD_IN_NJABL_DUL. Here is a standard header from Spam Assassin that we get when we sent each other email. Code: 3.4 HELO_DYNAMIC_IPADDRRelay HELO'd using suspicious hostname (IP addr1) 0.1 HTML_TAG_EXIST_TBODY BODY: HTML has tbody tag 0.7 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME 0.0 HTML_MESSAGE BODY: HTML included in message 2.6 NO_DNS_FOR_FROMDNS: Envelope sender has no MX or A DNS records 2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [68.56.175.199 listed in dnsbl.sorbs.net] 1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP [68.56.175.199 listed in combined.njabl.org] -0.2 AWLAWL: From: address is in the auto white-list Thanks for any help with this. Wayne -- View this message in context: http://www.nabble.com/Spam+Assassin+Detecting+our+emails+as+spam-t1653798.html#a4480701 Sent from the SpamAssassin - Users forum at Nabble.com.
Re: Spam Assassin Detecting our emails as spam
I have just set up Spam Assassin on our server. It is working very nicely however whenever we try to send an email from our own server to someone else on the same server, it gets picked up as spam. I am wondering if anyone here has experience with Spam Assassin and can help me fix the issues below as I don't know what they mean exactly. I have spam assassin set to detect at 8 points whether or not an email is spam. We are way over that because of the following reasons. What do I have to fix on our server to fix the 4 issues below? 1. We are losing 3.4 points because of HELO_DYNAMIC_IPADDR. 2. We are losing 2.6 points because of NO_DNS_FOR_FROM. 3. We are losing 2.0 points because of RCVD_IN_SORBS_DUL. 4. We are losing 1.7 points because of RCVD_IN_NJABL_DUL. Hi, you did not show the full headers - but probably your server failed to indicate in its received headers that the mail from the dynamic ip was authenticated, or SA failed to parse the received header Wolfgang Hamann
Re: Spam Assassin Detecting our emails as spam
Don't use a dialup and send direct?
{o.o}
- Original Message -
From: spectacularstuff [EMAIL PROTECTED]
To: users@spamassassin.apache.org
Sent: Friday, May 19, 2006 22:47
Subject: Spam Assassin Detecting our emails as spam
I have just set up Spam Assassin on our server.
It is working very nicely however whenever we try to send an email from our
own server to someone else on the same server, it gets picked up as spam.
I am wondering if anyone here has experience with Spam Assassin and can help
me fix the issues below as I don't know what they mean exactly.
I have spam assassin set to detect at 8 points whether or not an email is
spam. We are way over that because of the following reasons.
What do I have to fix on our server to fix the 4 issues below?
1. We are losing 3.4 points because of HELO_DYNAMIC_IPADDR.
2. We are losing 2.6 points because of NO_DNS_FOR_FROM.
3. We are losing 2.0 points because of RCVD_IN_SORBS_DUL.
4. We are losing 1.7 points because of RCVD_IN_NJABL_DUL.
Here is a standard header from Spam Assassin that we get when we sent each
other email.
Code:
3.4 HELO_DYNAMIC_IPADDRRelay HELO'd using suspicious hostname (IP
addr1)
0.1 HTML_TAG_EXIST_TBODY BODY: HTML has tbody tag
0.7 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME
0.0 HTML_MESSAGE BODY: HTML included in message
2.6 NO_DNS_FOR_FROMDNS: Envelope sender has no MX or A DNS records
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP
address
[68.56.175.199 listed in dnsbl.sorbs.net]
1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[68.56.175.199 listed in combined.njabl.org]
-0.2 AWLAWL: From: address is in the auto white-list
Thanks for any help with this.
Wayne
--
View this message in context:
http://www.nabble.com/Spam+Assassin+Detecting+our+emails+as+spam-t1653798.html#a4480701
Sent from the SpamAssassin - Users forum at Nabble.com.
Re: Spam Assassin Detecting our emails as spam
spectacularstuff wrote: I have just set up Spam Assassin on our server. It is working very nicely however whenever we try to send an email from our own server to someone else on the same server, it gets picked up as spam. I am wondering if anyone here has experience with Spam Assassin and can help me fix the issues below as I don't know what they mean exactly. I have spam assassin set to detect at 8 points whether or not an email is spam. We are way over that because of the following reasons. What do I have to fix on our server to fix the 4 issues below? 1. We are losing 3.4 points because of HELO_DYNAMIC_IPADDR. 2. We are losing 2.6 points because of NO_DNS_FOR_FROM. 3. We are losing 2.0 points because of RCVD_IN_SORBS_DUL. 4. We are losing 1.7 points because of RCVD_IN_NJABL_DUL. Here is a standard header from Spam Assassin that we get when we sent each other email. Code: 3.4 HELO_DYNAMIC_IPADDRRelay HELO'd using suspicious hostname (IP addr1) 0.1 HTML_TAG_EXIST_TBODY BODY: HTML has tbody tag 0.7 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME 0.0 HTML_MESSAGE BODY: HTML included in message 2.6 NO_DNS_FOR_FROMDNS: Envelope sender has no MX or A DNS records 2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [68.56.175.199 listed in dnsbl.sorbs.net] 1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP [68.56.175.199 listed in combined.njabl.org] -0.2 AWLAWL: From: address is in the auto white-list Thanks for any help with this. Wayne -- View this message in context: http://www.nabble.com/Spam+Assassin+Detecting+our+emails+as+spam-t1653798.html#a4480701 Sent from the SpamAssassin - Users forum at Nabble.com. Read about trusted_networks and internal_networks in the Mail::SpamAssassin::Conf man page. These parameters go into your local.cf configuration file. Andrew
Re: SPAM-LOW: Re: Spam Assassin Detecting our emails as spam
Thank you for all of the suggestions and comments.
[
A) But probably your server failed to indicate in its received headers that the mail from the dynamicIP was authenticated, or SA failed to parse the received header
B) Don't use a dial-up and send direct? {o.o}
C) Read about trusted_networks and internal_networks in the Mail::SpamAssassin::Conf man page. These parameters go into your Local.cf configuration file.
[
[My Replies]
A) There are 4 main things wrong. Is there the error failing to parse the received header for all of them?
How do I change that if that is the case. I am using smartermail if anyone is familiar with it.
How do I get SA to parse the received header if that is the case?
I have placed a header below.
B) We are not using a dial-up. What do you mean send direct?
We have an Ip for our server and we have our mail server on the same box using a different IP.
We have reverse DNS turned on for both IP's.
C) I have been searching for a manual everywhere for Windows. I cannot find one.
I am on a windows system and do not have access to the man command.
[This header to an email being picked up as spam and below it is the SA points]
Received: from localhost byServer-Name-RemovedWith SpamAssassin (version 3.1.1);Tue, 16 May 2006 22:26:26 -0500From: "Spectacular Stuff" email-address-removedTo: [EMAIL PROTECTED]Subject: SPAM: Re: your alltel email messageDate: Tue, 16 May 2006 23:25:54 -0400 (Eastern Daylight Time)Message-Id: [EMAIL PROTECTED]X-Spam-Flag: YESX-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on DEDE143X-Spam-Level: *X-Spam-Status: Yes, score=9.9 required=8.0 tests=AWL,HELO_DYNAMIC_IPADDR,HTML_MESSAGE,HTML_TAG_EXIST_TBODY,NO_DNS_FOR_FROM,RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.1.1MIME-Version: 1.0Content-Type: multipart/mixed; boundary="--=_446A97E2.4BEC"X-SmarterMail-Spam: SPF_NoneX-Rcpt-To: email-address-removed
[SA Points]
Content analysis details: (9.9 points, 8.0 required)
Pts rule namedescription
-- --
3.4 HELO_DYNAMIC_IPADDRRelay HELO'd using suspicious hostname (IP addr1)
0.1 HTML_TAG_EXIST_TBODY BODY: HTML has "tbody" tag
0.0 HTML_MESSAGE BODY: HTML included in message
2.6 NO_DNS_FOR_FROMDNS: Envelope sender has no MX or A DNS records
2.0 RCVD_IN_SORBS_DULRBL: SORBS: sent directly from dynamic IP address
[68.56.175.199 listed in dnsbl.sorbs.net]
1.7 RCVD_IN_NJABL_DULRBL: NJABL: dialup sender did non-local SMTP
[68.56.175.199 listed in combined.njabl.org]
0.1 AWLAWL: From: address is in the auto white-list
Wayne
---Original Message---
From: [EMAIL PROTECTED]
Date: 05/20/06 02:46:01
To: spectacularstuff
Cc: users@spamassassin.apache.org
Subject: SPAM-LOW: Re: Spam Assassin Detecting our emails as spam
I have just set up Spam Assassin on our server.
It is working very nicely however whenever we try to send an email from our
own server to someone else on the same server, it gets picked up as spam.
I am wondering if anyone here has experience with Spam Assassin and can help
me fix the issues below as I don't know what they mean exactly.
I have spam assassin set to detect at 8 points whether or not an email is
spam. We are way over that because of the following reasons.
What do I have to fix on our server to fix the 4 issues below?
1. We are losing 3.4 points because of HELO_DYNAMIC_IPADDR.
2. We are losing 2.6 points because of NO_DNS_FOR_FROM.
3. We are losing 2.0 points because of RCVD_IN_SORBS_DUL.
4. We are losing 1.7 points because of RCVD_IN_NJABL_DUL.
Hi,
you did not show the full headers - but probably your server failed to indicate in its
Received headers that the mail from the dynamic ip was authenticated, or SA failed
to parse the received header
Wolfgang Hamann
Re: SPAM-LOW: Re: Spam Assassin Detecting our emails as spam
The messages getting tagged most positively are on a segment of addresses
that are tagged as dynamically assigned addresses, colloquially called
dialup addresses in the anti-spam community. That is what these mean:
RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL
This is good for several points on any spam checking engine if they do
not go through an emailer that vouches for them.
A major question you never answered is whether it is your own site
filtering outbound mail or other sites that are declaring your email
to be spam.
Looking at your own email it comes from a COMCAST cable connection
in Palmer Ranch Florida through the WFGB mailer. The WFGB mailer is
not in SORBS anywhere. YOUR address most certainly is a dialup. So
it WILL get tagged unless your mail goes through a machine that
properly vouches for it. 68.32.0.0/11 (68.32.0.0-68.63.255.255) is
a dynamic IP netblock.
{^_^}
- Original Message -
From: WFGB Team [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: users@spamassassin.apache.org
Sent: Saturday, May 20, 2006 07:53
Subject: Re: SPAM-LOW: Re: Spam Assassin Detecting our emails as spam
Thank you for all of the suggestions and comments.
[
A) But probably your server failed to indicate in its received headers that
the mail from the dynamic IP was authenticated, or SA failed to parse the
received header
B) Don't use a dial-up and send direct? {o.o}
C) Read about trusted_networks and internal_networks in the
Mail::SpamAssassin::Conf man page. These parameters go into your
Local.cf configuration file.
[
[My Replies]
A) There are 4 main things wrong. Is there the error failing to parse the
received header for all of them?
How do I change that if that is the case. I am using smartermail if anyone
is familiar with it.
How do I get SA to parse the received header if that is the case?
I have placed a header below.
B) We are not using a dial-up. What do you mean send direct?
We have an Ip for our server and we have our mail server on the same box
using a different IP.
We have reverse DNS turned on for both IP's.
C) I have been searching for a manual everywhere for Windows. I cannot find
one.
I am on a windows system and do not have access to the man command.
[This header to an email being picked up as spam and below it is the SA
points]
Received: from localhost by Server-Name-Removed
With SpamAssassin (version 3.1.1);
Tue, 16 May 2006 22:26:26 -0500
From: Spectacular Stuff email-address-removed
To: [EMAIL PROTECTED]
Subject: SPAM: Re: your alltel email message
Date: Tue, 16 May 2006 23:25:54 -0400 (Eastern Daylight Time)
Message-Id: [EMAIL PROTECTED]
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on DEDE143
X-Spam-Level: *
X-Spam-Status: Yes, score=9.9 required=8.0 tests=AWL,HELO_DYNAMIC_IPADDR
HTML_MESSAGE,HTML_TAG_EXIST_TBODY,NO_DNS_FOR_FROM,RCVD_IN_NJABL_DUL
RCVD_IN_SORBS_DUL autolearn=no version=3.1.1
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=--=_446A97E2.4BEC
X-SmarterMail-Spam: SPF_None
X-Rcpt-To: email-address-removed
[SA Points]
Content analysis details: (9.9 points, 8.0 required)
Pts rule name description
--
--
3.4 HELO_DYNAMIC_IPADDRRelay HELO'd using suspicious hostname (IP
addr1)
0.1 HTML_TAG_EXIST_TBODY BODY: HTML has tbody tag
0.0 HTML_MESSAGE BODY: HTML included in message
2.6 NO_DNS_FOR_FROMDNS: Envelope sender has no MX or A DNS records
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP
address
[68.56.175.199 listed in dnsbl.sorbs.net]
1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[68.56.175.199 listed in combined.njabl.org]
0.1 AWLAWL: From: address is in the auto white-list
Wayne
---Original Message---
From: [EMAIL PROTECTED]
Date: 05/20/06 02:46:01
To: spectacularstuff
Cc: users@spamassassin.apache.org
Subject: SPAM-LOW: Re: Spam Assassin Detecting our emails as spam
I have just set up Spam Assassin on our server.
It is working very nicely however whenever we try to send an email from
our
own server to someone else on the same server, it gets picked up as spam.
I am wondering if anyone here has experience with Spam Assassin and can
help
me fix the issues below as I don't know what they mean exactly.
I have spam assassin set to detect at 8 points whether or not an email is
spam. We are way over that because of the following reasons.
What do I have to fix on our server to fix the 4 issues below?
1. We are losing 3.4 points because of HELO_DYNAMIC_IPADDR.
2. We are losing 2.6 points because of NO_DNS_FOR_FROM.
3. We are losing 2.0 points because of RCVD_IN_SORBS_DUL.
4. We are losing 1.7 points because of RCVD_IN_NJABL_DUL.
Hi,
you did not show the full headers
Re: Spam Assassin Detecting our emails as spam
On 5/20/2006 11:44 PM, WFGB Team wrote: [My Replies] A) Since I am unsure what MSA is I did some checking up. How do I know if I am set up for MSA? I am using Smartermail. I am equally unsure of what MTA is. I know what the MX Records are sort of. Looking at the headers of the email you sent me, you're using the same SMTP service for both incoming mail from other domains (your MX), for accepting mail from your user's MUAs (your MSA) and for sending mail to other sites (your MTA). How do I know if I even have MSA clients? Your very own MUA is a client to your MSA. We have a dedicated server. We only have about 10 email addresses on 1 domain name and they are all POP3 and SMTP. We have 1 email address on another domain. B) I read that page but it didn't make any sense to me. I can put the trusted network up but how do I know what everyone's IP addresses are or should I put our own mail server IP? Trusted_networks 10.222.111/24 Since you're using the same SMTP service for everything you need to do one of the following (I'd look for help on some Smartermail mailing list): - get your SMTP server software to include (RFC 3848) auth tokens in it's mail headers - not scan (pipe through SpamAssassin) mail from authenticated users Yes, you should include the IPs of your mail server in your config. Something like this is probably correct for your setup: trusted_networks 127.0.0.1 209.200.82.144 Obviously if you're users are on dynamic IP space you can't include their IPs. This is where auth tokens, above, come in or not scanning their mail at all. Daryl
Re: Spam Assassin Detecting our emails as spam
Okay Please forgive my ignorance here as I am attempting to absorb and understand all of this. I am presuming the meaning of dialup here is not the same as a dialup ISP such as Juno or Netzero, etc etc etc. because all of our people on the server are on high-speed internet and not dialup accounts. ]] A major question you never answered is whether it is your own site filtering outbound mail or other sites that are declaring your email to be spam. ]] [My Reply] If someone that has an email @spectacularstuff.com sends an email to someone else that has an email @spectacularstuff.com, the email will get marked as spam because of those things mentioned in my previous emails. That is what I am trying to prevent. To get around the issue, I have raised the bar on SPAM from 8 points to 11 points. This is allowing more spam to get through but also allowing our emails to get through. Let me ask a more direct question because I don't have all of the knowledge yet to understand some of the answers being given. They are more confusing to me than anything. Just working on 1 thing right now. If I send an email to another domain on our own server I will get the following: 3.4 HELO_DYNAMIC_IPADDRRelay HELO'd using suspicious hostname (IP addr1) What do I have to do or change on the server so that doesn't happen? Thanks, Wayne -- View this message in context: http://www.nabble.com/Spam+Assassin+Detecting+our+emails+as+spam-t1653798.html#a4489396 Sent from the SpamAssassin - Users forum at Nabble.com.
Re: Spam Assassin Detecting our emails as spam
Thanks Daryle, I just read your replies That makes sense. I will have to read up on a few things... 1st: What auth tokens are. 2nd: Whether Smartmail can allow those and the RFC number you mentioend 3rd: how to set SA to utilize those. Thanks again. Wayne -- View this message in context: http://www.nabble.com/Spam+Assassin+Detecting+our+emails+as+spam-t1653798.html#a4489404 Sent from the SpamAssassin - Users forum at Nabble.com.
Re: Spam Assassin Detecting our emails as spam
Hi Daryl, I put the trusted networks in and that seem to get rid of a few things but now it brought out 4 or 5 others... lol I understand what the following is. I just don't know how to fix it. Do you know how to fix this issue? 3.2 NO_DNS_FOR_FROMDNS: Envelope sender has no MX or A DNS records.. I do have an MX right? I do have an A DNS record. I saw it. What am I doing wrong that SA doesn't see those things. (My biggest question is how do I fix that. What do I have to do or how do I have to configure the server?) Thanks, Wayne -- View this message in context: http://www.nabble.com/Spam+Assassin+Detecting+our+emails+as+spam-t1653798.html#a4489536 Sent from the SpamAssassin - Users forum at Nabble.com.
Re: Spam Assassin Detecting our emails as spam
On 5/21/2006 12:30 AM, spectacularstuff wrote: Hi Daryl, I put the trusted networks in and that seem to get rid of a few things but now it brought out 4 or 5 others... lol I understand what the following is. I just don't know how to fix it. Do you know how to fix this issue? 3.2 NO_DNS_FOR_FROMDNS: Envelope sender has no MX or A DNS records.. I do have an MX right? I do have an A DNS record. I saw it. What am I doing wrong that SA doesn't see those things. (My biggest question is how do I fix that. What do I have to do or how do I have to configure the server?) Assuming the envelope sender (return-path) ends in @spectacularstuff.com you shouldn't hit this... unless your mail server is having problems resolving DNS records. From a command shell on your server, make sure you can resolve the A and MX records for whatever the domain in the envelope-sender/return-path is in the affected messages: nslookup -type=mx spectacularstuff.com nslookup -type=a spectacularstuff.com Daryl
