hi,
Your plug-in approach seems to me more transparent too, if we don't
consider patching the qmail system. It is easy for a programmer or a
good administrator. Also it will be easy if you use netqmail
distribution. But mostly the situation is not like above.
Anyway it is not a problem to include both features. :)
Thanks for your comments,
Baris Simsek
http://www.enderunix.org/simsek/
Mark Bronstein wrote:
I think what the qmailqueue patch does is have qmail-smtp check the
environment variable QMAILQUEUE to see if an alternative program to
bin/qmail-queue should be run. See
http://www.memoryhole.net/qmail/qmailqueue-patch. This patch is
included in the net-qmail distribution
So by setting QMAILQUEUE to "bin/qmail-qsheff" either in the run file or
in tcprules. qsheff would run instead of qmail-queue. What I'm not sure
of is whether qmail-qsheff needs to be changed to have it forward to
qmail-queue. It looks like qmail-qsheff may already do that. Not sure
though.
What I like about using this "plug in" approach, is that it seems to me
to be a more transparent approach then your "wrapper" approach. I'm sure
others would disagree. But it as long as qsheff does or could hand off
to qmail-queue when it is done, then either approach would be possible.
Mark
Baris Simsek wrote:
hi Mark,
I don't know details, how to qmailqueue patch works. If I am wrong
correct me please, it looks for an environment variable to execute an
external program before running qmail-queue???
If it works like this, adding this feature will be easy. qsheff
executes qmail-queue by itself. So If qmailqueue patch is enabled,
qsheff will perform filtering but won't execute qmail-queue, because
of it is already running.
It is in my todo list ;)
regards,
Baris Simsek
http://www.enderunix.org/simsek/
Mark Bronstein wrote:
Thanks Baris,
Do you have on your list of upgrades to allow the option of
installing qsheff to run as a plugin using the QMAILQUEUE_PATCH,
rather than have to use your wrapper around djb's qmail-queue
executable?
Thanks again for your work on this software,
Mark
Baris Simsek wrote:
Hello,
I am aware of that. I am going to change the wblist parser. Please
wait for 2.0. it will be released in 2 weeks with some cool features
like full regular expression support, custom return message to
senders include spam word or virusname...
Thanks for your feedbacks.
regards,
Baris Simsek
http://www.enderunix.org/simsek/
Mark Bronstein wrote:
Thanks Jaymer. I guess its good to confirm that there is a
problem. I hope we can get some help resolving it since I do think
the basic design of the program is good.
Mark
Jaymer wrote:
hi mark
i have a 30-40 item REJECT list, and never used the
ACCEPTS.
but i've found 'wierdness' as well... seems like on
the last r4 release (which i had to upgrade to on new
years eve cause everything mysteriously quit working)
i started receiving email which had previously been
filtered.
i clearly have, for example, [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> in the
REJECT list, yet email still arrives when addressed to
that entry... and i know for sure that all that wasn't
coming through prior to that release. i have not tried
r5. sorry i can't help specifically, but at least i
answered in english :) and you got a reply... i
usually don't get replies.
jaymer...
PS _ having said that, i modified my wbl file and
added this
ACCEPT [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
REJECT @mydomain.com
i successfully sent mail to [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
i added a user [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> and sent
an email
which was accepted, even though it appears to violate
the generic REJECT rule.
then i added REJECT [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> and
it WAS
rejected finally.
SO, i have the opposite experience as you, but still
incorrect if, by design, we are supposed to be able to
filter at the domain level.
--- Mark Bronstein <[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]> wrote:
Can someone explain how to use multiple wblist rules
together?
I want to limit incoming mail to a few known users and assume
mail to anyone else is just spam.
so I tried the following rules which I had thought
should only allow mail in addressed to user1 and user2 and reject
the
rest:
ACCEPT [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ACCEPT
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
REJECT @domain.com
This doesnt seem to work. All mail to domain.com
ends up being rejected.
TIA,
Mark Bronstein
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
