If I understand that correctly nothing at all gets through
the first filter except mail that has been through gmail once.
If that is correct a simple clone will do the rest.
#initial filter for "has been through gmail once" goes here.
# copy email to second recipient
:0 c
! secondrecipi...@foo
Yeah. I realize that's probably what's getting jdow confused as well.
Hopefully my previous message explains it better. One bit I forgot to add,
was something jdow asked, 'what happens if someone e-mails
kirash4@gmaildirectly'
GMail forwards it back to my @pcraft domain. And that too will have
On 01/24/2013 01:26 AM, jdow wrote:
If you subtract out the loop are you trying to make a courtesy copy to
one or more other addresses for all mail that is coming in? Your
brief description below suggests that is the case. But the whole GMail
loop is "undocumented" so it's hard to guess what rea
On Wed, 23 Jan 2013 16:28:07 -0700, Ashley M. Kirchner wrote:
> :0
> * !^X-Forwarded-For: kira...@gmail.com
> myt...@pcigrafx.com
> * !^X-Forwarded-For: kira...@gmail.com myt...@pcraft.com
> * !^From.*kira...@gmail.com
> * !^To.*myt...@papillon.pcraft.com
> ! kira...@gmail.com
>
> :0c
> * ^X-
That does not seem to match what I broke down as the rule.
Whose account is getting filtered. That will help analyze the
rule. The loop through GMail is muddying the water here. And note
that you CANNOT do the "else" clause without a clone operation. I
presume that is what the GMail loop kludge i
Let's try this:
In simple form, it looks like this:
if (message does NOT contain header) {
send to GMail
} else {
drop in recipient mailbox
send copy to other email
}
The first recipe works, as specified, and does what it should do which is
to check whether an incoming e-mail to the system
OK, you do not want things to continue processing. So what I posted will
not solve your problem.
So what you have for rule 1 is:
not Xforwarded to both kira...@gmail.com and ash...@pcraft.com
and not xforwarded to both kira...@gmail.com and ash...@pcigrafx.com
and not from kira...@gm
No, the second rule should ONLY process when a message passes the first
rule (and does NOT get bounced out to gmail.) I believe, please correct me
if I'm wrong here, but I believe the way you've rewritten it, rule 2 will
ALWAYS run, regardless of the outcome of rule 1. This will result in
duplica
The basic rule to remember with procmail is that once the email is
delivered processing is ended. So if the rule passes you must then
clone the email and deliver the clone. That allows the rules to keep
on processing.
I imagine you also want the second rule to continue processing as well.
Someth
The way this should work is as follows:
- new e-mail arrives at the recipient's box and procmail picks it up and
checks the X-Forward-For header
- if the header does NOT contain any of those listed, it forwards the
message to the specified gmail address
> STOP <
- if the header exists and conta
On 2013/01/23 15:28, Ashley M. Kirchner wrote:
Ok, I'm still trying to figure this out. On the new, test account, i can get it
to log so I just need to figure out the other two. However, I recreated the
same recipe on the test account and what I'm seeing in the log is the first part
of the reci
Ok, I'm still trying to figure this out. On the new, test account, i can
get it to log so I just need to figure out the other two. However, I
recreated the same recipe on the test account and what I'm seeing in the
log is the first part of the recipe only, it doesn't seem to do anything
with the
Ok, well those recipes are working and logging to /var/log/procmail.
I don't understand why this one, which is a lot shorter and simpler, won't
log. Nor will it work properly.
On Wed, Jan 23, 2013 at 2:54 PM, Michael Schwendt wrote:
> On Wed, 23 Jan 2013 14:45:52 -0700, Ashley M. Kirchner wrot
On Wed, 23 Jan 2013 14:45:52 -0700, Ashley M. Kirchner wrote:
> a) selinux doesn't exist on this box
> b) doesn't matter where the log file is
>
> And related to a), I have two other accounts that are successfully logging
> to /var/log/procmail. They dump custom messages. The differences I see
a) selinux doesn't exist on this box
b) doesn't matter where the log file is
And related to a), I have two other accounts that are successfully logging
to /var/log/procmail. They dump custom messages. The differences I see is
that those recipes have this at the top, under the LOGFILE line:
LOGAB
Once upon a time, Ashley M. Kirchner said:
> It works if I use ${HOME} instead of ${HOMEDIR}.
>
> It also works if the path is set to /var/log/procmail
>
> If I log in to the account with the actual recipe, and I echo 'fubar' |
> procmail, that too dumps stuff into the log file.
>
> So why won'
It works if I use ${HOME} instead of ${HOMEDIR}.
It also works if the path is set to /var/log/procmail
If I log in to the account with the actual recipe, and I echo 'fubar' |
procmail, that too dumps stuff into the log file.
So why won't it work when in this recipe:
LOGFILE=/var/log/procmail
VE
On Wed, 23 Jan 2013 13:32:29 -0700, Ashley M. Kirchner wrote:
> Ok, adding those two lines does nothing. I have:
>
> LOGFILE=/var/log/procmail
> VERBOSE=on (also tried 'yes')
>
> This is at the top of the recipe. I'm getting nothing in that log file.
> It exists, and it's writable.
Create a
Ok, adding those two lines does nothing. I have:
LOGFILE=/var/log/procmail
VERBOSE=on (also tried 'yes')
This is at the top of the recipe. I'm getting nothing in that log file.
It exists, and it's writable.
On Wed, Jan 23, 2013 at 12:11 PM, Heinz Diehl wrote:
> On 23.01.2013, Ashley M. Kir
On 23.01.2013, Ashley M. Kirchner wrote:
> So perhaps someone here might be able to help. I'm trying to figure out
> why a recipe isn't working (when it used to in the past.)
First let procmail write a logfile:
LOGFILE=${HOMEDIR}/procmail.log
And then let it be verbose:
VERBOSE=on
After t
On Wed, 23 Jan 2013 11:38:36 -0700, Ashley M. Kirchner wrote:
> Actually, I just noticed that recipe isn't complete. In my haste I didn't
> type out the complete address. It should read salesd...@pcraft.com - it's
> being forwarded to another e-mail address.
>
> And I have no procmail log ... a
Actually, I just noticed that recipe isn't complete. In my haste I didn't
type out the complete address. It should read salesd...@pcraft.com - it's
being forwarded to another e-mail address.
And I have no procmail log ... anywhere.
On Wed, Jan 23, 2013 at 11:24 AM, Michael Schwendt wrote:
> O
On Wed, 23 Jan 2013 11:12:32 -0700, Ashley M. Kirchner wrote:
> :0
> * !^X-Forwarded-For: kira...@gmail.com ash...@pcraft.com
> * !^X-Forwarded-For: kira...@gmail.com ash...@pcigrafx.com
> * !^From.*kira...@gmail.com
> * !^To.*ash...@papillon.pcraft.com
> ! kira...@gmail.com
>
> :0c
> * ^X-Forwar
Hey folks,
Seems the procmail list has fallen off of the face of the planet ... at
least, the address given on the procmail.org website doesn't seem to work
anymore.
So perhaps someone here might be able to help. I'm trying to figure out
why a recipe isn't working (when it used to in the past.)
24 matches
Mail list logo
