[ingo] My ingo filters don't seem to be working -- SOLVED!

[Kevin Hanser]

I have fixed my filter problem.  It seems I needed to add this line to my
/etc/procmailrc to let procmail know where my user mail folders should go:

MAILDIR=$HOME/mail

Once I added that in, my filters are now working great!

k

Quoting Kevin Hanser <ingo at hanser.org>:

> Hmmm... My /etc/procmailrc currently has the following in it:
>
> # Use mbox-style mailbox in /var/spool/mail
> DEFAULT=/var/spool/mail/$LOGNAME
>
> ...
> Which seems to be pointing to my inbox, rather than where my mail
> folders end up
> going.  If I change this value... will procmail still know where my
> inbox is (it
> actually is in /var/spool/mail/<username>)?
>
> thx
>
> k
>
>
> Quoting Ben Chavet <ben at chavet.net>:
>
>> Ok, this makes sense now.  You are going to want to modify the procmail
>> $DEFAULT
>>   variable.  There are a couple of ways of doing this.  The way I do 
>> it is by
>> using the /etc/procmailrc global procmail config file, adding the following:
>>
>>    ### Using mbox ###
>>    DEFAULT=/home/$LOGNAME/mail
>>
>> or
>>
>>    ### Using maildir ###
>>    DEFAULT=$HOME/.maildir/
>>
>> The other way of doing it is by specifying $DEFAULT in the
>> ingo/config/backends.php server config.  I haven't actually used 
>> this method,
>> and it's been a long time since I've looked at any ingo source code, so
>> I don't
>> have any pointers on this, other than I'm pretty sure it can be done.
>>
>> Hope that helps
>>
>> --Ben
>>
>> Quoting Kevin Hanser <ingo at hanser.org>:
>>
>>> Ok, that seems to have helped a little bit.
>>>
>>> However, once I did as you suggested, my mail just started
>>> disappearing!  Didn't
>>> show up in inbox, or any other folder.
>>>
>>> I checked my mail logs to make sure that the mail was being received and
>>> processed, and sure enough it was.  I then looked in my home 
>>> directory, and I
>>> found the problem.  With the procmail recipies that ingo is creating, it's
>>> delivering the messages into mbox files _directly in my home
>>> directory_.  On my
>>> machine, my mail folders all reside in a subdir of my home directory, mail.
>>> Ingo however is just dumping them into folders in my main home directory.
>>>
>>> I'm using dovecot as my IMAP server, and according to the IMP docs for
>>> dovecot,
>>> you set the default mail folder to ''.  (since dovecot takes care of that
>>> itself in its config I guess, and places them into the mail subdir).  Could
>>> this be why ingo is delivering to my home directory instead of the mail
>>> directory?  Is it getting that setting of '' from the IMP setup, and then
>>> assuming that my mail folders should be there too?
>>>
>>> For now, I have manually edited my .procmailrc to add mail/ to the
>>> front of each
>>> folder that it's to be dropped into, and that seems to do the trick.
>>>
>>> It seems that maybe ingo needs an option to allow the user to specify what
>>> subdir your mail folders reside in, so that it writes the procmail 
>>> recipies to
>>> get the messages in the right place....  Maybe have the option of using
>>> the IMP
>>> default, or manually typing it in yourself...?
>>>
>>> k
>>>
>>> Quoting Ben Chavet <ben at chavet.net>:
>>>
>>>> Make sure to check the box "Stop checking if this rule matches". 
>>>> Otherwis, a
>>>> copy of everything will still end up in your inbox.
>>>>
>>>> --Ben
>>>>
>>>> Quoting Kevin Hanser <ingo at hanser.org>:
>>>>
>>>>> Hello,
>>>>>
>>>>> Just recently installed the newest IMP 4.0, and with it Ingo.  I 
>>>>> like how ingo
>>>>> can interface w/procmail so as to filter my mail before it gets 
>>>>> to the inbox,
>>>>> but for some reason my filters don't seem to be working.
>>>>>
>>>>> For example, I created a filter for the IMP mailing list that says:
>>>>>
>>>>> if
>>>>> Subject Contains [imp]
>>>>> or
>>>>> to field is "imp2 at hanser.org"
>>>>> or
>>>>> to field is "imp at lists.horde.org"
>>>>> then
>>>>> deliver it to the IMP folder.
>>>>>
>>>>> I saved the filter, and it created this in my .procmailrc:
>>>>>
>>>>> ##### IMP List #####
>>>>> :0 c
>>>>> * ^Subject:.*\[imp\]
>>>>> IMP
>>>>>
>>>>> :0 Ec
>>>>> * ^To:.*imp2 at hanser\.org
>>>>> IMP
>>>>>
>>>>> :0 Ec
>>>>> * ^To:.*imp at lists\.horde\.org
>>>>>
>>>>> Unfortunately, I've never used procmail recipies before, so I 
>>>>> can't tell if this
>>>>> is valid or not.  It looks OK to me, from what I've read about 
>>>>> procmail, but my
>>>>> mail isn't getting delivered to the proper folder... it all just 
>>>>> ends up in my
>>>>> inbox.
>>>>>
>>>>> I checked my sendmail config to make sure it was sending mail 
>>>>> thru procmail, and
>>>>> it seems ok.  My mailer lines @ the bottom of my sendmail.mc look 
>>>>> like this;
>>>>>
>>>>> MAILER(smtp)dnl
>>>>> MAILER(procmail)dnl
>>>>>
>>>>> Any ideas on why my filters aren't working?  This may be more of 
>>>>> a procmail
>>>>> problem than an ingo problem, but I was hoping that someone here 
>>>>> might have
>>>>> more insight into the inner workings of procmail than I do :)
>>>>>
>>>>> any suggestions are greatly appreciated.
>>>>>
>>>>> thx!
>>>>>
>>>>> k
>>>>>
>>>>> --
>>>>> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
>>>>> Frequently Asked Questions: http://horde.org/faq/
>>>>> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>>>>>
>>>>
>>>>
>>>> -- Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
>>>> Frequently Asked Questions: http://horde.org/faq/
>>>> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>>>>
>>>
>>>
>>>
>>> -- Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
>>> Frequently Asked Questions: http://horde.org/faq/
>>> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>>>
>>
>>
>> -- Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>>
>
>
>
> -- Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>