headers
Riser | 1 Apr 2000 04:10

Re: procmail delievering mail


Subject: procmail delievering mail 

> I was looking at a bunch of faqs and all over procmails site and couldnt
> find how to make procmail deliever to user home directories and not to
> /var/mail/$LOGIN. Im guessing its something in the /etc/procmailrc but i
> cant find a list of commands for the file. If anyone knows a good procmail
> site or a good how to id like to know.  Thanks for any info you can give.
> 
> Brian

You can  make use of the procmailrc file.It needed to be created by youself,and generally its location is
/etc directory.If you want to deliever mail to user home directory instead of /var/mail/$LOGIN,you can
add this 
in your procmailrc file:
  MAILDIR=$HOME
  DEFAULT=$MAILDIR/mbox
  ORGMAIL=$MAILDIR/mbox
  LOCKFILE=$HOME/.lockmail
Good luck!
                                                        Riser
Permalink | Reply | 1 comment |
headers
Darren Wyn Rees | 1 Apr 2000 04:48
Picon

stripping 'footer ads' from mailing lists

what is the most prudent way of stripping
footer ads placed in 'free' mailing lists ?

here's an example (i've numbered the lines) :

1 ------------------------------------------------------------------------
2 Get a NextCard Visa, in 30 seconds!
3 1. Fill in the brief application
4 2. Receive approval decision within 30 seconds
5 3. Get rates as low as 2.9% Intro or 9.9% Fixed APR
6 Apply NOW!
7 http://click.egroups.com/1/975/1/_/514520/_/954556624/
8 ------------------------------------------------------------------------

is sed the best tool for this job ?

thanks for any useful comments.

darren

--

-- 
Le biblioteche ci hanno dato il potere,
poi il lavoro è venuto e ci ha reso liberi.
Che prezzo ora, per un piccolo assaggio di dignità...
Permalink | Reply | 4 comments |
headers
David W. Tamkin | 1 Apr 2000 18:41
Picon
Favicon

Re: stripping 'footer ads' from mailing lists

Darren Wyn Rees asked,

| what is the most prudent way of stripping
| footer ads placed in 'free' mailing lists ?

| is sed the best tool for this job ?

That depends on particulars.  Since head is going to be a smaller binary
than sed, head may be more efficient, in exchange for a little more work
inside procmail.  In these examples, the assumption is that "pattern" is
on the first line to be dropped; if "pattern" is on the last line to be
kept, make the commented replacements:

  :0
  * ()\/pattern(.*$)*
# if pattern should be kept, use this instead of above:
# * pattern.*$\/(.*$)*
  {
   FOOTER=$MATCH

   :0
   * 1^1 B ?? ^.*$
   * -1^1 FOOTER ?? ^.*$
   { KEEPLINES = $= }

   :0bfi
   | head -$KEEPLINES
  }

Otherwise, you can use sed:
(Continue reading)

Permalink | Reply | 3 comments |
headers
Walter Dnes | 2 Apr 2000 03:28

Re: RBL for procmail ?

On Tue, Mar 28, 2000 at 05:52:43PM +0200, Fabien Penso wrote

> I manage a mail server for a lot of people so it's difficult for me to
> let things like rbl, mail-abuse, etc which could reject some mails for
> my users which could be important. But I hate SPAM so I'd like to
> activate rbl, etc for me and I was wondering if I could do that through
> procmail.
  I suggest that you get the mailserver to check with RBL/RSS/DUL/etc.
But rather than bouncing the email, insert a warning X-header into the
email headers.  Those people who *WANT* to filter can then look for
"X-RBL:" or "X-RSS:" etc.  Those who fear false-positives can ignore the
extra headers.

--

-- 
Walter Dnes <waltdnes <at> waltdnes.org> SpamDunk Project procmail spamfilter
at http://www.waltdnes.org   This message coming to you in living Linux.
Permalink | Reply | 1 comment |
headers
Walter Dnes | 2 Apr 2000 03:28

Re: reg.expr.

On Mon, Mar 27, 2000 at 09:49:42AM +0200, Jost Schaper wrote
> I do not know, wether it is worth to subscribe (have lost majordomo's
> adress):
  OK, I'll cc: this to your address

> The letters I receive are similar to the following:
> ½£µÀ¶ÍÁ¶ÉíÐĵĺ÷½·¨£¬»¶Ó­²Î¼Ó£
> 
> and these:
> £­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­£­
> ¡¡¡¡±±¾©ÆßÒÕÌåÓý·¢Õ¹ÓÐÏÞ¹«Ë¾£¨¼ò³Æ"ÆßÒÕÌåÓý"£©³É
> Á¢ÓÚ1999Äê¡£¹«Ë¾Ö÷ÓªÏîĿΪÍƹã¸÷ÖÖÌåÓý»î¶¯£¬ÓÈÆä
> ÊÇÐÂÐË¡¢ÁíÀàÌåÓý»î¶¯£¬²¢×¢Öؽ«ÓéÀÖ½¡ÉíÈÚÈëÆäÖС£
> ÆßÒÕÌåÓýµÄ×éÖ¯ÕßÊÇһȺ³äÂú»îÁ¦ºÍ½øÈ¡¾«ÉñµÄÄêÇáÈË£¬
> ÎÒÃÇÊÓÍƹãÌåÓýÔ˶¯Îª¼ºÈΣ¬ÔÚÔ˶¯ÖиÐÊÜÈËÓë×ÔÈ»µÄ
> Èںϣ¬ÌåÑéÈËÄÚÔڵľ«Éñ£¬ÅàÑøÓÂÍùֱǰµÄÆ·µÂ¡£ÔÚ¹«
> ˾³ÉÁ¢²»µ½Ò»ÄêµÄʱ¼äÀÒÑÈ¡µÃÁË׿ÓгÉЧµÄ·¢Õ¹ºÍ
> Ï൱ÉîÔ¶µÄÓ°Ïì¡£
> 
> I am thinking of have .procmail look for these in the Subject and/or the
> body of the mail, but I do not know how to formulate this as
> reg.-expressions in the first line or the complete lines for procmail.
  Drop by my webpage (see URL below) and check out my Chinese spamfilter
(The pointer is on the main page).  It flags any email with more than 5%
high-bit characters (i.e. CHAR(128)..CHAR(255).  If you normally
correspond with people who send a few high-bit characters (e.g. French
accents or German umlauts) email me, and I'll help tweak the filter to
avoid false positives.

--

--
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jost Schaper | 2 Apr 2000 12:27
Favicon

Re: reg.expr.

Walter, 
thank you for your mail.
I have downloaded the zip-file.
But, the problems are my german friends, who sometimes do even use
german Umlaute in their headers, but also in the bodies.

My way was the following:
I had procmail resend the spam 4 times to the sender-mailing-list - not
very polite, but it worked in most cases.
Then I updated to SuSE-LINUX 6.3 with the new sendmail-access-file,
where I put all collected adresses.

But your .procmail-receipt looks more interesting.
Could you please send me the anti-chinese-pro-german anti-spam-filter?
äÄöÖüÜß

Thank you,
Jost

Walter Dnes wrote:
> 
> On Mon, Mar 27, 2000 at 09:49:42AM +0200, Jost Schaper wrote
> > I do not know, wether it is worth to subscribe (have lost majordomo's
> > adress):
>   OK, I'll cc: this to your address
> 
> > The letters I receive are similar to the following:
> > ½£µÀ¶ÍÁ¶ÉíÐĵĺ÷½·¨£¬»¶Ó­²Î¼Ó£
> >
> > and these:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ries van Twisk | 3 Apr 2000 15:17
Picon

Preventing mail loops and autoresponding.

Dear promail users,

I can prevent certain mail loop with like : >X-Loop:  
$LOGNAME <at> FQDN>
This is working Ok/ if I recurse the ,procmailrc or a mailserver 
bounces back the e-mail. This is tested and working ok.

But what if a mail client or a mail server is generating a entirely 
new mail message in respond to a 'vacation' message I have send 
hem?
I think Pegasus is doing this and M$ exange server (I think, I'm not 
sure) I didn't tryd it out yet because I'm still at a testing stage but I 
do get bounced mail over and over again if I turn the mail received 
option on. I now I can store someones e-mail address but I do need 
to send this message everytime that person sends me a message.

How can I detect situation and stop autoreplying in procmail?

Ries van Twisk
Permalink | Reply | 0 comments |
headers
Ries van Twisk | 3 Apr 2000 15:33
Picon

Preventing mail loops and autoresponding. part 2

Ok, 
the ^FROM_DEAMON should prevent this (I already had
it in pleace, see last message)

But ^FROM_DEAMON does not catch the Pegasus Mail Client.
SHould I just make a filter for every know mail client?

Ries
Permalink | Reply | 0 comments |
headers
Ries van Twisk | 3 Apr 2000 16:01
Picon

Preventing mail loops and autoresponding. Solved


I solved th problem.
I forgot to use th <-r> on formail.

RIes
Permalink | Reply | 0 comments |

Gmane