Re: Procmail Decoding Mime Messages
Polytropon free...@edvax.de writes: On Wed, 24 Apr 2013 16:07:35 -0500, Martin McCormick wrote: Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? [...] Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? I think this is possible with uudecode, in this case b64decode. See man uuencode for more information. uuencode predates MIME. Although there are MIME types defined for it, the base-system tools don't handle the MIME headers or section marking. For this purpose, a MIME-aware tool (such as ripmime, or metamail, or mmencode) will be much more useful as part of an automated filtering system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Procmail Decoding Mime Messages
Forgot to cc the list. On 04/24/2013 04:47 PM, Ryan Frederick wrote: I believe mimencode is in ports as converters/mmencode. It is also included as part of mail/metamail. Ryan On 04/24/2013 04:07 PM, Martin McCormick wrote: Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? I use bogofilter to filter spam and it does a very good job after one builds a core of spammishness, but legitimate messages are often-times filled with base64 sections that look like garbage to the regular expressions that one puts in .procmailrc for sorting mail. When searching for information, I found something called mimencode which both encodes and decodes these attachments, but there is no FreeBSD port called mimencode so it occurred to me that some other application might exist which is in the ports that does basically the same thing. Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? Thank you. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Procmail Decoding Mime Messages
On Wed, 24 Apr 2013 16:07:35 -0500, Martin McCormick wrote: Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? [...] Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? I think this is possible with uudecode, in this case b64decode. See man uuencode for more information. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Procmail Decoding Mime Messages
Polytropon wrote:
On Wed, 24 Apr 2013 16:07:35 -0500, Martin McCormick wrote:
Is there a filter that one can run in procmail in which
base64 encoded data go in and text comes out so one can allow
procmailrc to do its work?
Good question, I havent tried that yet, (but should),
but I have been demiming both to help majordomo on servers, via procmail
on local (to reduce bulk on my future archives of personal mail).
2 tools worth knowing in /usr/ports/mail/ : demime emil
A few notes from my
http://berklix.com/~jhs/src/bsd/fixes/freebsd/ports/jhs/mail/Makefile.local
(where I've also more notes on eg much hated quoted-printable )
SUBDIR += emil
# A candidate to be assesed for stripping quoted-printable from
# majordomo on server, to help cluless people.
# Something needed to replace demime as demime has been removed.
# SUBDIR += mime4j
# It won't do any decoding of base64 or quoted-printable
#encoded header fields and bodies.
SUBDIR += demime
# For majordomo on list servers,
# For all the many lazy incompetents who cant turn off sending
# HTML to mail lists, despite having had a decade to learn.
# ( for a few people who do understand they should, have tried to, but
# can''t find where to turn off their HTML, if their ISP even allows.
# Missing in FreeBSD-9.1-RELEASE so see also SUBDIR += mail/emil
Is there anything which will take a raw email message
and spit out linear strings which can be processed like normal
text?
See man emil ; man demime
PS Trying to get procmail to work with a macro with a pipe defined
after + $RCVSTOREUNSEEN, was a long pain I failed so I use a
longer version below which works, appended for syntax example.
RCVSTORE=/usr/local/libexec/nmh/rcvstore
RCVSTOREUNSEEN=$RCVSTORE -nounseen
# A 2nd copy, just text, stripped of MIME enclosures is
# stored in $PRI_MAIL by $RCVSTOREUNSEEN
# The 2nd copy is stored with $RCVSTORE -nounseen so I dont have to
# click the archive copy from within exmh.
NOMIME=/usr/local/bin/demime -8 -
# Demime is not in current after 9.1-RELEASE
# To not demime instead use NOMIME=cat
# NOMIME=cat
# NOMIME=/usr/local/bin/emil
# Emil converts a .jpg MIME to a uuencoded appended without MIME
# I can not seem to achieve something like this:
# XYZ=$NOMIME | $RCVSTOREUNSEEN
{
:0 cw
| $NOMIME | $RCVSTOREUNSEEN +$PRI_MAIL/my/archive
:0 wc
| $RCVSTORE +$INBOX_PLAIN
}
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
Reply below not above, like a play script. Indent old text with .
Send plain text. No quoted-printable, HTML, base64, multipart/alternative.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Procmail Decoding Mime Messages
On Wed, 24 Apr 2013, Martin McCormick wrote: Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? I use bogofilter to filter spam and it does a very good job after one builds a core of spammishness, but legitimate messages are often-times filled with base64 sections that look like garbage to the regular expressions that one puts in .procmailrc for sorting mail. When searching for information, I found something called mimencode which both encodes and decodes these attachments, but there is no FreeBSD port called mimencode so it occurred to me that some other application might exist which is in the ports that does basically the same thing. Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? mail/maildrop has a reformime program which may be useful. maildrop itself is like a better and easier to use procmail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: procmail config help
On Wed, 17 Nov 2010 19:59:10 + (UTC), AN a...@neu.net said: A If anyone has a working procmail config file to share that would be A appreciated. When messing with procmail, start with the simplest setup that can possibly work. Your logfile has to exist, or procmail will ignore it. If you already have a working .procmailrc file, here's a safe way to add tweaks: 1. copy an existing mail message to /tmp/msg, 2. cp $HOME/.procmailrc $HOME/.procnew and DON'T touch the original, 3. run procmail -m $HOME/.procnew /tmp/msg to test. Try the .procmailrc skeleton below. The .whitelist and .blacklist files hold email addresses (one per line) that you want to pass or block, respectively. Logfiles are stored in the user's ~/mail directory. -- Karl Vogel I don't speak for the USAF or my company Why you might be the reincarnation of someone famous #11: When your boss criticizes your sales projection figures, you hack off your ear. --The Top Five List, t...@walrus.com --- # $Revision: 1.60+6 $ $Date: 2010-07-08 15:19:01-04 $ # # NAME: #$HOME/.procmailrc # # DESCRIPTION: #procmail handles local mail delivery. Use this file to: #- store your mail in a given folder, #- forward or discard mail depending on the contents, or #- run your mail through a program automatically. # Search path. PATH=/usr/local/bin:/bin:/usr/bin:$HOME/bin # Default mail folder. DEFAULT=/var/mail/andy # Current directory while procmail is executing. # All pathnames are relative to this directory. MAILDIR=$HOME/mail # File containing error messages or diagnostics. If this # file does not exist, said messages will be bounced # back to the message sender. LOGFILE=$MAILDIR/MAILLOG # If yes, keep an abstract of the From and Subject lines of # each delivered message, the folder it was delivered to, # and the size of the message. If no, skip this abstract. LOGABSTRACT=yes # If on, describe actions of procmail in detail. #VERBOSE=on # Number of seconds before procmail zaps a lockfile by force. LOCKTIMEOUT=5 # Default shell and umask value. SHELL=/bin/sh UMASK=022 # Frequently-used variables. WEEK=`/bin/date +%Yw%W` # # Rules section. # # RULE: Save a copy of all incoming headers in a file called # $HOME/mail/HEADERS.wNN # where = year # NN = the week number starting on Monday. :0 chw: $HOME/hdr.lck | /bin/cat - $HOME/mail/HEADERS.$WEEK; # # RULE: pass anything in the sender whitelist. :0: * ? formail -xFrom: -xFrom -xTo: -xReply-To: -xCc: \ | fgrep -is -f $HOME/.whitelist $DEFAULT # # RULE: kill anything in the sender blacklist. :0: * ? formail -xFrom: -xFrom -xTo: -xReply-To: -xCc: \ | fgrep -is -f $HOME/.blacklist spam-folder # # Keep everything else. :0 : $DEFAULT ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: procmail config help
On Wed, 17 Nov 2010, AN wrote:
I am trying to configure sendmail with spamassassin to move mail marked as
spam to a spam folder in the users home directory. I have the following
installed:
p5-Mail-SpamAssassin-3.3.1 A highly efficient mail filter for identifying
spam
razor-agents-2.84 A distributed, collaborative, spam detection and
filtering
spamass-milter-0.3.1_10 Sendmail Milter (mail filter) plugin for SpamAssassin
p5-Mail-DKIM-0.38 Perl5 module to process and/or create DKIM email
procmail-3.22_6 A local mail delivery agent
I would like to setup this configuration for each individual instead of
system wide. I have the following procmail file in the user home directory:
#Uncomment the following lines and use tail -f procmail.log to debug
LOGFILE=/home/andy/procmail.log
VERBOSE=yes
LOGABSTRACT=all
# Feed redirected spam to sa-learn, and also store a copy in a folder called
spam.
# This folder of false negatives could be useful if we needed to rebuild our
Bayes
# database in the future.
:0
* ^To:.*s...@example.com
{
* 256000
:0c: spamassassin.spamlock
| sa-learn --spam
:0: spamassassin.filelock
spam
}
# Send all other mail through SpamAssassin
:0fw: spamassassin.lock
* 256000
| spamassassin
:0: spamassassin.filelock2
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
#/dev/null
/home/andy/Mail/spam
Spam messages are still being delivered to the user inbox.
I tried to setup logging with the following:
LOGFILE=/home/andy/procmail.log
VERBOSE=yes
LOGABSTRACT=all
When I tried to send a test spam message nothing is written to the log file.
How can I get logging to work to try to debug the problem?
If anyone has a working procmail config file to share that would be
appreciated.
Any help debugging this would be greatly appreciated.
TIA
Do you have a shell statement in your procmailrc file? Anyway here is an example
of what we use. It is a combination of bogofilter and spamassassin. If this does
not help, make things simple, start with some of the examples in man procmailex.
SHELL=/bin/sh
# Directory for storing procmail configuration and log files
COMSAT=no
PATH=/bin:/usr/bin:/usr/local/bin/
FGREP=/usr/bin/fgrep
FROM=`formail -x From:`
MAILDIR=$HOME
PMDIR=$HOME/.procmail
LOGFILE=$PMDIR/`date +%Y%m`.log
DEFAULT=$HOME/mbox
##LOGABSTRACT=all
VERBOSE=no
SPAMDIR=spam`date +%m%y`
## whitelist
:0
* ? (echo $FROM | $FGREP -iqf $PMDIR/whitelist)
${DEFAULT}
## filter mail through bogofilter, tagging it as spam and
## updating the word lists
:0fw
| bogofilter -e -p
# if bogofilter failed, return the mail to the queue, the MTA will
# retry to deliver it later
# 75 is the value for EX_TEMPFAIL in /usr/include/sysexits.h
:0e
{ EXITCODE=75 HOST }
# if bogofilter thinks it is spam, that's enough..
:0
* ^X-Bogosity: Yes
{
LOG=bogofilter
:0
$SPAMDIR
}
# run spam assassin on it!
:0fw: spamassassin.lock
| spamassassin -L
# if spam assassin thinks it is spam but bogofilter doesn't,
# give preference to spam assassin and retrain BF
:0
* ^X-Spam-Status: Yes
* ^X-Bogosity: No
{
# Retrain bogofilter
:0c
| bogofilter -Ns
LOG=spamassassin
:0
$SPAMDIR
}
I edited this a bit to remove user specific information, so I may have
introduced an error. This file will [should??] log if you make the appropriate
changes.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: procmail regex help ... sometimes works, sometimes doesn't...
in message 471394.79697...@web111611.mail.gq1.yahoo.com, wrote George Sanders thusly... I have added a very standard, very common regex line to my .procmailrc to filter character sets I can't read: UNREADABLE='[^?]*big5|iso-2022-jp|ISO-2022-KR|euc-kr|gb2312|ks_c_5601-1987|ks_c_5601|3Deuc-kr|koi8' :0: * ^Content-Type:.*multipart * B ?? $ ^Content-Type:.*^?.*charset=?($UNREADABLE) unreadable_messages I know that this works because my unreadable_messages mail file is now full of messages with headers like: From: =?GB2312?B?xMLTq9Or?= uigvru...@heki.net Subject: =?GB2312?B?MjAxMMTqyMvBptfK1LS4w9bYytPKssO0?= To: me m...@me.com Content-Type: text/html; charset=gb2312 However, a lot of mail gets through to my inbox that matches: From: osdeiiftn...@gmail.com xjyfgz...@gmail.com Reply-To: osdeiiftn...@gmail.com xjyfgz...@gmail.com Message-ID: 533pbxxy2oc To: me m...@me.com Subject: Fw: \xb8\xf2\xad\xe8\xa5X\xa8\xd3\xbd\xe6~\xb1o\xb4\xa9\xa9f\xaa\xb1\xb5L\xaeM\xa4\xba\xaeg\xb2n\xa7o X-Mailer: inhalation Organization: Microsoft Outlook Express 6.00.2462. Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=1-104247307-2712732737=:8213 Status: RO X-Status: X-Keywords: X-UID: 63502 --1-104247307-2712732737=:8213 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: quoted-printable However, big5 is very clearly listed in my regex above, and as far as I can tell, this mail should match perfectly... I cannot see why these big5 emails are not matching my procmail regex ... is it obvious to anyone ? Is Content-Type: completely missing from the body of your first example? Do you have your examples flipped? I would have thought that first example would have delivered in your inbox second one in your unreadable_messages one. In any case, what does the procmail log say? See also http://www.professional.org/procmail/sandbox.html#. Do try your luck on procm...@lists.rwth-aachen.de list, http://mailman.rwth-aachen.de/mailman/listinfo/procmail. - parv -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: procmail regex help ... sometimes works, sometimes doesn't...
On 3/29/2010 3:27 AM, p...@pair.com wrote: From: osdeiiftn...@gmail.com xjyfgz...@gmail.com Reply-To: osdeiiftn...@gmail.com xjyfgz...@gmail.com Message-ID: 533pbxxy2oc To: me m...@me.com Subject: Fw: \xb8\xf2\xad\xe8\xa5X\xa8\xd3\xbd\xe6~\xb1o\xb4\xa9\xa9f\xaa\xb1\xb5L\xaeM\xa4\xba\xaeg\xb2n\xa7o X-Mailer: inhalation Organization: Microsoft Outlook Express 6.00.2462. Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=1-104247307-2712732737=:8213 Status: RO X-Status: X-Keywords: X-UID: 63502 --1-104247307-2712732737=:8213 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: quoted-printable [...] Is Content-Type: completely missing from the body of your first example? Do you have your examples flipped? I would have thought that first example would have delivered in your inbox second one in your unreadable_messages one. It's actually a single example of a multipart message; that blank line followed by the random dashes and numbers delimits a part. I'm wondering if Procmail is having trouble matching this because the offending charset is specified in a multipart content header rather than in the message headers. -- Mark Shroyer http://markshroyer.com/contact/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: procmail regex help ... sometimes works, sometimes doesn't...
On 3/28/2010 6:34 PM, George Sanders wrote: I have added a very standard, very common regex line to my .procmailrc to filter character sets I can't read: UNREADABLE='[^?]*big5|iso-2022-jp|ISO-2022-KR|euc-kr|gb2312|ks_c_5601-1987|ks_c_5601|3Deuc-kr|koi8' :0: * ^Content-Type:.*multipart * B ?? $ ^Content-Type:.*^?.*charset=?($UNREADABLE) unreadable_messages I know that this works because my unreadable_messages mail file is now full of messages with headers like: From: =?GB2312?B?xMLTq9Or?= uigvru...@heki.net Subject: =?GB2312?B?MjAxMMTqyMvBptfK1LS4w9bYytPKssO0?= To: me m...@me.com Content-Type: text/html; charset=gb2312 However, a lot of mail gets through to my inbox that matches: From: osdeiiftn...@gmail.com xjyfgz...@gmail.com Reply-To: osdeiiftn...@gmail.com xjyfgz...@gmail.com Message-ID: 533pbxxy2oc To: me m...@me.com Subject: Fw: \xb8\xf2\xad\xe8\xa5X\xa8\xd3\xbd\xe6~\xb1o\xb4\xa9\xa9f\xaa\xb1\xb5L\xaeM\xa4\xba\xaeg\xb2n\xa7o X-Mailer: inhalation Organization: Microsoft Outlook Express 6.00.2462. Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=1-104247307-2712732737=:8213 Status: RO X-Status: X-Keywords: X-UID: 63502 --1-104247307-2712732737=:8213 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: quoted-printable However, big5 is very clearly listed in my regex above, and as far as I can tell, this mail should match perfectly... I cannot see why these big5 emails are not matching my procmail regex ... is it obvious to anyone ? This is just a shot in the dark, but do you find that the unreadable messages that this rule successfully matches have the relevant Content-Type header in the message's main header group, whereas the messages that should match but fail to do so have the Content-Type header in a MIME attachment, as in your example? (Apologies for the imprecise terminology.) -- Mark Shroyer http://markshroyer.com/contact/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Procmail error
On Mon, 7 Jul 2008 22:05:04 -0700 Rem P Roberti [EMAIL PROTECTED] wrote: Probably the wrong forum for this, but since it's on a freebsd system: I have mutt installed on two other freebsd computers. I fetch pop mail via getmail, and procmail puts things where they belong. I just installed freebsd 7.0 on another computer with what I thought were the exact same settings for all of the mail programs involved. When I try to retrieve mail I get this error message: Delivery error (command procmail 3695 error (127, exec of command procmail failed (refuse to invoke external commands as root or GID 0 by default))) I'm a relative newbie here and would appreciate it if someone could give me a heads up on this. Rem Are you running getmail as root? -- Anders Trobäck http://www.troback.com/ Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming, or what? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail error
Probably the wrong forum for this, but since it's on a freebsd system: I have mutt installed on two other freebsd computers. I fetch pop mail via getmail, and procmail puts things where they belong. I just installed freebsd 7.0 on another computer with what I thought were the exact same settings for all of the mail programs involved. When I try to retrieve mail I get this error message: Delivery error (command procmail 3695 error (127, exec of command procmail failed (refuse to invoke external commands as root or GID 0 by default))) I'm a relative newbie here and would appreciate it if someone could give me a heads up on this. Rem Are you running getmail as root? Boy, I hope not. And I have this entry in my aliases file: root: rem so I'm not collecting mail as root. Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail error
On Mon, Jul 07, 2008 at 11:22:19PM -0700, Rem P Roberti wrote: Probably the wrong forum for this, but since it's on a freebsd system: I have mutt installed on two other freebsd computers. I fetch pop mail via getmail, and procmail puts things where they belong. I just installed freebsd 7.0 on another computer with what I thought were the exact same settings for all of the mail programs involved. When I try to retrieve mail I get this error message: Delivery error (command procmail 3695 error (127, exec of command procmail failed (refuse to invoke external commands as root or GID 0 by default))) I'm a relative newbie here and would appreciate it if someone could give me a heads up on this. Rem Are you running getmail as root? Boy, I hope not. And I have this entry in my aliases file: root: rem so I'm not collecting mail as root. What does your getmailrc look like? I've got this section in there. You should have similar: [destination] type = MDA_external path = /usr/local/bin/procmail user = frank -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail error
On 2008.07.08 16:46:18 +, Frank Shute wrote: On Mon, Jul 07, 2008 at 11:22:19PM -0700, Rem P Roberti wrote: Probably the wrong forum for this, but since it's on a freebsd system: I have mutt installed on two other freebsd computers. I fetch pop mail via getmail, and procmail puts things where they belong. I just installed freebsd 7.0 on another computer with what I thought were the exact same settings for all of the mail programs involved. When I try to retrieve mail I get this error message: Delivery error (command procmail 3695 error (127, exec of command procmail failed (refuse to invoke external commands as root or GID 0 by default))) I'm a relative newbie here and would appreciate it if someone could give me a heads up on this. Rem Are you running getmail as root? Boy, I hope not. And I have this entry in my aliases file: root: rem so I'm not collecting mail as root. What does your getmailrc look like? I've got this section in there. You should have similar: [destination] type = MDA_external path = /usr/local/bin/procmail user = frank Here is the entry I use: [destination] type = MDA_external path = /usr/local/bin/procmail unixfrom = True This getmailrc file is the same one that I use on two other computers with not problems. Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail error
On Tue, Jul 08, 2008 at 08:52:33AM -0700, Rem P Roberti wrote: On 2008.07.08 16:46:18 +, Frank Shute wrote: On Mon, Jul 07, 2008 at 11:22:19PM -0700, Rem P Roberti wrote: Probably the wrong forum for this, but since it's on a freebsd system: I have mutt installed on two other freebsd computers. I fetch pop mail via getmail, and procmail puts things where they belong. I just installed freebsd 7.0 on another computer with what I thought were the exact same settings for all of the mail programs involved. When I try to retrieve mail I get this error message: Delivery error (command procmail 3695 error (127, exec of command procmail failed (refuse to invoke external commands as root or GID 0 by default))) I'm a relative newbie here and would appreciate it if someone could give me a heads up on this. Rem Are you running getmail as root? Boy, I hope not. And I have this entry in my aliases file: root: rem so I'm not collecting mail as root. What does your getmailrc look like? I've got this section in there. You should have similar: [destination] type = MDA_external path = /usr/local/bin/procmail user = frank Here is the entry I use: [destination] type = MDA_external path = /usr/local/bin/procmail unixfrom = True This getmailrc file is the same one that I use on two other computers with not problems. The problem is that you're invoking getmail as root on this machine and not the others. http://pyropus.ca/software/getmail/troubleshooting.html#error-messages -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail error
What does your getmailrc look like? I've got this section in there. You should have similar: [destination] type = MDA_external path = /usr/local/bin/procmail user = frank Here is the entry I use: [destination] type = MDA_external path = /usr/local/bin/procmail unixfrom = True This getmailrc file is the same one that I use on two other computers with not problems. Problem solved. I added allow_root_commands = True to the [destination] entries in the getmailrc and that fixed it. Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail/processing question
Jack Barnett wrote: Procmail is working, but during a system upgrade I basically broke it for a bit. While it was down, all the mail was being collected in /var/mail/[username] Normally, it processes incoming mail and puts it in /home/[username]/Maildir/XYZ (this is what courier imap is using). It is working and processing mail as normal; but the problem is that /var/mail/[username] has collected tons of mail that needs to be processed via procmail. Is there a way I can pipe all this mail into procmail so that it'll be processed like normal. I'm thinking something like cat /var/mail/[username] | procmail -SomeFancyOption thoughts? disregard, I figured it out. there is a program called 'formail' (format mail) cat /var/mail/[username] | formail -s procmail :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail filter for them all?
Jack Barnett wrote: I have sendmail using procmail as the local deliver and each user has this in their .procmailrc file: LOGFILE=/u1/logs/$USER.procmail.log :0 $HOME/Maildir/ Is there a way to do that globally for all users so that they don't each need their own .procmailrc file? /usr/local/etc/procmailrc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail and sendmail
On 2006-04-28 17:50, Efren Bravo [EMAIL PROTECTED] wrote: Hi, To store the users' mails on the server each one into separate file I've installed procmail v3.22 from ports and unpacked it to add / to MAILSPOOLSUFFIX var inside /src/authenticate.c file and I rebuilt and installed it again. #ifndef MAILSPOOLSUFFIX #define MAILSPOOLSUFFIX / /* suffix to force maildir or MH style */ #endif but it doesn't work. What I missing? Some suggestion? Is your Sendmail setup configured to use procmail for local email delivery? If not, you need to do that, and add your local system-wide procmail options or filters to `/usr/local/etc/procmailrc'. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail and sendmail
--- Giorgos Keramidas [EMAIL PROTECTED] escribió: On 2006-04-28 17:50, Efren Bravo [EMAIL PROTECTED] wrote: Hi, To store the users' mails on the server each one into separate file I've installed procmail v3.22 from ports and unpacked it to add / to MAILSPOOLSUFFIX var inside /src/authenticate.c file and I rebuilt and installed it again. #ifndef MAILSPOOLSUFFIX #define MAILSPOOLSUFFIX / /* suffix to force maildir or MH style */ #endif but it doesn't work. What I missing? Some suggestion? Is your Sendmail setup configured to use procmail for local email delivery? Yes, I've added these lines to mc file and I rebuilt sendmail.cf file and restarted sendmail. FEATURE(local_procmail) MAILER(procmail) If not, you need to do that, and add your local system-wide procmail options or filters to `/usr/local/etc/procmailrc'. After installed the procmail, where can I find the procmailrc file because it's not into /usr/local/etc/ path ? __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail and sendmail
On 2006-04-28 19:22, Efren Bravo [EMAIL PROTECTED] wrote:
Giorgos Keramidas wrote:
If not, you need to do that, and add your local system-wide procmail
options or filters to `/usr/local/etc/procmailrc'.
After installed the procmail, where can I find the procmailrc file
because it's not into /usr/local/etc/ path ?
Nowhere, you create one yourself. Very very carefully, because these
rules will be applied to *all* incoming local email.
The manpage of procmail(1) explains where Procmail will look for
filtering rules:
If no rcfiles and no -p have been specified on the command line,
procmail will, prior to reading $HOME/.procmailrc, interpret
commands from /usr/local/etc/procmailrc (if present). Care must be
taken when creating /usr/local/etc/procmailrc, because, if
circumstances permit, it will be executed with root privileges
(contrary to the $HOME/.procmailrc file of course).
For example, in your system-wide `procmailrc' file you can use rules
like the following:
MAILDIR=$HOME/Mail
DEFAULT=$HOME/Mailbox
LOGABSTRACT=no
LOGFILE=$HOME/procmail.log
:0 H
* ^X-Spam-Flag: YES
spam/.
:0 H
* ^Subject: {Spam not delivered}
spam/.
:0 H
* ^Subject: {Possible Spam}
spam/.
The /. suffix of the folder names means they are MH-style mail
folders. You can also use a plain / suffix for Maildir folders,
or no suffix at all for plain Unix mbox-style files.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail/formail syntax question
On Sun, Oct 23, 2005 at 03:09:51PM -0400, stan wrote: I'm trying to get procmail to rewrite the TO: header. I've tried something like: TO=`formail -xTo:` I think this command is expanded only once, and gives an empty string because you didn't give formail any input. # is moved to viruses. :0: * ^X-Virus-Status: Yes | formail -I To: is_virus, $TO snip But this does not seem to be working. What am I doing wrong? Why don't you put it in an appropriate mailbox directly? E.g: :0: * ^X-Virus-Status: Yes /home/username/Mail/virus :0: * ^X-Spam-Status: Yes /home/username/Mail/probably_spam Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpk5BDfQAFVK.pgp Description: PGP signature
Re: procmail/formail syntax question
On Sun, Oct 23, 2005 at 10:07:17PM +0200, Roland Smith wrote: On Sun, Oct 23, 2005 at 03:09:51PM -0400, stan wrote: I'm trying to get procmail to rewrite the TO: header. I've tried something like: TO=`formail -xTo:` I think this command is expanded only once, and gives an empty string because you didn't give formail any input. # is moved to viruses. :0: * ^X-Virus-Status: Yes | formail -I To: is_virus, $TO snip But this does not seem to be working. What am I doing wrong? Why don't you put it in an appropriate mailbox directly? E.g: :0: * ^X-Virus-Status: Yes /home/username/Mail/virus :0: * ^X-Spam-Status: Yes /home/username/Mail/probably_spam That is _exactly_ wht _I_ do. However this is for a friend who recieves mail on this machine, then uses IMAP to fecth it to a Windoze box where he reads it with Outlook. He aparently does not now how to filter within Outlook on anything but the subject. So, I need to be able to rewrite the subject. Yes it's dumb but -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail/formail syntax question
On 2005-10-23 17:49, stan [EMAIL PROTECTED] wrote: On Sun, Oct 23, 2005 at 10:07:17PM +0200, Roland Smith wrote: On Sun, Oct 23, 2005 at 03:09:51PM -0400, stan wrote: I'm trying to get procmail to rewrite the TO: header. I've tried something like: TO=`formail -xTo:` I think this command is expanded only once, and gives an empty string because you didn't give formail any input. # is moved to viruses. :0: * ^X-Virus-Status: Yes | formail -I To: is_virus, $TO snip But this does not seem to be working. What am I doing wrong? Why don't you put it in an appropriate mailbox directly? E.g: :0: * ^X-Virus-Status: Yes /home/username/Mail/virus :0: * ^X-Spam-Status: Yes /home/username/Mail/probably_spam That is _exactly_ wht _I_ do. However this is for a friend who recieves mail on this machine, then uses IMAP to fecth it to a Windoze box where he reads it with Outlook. He aparently does not now how to filter within Outlook on anything but the subject. So, I need to be able to rewrite the subject. Yes it's dumb but ``Much confusion in you I sense, young Jedi.'' If you want to rewrite the *SUBJECT* of the messages, then why are you trying to rewrite the *RECIPIENT* header? Having said that, I think that what you're missing is the 'f' option in the rule that pipes mail to formail and that you don't really need formail for something as simple: :0 Hf * X-Virus-Status: Yes | sed -e 's/^[sS]ubject:[[:space:]]\+/Subject: [virus] ' ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail/formail syntax question
On Mon, Oct 24, 2005 at 01:13:18AM +0300, Giorgos Keramidas wrote: On 2005-10-23 17:49, stan [EMAIL PROTECTED] wrote: On Sun, Oct 23, 2005 at 10:07:17PM +0200, Roland Smith wrote: On Sun, Oct 23, 2005 at 03:09:51PM -0400, stan wrote: I'm trying to get procmail to rewrite the TO: header. I've tried something like: TO=`formail -xTo:` I think this command is expanded only once, and gives an empty string because you didn't give formail any input. # is moved to viruses. :0: * ^X-Virus-Status: Yes | formail -I To: is_virus, $TO snip But this does not seem to be working. What am I doing wrong? Why don't you put it in an appropriate mailbox directly? E.g: :0: * ^X-Virus-Status: Yes /home/username/Mail/virus :0: * ^X-Spam-Status: Yes /home/username/Mail/probably_spam That is _exactly_ wht _I_ do. However this is for a friend who recieves mail on this machine, then uses IMAP to fecth it to a Windoze box where he reads it with Outlook. He aparently does not now how to filter within Outlook on anything but the subject. So, I need to be able to rewrite the subject. Yes it's dumb but ``Much confusion in you I sense, young Jedi.'' If you want to rewrite the *SUBJECT* of the messages, then why are you trying to rewrite the *RECIPIENT* header? Having said that, I think that what you're missing is the 'f' option in the rule that pipes mail to formail and that you don't really need formail for something as simple: :0 Hf * X-Virus-Status: Yes | sed -e 's/^[sS]ubject:[[:space:]]\+/Subject: [virus] ' Yes, Oh freat master, I sense a great confusion :-) It's the To: header he wants rewriten. I'll try your magic spell with To: -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail/formail syntax question
Please do *not* remove the mailing list from the Cc: header, unless there is a very good reason (i.e. confidential information in the message text). On 2005-10-23 19:11, stan [EMAIL PROTECTED] wrote: On Mon, Oct 24, 2005 at 01:13:18AM +0300, Giorgos Keramidas wrote: On 2005-10-23 17:49, stan [EMAIL PROTECTED] wrote: On Sun, Oct 23, 2005 at 10:07:17PM +0200, Roland Smith wrote: On Sun, Oct 23, 2005 at 03:09:51PM -0400, stan wrote: I'm trying to get procmail to rewrite the TO: header. I've tried something like: TO=`formail -xTo:` :0 Hf * X-Virus-Status: Yes | sed -e 's/^[sS]ubject:[[:space:]]\+/Subject: [virus] ' Mmm, we are close here I put in: # test :0 Hf | sed -e 's/^[tT]o:[[:space:]]\+/To: [STAN] ' (Unconditional to test the action). That's plainly wrong. The To: header will contain broken crap instead of a recipient address. Just *DON'T* do that. Try to modify the Subject: instead. I'm positively sure than even the crapware from a well-known Redmond-based company can filter based on the subject of individual posts. But I got this error in the procmail logfile: sed: 1: s/^[tT]o:[[:space:]]\+/ ...: unescaped newline inside substitute pattern It may be that procmail does weird things with the regexp string or that procmail doesn't accept extended regexps (I think I remember finding out about this one a while ago). Let's see: % flame:/home/keramida$ cd /tmp/stan/ % flame:/tmp/stan$ ls -l % total 6 % -rw--- 1 keramida wheel - 4109 Oct 24 02:13 mbox % flame:/tmp/stan$ cat procmailrc % :0 Hf % | sed -e 's/^[tT]o:[[:space:]]\+/To: [STAN] ' % flame:/tmp/stan$ formail -s procmail /tmp/stan/procmailrc mbox | grep -i to: % sed: 1: s/^[tT]o:[[:space:]]\+/ ...: unescaped newline inside substitute pattern % flame:/tmp/stan$ When I avoid using the \+ trick, it works fine: % flame:/tmp/stan$ cat procmailrc % :0 Hf % | sed -e 's/^[tT][oO]:[[:space:]][[:space:]]*\([^[:space:]]\)/To: [STAN] \1/' % % :0 % /tmp/stan/newbox % flame:/tmp/stan$ formail -s procmail /tmp/stan/procmailrc mbox % flame:/tmp/stan$ ls -l % total 14 % -rw--- 1 keramida wheel - 4109 Oct 24 02:13 mbox % -rw--- 1 keramida wheel - 4116 Oct 24 02:20 newbox % -rw-rw-r-- 1 keramida wheel - 105 Oct 24 02:19 procmailrc % flame:/tmp/stan$ diff -u mbox newbox % --- mboxMon Oct 24 02:13:03 2005 % +++ newbox Mon Oct 24 02:20:05 2005 % @@ -36,7 +36,7 @@ % for [EMAIL PROTECTED]; Sun, 23 Oct 2005 19:11:03 -0400 % Date: Sun, 23 Oct 2005 19:11:03 -0400 % From: stan [EMAIL PROTECTED] % -To: Giorgos Keramidas [EMAIL PROTECTED] % +To: [STAN] Giorgos Keramidas [EMAIL PROTECTED] % Subject: Re: procmail/formail syntax question % Message-ID: [EMAIL PROTECTED] % References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] So it *does* work, using plain regexps and not extended regexps and it changes the To: header as expected (even though that's wrong, as I said above). - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail/formail syntax question
On 2005-10-23 18:56, stan [EMAIL PROTECTED] wrote: On Mon, Oct 24, 2005 at 01:13:18AM +0300, Giorgos Keramidas wrote: On 2005-10-23 17:49, stan [EMAIL PROTECTED] wrote: On Sun, Oct 23, 2005 at 10:07:17PM +0200, Roland Smith wrote: On Sun, Oct 23, 2005 at 03:09:51PM -0400, stan wrote: I'm trying to get procmail to rewrite the TO: header. I've tried something like: TO=`formail -xTo:` [...] So, I need to be able to rewrite the subject. Yes it's dumb but ``Much confusion in you I sense, young Jedi.'' If you want to rewrite the *SUBJECT* of the messages, then why are you trying to rewrite the *RECIPIENT* header? Having said that, I think that what you're missing is the 'f' option in the rule that pipes mail to formail and that you don't really need formail for something as simple: :0 Hf * X-Virus-Status: Yes | sed -e 's/^[sS]ubject:[[:space:]]\+/Subject: [virus] ' Yes, Oh freat master, I sense a great confusion :-) It's the To: header he wants rewriten. You can always hit the Windows user hard on the head with a cluebat. All the mail reading software for Windows that I've recently had to work with supports filtering by the _SUBJETC_ of the messages too :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail/formail syntax question
On Mon, Oct 24, 2005 at 02:25:30AM +0300, Giorgos Keramidas wrote: Please do *not* remove the mailing list from the Cc: header, unless there is a very good reason (i.e. confidential information in the message text). Sorry, I hit r instead of l in mutt. My apoligies. -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail/formail syntax question
On 2005-10-23 19:53, stan [EMAIL PROTECTED] wrote: On Mon, Oct 24, 2005 at 02:25:30AM +0300, Giorgos Keramidas wrote: Please do *not* remove the mailing list from the Cc: header, unless there is a very good reason (i.e. confidential information in the message text). Sorry, I hit r instead of l in mutt. My apoligies. That's ok. I usually hit 'g' (group-reply), and it's not too much trouble to Cc: the list again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail/formail syntax question
On Mon, Oct 24, 2005 at 04:28:49AM +0300, Giorgos Keramidas wrote: On 2005-10-23 19:53, stan [EMAIL PROTECTED] wrote: On Mon, Oct 24, 2005 at 02:25:30AM +0300, Giorgos Keramidas wrote: Please do *not* remove the mailing list from the Cc: header, unless there is a very good reason (i.e. confidential information in the message text). Sorry, I hit r instead of l in mutt. My apoligies. That's ok. I usually hit 'g' (group-reply), and it's not too much trouble to Cc: the list again. hits g Oh, and I learned another mutt command! Another secret mutt user surfaces :-) -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On 2005-08-26 08:34, Brian [EMAIL PROTECTED] wrote: All my recipes that used to work in 4-stable seem to fail in 5-stable. When I invoke procmail with what looks like the same files, I get unknown mailer error 1 messages in maillog. It would be nice if we could see some of these rules and the exact log messages. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
- Original Message - From: Giorgos Keramidas [EMAIL PROTECTED] To: Brian [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Friday, August 26, 2005 9:25 AM Subject: Re: procmail in v4 vs v5 On 2005-08-26 08:34, Brian [EMAIL PROTECTED] wrote: All my recipes that used to work in 4-stable seem to fail in 5-stable. When I invoke procmail with what looks like the same files, I get unknown mailer error 1 messages in maillog. It would be nice if we could see some of these rules and the exact log messages. more .forward |IFS=' ' exec /usr/local/bin/procmail -f- || exit 75 #bri more .procmailrc VERBOSE=no # For debugging uncomment this line #LOGABSTRACT=all # Tell procmail where to store your mail. This changes depending on which Unix m ail client you use. # Pine uses $HOME/mail # Mutt and Elm use $HOME/Mail MAILDIR=$HOME/mail #This directory must exist!!! # Use a seperate directory to store reciepes and logs PMDIR=$HOME/Procmail # Tell procmail where to put the log file LOGFILE=$PMDIR/log # Add recipe files here INCLUDERC=$PMDIR/spamassassin.rc #INCLUDERC=$PMDIR/nkvir-rc INCLUDERC=$PMDIR/lists.rc Procmail and mail directories both exist. Error snapshot- Aug 26 08:20:37 entwistle sm-mta[658]: j7QFKbVD000654: to=|exec /usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31237, dsn=5.3.0, stat=unknown mailer error 1 Additional googling suggests adding a local mc file to enable procmail as a delivery agent. Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On 2005-08-26 10:02, Brian [EMAIL PROTECTED] wrote: Giorgos Keramidas wrote: On 2005-08-26 08:34, Brian [EMAIL PROTECTED] wrote: All my recipes that used to work in 4-stable seem to fail in 5-stable. When I invoke procmail with what looks like the same files, I get unknown mailer error 1 messages in maillog. It would be nice if we could see some of these rules and the exact log messages. more .forward |IFS=' ' exec /usr/local/bin/procmail -f- || exit 75 #bri Try without all this fanciness: % echo '|/usr/local/bin/procmail' ~/.forward % chmod 0600 .forward Error snapshot- Aug 26 08:20:37 entwistle sm-mta[658]: j7QFKbVD000654: to=|exec /usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31237, dsn=5.3.0, stat=unknown mailer error 1 This doesn't look very right. It seems that Sendmail is trying to locate a binary called: exec /usr/local/bin/procmail Additional googling suggests adding a local mc file to enable procmail as a delivery agent. Not necessarily, but that's a different thing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On Fri, 26 Aug 2005, Giorgos Keramidas wrote: On 2005-08-26 10:02, Brian [EMAIL PROTECTED] wrote: Giorgos Keramidas wrote: On 2005-08-26 08:34, Brian [EMAIL PROTECTED] wrote: All my recipes that used to work in 4-stable seem to fail in 5-stable. When I invoke procmail with what looks like the same files, I get unknown mailer error 1 messages in maillog. It would be nice if we could see some of these rules and the exact log messages. more .forward |IFS=' ' exec /usr/local/bin/procmail -f- || exit 75 #bri Try without all this fanciness: % echo '|/usr/local/bin/procmail' ~/.forward % chmod 0600 .forward Error snapshot- Aug 26 08:20:37 entwistle sm-mta[658]: j7QFKbVD000654: to=|exec /usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31237, dsn=5.3.0, stat=unknown mailer error 1 This doesn't look very right. It seems that Sendmail is trying to locate a binary called: exec /usr/local/bin/procmail Additional googling suggests adding a local mc file to enable procmail as a delivery agent. Not necessarily, but that's a different thing. heres an error update. Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: to=|/usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31250, dsn=5.3.0, stat=unknown mailer error 1 Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: j7QIlegN001347: DSN: unknown mailer error 1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On 2005-08-26 11:50, Brian W. [EMAIL PROTECTED] wrote: Giorgos Keramidas wrote: Brian W. wrote: Error snapshot- Aug 26 08:20:37 entwistle sm-mta[658]: j7QFKbVD000654: to=|exec /usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31237, dsn=5.3.0, stat=unknown mailer error 1 This doesn't look very right. It seems that Sendmail is trying to locate a binary called: exec /usr/local/bin/procmail Additional googling suggests adding a local mc file to enable procmail as a delivery agent. Not necessarily, but that's a different thing. heres an error update. Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: to=|/usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31250, dsn=5.3.0, stat=unknown mailer error 1 Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: j7QIlegN001347: DSN: unknown mailer error 1 Hmmm, that's a bit odd. What changes does your sendmail.mc file have from the stock version? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
I have in no way modofied it, I have what mergemaster gave me. Brian On Fri, 26 Aug 2005, Giorgos Keramidas wrote: On 2005-08-26 11:50, Brian W. [EMAIL PROTECTED] wrote: Giorgos Keramidas wrote: Brian W. wrote: Error snapshot- Aug 26 08:20:37 entwistle sm-mta[658]: j7QFKbVD000654: to=|exec /usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31237, dsn=5.3.0, stat=unknown mailer error 1 This doesn't look very right. It seems that Sendmail is trying to locate a binary called: exec /usr/local/bin/procmail Additional googling suggests adding a local mc file to enable procmail as a delivery agent. Not necessarily, but that's a different thing. heres an error update. Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: to=|/usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31250, dsn=5.3.0, stat=unknown mailer error 1 Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: j7QIlegN001347: DSN: unknown mailer error 1 Hmmm, that's a bit odd. What changes does your sendmail.mc file have from the stock version? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On 2005-08-26 12:16, Brian W. [EMAIL PROTECTED] wrote: On Fri, 26 Aug 2005, Giorgos Keramidas wrote: On 2005-08-26 11:50, Brian W. [EMAIL PROTECTED] wrote: Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: to=|/usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31250, dsn=5.3.0, stat=unknown mailer error 1 Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: j7QIlegN001347: DSN: unknown mailer error 1 Hmmm, that's a bit odd. What changes does your sendmail.mc file have from the stock version? I have in no way modofied it, I have what mergemaster gave me. Right. Now, if it's not too much trouble to ask, please run the following commands and show me the output. You don't have to be root when these are run: # cd /etc/mail # diff -u sendmail.mc `hostname`.mc # cat sendmail.mc # ls -ld /usr/local/bin/procmail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On 2005-08-26 12:36, Brian W. [EMAIL PROTECTED] wrote: Right. Now, if it's not too much trouble to ask, please run the following commands and show me the output. You don't have to be root when these are run: # cd /etc/mail # diff -u sendmail.mc `hostname`.mc # cat sendmail.mc # ls -ld /usr/local/bin/procmail ok, my listing shiows different filenames. Yes, yes. Pardon the mindslip. I was sitting on a Solaris machine and forgot we call our template sendmail.mc file ``freebsd.mc''. pwd /etc/mail ls Makefilefreebsd.mc mailertable.sample README freebsd.submit.cf relay-domains access.sample freebsd.submit.mc sendmail.cf aliases helpfilesubmit.cf aliases.db local-host-namesvirtusertable.sample freebsd.cf mailer.conf I don't see a `hostname`.mc file here :-/ ls -ld /usr/local/bin/procmail -rwsr-sr-x 1 root mail 76828 Aug 1 04:22 /usr/local/bin/procmail This is a box that went right from 5.3 release to 5-stable. It seems you have no local `hostname`.mc file, so you probably lost some changes in the mergemaster run of the update. Can you check out the differences of your ``/etc/mail/freebsd.mc'' file and the one that is part of the source tree, at ``/usr/src/etc/sendmail/freebsd.mc'' ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On Fri, 26 Aug 2005, Giorgos Keramidas wrote: On 2005-08-26 12:36, Brian W. [EMAIL PROTECTED] wrote: Right. Now, if it's not too much trouble to ask, please run the following commands and show me the output. You don't have to be root when these are run: # cd /etc/mail # diff -u sendmail.mc `hostname`.mc # cat sendmail.mc # ls -ld /usr/local/bin/procmail ok, my listing shiows different filenames. Yes, yes. Pardon the mindslip. I was sitting on a Solaris machine and forgot we call our template sendmail.mc file ``freebsd.mc''. pwd /etc/mail ls Makefilefreebsd.mc mailertable.sample README freebsd.submit.cf relay-domains access.sample freebsd.submit.mc sendmail.cf aliases helpfilesubmit.cf aliases.db local-host-namesvirtusertable.sample freebsd.cf mailer.conf I don't see a `hostname`.mc file here :-/ ls -ld /usr/local/bin/procmail -rwsr-sr-x 1 root mail 76828 Aug 1 04:22 /usr/local/bin/procmail This is a box that went right from 5.3 release to 5-stable. It seems you have no local `hostname`.mc file, so you probably lost some changes in the mergemaster run of the update. Can you check out the differences of your ``/etc/mail/freebsd.mc'' file and the one that is part of the source tree, at ``/usr/src/etc/sendmail/freebsd.mc'' ? No difference sir.. diff /etc/mail/freebsd.mc /usr/src/etc/sendmail/freebsd.mc Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On Fri, 26 Aug 2005, Giorgos Keramidas wrote: On 2005-08-26 12:16, Brian W. [EMAIL PROTECTED] wrote: On Fri, 26 Aug 2005, Giorgos Keramidas wrote: On 2005-08-26 11:50, Brian W. [EMAIL PROTECTED] wrote: Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: to=|/usr/local/bin/procmail, ctladdr=[EMAIL PROTECTED] (1005/1005), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=31250, dsn=5.3.0, stat=unknown mailer error 1 Aug 26 11:47:40 entwistle sm-mta[1347]: j7QIlegN001345: j7QIlegN001347: DSN: unknown mailer error 1 Hmmm, that's a bit odd. What changes does your sendmail.mc file have from the stock version? I have in no way modofied it, I have what mergemaster gave me. Right. Now, if it's not too much trouble to ask, please run the following commands and show me the output. You don't have to be root when these are run: # cd /etc/mail # diff -u sendmail.mc `hostname`.mc # cat sendmail.mc # ls -ld /usr/local/bin/procmail ok, my listing shiows different filenames. pwd /etc/mail ls Makefilefreebsd.mc mailertable.sample README freebsd.submit.cf relay-domains access.sample freebsd.submit.mc sendmail.cf aliases helpfilesubmit.cf aliases.db local-host-namesvirtusertable.sample freebsd.cf mailer.conf ls -ld /usr/local/bin/procmail -rwsr-sr-x 1 root mail 76828 Aug 1 04:22 /usr/local/bin/procmail This is a box that went right from 5.3 release to 5-stable. brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail in v4 vs v5
On 2005-08-26 13:01, Brian W. [EMAIL PROTECTED] wrote: On Fri, 26 Aug 2005, Giorgos Keramidas wrote: On 2005-08-26 12:36, Brian W. [EMAIL PROTECTED] wrote: Right. Now, if it's not too much trouble to ask, please run the following commands and show me the output. You don't have to be root when these are run: # cd /etc/mail # diff -u sendmail.mc `hostname`.mc # cat sendmail.mc # ls -ld /usr/local/bin/procmail ok, my listing shiows different filenames. Yes, yes. Pardon the mindslip. I was sitting on a Solaris machine and forgot we call our template sendmail.mc file ``freebsd.mc''. pwd /etc/mail ls Makefilefreebsd.mc mailertable.sample README freebsd.submit.cf relay-domains access.sample freebsd.submit.mc sendmail.cf aliases helpfilesubmit.cf aliases.db local-host-namesvirtusertable.sample freebsd.cf mailer.conf I don't see a `hostname`.mc file here :-/ ls -ld /usr/local/bin/procmail -rwsr-sr-x 1 root mail 76828 Aug 1 04:22 /usr/local/bin/procmail This is a box that went right from 5.3 release to 5-stable. Nothing weird here. My procmail executable even has the same size :-) It seems you have no local `hostname`.mc file, so you probably lost some changes in the mergemaster run of the update. Can you check out the differences of your ``/etc/mail/freebsd.mc'' file and the one that is part of the source tree, at ``/usr/src/etc/sendmail/freebsd.mc'' ? No difference sir.. If we assume that you did generate your current sendmail.cf from the source version of freebsd.mc, then this looks a lot like a procmail ruleset problem. I'll take another good look at your procmail rules, but in the mean time can you try with a minimal .procmailrc and see if this unbreaks it all? $ cd $ cp .procmailrcA dot.procmailrc~ $ echo 'DEFAULT=$HOME/Mailbox' .procmailrc If that works, then we are certain that the old rules are broken. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
On 2005-07-12 19:09, Matt Juszczak [EMAIL PROTECTED] wrote: Can you run memtest on the machine? This could be caused by failing physical memory chips :-/ Memtest comes through OK. Hmmm, this could be a procmail bug then. If it's not too much trouble for you, can you rebuild a debug version of procmail and try to grab a core file from it when it crashes? On a fairly recent system, building a debugging version of procmail should be as easy as: # cd /usr/ports/mail/procmail # make clean # make DEBUG_FLAGS='-g' all deinstall install Then, when you have a core file from procmail, please send your procmail binary and the core file to me. - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
I assume that you've checked that you're running the latest version (or ports version) of procmail? Yes, I've checked. It seems to be doing it more often now too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
On 2005-07-07 11:45, Matt Juszczak [EMAIL PROTECTED] wrote: Getting flooded with: pid 65128 (procmail), uid 3005: exited on signal 11 On 2005-07-12 14:23, Matt Juszczak [EMAIL PROTECTED] wrote: I assume that you've checked that you're running the latest version (or ports version) of procmail? Yes, I've checked. It seems to be doing it more often now too. Can you run memtest on the machine? This could be caused by failing physical memory chips :-/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
Can you run memtest on the machine? This could be caused by failing physical memory chips :-/ Memtest comes through OK. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
On 2005-07-07 11:45, Matt Juszczak [EMAIL PROTECTED] wrote: Getting flooded with: pid 65128 (procmail), uid 3005: exited on signal 11 pid 65138 (procmail), uid 806: exited on signal 11 pid 65142 (procmail), uid 24112: exited on signal 11 [...] This is a high traffic mail server is this normal? Why does procmail sometimes exit on signal 11 like this? Signal 11 is a segmentation fault. This _might_ be an indication of hardware/memory problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
Signal 11 is a segmentation fault. This _might_ be an indication of hardware/memory problems. Actually all the seg faults signal 11 happened at one time (within 20 seconds), after checking messages it hasn't happened since. Could it have been a fluke? -Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
On 2005-07-07 13:20, Matt Juszczak [EMAIL PROTECTED] wrote: Signal 11 is a segmentation fault. This _might_ be an indication of hardware/memory problems. Actually all the seg faults signal 11 happened at one time (within 20 seconds), after checking messages it hasn't happened since. Could it have been a fluke? Do the segfaults only happen when you run procmail? If other programs fail randomly with segfaults, then it's more likely to be a general memory-hardware problem. If it's only procmail that fails it could be just a procmail bug. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
Do the segfaults only happen when you run procmail? If other programs fail randomly with segfaults, then it's more likely to be a general memory-hardware problem. If it's only procmail that fails it could be just a procmail bug. Procmail is the only one segfaulting with signal 11. POP3 has exiting with signal 6 a few times, but only a few, and its been sporadic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail kill problems in dmesg?
Matt Juszczak [EMAIL PROTECTED] writes: Procmail is the only one segfaulting with signal 11. POP3 has exiting with signal 6 a few times, but only a few, and its been sporadic. I assume that you've checked that you're running the latest version (or ports version) of procmail? mkb. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail keeps dieing on freebsd 5.4 with postfix
Matt Juszczak wrote: Hi all, We had a mail server running with FreeBSD 5.4, about 3,000 accounts, and postfix. Recently, I turned procmail on in postfix (mailbox_command=/usr/procmail) and the machine has been locking up weekly ever since. And when this machines crashes, it crashes hard ... and procmail is always on the screen as the error causer when it happens. Patient: Doctor, my arm hurts when I do this. Doctor: Then stop doing that. Seriously though, you need to provide some more detailed information if you want anyone here to be able to help you. Start with explaining why you decided to change MDAs in the first place since I'm sure I'm not the only one thinking you must be nuts to make such a major change on a production system with a potential 3000-user lynch mob waiting in the wings. What were you using for local delivery before this? Was there a problem with it or were you looking for new features, etc.? I know you all want messages, but I never seem to be here and my co workers reboot the box on me to fix it. Both times; however, we've had to run fsck from single user mode and also refresh the postfix queue. If you're not around to see the console messages how do you know procmail is always the error causer? Perhaps this is conveyed to you by your co-workers but if so, why don't they tell you the complete error message so you can convey it to us? Leaving that aside, however, what about the logs? Certainly /var/log/maillog should provide some clues if the problem is really your MDA (more on this below). Also we'd need to know something about your configuration (i.e. contents of main.cf and master.cf for starters) to help you with a MTA/MDA problem. Does anyone have any ideas why procmail could be causing my system to completely hard lock every other couple of days? I disabled procmail for now and I know (knock on wood) the machine should be fine like it used to be ... but all these hard locks could eventually drive the freebsd box mad, and I wouldn't want to do a reinstall. FWIW this doesn't sound like a software issue (except maybe a massive memory leak(??)) but then again, I'm saying this with very little useful information provided by you. Have you done any basic hardware checks (e.g. memtest, case and cpu cooling, power supply integrity, etc.)? You've stated that these lock-ups occur every week at the beginning of your post then you say later it's every couple of days. Which is it? Also, please try to precisely define locking up and crashes. It's unclear to me based on your description and the (possibly misleading) subject line what portions of the system are affected. Precision matters IMHO. Cheers, G ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail keeps dieing on freebsd 5.4 with postfix
Appreciate the response :) Here's my message the way it should have been originally Seriously though, you need to provide some more detailed information if you want anyone here to be able to help you. Start with explaining why you decided to change MDAs in the first place since I'm sure I'm not the only one thinking you must be nuts to make such a major change on a production system with a potential 3000-user lynch mob waiting in the wings. What were you using for local delivery before this? Was there a problem with it or were you looking for new features, etc.? We are currently moving to a new mail server that is FreeBSD-based. Our old mail server is a chrooted slackware box that hasn't been upgraded in years because no one even had access to it for a while (the management of the company I work for used to stink, its better now). Our new mail server has 3000 accounts on it, that are active, but only about 50 of them are actually functioning (one of our virtual domains). We haven't switched the MX record for our main ISP yet, we're waiting to make sure the box is stable first. So to answer your question, there is only about a 50-user lynch mob and most of those users are internal to our ISP (employees, etc.) I would not make a change on something that had more live users, especially paying customers. Our current mail server supports procmail, and we have about 50 users who use it. Therefore, thats why I was turning it on on the new server. We're working on basically mirroring the old server to the new one and making sure that our change will be swift and efficient. I've considered using postfix's internal LDA and just calling procmail from inside a .forward file for those users who need it/want it ... this might end up fixing the problems. If you're not around to see the console messages how do you know procmail is always the error causer? Perhaps this is conveyed to you by your co-workers but if so, why don't they tell you the complete error message so you can convey it to us? Leaving that aside, however, what about the logs? Certainly /var/log/maillog should provide some clues if the problem is really your MDA (more on this below). Also we'd need to know something about your configuration (i.e. contents of main.cf and master.cf for starters) to help you with a MTA/MDA problem. Its happened twice now. The first time this problem happened was late at night, about 2 days after I made the change to the LDA. The machine would not respond to ping, and nagios was alerting us like crazy that the box was down. The machine was non-responsive to the keyboard, and the console had a dump on it, about 15 lines long, with procmail written all over it. I turned procmail off after rebooting the machine, running fsck, restoring postfix to a functioning state, etc. Procmail remained disabled for about three weeks, in which the box ran fine. Yesterday afternoon we switched the LDA back to procmail, and the machine ran fine over night. On my way into work today, I got paged that the box was down from nagios and called. The tech that was here rebooted the machine, but before he did he said, in his own words There was a bunch of crap on the screen with procmail this and procmail that, and the machine was locked hard.. I've disabled procmail again and it seems to be running stable. As far as logs, nothing the maillog cuts out at 11:14 AM and cuts back in at 11:21 AM, with no errors in between. FWIW this doesn't sound like a software issue (except maybe a massive memory leak(??)) but then again, I'm saying this with very little useful information provided by you. Have you done any basic hardware checks (e.g. memtest, case and cpu cooling, power supply integrity, etc.)? Yes, the machine has been checked. We ran memtest on it, etc., with no problems. The machine is about 2 months old; however, so its passed its burn in test but could have issues, but I doubt thats the problem. You've stated that these lock-ups occur every week at the beginning of your post then you say later it's every couple of days. Which is it? Also, please try to precisely define locking up and crashes. It's unclear to me based on your description and the (possibly misleading) subject line what portions of the system are affected. Precision matters IMHO. See above. Its occured twice in a one month span but most of that time procmail was not running. It occurs usually within 24-48 hours of switching procmail back on. Thanks, hope this helps a little more! -Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail keeps dieing on freebsd 5.4 with postfix
OK, here's the funny thing. We did a mail flood test, and our mail server stood up fine, but our LDAP server (which was handling all the queries) ended up crashing with a similar message ... so now I've got two machines running 5.4 with the same behavior. Here's the message. Remember, this is on the LDAP machine, not the Postfix/Procmail machine, but the error we received earlier was similar. Kernel Trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode CPUID=1, apic ID=00 fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc6644eff stack pointer = 0x10: 0xdaa86b48 frame pointer = 0x10 :0xdae86b5c code segment: base 0x0 limit 0xf type 0x1d, can't read my handwriting here def32, 1 processes eflags = resume, IOPL=0 current process = 44091 (slapd) trap number = 12 panic page fault cpuid = 1 Hope that helps. I dont think FreeBSD should crash like this because it was getting hit hard with queries . but I could be wrong. -Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail keeps dieing on freebsd 5.4 with postfix
On Wed, 15 Jun 2005, Matt Juszczak wrote: We are currently moving to a new mail server that is FreeBSD-based. Our old mail server is a chrooted slackware box that hasn't been upgraded in years because no one even had access to it for a while (the management of the company I work for used to stink, its better now). Our new mail server has 3000 accounts on it, that are active, but only about 50 of them are actually functioning (one of our virtual domains). We haven't switched the MX record for our main ISP yet, we're waiting to make sure the box is stable first. So to answer your question, there is only about a 50-user lynch mob and most of those users are internal to our ISP (employees, etc.) I would not make a change on something that had more live users, especially paying customers. Our current mail server supports procmail, and we have about 50 users who use it. Therefore, thats why I was turning it on on the new server. We're working on basically mirroring the old server to the new one and making sure that our change will be swift and efficient. I've considered using postfix's internal LDA and just calling procmail from inside a .forward file for those users who need it/want it ... this might end up fixing the problems. Did you build procmail from ports or bare? Just asking because there are ten patch files included with the port... -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail keeps dieing on freebsd 5.4 with postfix
Ports ... I always use ports. On Wed, 15 Jun 2005, Warren Block wrote: On Wed, 15 Jun 2005, Matt Juszczak wrote: We are currently moving to a new mail server that is FreeBSD-based. Our old mail server is a chrooted slackware box that hasn't been upgraded in years because no one even had access to it for a while (the management of the company I work for used to stink, its better now). Our new mail server has 3000 accounts on it, that are active, but only about 50 of them are actually functioning (one of our virtual domains). We haven't switched the MX record for our main ISP yet, we're waiting to make sure the box is stable first. So to answer your question, there is only about a 50-user lynch mob and most of those users are internal to our ISP (employees, etc.) I would not make a change on something that had more live users, especially paying customers. Our current mail server supports procmail, and we have about 50 users who use it. Therefore, thats why I was turning it on on the new server. We're working on basically mirroring the old server to the new one and making sure that our change will be swift and efficient. I've considered using postfix's internal LDA and just calling procmail from inside a .forward file for those users who need it/want it ... this might end up fixing the problems. Did you build procmail from ports or bare? Just asking because there are ten patch files included with the port... -Warren Block * Rapid City, South Dakota USA !DSPAM:42b076c8956801608011501! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail: how to deliver email over an ssh-tunnel to my smtp server.
Rob wrote: Hello, I'm having 4.11 and 5.3 FreeBSD PCs. All incoming email arrives through fetchmail (using imap protocol). I then filter all email with procmail, which is configured such that it trashes spam, or delivers to local mailbox, or forwards to another external address. For external delivery, I have set up an ssh tunnel to my smtp server: ssh -N -f -L 2525:localhost:25 smtp.server.it What do I have to do next, to have the delivery work properly? Can I tell procmail to push the email directly onto the port 2525 of the ssh tunnel? Or do I have to reconfigure sendmail for this? (sendmail reconfiguration info looks like a nightmare to me though). Do I have other options? I'll answer my own question here, just for the record. Use msmtp, which is highly configurable, for example defining its own outgoing port. In the .procmailrc file I only need to add: :0 | /usr/local/bin/msmtp [EMAIL PROTECTED] to forward the email with msmtp, over my own ssh tunnel port. Works like a charm. Rob. __ Yahoo! Messenger Show us what our next emoticon should look like. Join the fun. http://www.advision.webevents.yahoo.com/emoticontest ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Lockfile
On Tue, 21 Dec 2004, Gardner Bell wrote: Hi, I'm trying to setup procmail to deliver my mail but I continuously receive the following errors in my log file. procmail: Locking ~/Mail/Lists/FreeBSD-Questions.lock procmail: Error while writing to ~/Mail/Lists/_YmHxxx.gardnerbell.ca I do receive my mail but it always ends up in the default location that I have specified. In my .procmailrc file I have the following environment variables: MAILDIR=$HOME/Mail DEFAULT=$HOME/Mail/received PMDIR=$HOME/.procmailrc LISTFOLDER=$HOME/Mail/Lists SENDMAIL=/usr/sbin/sendmail This is the recipe that fails to acquire a lock :0: * ^(From|To).*freebsd.org ~/Mail/Lists/FreeBSD-Questions You want the receipe to store emails in /home/you/Mail/Lists/FreeBSD-Questions? So the receipe has to be: :0: * [EMAIL PROTECTED] Lists/FreeBSD-Questions Oliver -- ... don't touch the bang bang fruit ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Lockfile
On Tuesday 21 December 2004 01:27 pm, Oliver Fuchs [EMAIL PROTECTED] wrote: On Tue, 21 Dec 2004, Gardner Bell wrote: Hi, I'm trying to setup procmail to deliver my mail but I continuously receive the following errors in my log file. procmail: Locking ~/Mail/Lists/FreeBSD-Questions.lock procmail: Error while writing to ~/Mail/Lists/_YmHxxx.gardnerbell.ca I do receive my mail but it always ends up in the default location that I have specified. In my .procmailrc file I have the following environment variables: MAILDIR=$HOME/Mail DEFAULT=$HOME/Mail/received PMDIR=$HOME/.procmailrc LISTFOLDER=$HOME/Mail/Lists SENDMAIL=/usr/sbin/sendmail This is the recipe that fails to acquire a lock :0: * ^(From|To).*freebsd.org ~/Mail/Lists/FreeBSD-Questions You want the receipe to store emails in /home/you/Mail/Lists/FreeBSD-Questions? So the receipe has to be: :0: * [EMAIL PROTECTED] Lists/FreeBSD-Questions I use: * ^List-Id:.*freebsd-questions.freebsd.org so that mail from other fbsd lists aren't mixed up in the wrong folders, and so I can separate CC responses. - jt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Lockfile
On Tue, Dec 21, 2004 at 03:56:21PM -0500, Gardner Bell wrote: Hi, I'm trying to setup procmail to deliver my mail but I continuously receive the following errors in my log file. procmail: Locking ~/Mail/Lists/FreeBSD-Questions.lock procmail: Error while writing to ~/Mail/Lists/_YmHxxx.gardnerbell.ca I do receive my mail but it always ends up in the default location that I have specified. In my .procmailrc file I have the following environment variables: MAILDIR=$HOME/Mail DEFAULT=$HOME/Mail/received PMDIR=$HOME/.procmailrc LISTFOLDER=$HOME/Mail/Lists SENDMAIL=/usr/sbin/sendmail This is the recipe that fails to acquire a lock :0: * ^(From|To).*freebsd.org ~/Mail/Lists/FreeBSD-Questions The permissions on my Mail and Lists directory are set to drwx-- Any help to resolve this is appreciated. TIA Gardner Bell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This would be a me too reply. I have similar setup as the one you have and I notice the failure of procmail acquiring lock whenever there are too many messages (more than 5k) in my freebsd-questions mail folder (mbox format). I'm also subscribed to freebsd-current, freebsd-stable and a host of other lists, but it only happens to me so far on freebsd-questions (highest volume list). The only work around is to keep the number of messages hovering below 5k or so. I suspect this is an obscure bug with procmail handling high volume mboxes. Maybe using mail folder instead of mbox will help, but I have not tried this. -- Hong ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Lockfile
On Tue, Dec 21, 2004 at 02:08:52PM -0800 Joshua Tinnin wrote: On Tuesday 21 December 2004 01:27 pm, Oliver Fuchs [EMAIL PROTECTED] wrote: On Tue, 21 Dec 2004, Gardner Bell wrote: Hi, I'm trying to setup procmail to deliver my mail but I continuously receive the following errors in my log file. procmail: Locking ~/Mail/Lists/FreeBSD-Questions.lock procmail: Error while writing to ~/Mail/Lists/_YmHxxx.gardnerbell.ca I do receive my mail but it always ends up in the default location that I have specified. In my .procmailrc file I have the following environment variables: MAILDIR=$HOME/Mail DEFAULT=$HOME/Mail/received PMDIR=$HOME/.procmailrc LISTFOLDER=$HOME/Mail/Lists SENDMAIL=/usr/sbin/sendmail This is the recipe that fails to acquire a lock :0: * ^(From|To).*freebsd.org ~/Mail/Lists/FreeBSD-Questions You want the receipe to store emails in /home/you/Mail/Lists/FreeBSD-Questions? So the receipe has to be: :0: * [EMAIL PROTECTED] Lists/FreeBSD-Questions I use: * ^List-Id:.*freebsd-questions.freebsd.org so that mail from other fbsd lists aren't mixed up in the wrong folders, and so I can separate CC responses. - jt Both recipies have worked for me, thanks for the help Gardner ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail + Sieve ?
On Tue, Jul 27, 2004 at 01:29:51PM +0200, Philipp Koock wrote: Now, exim recevies the mail, passes it to procmail via some kind of pipe and procmail uses cyrdeliver to put mails into the corredsponding cyrus imap mail folders ... now is there a way to put sieve between procmail and cyrus ? like make sieve filter all messages that procmail didn't ? removing the target mailbox from the cyrdeliver command doesn't help. How do i pass mail to cyrus so that is still applys the sieve rules ? sieve is integrated into cyrus. no need to change your procmail rules. deliver(8) will apply the corresponding sieve scripts and finally store the message in the right mailbox. sieve scripts are installed via installsieve(1). for more information see http://www.cyrusoft.com/sieve/ and please stop reposting the same question! hth, toni -- Wer es einmal so weit gebracht hat, dass er nicht | toni at stderror dot at mehr irrt, der hat auch zu arbeiten aufgehoert| Toni Schmidbauer -- Max Planck | pgpPfpnVs1sUE.pgp Description: PGP signature
Re: Procmail port 3.22 and FreeBSD 5.2.1
On Tue, Jul 27, 2004 at 11:14:38AM +1200, Jonathan Chen wrote: On Mon, Jul 26, 2004 at 07:20:24AM -0400, Paul R Culmo wrote: Greetings, [...] I've searched high and low and found some really good docs, on how to do it to get it working. Yes I've compiled and installed the port, that's not a problem. Integrating into Sendmail is the problem, but from pine if I | /usr/local/bin/procmail it will work. Has anyone had any trouble with procmail on FBSD 5.2.1 or any version of FBSD ? You need to create a ~/.forward file with the following contents: |/usr/local/bin/procmail Not if he's using 'FEATURE(local_procmail)' -- that makes procmail the default local delivery agent. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpvFhiiei2xC.pgp Description: PGP signature
Re: Procmail port 3.22 and FreeBSD 5.2.1
On Mon, Jul 26, 2004 at 07:20:24AM -0400, Paul R Culmo wrote: Greetings, [...] I've searched high and low and found some really good docs, on how to do it to get it working. Yes I've compiled and installed the port, that's not a problem. Integrating into Sendmail is the problem, but from pine if I | /usr/local/bin/procmail it will work. Has anyone had any trouble with procmail on FBSD 5.2.1 or any version of FBSD ? You need to create a ~/.forward file with the following contents: |/usr/local/bin/procmail -- Jonathan Chen [EMAIL PROTECTED] -- Opportunity does not knock, it presents itself when you beat down the door - W.E. Channing ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail port 3.22 and FreeBSD 5.2.1
On Tue, 27 Jul 2004, Jonathan Chen wrote: On Mon, Jul 26, 2004 at 07:20:24AM -0400, Paul R Culmo wrote: Greetings, [...] I've searched high and low and found some really good docs, on how to do it to get it working. Yes I've compiled and installed the port, that's not a problem. Integrating into Sendmail is the problem, but from pine if I | /usr/local/bin/procmail it will work. Has anyone had any trouble with procmail on FBSD 5.2.1 or any version of FBSD ? You need to create a ~/.forward file with the following contents: |/usr/local/bin/procmail That's not needed when sendmail uses procmail directly. My 4.10 system just has FEATURE(local_procmail) in /etc/mail/hostname.mc. -Warren Block * Rapid City, South Dakota USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail port 3.22 and FreeBSD 5.2.1
On Tue, 27 Jul 2004, Jonathan Chen wrote: You need to create a ~/.forward file with the following contents: |/usr/local/bin/procmail Thanks for the reply :) but I tried creating the .forward file with these contents and also the | exec /usr/local/bin/procmail exit 75 Which I read in a website during my searches, To no avail this did not work either,this is a weird one..for sure. However, I am loving this challenge. I do really like FreeBSD very much. It's MEGA fast. Thanks again. -- Paul R Culmo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail port 3.22 and FreeBSD 5.2.1
On Mon, Jul 26, 2004 at 09:59:31PM -0400, Paul R Culmo wrote: On Tue, 27 Jul 2004, Jonathan Chen wrote: You need to create a ~/.forward file with the following contents: |/usr/local/bin/procmail Thanks for the reply :) but I tried creating the .forward file with these contents and also the | exec /usr/local/bin/procmail exit 75 This will definitely *not* work. Why don't your try what I've given you? Include the quotes in the file as well. -- Jonathan Chen [EMAIL PROTECTED] -- Opportunity does not knock, it presents itself when you beat down the door - W.E. Channing ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail port 3.22 and FreeBSD 5.2.1
On Mon, 26 Jul 2004, Warren Block wrote: You need to create a ~/.forward file with the following contents: |/usr/local/bin/procmail That's not needed when sendmail uses procmail directly. My 4.10 system just has FEATURE(local_procmail) in /etc/mail/hostname.mc. Waren that is what I have been reading online many sites and FAQ that you don't need the .forward file but I thanked Jonathan for his input as I appreciate any input. I've tried the .forward file but wait.. this just in.. I found a few things , The kernel had IPV6 compiled in which I don't need, at the moment. Perhaps in another project I'll try that. I commented it out in my config and recompiled..installed and bounced the box. Still No worke... I found a entry in my hostname.mc that read Feature(local_lmtp) Commented out.. Performed the typical under /etc/mail make all install restart Working like a champion now.. so perhaps between the IPV6 components in the Knrl and my fixing the .mc file it's workig like it should. So for those other newbies, comment out any FEATURE(local..) other than FEATURE(local_procmail) and be sure that MAILER(procmail) comes first in the .mc file before anything else. Thanks to you and Jonathan once again for your input! :) - Paul R Culmo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail help please
On Wed, Mar 24, 2004 at 02:17:21PM +, Wayne K9DI wrote: Wayne K9DI Leader Dog Patriot here. I am writing to ask for some help. I was reading a procmail quickstart guide (by Nancy McGough) and I got to the part about the .forward file. The guide stated that most modern systems don't use .forward so my question is do I need a .forward file on system running FreeBSD 5.2? It depends on how you configure your mail system. If you use what is provided by default -- sendmail(8) as the MTA, mail.local(1) as the MDA, then running procmail(1) via a .forward file should just work. However, most people wishing to use procmail will set it up as the standard mail delivery agent -- for sendmail, all you need to do is add: FEATURE(local_procmail)dnl to your `hostname`.mc file and build and install a sendmail configuration from that. If you do that, then all of the mail delivered on your system will be processed by procmail automatically, and all you need is a ~/.procmailrc file containing your procmail recipes (procmail will just deliver to the default mailbox if there isn't a ~/.procmailrc). There are usually similar ways of making procmail the default delivery agent for other MTAs -- there's plenty of HOWTOs and other information available if you search the net. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: procmail
On Fri, 27 Feb 2004 14:56:50 -0600 Brian H [EMAIL PROTECTED] wrote: I am trying to get procmail to send email to my Maildir in my home directory, but it keeps putting it in /var/mail/henninb. I am sure I just missed a setting, can someone help point it out. here is how everything is setup currently. -- cut for brevity -- ~/.pmdir cat recipes :0: * ^FROM:.*(aol.com|spamsenders) /dev/null :0: Inbox/ cat .qmail |preline /usr/bin/procmail -t ~/.procmailrc || exit 111 cat .procmailrc VERBOSE=on MAILDIR=$HOME/Maildir/ PMDIR=$HOME/.pmdir LOGFILE=$PMDIR/log here's an example with postfix + procmail (looks like you should remove the :0: Inbox lines : $ less .forward |/usr/bin/procmail $ less .procmailrc VERBOSE=off SHELL=/bin/sh DEFAULT=$HOME/Maildir/ ORGMAIL=$HOME/Maildir/ MAILDIR=$HOME/Maildir/ PMDIR=$HOME/.procmail LOGFILE=$PMDIR/log ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: procmail
I tried removing everything in my recipes file, but that didn't work. Any more thoughts? Thanks, brian -Original Message- From: albi [mailto:[EMAIL PROTECTED] Sent: Friday, February 27, 2004 3:24 PM To: [EMAIL PROTECTED] Subject: Re: procmail On Fri, 27 Feb 2004 14:56:50 -0600 Brian H [EMAIL PROTECTED] wrote: I am trying to get procmail to send email to my Maildir in my home directory, but it keeps putting it in /var/mail/henninb. I am sure I just missed a setting, can someone help point it out. here is how everything is setup currently. -- cut for brevity -- ~/.pmdir cat recipes :0: * ^FROM:.*(aol.com|spamsenders) /dev/null :0: Inbox/ cat .qmail |preline /usr/bin/procmail -t ~/.procmailrc || exit 111 cat .procmailrc VERBOSE=on MAILDIR=$HOME/Maildir/ PMDIR=$HOME/.pmdir LOGFILE=$PMDIR/log here's an example with postfix + procmail (looks like you should remove the :0: Inbox lines : $ less .forward |/usr/bin/procmail $ less .procmailrc VERBOSE=off SHELL=/bin/sh DEFAULT=$HOME/Maildir/ ORGMAIL=$HOME/Maildir/ MAILDIR=$HOME/Maildir/ PMDIR=$HOME/.procmail LOGFILE=$PMDIR/log ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail
On Friday 27 February 2004 03:55 pm, Henning, Brian wrote: I tried removing everything in my recipes file, but that didn't work. Any more thoughts? Thanks, brian -Original Message- From: albi [mailto:[EMAIL PROTECTED] Sent: Friday, February 27, 2004 3:24 PM To: [EMAIL PROTECTED] Subject: Re: procmail On Fri, 27 Feb 2004 14:56:50 -0600 Brian H [EMAIL PROTECTED] wrote: I am trying to get procmail to send email to my Maildir in my home directory, but it keeps putting it in /var/mail/henninb. I am sure I just missed a setting, can someone help point it out. here is how everything is setup currently. -- cut for brevity -- ~/.pmdir cat recipes :0: * ^FROM:.*(aol.com|spamsenders) /dev/null :0: Inbox/ cat .qmail |preline /usr/bin/procmail -t ~/.procmailrc || exit 111 cat .procmailrc VERBOSE=on MAILDIR=$HOME/Maildir/ PMDIR=$HOME/.pmdir LOGFILE=$PMDIR/log here's an example with postfix + procmail (looks like you should remove the :0: Inbox lines : $ less .forward |/usr/bin/procmail $ less .procmailrc VERBOSE=off SHELL=/bin/sh DEFAULT=$HOME/Maildir/ ORGMAIL=$HOME/Maildir/ MAILDIR=$HOME/Maildir/ PMDIR=$HOME/.procmail LOGFILE=$PMDIR/log A couple of items: 1. In recipe examples that I've seen, there is a space between the zero and second colon in :0 :. I don't know if this matters. 2. To test the recipes, make a copy of the mailbox and run formail. (formail is installed with procmail.) cd ~ cp /var/mail/henninb ./henninb2 formail -ds procmail ./henninb2 If the recipes work, then the problem may be that procmail isn't being executed successfully. Good luck, Andrew Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: procmail
Hi Brian, --On Friday, February 27, 2004 03:55:47 PM -0600 Henning, Brian [EMAIL PROTECTED] wrote: I tried removing everything in my recipes file, but that didn't work. Any more thoughts? What is the contents of your /var/qmail/control/defaultdelivery file? Is it ./Maildiror ./Maildir/ ? Also regarding Andrew Gould's post, in part below, 1. In recipe examples that I've seen, there is a space between the zero and second colon in :0 :. I don't know if this matters. With the Maildir format, the second : is not needed in recipes, as no locking is needed, just one of the benefits of Maildir format over mbox. Mail is not stored on a spool, but as individual emails.. One other thing I just thought of... I have this at the top of my .procmailrc file... (in my home dir).. Put your paths here.. and DEFAULT=~/Maildir/ MAILDIR=$HOME/Maildir/ You also need a catchall recipe at the bottom.. :0w /home/yourname/Maildir or some such.. -- Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: procmail
Hi Brian, --On Friday, February 27, 2004 04:36:51 PM -0600 Henning, Brian [EMAIL PROTECTED] wrote: cat /var/qmail/control/defaultdelivery cat: /var/qmail/control/defaultdelivery: No such file or directory Do I need to put maildir in here or something? Yes, you need to tell qmail what type of mailbox system you have. It will not deliver to Maildir if you do not have it.. I am assuming you have a stock setup of qmail with a /var/qmail/control dir in place.. just make a defaultdelivery file in the control dir, and put in ./Maildir/ into it, to have a Maildir format.. -- Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: procmail
Hey Gary, I gave that a try. echo ./Maildir/ /var/qmail/control/defaultdelivery When I run: gotmail --use-procmail --procmail-bin `which procmail` -u b1henning -p password It delivers in the mbox instead of the Maildir. I tried you recipie changes you sugested and the .procmailrc changes. Any other thoughts, Thanks for the help, Brian -Original Message- From: Gary [mailto:[EMAIL PROTECTED] Sent: Friday, February 27, 2004 4:54 PM To: FreeBSD Subject: RE: procmail Hi Brian, --On Friday, February 27, 2004 04:36:51 PM -0600 Henning, Brian [EMAIL PROTECTED] wrote: cat /var/qmail/control/defaultdelivery cat: /var/qmail/control/defaultdelivery: No such file or directory Do I need to put maildir in here or something? Yes, you need to tell qmail what type of mailbox system you have. It will not deliver to Maildir if you do not have it.. I am assuming you have a stock setup of qmail with a /var/qmail/control dir in place.. just make a defaultdelivery file in the control dir, and put in ./Maildir/ into it, to have a Maildir format.. -- Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: procmail
Hi Brian, --On Friday, February 27, 2004 05:01:03 PM -0600 Henning, Brian [EMAIL PROTECTED] wrote: I gave that a try. echo ./Maildir/ /var/qmail/control/defaultdelivery perfect.. When I run: gotmail --use-procmail --procmail-bin `which procmail` -u b1henning -p password It delivers in the mbox instead of the Maildir. I tried you recipie changes you sugested and the .procmailrc changes. I am not familiar with gotmail, but maybe it is calling the default global .procmailrc file instead of your local .procmailrc file. Also check your procmail logs (if you have it turned on), and your logs from gotmail, if it has logging capabilities.. also, the newer procmail versions do support Maildir delivery, whereas the older versions do not.. and the older versions should be used with a program called Safecat, but not needed for newer procmail versions. This not having a defaultdelivery file in your system also worries me, as it should have been installed by default. -- Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail
On Fri, 27 Feb 2004 17:01:03 -0600 Henning, Brian [EMAIL PROTECTED] wrote: When I run: gotmail --use-procmail --procmail-bin `which procmail` -u b1henning -p password It delivers in the mbox instead of the Maildir. I tried you recipie changes you sugested and the .procmailrc changes. gotmail is software to fetch email from hotmail, and afaik it completely bypasses any MTA you're running, so you clearly have a procmail-problem here in my .procmailrc there's Maildir defined, do you have that ? the logging can also be handy to see what's going on $ less .procmailrc VERBOSE=off SHELL=/bin/sh DEFAULT=$HOME/Maildir/ ORGMAIL=$HOME/Maildir/ MAILDIR=$HOME/Maildir/ PMDIR=$HOME/.procmail LOGFILE=$PMDIR/log ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: procmail
Hi Brian, --On Friday, February 27, 2004 03:55:47 PM -0600 Henning, Brian [EMAIL PROTECTED] wrote: cat .qmail | preline /usr/bin/procmail -t ~/.procmailrc || exit 111 Just noticed this.. try |preline procmail brian that's it. -- Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail recipe not working with mutt
On 02/05/04 at 06:33, Bryan Cassidy wrote: SNIP ### Mailboxes mailboxes =FreeBSD_Questions mailboxes =FreeBSD_Newbies mailboxes =FreeBSD_Hackers mailboxes =FreeBSD_KDE mailboxes =FreeBSD_Security_Notifications mailboxes =FreshPorts_Watch mailboxes =Fluxbox_Users mailboxes =Mutt mailboxes =CVS_ALL mailboxes =Sent mailboxes =Bryan_Cassidy mailboxes =CVS_PORTS mailboxes =Bob_Cassidy mailboxes =Default mailboxes =Bryan_Yahoo mailboxes =Jim Bonsey mailboxes =WKU_Linux mailboxes =Richard Just a thought, but does the (space) work when defined in a mailbox name (Jim Bonsey)in mutt? SNIP DEFAULT=$HOME/Mail/Default MAILDIR=$HOME/Mail PMDIR=$HOME/Procmail VERBOSE=no LOGFILE=$PMDIR/pmlog First thing to do to figure out why they are not going to the correct mailbox is to set VERBOSE to 'yes' VERBOSE=yes and watch the $LOGFILE and see if you can determine why it is failing. :0: * [EMAIL PROTECTED] FreeBSD_Questions :0: * ^TO_questions FreeBSD_Questions :0: * ^TO_ I hope this is just a typo... if not, it will catch anything and deliver it to your default mail spool. :0: * [EMAIL PROTECTED] Linux_WKU Again, not sure if this is a typo or not, but this will only match on a line that begins with [EMAIL PROTECTED] (also, you might want to consider escaping the .s in your recipes, as un-escaped dots (.) match any character--so a message that starts with [EMAIL PROTECTED] would make it into the Linux_WKU folder. Correct syntax would be [EMAIL PROTECTED] My thoughts on this rule is that it should probably be: :0: * [EMAIL PROTECTED] Linux_WKU SNIP :0: * .* Default This rule, IMO, is the reason why all of the rules below it go to Default. Any header (*) with any string (.*) will always match this rule. IF this is what you want, you should definitely have this one as the _LAST_ rule in your .procmailrc. :0: * ^From:[EMAIL PROTECTED] Bob_Cassidy :0: * ^From:[EMAIL PROTECTED] Jim Bonsey I'm pretty sure that you can't have spaces in the final delivery mailbox. You may want to change this one (and the one in your .muttrc) to Jim_Bonsey. :0: * ^From:[EMAIL PROTECTED] FreshPorts_Watch :0: * ^TO:[EMAIL PROTECTED] WKU_Linux You may match this one in the rule above, espceially if you modify it as I suggest, in which case this rule is a duplicate and may be removed. (Also, you may want to change the ^TO: to ^TO_) :0: * TO_:[EMAIL PROTECTED] FreeBSD_Security_Notifications Remove the : after the TO_ and this one should work fine. From the procmailrc man page: If the regular expression contains `^TO_' it will be substituted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope |Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)', which should catch all destination specifications containing a specific address. I also think that the .* is superfluous. Here's what I'd recommend (unless you are trying to messages that have [EMAIL PROTECTED], in which case, do have a .* after the _: :0: * [EMAIL PROTECTED] FreeBSD_Security_Notifications Hope this has helped. Bryan -- Bryan AlbrightLead IP Engineer [EMAIL PROTECTED] Qwest Internet Solutions Question: If you plug a charged UPS into itself, will it keep running forever? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail recipe not working with mutt
On Thu, Feb 05, 2004 at 06:33:32PM -0600, Bryan Cassidy wrote: Pretty much all my mailing list filters work but the FreeBSD Security Advisory one goes into =Default for some reason. All mail from my dad which is Bob_Cassidy, goes into =Default as well as mail from Richard and Jim. They all go into =Default instead of their correct folder. I just can't figure it out. Maybe someone could help me out here. Try moving this rule to the very bottom of the list and make sure it stays there - I think this rule matches everything, so if a message makes it to this rule it will automatically match which isn't what you want: :0: * .* Default Put these above the default rule: :0: * ^From:[EMAIL PROTECTED] Bob_Cassidy :0: * ^From:[EMAIL PROTECTED] Jim Bonsey :0: * ^From:[EMAIL PROTECTED] FreshPorts_Watch :0: * ^TO:[EMAIL PROTECTED] WKU_Linux :0: * TO_:[EMAIL PROTECTED] FreeBSD_Security_Notifications :0: * ^FROM:[EMAIL PROTECTED] Richard HTH. -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ http://jez.hancock-family.com/ - Another FreeBSD Diary http://ipfwstats.sf.net/- ipfw peruser traffic logging ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail + Mutt
On Fri, Dec 26, 2003 at 07:57:55AM +1100, Gautam Gopalakrishnan wrote:
On Thu, Dec 25, 2003 at 03:43:01PM -0600, Bryan Cassidy wrote:
I am using FreeBSD 4.8 with Mutt 1.5 and Procmail 3.22 and have setup
some filters. In my .procmailrc I have the following
:0: * [EMAIL PROTECTED] FreeBSD_Questions :0: *
^TO_questions FreeBSD_Questions
That must read:
:0:
* ^(To|C[Cc]):[EMAIL PROTECTED]
freebsd-questions
because sometimes people CC freebsd-questions
Except that '^TO_' in procmail recipies is a variable that expands
into a regular expression that matches pretty much all of the possible
header lines that can contain the delivery address. From
procmailrc(1):
If the regular expression contains `^TO_' it will be substituted by
`(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope
|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)', which should catch
all destination specifications containing a specific address.
There's another very similar pre-defined expression ^TO which I use --
I also match on the List-ID header, which is the most effective way of
catching messages delivered by through list: the ^TO stuff is to catch
messages CC'd to me as well as to the list:
# FreeBSD Questions
:0:
* (^TO|^List-ID:.*)(freebsd-)?questions(\.|@)FreeBSD\.ORG
| ${FORMAIL} -AX-Folder: FreeBSD/Questions FreeBSD/Questions
Note too that '.' in these REs is a wildcard, matching every single
character. You need to escape it '\.' to match it literally.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
pgp0.pgp
Description: PGP signature
Re: Procmail + Mutt
On Thu, Dec 25, 2003 at 03:43:01PM -0600, Bryan Cassidy wrote: I am using FreeBSD 4.8 with Mutt 1.5 and Procmail 3.22 and have setup some filters. In my .procmailrc I have the following :0: * [EMAIL PROTECTED] FreeBSD_Questions :0: * ^TO_questions FreeBSD_Questions That must read: :0: * ^(To|C[Cc]):[EMAIL PROTECTED] freebsd-questions because sometimes people CC freebsd-questions hth Gautam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail + Mutt
Hi, I had the same problem sorting the eMails from [EMAIL PROTECTED] Bryan Cassidy [EMAIL PROTECTED] wrote: I am using FreeBSD 4.8 with Mutt 1.5 and Procmail 3.22 and have setup some filters. In my .procmailrc I have the following :0: * [EMAIL PROTECTED] FreeBSD_Questions :0: * ^TO_questions FreeBSD_Questions :0: * .* Default And in my .muttrc file I have the following subscribe freebsd-questions subscribe freebsd subscribe [EMAIL PROTECTED] mailboxes =FreeBSD_Questions Sometimes I get e-mail in =Default that are sent to '[EMAIL PROTECTED]' why is this? I examined these eMails and found the following procmail-receipe work for me: ---8-- :0: * ^Sender:[EMAIL PROTECTED] FreeBSD-Questions --8--- Probably you can combine it with your receipe. HTH Sven -- Das Leben ist so hart, es sollte ein Job sein. Man sollte Geld dafuer verdienen, dass man es schafft --[rand. sig. #24] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Recipe Help - Pleeeeease..... - SOLVED
- Original Message - From: Drew Tomlinson [EMAIL PROTECTED] To: FreeBSD Questions [EMAIL PROTECTED] Sent: Wednesday, October 15, 2003 1:49 PM Subject: OT: Procmail Recipe Help - Please. I'm trying to use procmail to feed incoming mail to SpamAssassin and then forward the email to another address for one of my accounts. Because I use Postfix with Maildir, my /usr/local/etc/procmailrc file contains: DEFAULT=$HOME/Maildir/ so that messages that don't match any rule get delivered to the normal inbox. But for one person, I want to have all his mail scanned by SpamAssassin and then forwarded to a non-local email address. Here is his ~/.procmailrc file: # Forward all mail to SpamAssassin :0 fw | /usr/local/bin/spamc :0 fw ! [EMAIL PROTECTED] Duh! Needed to remove the 'fw' so line is just :0 The forwarding works but then procmail goes on to deliver a blank email in $HOME/Maildir/new. blacklamb# ll Maildir/new total 0 -rw--- 1 user user 0 Oct 15 11:30 1066242632.35780_0.blacklamb.mykitchentable.net -rw--- 1 user user 0 Oct 15 11:33 1066242826.35812_0.blacklamb.mykitchentable.net I assume this is because of the DEFAULT setting in the site-wide procmailrc. However, it is my understanding that since all mail matches the second rule, mail processing should stop at that point and nothing should be delivered to DEFAULT. What am I missing? Thanks, Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail, forward, and postfix
On Wed, 08 Oct 2003 22:16:42 -0700, David Bear [EMAIL PROTECTED] wrote: I don't understand a thing it does.. but I put it in my home directory anyway and called it .forward. It appears the procmail is no 'firing' when message come. Looking for any pointers? been through to procmail faq sites and thought there might be a recommendation here. Do you have a ~/.procmailrc file? If so, what is it? contents of .forward |IFS=' ' p=/usr/local/bin/procmail test -f $p exec $p -Yf- || exit 75 #Metropolis 'Metropolis' is the name of the account. Any pointers? Is procmail installed at /usr/local/bin/procmail? (Sorry had to ask) If so, then you need a .procmailrc file. It can be as simple as this: # Edit as appropriate PATH=/usr/local/bin:/sbin:/bin SHELL=/bin/sh # DIRECTORY where you want to store mail # MAKE SURE IT EXISTS MAILDIR=$HOME/mail LOGFILE=$HOME/.procmail.log VERBOSE=yes # Change to 'no' once you have it working LOGABSTRACT=all :0c: Backups # EOF All that will do is make a backup COPY (hence the :0c:) of all your incoming mail. It's an easy way to test to make sure procmail is working... that, and see if there is anything in the log file. TjL ps - nothing really FBSD-specific here, so you might want to checkout the super-handy procmail list: http://www.procmail.org/era/lists.html -- FBSD 4.9 on a Dell Inspiron 7500 laptop ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail filtering replacement w/ cyrus
On Sun, Sep 14, 2003 at 01:32:33PM +0200, dick hoogendijk wrote: Hi, I used to run procmail as my local mailer (w/ sendmail as MTU). The .procmailrc filters the incoming mail into separate folders. Now I've changed to cyrus-imapd and no longer use procmail. Cyrus has it's own local mailer (cyrdeliver). That's fine with me, bu now all mail is droped into the INBOX. The only way to filter it is through an mailclient running under X. Does someone know of a good way to filter my incoming mail _not_ only to user.xxx but to his/her other (imap) mailboxes as well? I was rather font of using mutt on the cli (which is much more complicated w/ imap) but losing my sorted filtered mailboxes does not make me happy. If filtering does not exist I think I'll go back to QPopper (pop3) and sendmail/procmail. Actually, this is quite a popular topic on the FreeBSD lists. A few moments searching a http://freebsd.rambler.ru/ will get you such handy messages as: http://freebsd.rambler.ru/bsdmail/freebsd-questions_2003/msg11082.html or http://freebsd.rambler.ru/bsdmail/freebsd-isp_2001/msg01947.html or http://freebsd.rambler.ru/bsdmail/freebsd-chat_2002/msg01762.html But note that Cyrus deliver has a built in 'sieve' function which will do a lot of what procmail does, and it has a remote interface which is handy when you want to set up a mail server box without giving login accounts to all of your mail users. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Procmail Recipie For FreeBSD Lists?
Quoting Drew Tomlinson ([EMAIL PROTECTED]): | About a year or two ago, someone posted his recipe for sorting FreeBSD | lists. This particular one was nice in that it extracted the list name | from the From line (I think) and then created the appropriate folder | if it didn't exist. Probably the most appropriate field to match against in the mailheader is ``List-Id'', which for this mailinglist is: List-Id: User questions freebsd-questions.freebsd.org I do not have that particular script which you refer to, but I'd just like to give a note of warning on automatically executing shell commands based on email data (since an attacker could easily insert hazardous commands). Why not just have some extra lines in your procmailrc file? Also, I've written some notes on sorting incoming mail: A guide to simple mail filtering on UNIX systems http://csl.sublevel3.org/docs/mailfiltering.php -- Christian Stigen Larsen -- http://csl.sublevel3.org -- mob: +47 98 22 02 15 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Recipie For FreeBSD Lists?
On Thu, Jul 03, 2003 at 08:53:30AM -0700, Drew Tomlinson wrote: About a year or two ago, someone posted his recipe for sorting FreeBSD lists. This particular one was nice in that it extracted the list name from the From line (I think) and then created the appropriate folder if it didn't exist. So freebsd-questions list items were put in the 'questions' folder, freebsd-stable in the 'stable' folder, and so on. I have search the archives for this post for the past two days but have been unsuccessful. I've tried to write it myself but this is not my area of expertise. Does anyone have such a recipe they are willing to share? Easy enough: :0: * List-Id:[^]+\/freebsd-[^.] $MATCH This will store each list in a folder prefixed by freebsd-. If you want freebsd-questions to be stored in a folder named questions, just move the \/ (which marks the beginning of the MATCH variable) to after the freebsd-. And if you want it to support other RFC2919-compliant lists (that is, ones which include the List-Id: header), simply remove freebsd- from the recipe. -- Paul Chvostek [EMAIL PROTECTED] it.canadahttp://www.it.ca/ Free PHP web hosting!http://www.it.ca/web/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Recipie For FreeBSD Lists?
Woops... On Thu, Jul 03, 2003 at 12:12:46PM -0400, Paul Chvostek wrote: Easy enough: :0: * List-Id:[^]+\/freebsd-[^.] $MATCH That should have been: :0: * ^List-Id:[^]+\/freebsd-[^.]+ $MATCH But I'm sure everyone already knew that... ;) -- Paul Chvostek [EMAIL PROTECTED] it.canadahttp://www.it.ca/ Free PHP web hosting!http://www.it.ca/web/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Recipie For FreeBSD Lists?
in message [EMAIL PROTECTED],
wrote Drew Tomlinson thusly...
About a year or two ago, someone posted his recipe for sorting FreeBSD
lists. This particular one was nice in that it extracted the list name
from the From line (I think) and then created the appropriate folder
if it didn't exist. So freebsd-questions list items were put in the
'questions' folder, freebsd-stable in the 'stable' folder, and so on. I
I use 'f-list' named folder. Change the following (part of larger recipes)
as you desire...
# get list id
:0
* ^List-ID:[]*.*\/[a-z]+.*
{ list_id = $MATCH }
# identify other lists on different criteria
# based on $list_id, assign $list
#
list=
# freebsd lists
:0
* list_id ?? ()\/[a-z]+[-.a-z]+freebsd\.org
{
# consider -gnats-submit list same as -bugs, but not -ports-bugs
:0
* list_id ?? ()(ports-bugs|cvs-ports)
{ list = f-ports }
:0 E
* list_id ?? ()(gnats-submit|bugs)
{ list = f-bugs }
# most interesting freebsd mailing lists
:0 E
* MATCH ?? ()\/(stable|ppc|cvs|mobile|questions|ports|java)
{ list = f-${MATCH} }
# dafault $list for/from any freebsd list
:0 E
{ list = f-misc }
}
# do other things
# file message
:0:
* list ?? ^^f-[a-z]+^^
$list
- Parv
--
A programmer, budding Unix system administrator, and amateur photographer
ISO employment...
http://www103.pair.com/parv/work/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Recipie For FreeBSD Lists?
- Original Message - From: Paul Chvostek [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 03, 2003 10:37 AM On Thu, Jul 03, 2003 at 10:12:22AM -0700, Drew Tomlinson wrote: :0: * ^List-Id:[^]+freebsd-\/[^.]+ Maildir/FreeBSD/$MATCH/new And I'm getting messages like this in my procmail log: procmail: Assigning PATH=/home/drew/bin:/bin:/usr/bin:/usr/local/bin procmail: Lock failure on Maildir/FreeBSD/alpha/new.lock procmail: Error while writing to Maildir/FreeBSD/alpha/new OK, I assume the error is because Maildir/FreeBSD/alpha/new does not exist. How can I get procmail to create the directory it needs? As you no doubt read on the procmail manpage: | If the mailbox name ends in /, then this | directory is presumed to be a maildir folder; i.e., proc- | mail will deliver the message to a file in a subdirectory | named tmp and rename it to be inside a subdirectory | named new. Now ... I obviously don't use maildir format, but to me, this would imply a format something like: :0 * ^List-Id:[^]+freebsd-\/[^.]+ FreeBSD/$MATCH/ I'm assuming that the leading Maildir/ is redundant, as is the pointer to the new folder. Thanks for pointing out my oversight and all of the help so far. I've added the / and now my recipe is: :0 * ^List-Id:[^]+freebsd-\/[^.]+ /Maildir/FreeBSD/$MATCH/ However I get these messages from the procmail log: procmail: Matched test procmail: Match on ^List-Id:[^]+freebsd-\/[^.]+ procmail: Unable to treat as directory /Maildir/FreeBSD/test procmail: Assigning LASTFOLDER=/Maildir/FreeBSD/test procmail: Opening /Maildir/FreeBSD/test procmail: Error while writing to /Maildir/FreeBSD/test I've tried without the leading /, without the Maildir, and without /Maildir/ but I keep getting the same type of error. Maildir is owned by me and is mode 700. I tried changing to 777 but that didn't help so I put it back to 700. According to the man page, the directory should be created if it doesn't exist. From the man page: If the mailbox is specified to be an MH folder or maildir folder, procmail will create the necessary directories if they don't exist, rather than treat the mailbox as a non-existent filename. I feel I am close. Can anyone enlighten me and point out what I'm missing? Thanks, Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Recipie For FreeBSD Lists?
On Thu, Jul 03, 2003 at 02:26:49PM -0700, Drew Tomlinson wrote: :0 * ^List-Id:[^]+freebsd-\/[^.]+ FreeBSD/$MATCH/ Thanks for pointing out my oversight and all of the help so far. I've added the / and now my recipe is: :0 * ^List-Id:[^]+freebsd-\/[^.]+ /Maildir/FreeBSD/$MATCH/ You're storing your Maildir in the root directory of the server? However I get these messages from the procmail log: procmail: Matched test procmail: Match on ^List-Id:[^]+freebsd-\/[^.]+ procmail: Unable to treat as directory /Maildir/FreeBSD/test procmail: Assigning LASTFOLDER=/Maildir/FreeBSD/test procmail: Opening /Maildir/FreeBSD/test procmail: Error while writing to /Maildir/FreeBSD/test It looks as if procmail doesn't have permissions to create directories in the root directory of your server. That's a Good Thing. I've tried without the leading /, without the Maildir, and without /Maildir/ but I keep getting the same type of error. Maildir is owned by me and is mode 700. That's the right mode, but think about where the directory is, and where procmail wants to find out. Look in the procmail documentation (manpage for procmailrc) for variables like $DEFAULT, $MAILDIR, $HOME, etc. If the mailbox is specified to be an MH folder or maildir folder, procmail will create the necessary directories if they don't exist, rather than treat the mailbox as a non-existent filename. I feel I am close. Can anyone enlighten me and point out what I'm missing? Remember that paths that start with a / are absolute, and all other paths are relative to $MAILDIR. -- Paul Chvostek [EMAIL PROTECTED] it.canadahttp://www.it.ca/ Free PHP web hosting!http://www.it.ca/web/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail Recipie For FreeBSD Lists? - SOLVED
- Original Message - From: Paul Chvostek [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 03, 2003 2:48 PM Subject: Re: Procmail Recipie For FreeBSD Lists? On Thu, Jul 03, 2003 at 02:26:49PM -0700, Drew Tomlinson wrote: :0 * ^List-Id:[^]+freebsd-\/[^.]+ FreeBSD/$MATCH/ Thanks for pointing out my oversight and all of the help so far. I've added the / and now my recipe is: :0 * ^List-Id:[^]+freebsd-\/[^.]+ /Maildir/FreeBSD/$MATCH/ You're storing your Maildir in the root directory of the server? However I get these messages from the procmail log: procmail: Matched test procmail: Match on ^List-Id:[^]+freebsd-\/[^.]+ procmail: Unable to treat as directory /Maildir/FreeBSD/test procmail: Assigning LASTFOLDER=/Maildir/FreeBSD/test procmail: Opening /Maildir/FreeBSD/test procmail: Error while writing to /Maildir/FreeBSD/test It looks as if procmail doesn't have permissions to create directories in the root directory of your server. That's a Good Thing. I've tried without the leading /, without the Maildir, and without /Maildir/ but I keep getting the same type of error. Maildir is owned by me and is mode 700. That's the right mode, but think about where the directory is, and where procmail wants to find out. Look in the procmail documentation (manpage for procmailrc) for variables like $DEFAULT, $MAILDIR, $HOME, etc. If the mailbox is specified to be an MH folder or maildir folder, procmail will create the necessary directories if they don't exist, rather than treat the mailbox as a non-existent filename. I feel I am close. Can anyone enlighten me and point out what I'm missing? Remember that paths that start with a / are absolute, and all other paths are relative to $MAILDIR. Thanks for all of your help. I finally got it! The directory structure for Courier IMAP is Maildir equals INBOX. So in the IMAP client everything in $HOME/Maildir appears in the Inbox. Then any folders in the Inbox are stored in directories such as $HOME/Maildir/.folder.subfolder. In this case, the IMAP client Inbox would show one folder named folder. Then in folder there would be subfolder. So for me, I wanted questions list mail to get placed in $HOME/Maildir/FreeBSD.questions, stable list mail in $HOME/Maildir/FreeBSD.stable, etc. Since $MAILDIR is already defined as $HOME/Maildir, the correct recipe is as follows: :0 * ^List-Id:[^]+freebsd-\/[^.]+ .FreeBSD.$MATCH/ It's amazing how much trouble a misplaced . or / can cause! :) Thanks again. I would not have figured this out without your help. Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail isn't handing off mail like it should.
user2 and user3 in an effort to filter their mail as well, then forward it off to each one's respective mail accounts. The process is being run as user1 from cron rather than as root. All works fine except no mail is being filtered for either user2 or user3. It's basically coming in, and then immediately going out again to another location. I do exactly what you want on my machine. We need to see your .procmailrc file. What spam filtering program are you using? I use spamassassin which works really well, and you can change recipes to catch any that was not caught. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Procmail isn't handing off mail like it should.
Nobody has an answer for this? Do I need to setup my procmail settings on the server level and run it as root in order to solve this issue? Feedback is much appreciated. Thanks. At 11:39 AM 6/13/03 -0400, Dragoncrest wrote: Hi all. Ok, got a really weird setup here that I need some advice on. I've started using my home mail server for spam filtering for my dad and step brother. Well, it filters spam just fine for me, but all it's doing for them is downloading the mail, then forwarding it off to the dumping account without actually filtering the mail. I'm confused why. Ok, well, here's my basic setup. I'm firing up fetchmail at user level via cron to grab my mail, filter it, and then deliver it locally. My dad and step brother's mail is slightly different. Their mail is being pulled in by my fetchmail process, and it's supposed to be filtered and then forwarded from my machine off to a dumping account on my external domain so that all they recieve is spam and virus free mail. Problem is, all it's doing is grabbing the mail, then forwarding it off. It's not filtering it. I have even setup local accounts for them complete with an exact copy of my procmailrc file to try to help this, but it's not working. Ok, to give you a little better mental picture, here's a general layout. user1 (this is me) user2 (this is my dad) user3 (this is my step brother) user1 uses fetchmail to pull in the mail and pass it through spam assassin and deliver it to his local account. He also grabs the mail for user2 and user3 in an effort to filter their mail as well, then forward it off to each one's respective mail accounts. The process is being run as user1 from cron rather than as root. All works fine except no mail is being filtered for either user2 or user3. It's basically coming in, and then immediately going out again to another location. Any way I can rectify this? Do I have to setup separate fetchmail processes for each user? Or do I have to setup fetchmail as a daemon and somehow set it to process mail for all 3 user accounts individually. I'm kinda confused here. Any help is apreciated. Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: procmail question a little off topic
On 2003-02-23 14:51, Lowell Gilbert [EMAIL PROTECTED] wrote: David Bear [EMAIL PROTECTED] writes: sorry for the offtopic post here but I cant seem to get my procmail recipe's to fire. I know sendmail sees and uses procmail because maillog show its handing it of to procmail. Also, the mail inbox specified in the procmailrc file is receiving the message. Still, none of the messages that I want taking from inbox and put in other folders as specified in the recipe's section are being moved. Check the *procmail* log. Sound advice. Are you sure you can use bare '@' symbols in conditions? Yes. The following is from my (working) .procmailrc: : hecate:/home/giorgos grep '@' .procmailrc | tail -2 : * ^sender: [EMAIL PROTECTED] : * ^delivered-to: [EMAIL PROTECTED] : hecate:/home/giorgos - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: procmail question a little off topic
David Bear [EMAIL PROTECTED] writes: sorry for the offtopic post here but I cant seem to get my procmail recipe's to fire. I know sendmail sees and uses procmail because maillog show its handing it of to procmail. Also, the mail inbox specified in the procmailrc file is receiving the message. Still, none of the messages that I want taking from inbox and put in other folders as specified in the recipe's section are being moved. Check the *procmail* log. My bet would be that something will be obvious in there. Are you sure you can use bare '' symbols in conditions? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: procmail question a little off topic
On Fri, 21 Feb 2003, David Bear wrote: .procmailrc == # Frisch, SA, p 602 PATH=/bin:/usr/bin:/usr/local/bin:/usr/sbin:$HOME/bin MAILDIR=$HOME/mail DEFAULT=$MAILDIR/inbox # # catch systems for syslog entries # ppsrv3, PAC SMB server :0: * [EMAIL PROTECTED] syslogs/ppsrv3 ^^^ Shouldn't this be an absolute path? Don't count on procmail running in the same directory you think it is. (Maybe just a problem, and not *the* problem.) -Warren Block * Rapid City, South Dakota USA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: procmail question a little off topic
On 2003-02-21 17:48, Warren Block [EMAIL PROTECTED] wrote:
On Fri, 21 Feb 2003, David Bear wrote:
.procmailrc ==
PATH=/bin:/usr/bin:/usr/local/bin:/usr/sbin:$HOME/bin
MAILDIR=$HOME/mail
DEFAULT=$MAILDIR/inbox
#
# catch systems for syslog entries
# ppsrv3, PAC SMB server
:0:
* [EMAIL PROTECTED]
syslogs/ppsrv3
^^^ Shouldn't this be an absolute path? Don't count on procmail
running in the same directory you think it is. (Maybe just a problem,
and not *the* problem.)
It's ok. If you don't use an absolute path, procmail appends the
mailbox path of the rule to ${MAILDIR}/, which is already set to a
correct value in an earlier line ;-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: procmail - unsafe for mailing to programs
David Banning [EMAIL PROTECTED] writes: | david$ /usr/david/.forward: line 1: | /usr/local/bin/procmail || exit 75... |Address [EMAIL PROTECTED] is unsafe for mailing to programs and later | $ cat .forward | | /usr/local/bin/procmail || exit 75 The manpage suggests |exec /usr/local/bin/procmail || exit 75 I'm not sure whether that's the problem or not. My .forward file has always been |IFS=' 'p=/usr/local/bin/procmailtest -f $pexec $p -Yf-||exit 75 #mcglk which was probably originally in old procmail documentation, but which works great. Other than that, all your permissions look fine. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: procmail - unsafe for mailing to programs
On 2003-02-18 15:54, David Banning [EMAIL PROTECTED] wrote: Here is the problem; david$ mail david Subject: test to david test to david EOT david$ /usr/david/.forward: line 1: | /usr/local/bin/procmail || exit 75... Address [EMAIL PROTECTED] is unsafe for mailing to programs /usr/david/dead.letter... Saved message in /usr/david/dead.letter Read the sendmail FAQ entries about ``smrsh''. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
