Hi Again
Unfortunately the user currently experiencing the problem has deleted the
suspect emails so I am unable to check the header information.
I've looked in the vpopmail database and to be completely honest it all looks
in order.
I do have one additional piece of information, some output
Eric Shubert wrote:
Why is it that empF is not included in the stock toaster? Seems like a
nice feature to me.
Because Erik froze development on the 1.3 branch almost 2 years ago to
make time for the new version. I've been holding with this and
concentrating on the 2.0 branch - once the
Jake Vickers wrote:
Eric Shubert wrote:
Why is it that empF is not included in the stock toaster? Seems like
a nice feature to me.
Because Erik froze development on the 1.3 branch almost 2 years ago to
make time for the new version. I've been holding with this and
concentrating on the
Jake Vickers wrote:
Dave Hallowell wrote:
Glad to hear it worked. Now that you have the spec file patched, you
can create a new patch for others so they do not have to go through the
same process. Move the patched spec file to a new name, and then
install the .src.rpm
light goes on in Eric's head
That is indeed 'normal' behavior. Any mail addressed to
use...@domain.com is delivered to u...@domain.com. See man
dot-qmail, EXTENSION ADDRESSES section for an explaination.
Josh D. Dinsdale wrote:
Hi Again
Unfortunately the user currently experiencing the
Dave Hallowell wrote:
Jake Vickers wrote:
Dave Hallowell wrote:
Glad to hear it worked. Now that you have the spec file patched, you
can create a new patch for others so they do not have to go through the
same process. Move the patched spec file to a
2009/4/8 Dave Hallowell d...@acbsco.com:
Dave Hallowell wrote:
Jake Vickers wrote:
Dave Hallowell wrote:
Glad to hear it worked. Now that you have the spec file patched, you can
create a new patch for others so they do not have to go through the same
process. Move the patched spec file
A M wrote:
Hi all,
I miss the most of the comotion arround eMPF (work...) but I've to
point out the following:
The eMPF patch in itself should always apply error free in any
netqmail based qmail.
There are some issues with SRS, mainly because rules DO NOT take it
in cosideration... (code
Jake Vickers wrote:
A M wrote:
Hi all,
I miss the most of the comotion arround eMPF (work...) but I've to
point out the following:
The eMPF patch in itself should always apply error free in any
netqmail based qmail.
There are some issues with SRS, mainly because rules DO NOT take it
On Wed, Apr 8, 2009 at 9:38 PM, Jake Vickers j...@qmailtoaster.com wrote:
A M wrote:
Hi all,
I miss the most of the comotion arround eMPF (work...) but I've to
point out the following:
The eMPF patch in itself should always apply error free in any
netqmail based qmail.
There are
Dave Hallowell wrote:
How long have you been running the patch? I'm just loathe to add a
patch that I really don't have time to trouble shoot at this point,
especially if it has not been tested in length and make cause issues
with other things.
Once thing I've learned programming in Linux,
Hi Jake,
that would be correct. I created the empf patch yesterday and placed
into production yesterday. That was my very first attempt at creating
the patch. It is by no means stable. I was simply following your
suggestion to make it available to others. I understand and do not
expect you
I am getting messages about the auto whitelist yet I do not have that
feature enabled in my local.cf. How do I disable it and get this out of my
logs?
@400049dcf0ab20ea00a4 [9544] info: config: failed to parse line,
skipping, in (no file): use_auto_whitelist 1
@400049dcf0ab25aab14c
I figured out where I was having the problem with this. I had this set as a
$GLOBAL in my mysql table that is used to override my default spamassassin
rules.
Gilbert
- Original Message -
From: Gilbert T. Gutierrez, Jr. mailing-li...@phoenixinternet.net
To:
It appears we have now moved to 95.1
Gilbert
-
Managed Qmailtoaster servers are now available
Visit http://qmailtoaster.com/QMTManaged.html to order yours today!
Qmailtoaster is sponsored by
Greetings All,
I've just attempted to run qtp-newmodel on a CentOS 5.3 box.
All appeared to be going well until the build of 'spamassassin-toaster':
On my console, I got:
-
Building spamassassin-toaster-3.2.5-1.3.15 ...
Installing spamassassin-toaster-3.2.5-1.3.15 in the
Thanks for your reply, Jake.
We figured out what the problem was. One our less clueful users had done
two things to make a bit of a mess:
1) Set up a forward that was directed to both a remote address *and*
back to the forward itself(!)
and
2) Set up the same account as a 'catch-all'
Gilbert T. Gutierrez, Jr. wrote:
It appears we have now moved to 95.1
Gilbert
Saw that on the list earlier today. I'll work on getting a package up in
the next couple days. This version was only a bug fix version that did
not involve anything that pertains to how QMT uses it, so it's not a
Duncan Sterling wrote:
Greetings All,
I've just attempted to run qtp-newmodel on a CentOS 5.3 box.
All appeared to be going well until the build of 'spamassassin-toaster':
On my console, I got:
-
Building spamassassin-toaster-3.2.5-1.3.15 ...
Installing
Can i use procmail for this purpose? means, can i write userwise rules
in procmail?
Thanks and Regards,
S.Senthilvel,
On Sun, Apr 5, 2009 at 6:11 AM, Jake Vickers j...@qmailtoaster.com wrote:
senthil vel wrote:
Thanks Jake.. Can you please show me a direction to write a script for
this?
Jake Vickers wrote:
Duncan Sterling wrote:
Greetings All,
I've just attempted to run qtp-newmodel on a CentOS 5.3 box.
All appeared to be going well until the build of 'spamassassin-toaster':
On my console, I got:
-
Building spamassassin-toaster-3.2.5-1.3.15 ...
Jake Vickers wrote:
Duncan Sterling wrote:
Greetings All,
I've just attempted to run qtp-newmodel on a CentOS 5.3 box.
All appeared to be going well until the build of 'spamassassin-toaster':
On my console, I got:
-
Building spamassassin-toaster-3.2.5-1.3.15 ...
22 matches
Mail list logo
