shanew | 19 May 23:17 2015
Picon

Limit user actions in .procmailrc

I'm updating a fairly old and very idiosyncratic mail system, and one
of the features of this system is that only explicitly listed users
can call external commands from within a .procmailrc.  I think this is
actually accomplished by having both a "regular" procmail for the
listed users, but a "hobbled" procmail that was locally compiled to
disallow such things, but in any case, I'm wondering what options I
have to recreate similar functionality?

Is there something equivalent to sendmail's smrsh functionality for
procmail?

I've looked briefly at jailkit and jk_procmailwrapper, but it has
pretty limited documentation and makes it look like users already need
to live in jailed shells as well as requiring a non-standard mailbox
location, so it's definitely not my first choice.

Another idea that occurred to me would be to prevent .procmailrc
execution by setting DROPPRIVS equal to "no" in the system
/etc/procmailrc unless the LOGNAME value appears in a file that listed
allowed users?  Does this even seem do-able?  I don't know if this
would be an acceptable solution for us, but I won't even bother trying
if it's not possible (or just a plain "Bad Idea").

Somewhat related to that, is it possible to set DROPPRIVS to yes, and
then change it to no later in /etc/procmailrc?  I'm thinking of a
situation where the system procmailrc might look for a user with a
vacation message setup, drop to being them to run vacation, and then
set DROPPRIVS=no to prevent any .procmail from being executed.

Thanks for any insight you might have to offer
(Continue reading)

@lbutlr | 30 Apr 22:40 2015

test

Apologies, please ignore.

--

-- 
Say, give it up, give it up, television's taking its toll That's enough,
that's enough, gimme the remote control I've been nice, I've been good,
please don't do this to me Turn it off, turn it off, I don't want to
have to see
@lbutlr | 29 Apr 18:30 2015

Stripping extra stuff from text

I have the following which generates a 140 character blog for sending me an SMS alert:

MSGTEXT=`/usr/local/bin/formail -I ""`
SMSTEXT=`echo $MSGTEXT | lynx --dump --dont_wrap_pre -stdin | tr '\n' ' ' | /usr/bin/cut -c1-140`

:0c
      | (formail -brt -I"Subject: ${CLEANFROM}" \
        -I"To: ${MOBILE}" \
        -I"From: lbuter <at> kreme.com"; \
        echo $SMSTEXT) | $SENDMAIL -t

This works fine, but I end up with text like:

SMS:    This is the body of the email. It should be more than 140 characters to    = test if the cut pipe is working and
if this message will be 

As you can see, I have leading spaces, and an extraneous =, but if I remove lynx from the chain, I will get HTML
crap in the message on those messages.

Is there a simple way to remove any extra space AND encoding cruft, or do I just need to stack up some tr or sed
pipes? 

--

-- 
"Why, you stuck-up, half-witted, scruffy-looking... NERFHERDER!"
"Who's Scruffy looking?"
@lbutlr | 23 Mar 18:22 2015

strange error in my procmailrc

when the procmailrc hands off mail for my personal account it logs an error:

User me <at> mail.covisp.net has a .procmailrc, processing...
date: illegal time format
usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ... 
            [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format]

None of the other accounts with .procmailrcs log this error, but when I look in my .procmailrc for date:

$ grep date /home/me/.procmailrc 
DATE=`date '+%d-%b-%Y'`
MDATE=`date '+%Y-%m'`
YDATE=`date '%Y'`
LONGDATE=`date "+%y-%b-%d %I:%M:%S %z"`
LOG="`date`${NL}Checking Spam Status... "
  LOG="done. `date`$NL"
  LOG="Delivered `date`$NL"
LOG="Delivered `date`$NL”

None of these seem like they should be throwing any sort of error. They all execute fine from the command line
and date is in /bin/ so I don’t think it could be a path problem. Also, there are not errors logged to my
procmailk log file, only to the global log file/

--

-- 
'You don't think you've had enough, do you?' he said. I KNOW WHEN I'VE
HAD ENOUGH. 'Everyone says that, though. I KNOW WHEN EVERYONE'S HAD
ENOUGH. --Moving Pictures

____________________________________________________________
procmail mailing list   Procmail homepage: http://www.procmail.org/
(Continue reading)

Alan Clifford | 23 Mar 16:22 2015

Any dangers with this recipe?


I know I'm probably being petty and unreasonable but there we are.  A 
couple of events have really annoyed me.

Firstly, I politely asked a company to stop sending emails to an address. 
They said the couldn't and I think they quoted the data protection act. 
They said I had to do it myself on their website.  Hmmm, was that true?

The second event was a company that sent me several emails on the same day 
to an address that only appears as a contact address on my website.  I 
wondered if I could persuade them to stop.  As I don't want the website 
email address to be repeated here, I've used xxxx <at> example.com in the 
recipe below.

I've attempted to target specific people at the company concerned to annoy 
them with their own email spew. devnull <at> clifford.ac is rejected by 
sendmail so hopefully no mail loop.  And I tagged my gmail address I use 
for testing onto the the list of recipients so I could see what I was 
sending out.

Any problems/dangers?

:0
* ^to:.*xxx <at> example\.com
* ^from:.*michael <at> smmexevent\.com
{
   :0 c
   | $SENDMAIL -oi -f devnull <at> clifford.ac 
michael <at> smmexevent.com,michael=smmexevent.com <at> mail15.atl161.mcsv.net,postmaster <at> smmexevent.com,domain-admin <at> donhost.co.uk

(Continue reading)

Zhiliang Hu | 20 Feb 15:46 2015

help with a recipe

I have a recipe to sack all maildaemon mails to a file:

  :0 H
  * ^FROM_DAEMON|^FROM_MAILER|^From:.*(MAILER-DAEMON|spam_master|postmaster|ait-admin|Mail 
Delivery|bounce <at> )|^To:.*-request
  * ^Subject:.*(Error Condition|DELIVERY FAILURE|Delivery Status Notification|Delivery
delayed|Returned mail|Undeliverable|failure 
notice|Warning: could not send message)
  Mailerror

(Note /* ^FROM_DAEMON/ and /* ^Subject/ lines may be wrapped in this mail; 
the 4th line is "Mailerror".)

However it misses mail bounces like:

  From: postmaster <at> xxx.xxxxxxx.xx
  To: xxxxxxx-request <at> xxxxxxxxxx.xxx
  Subject: Undeliverable: xxxxxxxxxx

I could not find but does my construct have a problem?

Zhiliang
Julianony M | 31 Jan 22:13 2015
Picon

procmailrc to match body

I wrote a set of procmailrc recipes to "quarantine" certain category of
incoming mails to my site. It works with 3 simple steps: when a mail meets
certain criteria, it triggers a "quarantine" process by (1) holding the mail while send a confirmation mail to the sender; (2) when the confirmation mail is replied by the sender, the mail gets delivered normally; (3) when the confirmation mail is bounced, the mail is trashed.

So far everything worked well.

Lately I noticed a minor problem with my recipes to recognize certain bounced mails (a small proportion of all bounced).

My recipe to catch bounces is like:

:0
* ^FROM_DAEMON|^FROM_MAILER
* ^To:.*(mailmaster <at> xxxxxx.xxx)
{
   :0 B
   * ^.*Verify the mail you sent: \/[0-9a-zA-Z\.]+
   {
     MATCHED="$MATCH"

     :0 fw
     | cat "$MAILDIR/QUARRENTEEN/$MATCHED" >> $SPAM;

     :0 a
     | echo 'bounced, go to spam' > "$MAILDIR/QUARRENTEEN/$MATCHED"
   }

   :0 e
   /var/mail/Mail-error
}

which works well for most except one type of bounces from certain mail daemon, with multi-parts:

----------start quote---------------------
From: Mail Delivery Subsystem <MAILER-DAEMON <at> xxxxxx.xxx>
Subject: Returned mail: see transcript for details

(omitted)

   [ Part 2: "Delivery Status" ]

(omitted)

   [ Part 3: "Included Message" ]

 Date: Wed, 28 Jan 2015 14:05:32 -0600
 From: mailmaster <at> xxxxxxxx.xxx
 To: xxxxxxxxxxxxx <at> xxxxxxxxxxxxxxx.us
 Subject: Verify the mail you sent: 20150128.140532KAMGTNXTV

 This mail hub is withholding a mail just received from you:
  - sent to <xxxxxxxx <at> xxxxxxxxxx.xxx>
  - with the Subject: "Find lost or stolen items from your iPhone."
 
 This is to verify that the mail from your mailbox is not a spam.
 Please confirm by replying this mail (no need to write anything;
 only be sure to include this mail in the reply, and leave the Subject
 line and mail body as they are):
 
   Verify the mail you sent: 20150128.140532KAMGTNXTV
 
 Your mail will be automatically delivered when the system receives
 this confirmation from you.
 
 Thank you.
----------------end quote-----------------------

which fell into "Mail-error". It appears the body match failed. Any advice how the recipe should be modified in order to catch this?

Thanks, joe

____________________________________________________________
procmail mailing list   Procmail homepage: http://www.procmail.org/
procmail <at> lists.RWTH-Aachen.de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail
Richard Z | 3 Jan 17:10 2015

procmail local delivery and aliases expansion

Hi,

I am using esmtp which in turn uses "procmail -d %T" for local
mail delivery - and would prefer to avoid installing any of the
big sendmail-like packages.

Problem is, procmail does not expand aliases when used like this 
so mail from daemons to root etc ends up in the wrong places.

Coding the alias expansion myself should not be too difficult but
perhaps it has been done before?

Richard

---
Name and OpenPGP keys available from pgp key servers
Danny | 4 Dec 12:35 2014
Picon

Mail forward question

Hi Guys,

I have a working procmail setup that has been running for some time. When I
first did the configuration I had some mail being forwarded to another user on
the same system (Debian Weezy). However, now and then I would do some
maintenance. I noticed that the mail never got forwarded to user "shotgun".

Here is the recipe:

:0:
* ^(From|Cc|To|X-Loop|Sender|Bcc|X-BeenThere):.*newsletter <at> list\.rockauto\.com
#* ^TO_admin <at> iaftercare\.com
! shotgun <at> fever.havannah.local
$MAILDIR/incoming/offroading/rockauto

As you can see the mail is supposed to be placed in the folder "rockauto" which
is done, but it is not being forwarded to the user
"shotgun <at> fever.havannah.local" ...

Any particular reason why?

I am running Debian Weezy (or is it Wheezy?) ... Postfix 2.something ... fetchmail
something.something ... 

Thank You

Danny
Zhiliang Hu | 2 Dec 15:56 2014

help with a procmailrc recipe

To fight against increasingly aggressive spam mails, besides spam-assassin and 
a couple dozen filters I use to trash sure-spams, there still remain some mixed 
mails where I have to manually fish out good from bad or bad from good mails.

For this "small" portion of mails, I wrote a recipe to send automated inquery 
mails to verify if a suspecious mail is from a human-being: if it gets a human 
reply to confirm, the saved mail gets further delivered; if the inquery mail 
gets bounced, the saved mail gets deleted.  So far everything works fine except 
this last recipe to process bounce/delete:

:0
* ^FROM_DAEMON|^FROM_MAILER
{
    :0 w:bb.lock
    * B ?? Subject: verify mail you sent: ([0-9\.]{15}[A-Z]{9})
    THEMATCH = $MATCH

      :0 a
      | rm -f /var/mail/QUARRENTEEN/$THEMATCH

    :0 E:
    Mailerrors
}

The problem is that the saved file name is not caught by regular expression 
match. My auto-inquery mail "Subject:" line is like:

  Subject: verify mail you sent: 20141127.120132MUUNJUEDC

(Note this line is placed in the mail body in a bounce). I suspect if my regex 
is "perl" like and not supported by procmail or else?

Thanks in advance,

Zhiliang
Zhiliang Hu | 29 Nov 07:19 2014

help with a procmailrc recipe

To fight against increasingly aggressive spam mails, besides 
spam-assassin and a couple dozen filters I use to trash sure-spams, there 
still remain some mixed mails where I have to manually fish out good from 
bad or bad from good mails.

For this "small" portion of mails, I wrote a recipe to send automated 
inquery mails to verify if a suspecious mail is from a human-being: if it 
gets a human reply to confirm, the saved mail gets further delivered; if 
the inquery mail gets bounced, the saved mail gets deleted.  So far 
everything works fine except this last recipe to process bounce/delete:

:0
* ^FROM_DAEMON|^FROM_MAILER
{
    :0 w:bb.lock
    * B ?? Subject: verify mail you sent: ([0-9\.]{15}[A-Z]{9})
    THEMATCH = $MATCH

      :0 a
      | rm -f /var/mail/QUARRENTEEN/$THEMATCH

    :0 E:
    Mailerrors
}

The problem is that the saved file name is not caught by regular 
expression match. My auto-inquery mail "Subject:" line is like:

  Subject: verify mail you sent: 20141127.120132MUUNJUEDC

(Note this line is placed in the mail body in a bounce). I suspect if my 
regex is "perl" like and not supported by procmail or else?

Thanks in advance,

Zhiliang

Gmane