Displaying 20 results from an estimated 4000 matches similar to: "procmail recipe"
2009 Feb 02
1
OT: procmail recipe question
I'm trying to use procmail and I'm having trouble getting it to set some
headers. I have one mailing list that sets ?Newsgroups: in the header
and I want to remove it. I have the following test recipe:
:0
* ^Subject:.*\<testing
* ^(Mime-Version:|Content-)
| formail -IMime-Version: -IContent-
If I understand it correctly, it should remove the Mime-Verion and
Content headers.
The
2010 Feb 08
7
slowness in sendmail - 60 second timeout
I am sending an email from my machine devcentos5x64.
the transcript below (hangs for 60 seconds) at the line:
MAIL From:<root at devcentos5x64.msgnet.com> SIZE=56
AUTH=root at devcentos5x64.msgnet.com
The email succeeds - but I am trying to figure out the 60 second delay.
Neither email server is busy. Nothing is waiting.
the DNS on both machines point to the same nameserver. The DNS
2007 Dec 03
2
procmail/formail --> Maildir
Hello List,
i switched mailformat from mbox to maildir. Now i have a little problem with procmail/formail and headermanipulation of mails.
Here an example:
0
* ^From.*gmx.de
| (formail -t -I"procmail: gmx.de") >> /var/spool/mail/xxxxxx
So, i can add some different headerlines for later evaluation and the result is attached to inbox.
Now i have the problem that i don't know
2013 Feb 25
1
Procmail/Formail problem on 6.3
Hi!
In the process of making mysystem work again, having just done a
reinstall of 6.3 x86_64.
I have a considerable collection of procmail recipes for filtering
mail in various ways, and since the upgrade none of 'em is working.
procmail passes every mail thru spambayes, which gives back a rating
on spamminess. this happens, so it's not as if procmail is simply
punting.
that is
2009 Apr 05
3
hwclock and util-linux on 5.3
I am getting this error:
hwclock --debug
hwclock from util-linux-2.13-pre7
hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
[root at devcentos5x64 src]# uname -a
Linux devcentos5x64.msgnet.com 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14
EST 2009 x86_64 x86_64 x86_64 GNU/Linux
rpm -qa | grep
2004 Jan 11
24
More words for Allison
Here's the latest batch of words to get shipped out to Allison Smith.
Please submit reasonably small changes to me by tomorrow 10:00 AM
Eastern time, and I'll add them.
As usual, donations to what will be a ~$110 USD expense would be
appreciated, as I am paying for this round out of my pocket. Please
send to paypal address "jtodd@loligo.com". I did not include all
2010 May 11
4
AGI and Severe Weather Alerts
All,
I am toying with an idea of using an AGI to be able to 'call'
my phone, or phones, in case of severe weather warnings. I have been
tinkering with a script that reads from weather underground for the
forecast, based off a PHP version of a weather AGI I found on the net.
It seems rather trivial to have the AGI as a script, that does nothing
unless a condition is met, and
2007 Jun 07
2
procmail, and the care and feeding of mailing list content received
Some threads just go on too long. Personally I think a troll
has hijacked the main centos list again and is inducing food
fight behaviours while that troll perfectly 'innocently'
asserting that it is just respoding to all email.
see:
http://video.google.com/videoplay?docid=-4216011961522818645
for a discussion of the problem of 'capture' in FOSS projects.
But if one loses
2015 Apr 30
1
doveadm -D and -v options
According to doveadm-dsync man page the above two options are valid, but
they are rejected when used:
tornado # doveadm backup -v -u testuser remote:pi.me.name:4814
backup: invalid option -- 'v'
doveadm backup [-u <user>|-A] [-S <socket_path>] [-fPRU] [-l <secs>] [-r
<rawlog path>] [-m <mailbox>] [-g <mailbox_guid>] [-n <namespace> | -N]
[-x
2015 May 08
1
Additional userdb variables in passwd [was Re: Dovecot Replication - Architecture Endianness?]
On 8/05/2015 6:10 PM, Teemu Huovila wrote:
> On 05/07/2015 02:32 PM, Reuben Farrelly wrote:
>> On 7/05/2015 7:49 AM, Timo Sirainen wrote:
>>> On 06 May 2015, at 13:52, Reuben Farrelly
>>> <reuben-dovecot at reub.net> wrote:
>>>>
>>>> On 4/05/2015 11:06 PM, Teemu Huovila wrote:
>>>>>> Also is there a way to restrict
2012 Apr 30
1
Dovecot dsync mail replication issues
Hi,
I'm trying to set up some dsync based replication between two hosts on
my network. The current topology is a single server running Postfix
with a single dovecot installation with a Maildir per user (only 4 users
including myself). No NFS, just local system users on ext4. I am only
using system users, ie no virtual users. I am using dovecot deliver to
deliver mails into the
2004 Jan 17
0
New sounds posted
So, per the discussion last week and generous donations, we have some
new sound files with which to work.
The sounds are located in:
http://www.loligo.com/asterisk/sounds/
For those of you who just want to download the _new_ sounds, please fetch:
http://www.loligo.com/asterisk/sounds/20040117.newsounds.tar
All of the sounds in that tarball are also in the main ../sounds/
directory in
2015 May 07
2
Additional userdb variables in passwd [was Re: Dovecot Replication - Architecture Endianness?]
On 7/05/2015 7:49 AM, Timo Sirainen wrote:
> On 06 May 2015, at 13:52, Reuben Farrelly <reuben-dovecot at reub.net> wrote:
>>
>> On 4/05/2015 11:06 PM, Teemu Huovila wrote:
>>>> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs?
>>> You can set the userdb to return an empty mail_replica variable for
2009 May 17
0
procmail & formail
Dear all,
i have a mail server & vpopmail.
Now, i want to copy from each message to a directory.i find a way to do
it.
i put following line in .qmail-default :
|formail -X "" > ~/text.txt
Of course above line is test.Given line doesn't retrieves Return* header
field.
My question:
How i retrieve entire email same itslef?
Yours,
Mohsen
2007 Dec 09
2
centos 5.1 kernel crash on 2.6.23.9
Hi all - looks like I have a kernel dieing on me.
This is an AMD 6400+ with 4 GIG ram. I am using ext3 and software raid on 500G drives. (2) of them.
I have an external 1T usb disk connected for backup.
This is running 2.6.23.9 as I wanted to use kvm-amd.
It has died on me twice. Funny thing is it happens when I am NOT using the machine.
Any thoughts?
Jerry
--------------
Dec 8 22:23:57
2007 Feb 22
5
Problem creating domU: "Device 2049 (vbd) could not be connected. Hotplug scripts not working."
Hello,
My name is Fermín Galán. I have started recently to use Xen (so please
forgive me in advance if I''m too "newbie" :) and I''m facing my first
problems...
I''m trying to create a domU, but I''m getting an error:
tornado:~# xm create test.cfg -c
Using config file "/etc/xen/test.cfg".
Error: Device 2049 (vbd) could not be connected.
2017 Apr 12
7
email subject length issue
Sorry for the extra email. It send to quickly.
procmail: Assigning "SUBJECT= Tornado Monday, 03/27/2017 at 20:27:02. The
Point BB.OBSURGRH is"
jerry
2014 Aug 14
1
Segfault with indexer-worker using Tika/Solr
Using Dovecot 2.2.13 with Tika 1.5 on Centos 5 64bit
Tika is throwing an exception for some reason, which seems to be causing Dovecot's indexer to segfault. I'm using mdbox/gzipped compressed mail and private indexes for the shared folder. I'm importing mail via formail/dovecot-lda:
formail -s /usr/libexec/dovecot/dovecot-lda -d admin -m Public/TestSubFolder? < /tmp/Inbox.mbox
2005 Dec 22
1
dovecot -CVS and epoll and cvs not building
Hi,
After reviewing my dovecot ./configure options I thought I'd give
--with-ioloop=epoll a go again (as opposed to just using =poll) but I'm seeing
some errors appearing in the maillog that aren't there with standard poll:
Dec 23 02:34:47 tornado dovecot: imap-login: Login: user=<reuben>,
auth-method=plain, remote=220.237.24.149, TLS
Dec 23 02:34:48 tornado dovecot:
2015 Oct 28
2
sieve vacation - 2 questions
Hello,
still trying to move from procmail to sieve, but there are new problems.
Currently we use procmail for autoresponder and let user choose
timerange, in which responder should work. May be you set up today your
responder for 2 weeks in future where responder start and stop
automatically without further manuell intervention.
In procmail this is done by simple scripting and comparison of