Re: [Declude.JunkMail] Re: Documentation

2007-02-16 Thread Darin Cox
David replied offline, so I thought I would share the links he sent. http://shopping.declude.com/Version/Manuals/JunkMail/JM_4.0.8.asp http://shopping.declude.com/Version/Manuals/EVA/EVA_4.0.8.asp I found that 2.0.6 documentation is also available this way at

[Declude.JunkMail] disable subject line warning on one email account

2007-02-16 Thread Craig Edmonds
I would like to disable the subject line warning that gets placed in the subject line for one particular email account on a domain. He is complaining that he sees too many emails with a subject warning. Kind of like this. if the email address = [EMAIL PROTECTED] then don't put subject line

Re: [Declude.JunkMail] disable subject line warning on one email account

2007-02-16 Thread Darin Cox
Not a rule, but either a domain-level or user-level config to change the WARN action to IGNORE. Darin. - Original Message - From: Craig Edmonds To: declude.junkmail@declude.com Sent: Friday, February 16, 2007 6:33 AM Subject: [Declude.JunkMail] disable subject line warning on one

RE: [Declude.JunkMail] disable subject line warning on one email account

2007-02-16 Thread Craig Edmonds
Hi Darin, That sounds like it. Any instructions on how to do it? Put a file in the domain directory? What would the format be? Kindest Regards Craig Edmonds 123 Marbella Internet W: www.123marbella.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox

Re: [Declude.JunkMail] OT: SPF record question

2007-02-16 Thread Gary Steiner
I have a question to follow this subject. If users have Outlook and they are sending email fromm home or whereever using authentication, then the IP that shows up in the header will be their home connection. That being the case, unless your users are strictly using webmail, your SPF record

Re[2]: [Declude.JunkMail] OT: SPF record question

2007-02-16 Thread Sanford Whiteman
To me this indicates that SPF doesn't help you if your users are not using webmail. Is this correct? No, the connecting IP seen by remote servers will still be the last hop on your network, not the authenticating IP that submitted the mail. While this is thus an irrelevant concern

RE: SPAM-WARN:Re: [Declude.JunkMail] OT: SPF record question

2007-02-16 Thread Michael Thomas - Mathbox
Gary, Your logic is incorrect. SPF is a check made by the destination mail server (possibly my mail server) against the sending mail server (your mail server). Your users authenticate to your mail server, then submit a message to your mail server for delivery by your mail server to the remote

RE: SPAM-WARN:Re: [Declude.JunkMail] OT: SPF record question

2007-02-16 Thread Gary Steiner
Let me give you my case. For this example I used my home Comcast connection to send an email using Outlook and authentication. My server uses Declude and SmarterMail. The header of the received message shows one IP address in a single Received line: Received: from

Re: SPAM-WARN:Re: [Declude.JunkMail] OT: SPF record question

2007-02-16 Thread Darin Cox
Whitelisting SMTP Auth is the key here. Since you connect with a userID/PW to your mail server, Whitelisting connections done through SMTP AUTH bypasses Declude filtering. Darin. - Original Message - From: Gary Steiner [EMAIL PROTECTED] To: declude.junkmail@declude.com Sent: Friday,

RE: SPAM-WARN:Re: [Declude.JunkMail] OT: SPF record question

2007-02-16 Thread Michael Thomas - Mathbox
Gary, I guess, I should have asked this earlier, but you mentioned authenticated users, which is the other side of the coin. Are you testing SPF for outgoing mail? If so, why? Is it possible to send email from your mail server without authenticating? If none of that was pertinent, continue on