Menu
▾
▴
#293 Magnet enhancement
Posted from "Cutting Edge" to "Feature Requests" per
your (John) request...
---snip---
Often when an incoming Email comes in, the address
specified in the "TO" header is not the Email address
that it's being sent to. This can be forged easily and this
is often the case with mailing lists, newsletters, or even
spam.
With that in mind, I'm wondering if a magnet could be
added that would look at the (for) addess in
the "Recieved" header. (Received /from/by/for).
---snip---
Logged In: YES
user_id=640570
For that matter, if a TO magnet is set up, it should fire if that
Email address appears on any of the addresses in the TO:,
CC: or (for) sections of the header, IMO.
If multiple addresses are specified in the TO or CC headers, it
should file regardless of it's position.
Logged In: NO
That would be GREAT! 90% of the SPAM mail I receive has
my email address altered/unrecognizable in the header.
So -- just like REAL magnets, it would be nice to
have 'attractive' magnets, as well as 'rejective' magnets. I
sure would be nice if I could put an email which does NOT
contain my address in the header, into a 'special' (SPAM)
bucket --
Logged In: YES
user_id=470719
Magnets should be able to act on any header. I subscribe to
one mailinglist that cannot be identified reliably by either the
To: or From:, but these headers would work-- List-Owner:
Reply-To:
Logged In: YES
user_id=790153
It would also be practical to split a magnet into several
magnets.
One 'from' magnet, one 'to' magnet, etc.
Then it is much easier to manage the corpus/../magnet files
with an editor. Its tedious to add 'from' and 'to' to your e-mail
adresses, especially when you have a lot (thousands).
Logged In: YES
user_id=470099
In general:
Searching for terms in the header seems to be worthy. I am
getting mail from people who are sending with my own email
address. If I could look for HELO info, I could block this out!
Logged In: YES
user_id=865869
One other thing that would be a nice enhancement would be
a priority order to the magnets. For instance, I may want all
of my wonko.net mail going to my inbox, but someone is
consistently spoofing my address as the sender, thus the
magnet always lets it through.
If there were a priority order to the filters, I could easily find
a unique attribute, filter that to spam first, and then dump
everything else to my inbox.
I use this in my Outlook Express sort with some success, but
it would add significant power and flexibility to the magnet
function.
If a priority order isn't available, then how about multiple
variables for each magnet? The same thing could then be
accomplished.
Logged In: YES
user_id=556673
I think magnet's should be able to hit all over the email.
some predefined header fields and the possibility to enter a
name for a header field and completed by the possibility to
even search the body would make the magnets much more
powerful.
Logged In: YES
user_id=953722
There needs to be a way to create a magnet for emails that
appear to have no "To:" field or "Subject:" and the message
body appears to be blank.
Logged In: YES
user_id=53438
Just my 2 cents worth:
1) Magnets based upon any part of an Email header would be
great.
2) Prioritisation of Magnets would be great. I process 200K+
email messages a year and rely heavily on magnets, but some
of the messages magnetized are really SPAM and can't be
changed through the UI.
Logged In: YES
user_id=100515
in the wake of recent viruses (Sobig, etc) how about also
adding a magnet that could involve attachments. For
example, if attachment name = "document.zip" then bucket
= "virus"
- Mayuresh
Logged In: YES
user_id=1335367
I second this suggestion. Recently I keep receiving a spam
mail whose sender is myself, which makes it impossible to
remove using POPFile as the content of mail appears to be
very "benign". If I could filter mail based
on "Received/from/by/for" as suggested, this would solve this
problem of forged sender.
Sample spam header for your reference.
Return-Path: <carlliu@evermoresw.com.cn>
Delivered-To: carlliu@evermoresw.com.cn
Received: (qmail 30290 invoked by uid 511); 26 Aug 2005
04:50:02 +0800
Received: from carlliu@evermoresw.com.cn by mail by uid
502 with qmail-scanner-1.20
(clamscan: 0.66. Clear:RC:0(207.255.233.246):.
Processed in 1.323145 secs); 25 Aug 2005 20:50:02 -0000
Received: from unknown (HELO 207-255-233-246-
dhcp.jst.pa.atlanticbb.net) (207.255.233.246)
by 0 (qmail 1.03 + ejcp v14) with SMTP;
26 Aug 2005 04:50:00 +0800
Received: from localhost.localdomain (HELO
localhost.localdomain [127.0.0.1])
by bureaucratic.inmail24.com (Mostfix) with
ESMTP id BAD2053BFF
for <carlliu@evermoresw.com.cn>; Thu, 25 Aug
2005 16:37:49 -0500
Message-Id: <200309010816.06350.baseline@inmail24.com>
Date: Thu, 25 Aug 2005 15:37:49 -0600
From: "carlliu@evermoresw.com.cn"
<carlliu@evermoresw.com.cn>
To: carlliu@evermoresw.com.cn
Subject: bus: Re: your web site needs this..
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.0.13
X-Mailer: Ximian Evolution 1.4.3
X-Text-Classification: bus
X-POPFile-Link: http://127.0.0.1:8080/jump_to_message?
view=2176
Logged In: YES
user_id=1335367
Actually, there is no need to enhance the magnet if you could
expand your word analysis to include all headers of the mail.