Pegasus Mail & Mercury

David:

I use Pegasus as an intermediate tool to filter for SPAM.  I have a Content Control file for some of the filters to Forward the email to "Admin".  This allows me to login to Pegasus as "Admin" and check for "false positives" and forward any messages that may occur.  Sometimes we receive "false positives" with the "To:" line reading "undisclosed recipients" or the "To:" line will display an email address that is not at our domain.  It appears that these emails are being sent as a "BCC".  Is it possible to add some sort of an "X-Recipient header" giving information about the actual recipient at our domain?

This would really help me determine who is supposed to receive this email.

Thanks,

Charlie
  ~~~

cfastner:

David:

I use Pegasus as an intermediate tool to filter for SPAM. I have a Content Control file for some of the filters to Forward the email to "Admin". This allows me to login to Pegasus as "Admin" and check for "false positives" and forward any messages that may occur. Sometimes we receive "false positives" with the "To:" line reading "undisclosed recipients" or the "To:" line will display an email address that is not at our domain. It appears that these emails are being sent as a "BCC". Is it possible to add some sort of an "X-Recipient header" giving information about the actual recipient at our domain?

This would really help me determine who is supposed to receive this email.

Thanks,

Charlie
~~~

 

The X-Envelope-To: header usually provides this header for mail delivered by Mercury/32 core however mail moved out of the normal processing does not get this header.   If you use POPFileD with the POPFile Bayesian anti-spam system it will also add the X-Recipient: with the original RCPT TO: address.  That's what I use to forward the false positive mail on the the original user.  Actually it does not happen all that often since I have a 0.035 FPR with POPFileD.

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

Thomas:

The problem is that the Content Control forwards it to "Admin" so the "X-Envelope-To:" header reads "Admin" instead of the ORIGINAL Recipient so I can't tell who it was INTENDED to go to!

Thanks for the response.

Charlie
  ~~~

 

Hello!

 

As I do not use Mercury myself, I am not sure whether my following suggestion may help you.

If the messages you have forwarded do not have an "X-Recipient-header:"- or an "X-Envelope-To:"-line, you may find a similar entry in the headers - "similar" means: an entry that descriibes what recipient the message was originally sent to. I am thinking of the "Received:"-lines that sometimes tell you that.

Look at this example:

Received: from example.com by domain000.example.com with local (Exim 4.63)
 (envelope-from <domain000.example.com>)
 id 1Ih6N6-0007MO-L1
 for original_recipien @example_2.com; Sun, 14 Oct 2007 18:31:20 +0200

Note the "for"-line of the end of that "Received:"-header. Can you filter for such an entry?

 

---

Support Pegasus Mail here: http://www.pmail.com/donate.htm

Visit the Pegasus Mail Online shop here: http://www.cafepress.com/pegasusmail

cfastner:

Thomas:

The problem is that the Content Control forwards it to "Admin" so the "X-Envelope-To:" header reads "Admin" instead of the ORIGINAL Recipient so I can't tell who it was INTENDED to go to!

Thanks for the response.

Charlie
~~~

 

Note that I said that POPFileD added the original RCPT TO: header; you might want to look into using POPFileD.  You need to look through the headers to see if your ISP adds a similar header to the message, yuo might even see it in one of the original Received: headers. 

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team