Well, it's essentially the same answer. The Recipient: information is included only if it is different than the To: address. I suppose if there are a hundred To: addresses, finding the Recipient is a problem because you can't make the window that wide. Perhaps all of those boxes need a popup to show the complete contents.
 
                 Randy.
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Woodie Sayles
Sent: Wednesday, April 07, 2004 11:17 PM
To: [email protected]
Subject: RE: tf exceptions

Sorry -- I meant to say the "To:" field, not the "From:" field. The way it is displayed in SpamEye was helpful because even if there were multiple "To:" addresses, I could see who on my system the email was addressed to.
 

Woodie Sayles
[EMAIL PROTECTED] 
Webfoot.Net
2030 Main Street
Dunedin, FL  34698
(727) 442-5770
(727) 442-3380 - fax

Fast, friendly, professional web design and hosting.
Visit our web site at http://www.webfoot.net to see what we can do for you!

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Brukardt
Sent: Wednesday, April 07, 2004 7:14 PM
To: [email protected]
Subject: RE: tf exceptions

"Mail From:" is only included on the "From:" line when it is different from "From:". If you see any case where it is omitted and is *not* the same, I'd like to see an example.
 
Sometimes you do need a pretty wide screen to see it. But there isn't much reason to look at it manually, as it will be analyzed by the Analyze Spam button and included in the domains if appropriate.
 
                             Randy.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Woodie Sayles
Sent: Tuesday, April 06, 2004 4:29 PM
To: [email protected]
Subject: RE: tf exceptions

Speaking of the "Mail From:" line in the RCP file, is anyone else having any problems because that doesn't always show up in the "From:" line in TFV? Sometimes I use SpamEye so I can see who it was addressed to on my system. If there's another way to get that information from TFV, it would be very helpful to know.

Woodie Sayles
[EMAIL PROTECTED] 
Webfoot.Net
2030 Main Street
Dunedin, FL  34698
(727) 442-5770
(727) 442-3380 - fax

Fast, friendly, professional web design and hosting.
Visit our web site at http://www.webfoot.net to see what we can do for you!

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Brukardt
Sent: Tuesday, April 06, 2004 5:12 PM
To: [email protected]
Subject: RE: tf exceptions

TF Classic checks just the "Mail From" line in the RCP, not the "From:" line in the mail message. They don't have to be the same, although they often are.
 
TF Pro changes this (it checks both), as well as adding pass lists for "To:" and "Subject:". Sign up today. :-)
 
              Randy.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of James Goines
Sent: Tuesday, April 06, 2004 3:09 PM
To: [email protected]
Subject: Re: tf exceptions

As a follow-up question, what address line is scanned for the pass/no-delete? 

I have been trying to use this but some of my messages still get trashed for a URL check.

James

Randy Brukardt wrote:
Kerry Barlow wrote:

  
Hi all: Maybe this has been explained before, but I cannot find it in my
    
archives.
  
If I add an email name to the TF exception list, will TF still trash any
files that may be a virus from that address?
    

Something found on the Pass list turns off *all* TF checks. That includes
any virus checks in TF. It has no affect on checks made by other plugins,
such as AVP. (It also will not affect the F-Prot antivirus module in TF Pro
1.01 - but that's still in the future.)

Something found on the No Delete list will be filtered by TF, but no delete
actions will be applied.

                  Randy.

This is the discussion list for the IMS Free email server software.
  To unsubscribe send mailto:[EMAIL PROTECTED]

            Delivered by Rockliffe MailSite
           http://www.rockliffe.com/mailsite
                Rock Solid Software (tm)


  

Reply via email to