headers
W. Andrew Loe III | 1 Nov 2004 03:55
Favicon

Web-Based Front End

Does anyone have suggestions for other good web based front ends? I have
only experimented with ProcBuilder
(http://www.uvm.edu/opensource/?Page=procbuilder.html). ProcBuilder
doesn't do exactly what I want though.
Permalink | Reply | 1 comment |
headers
Stephen Kühn | 1 Nov 2004 04:27
Picon

Re: Web-Based Front End

On Mon, 2004-11-01 at 13:55, W. Andrew Loe III wrote:
> Does anyone have suggestions for other good web based front ends? I have
> only experimented with ProcBuilder
> (http://www.uvm.edu/opensource/?Page=procbuilder.html). ProcBuilder
> doesn't do exactly what I want though.

Webmin.

http://www.webmin.com

--
stephen kuhn
mobile: 0410-728-389
illawarra and regional new south wales
-----------------------------------------------
GNU/Linux/OpenSource Solutions and Alternatives
100% Microsoft Free and no viruses
Registered Linux User # 267497

Windows: Where do you want to go today?
MacOS: Where do you want to be tomorrow?
Linux: Are you coming or what?

-----------------------------------------------
"`Credit?' he said. `Aaaargggh...' These two words are usually coupled
together in the Old Pink Dog Bar." -- Ford in a spot of bother.
Permalink | Reply | 0 comments |
headers
Robert & Sabine von Knobloch | 1 Nov 2004 15:06
Picon
Favicon

WG: Upgrading from mbox to maildir

Thanks for the tip Jeff, it works fine now.
I put "DROPRIVS=yes" in /etc/procmailrc.

Robert von knobloch

-----Ursprungliche Nachricht-----
Von: procmail-bounces <at> lists.RWTH-Aachen.DE
[mailto:procmail-bounces <at> lists.RWTH-Aachen.DE]Im Auftrag von Jeffrey
Cunningham
Gesendet: Sonntag, 31. Oktober 2004 19:49
An: procmail <at> lists.RWTH-Aachen.DE
Betreff: Re: Upgrading from mbox to maildir

> From: von.knobloch <at> t-online.de (Robert & Sabine von Knobloch)
> Subject: Upgrading from mbox to maildir
> To: "Procmail (E-Mail)" <procmail <at> lists.rwth-aachen.de>
> Message-ID: <001201c4bf2a$a6f59320$0100a8c0 <at> praxis.vk>
> Content-Type: text/plain; charset=iso-8859-1
>
> Dear Procmailers,
>
> I have changed my system (who said never change a running system ??)to
> use Maildir, rather than mbox (which has worked well for quite a
> while). After much seeking for procmail syntax to match the new
> directory structure (there are many different answers on the web), I
> have it almost working. My remaining problem (and I can't see how it
> can occur) is that the incoming mails are being delivered correctly to
> the right directories, but with the wrong username.
> I have an account called 'postbote' that gets all mails and should
> then put them in the directory structure (this is how it was with
(Continue reading)

Permalink | Reply | 0 comments |
headers
Poohba | 1 Nov 2004 16:03
Picon

Blacklist via mail folder

I heard of this but I can't seem to find the email that tells how to do
this.  I want to put emails in a mail folder (file) and use that to
check for unwanted address.
Permalink | Reply | 5 comments |
headers
Michelle Konzack | 1 Nov 2004 18:31
Picon
Favicon

Re: Blacklist via mail folder

Am 2004-11-01 10:03:52, schrieb Poohba:
> I heard of this but I can't seem to find the email that tells how to do
> this.  I want to put emails in a mail folder (file) and use that to
> check for unwanted address.

You can check ma Blacklist-Filter at:

<http://devel.debian.tamay-dogan.homelinux.net/bash/usr/bin/tdmail-bl>

Add it to your

  ____( '/home/michelle/.procmailrc' )__________________________________
 /
| :0 fw
| | /usr/bin//tdmail-bl blacklist 
| 
| :0
| * ^Subject:.*(*****BLACKLIST*****)
| Blacklist/
 \______________________________________________________________________

This will use the blacklist

$HOME/.procmail/LIST_blacklist
                     ^^^^^^^^^
        first parameter of 'tdmail-bl'

But you can add a second parameter like 

  ____( '/home/michelle/.procmailrc' )__________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dallman Ross | 1 Nov 2004 18:54

Re: Blacklist via mail folder

On Mon, Nov 01, 2004 at 10:03:52AM -0500, Poohba wrote:
> I heard of this but I can't seem to find the email that tells how to do
> this.  I want to put emails in a mail folder (file) and use that to
> check for unwanted address.

You need to be a little more specific about what addresses you want
to grab from there.  Sender?  Putative From:?  Bogus addresses in
the To: or Cc: lines?  Or do you mean you want to grep all that cruft
for the sender addresses in newcoming mail?  That seems to me bound to
lead to false positives.  E.g., if your friend Moe writes you but he
was Cc'd on spam, then he'd be blocked.

So I assume you mean the senders' addresses, essentially the Envelope-From
addresses that would appear in the initial From_ line.  So why would
you want to save ll the rest of the headers and bodies of these emails?
It seems like a screwy approach to me.

Nevertheless, coding it is easy enough.  Fore example, looking at
my recent cache of last-100 spams, I grep the From_ lines for the
string "cole" (chosen kind of at random) like so:

 formail -IReply-To: -fzrx To: -s < myspam | grep cole

Here's what I got:

  6:53pm [~/Mail] 363[1]> formail -IReply-To: -fzrx To: -s < myspam | grep -i cole
 colemanmcPhersonwz <at> msn.com
 nicole_hargrove_tp <at> abm.uu.se
 coleen.bowers_ln <at> 0.1.5.2.8.6.9.5.1.4.1.tpc.int
(Continue reading)

Permalink | Reply | 3 comments |
headers
Poohba | 1 Nov 2004 23:45
Picon

Re: Blacklist via mail folder

The address I want is the sender and from I guess.  Which is suggested
to go by?

On Mon, 2004-11-01 at 12:54, Dallman Ross wrote:
> On Mon, Nov 01, 2004 at 10:03:52AM -0500, Poohba wrote:
> > I heard of this but I can't seem to find the email that tells how to do
> > this.  I want to put emails in a mail folder (file) and use that to
> > check for unwanted address.
> 
> You need to be a little more specific about what addresses you want
> to grab from there.  Sender?  Putative From:?  Bogus addresses in
> the To: or Cc: lines?  Or do you mean you want to grep all that cruft
> for the sender addresses in newcoming mail?  That seems to me bound to
> lead to false positives.  E.g., if your friend Moe writes you but he
> was Cc'd on spam, then he'd be blocked.
> 
> So I assume you mean the senders' addresses, essentially the Envelope-From
> addresses that would appear in the initial From_ line.  So why would
> you want to save ll the rest of the headers and bodies of these emails?
> It seems like a screwy approach to me.
> 
> Nevertheless, coding it is easy enough.  Fore example, looking at
> my recent cache of last-100 spams, I grep the From_ lines for the
> string "cole" (chosen kind of at random) like so:
> 
>  formail -IReply-To: -fzrx To: -s < myspam | grep cole
> 
> Here's what I got:
> 
>   6:53pm [~/Mail] 363[1]> formail -IReply-To: -fzrx To: -s < myspam | grep -i cole
(Continue reading)

Permalink | Reply | 2 comments |
headers
Sean | 2 Nov 2004 01:30
Picon

Multple actions per recipe (eg. bounce AND deliver locally).

I'm having a difficult time getting procmail to both deliver a message and
send a bounce back (autoresponder).

So far my only solution is to deliver everything local in .forward and
send to procmail.
eg:
	#cat .forward
	"|IFS=' '&& exec /usr/bin/procmail -f-||exit 75 #autoreply"
	\autoreply

This is not optimal.

I've setup a new .procmailrc with the following:
#cat .procmailrc
LOGFILE="$HOME/procmail.log"
LOGABSTRACT=all
VERBOSE=on
:0
* $ ?/usr/bin/test -e $HOME/autoreply.txt
{
        :0
        * $ !^From:.*$LOGNAME <at> domain\.com
        * $ !^X-Loop: $LOGNAME <at> $HOST
        * $ !^FROM_DAEMON
        * $ !^FROM_MAILER
        | ( formail -r -A"X-Loop: $LOGNAME <at> $HOST"; cat
"$HOME/autoreply.txt" ) | /usr/lib/sendmail -t -oi
	Maildir/
}
(Continue reading)

Permalink | Reply | 1 comment |
headers
Justin Gombos | 2 Nov 2004 02:40
Picon
Favicon

Re: Multple actions per recipe (eg. bounce AND deliver locally).

* Sean <null <at> tinfoilhat.ca> [2004-11-01 20:34]:
>
> I'm having a difficult time getting procmail to both deliver a
> message and send a bounce back (autoresponder).
> [...]
> :0

You need a flag here, telling procmail to continue processing.  Off
the top of my head, I believe this is the 'c' flag, which would make
your first line:

  :0c

I have a recipe that autoresponds to those who send me Word docs via
email attachment, telling them it's inappropriate and refers them to
Richard Stallman's web page that discusses it; then my script proceeds
to deliver the message to me as normal.  Let me know if you want me to
post it.  I also have a script that does the same for winmail.dat
attachments - available on request.  These scripts are similar to what
you're looking for.
Permalink | Reply | 0 comments |
headers
Professional Software Engineering | 2 Nov 2004 03:38

Re: Multple actions per recipe (eg. bounce AND deliver locally).

At 18:30 2004-11-01 -0600, Sean wrote:
>I'm having a difficult time getting procmail to both deliver a message and
>send a bounce back (autoresponder).
>
>So far my only solution is to deliver everything local in .forward and
>send to procmail.
>eg:
>         #cat .forward
>         "|IFS=' '&& exec /usr/bin/procmail -f-||exit 75 #autoreply"
>         \autoreply
>
>This is not optimal.

I don't know if you normally have to use the .forward or not (if procmail 
isn't set up as the LDA on your host, then you're stuck with invoking it 
that way), but you should revert back to whatever you needed to just invoke 
procmail.

>I've setup a new .procmailrc with the following:
>#cat .procmailrc
>LOGFILE="$HOME/procmail.log"
>LOGABSTRACT=all
>VERBOSE=on
>:0

The 'c'opy flag is notably absent (and only needs to be on the first recipe 
here - if you put it on the second one, then you'd have an EXTRA copy in 
your system mailbox as well).  Thus, the recipe operates on the ONE copy of 
the message, and when it's been piped to formail, it is considered to be 
delivered.
(Continue reading)

Permalink | Reply | 4 comments |

Gmane