I see that, snprintf is not working in your box. I know, it is not a
portable function but the modern OSs already has this function.
Let me check Core 2, if it fails I'll inform you. If not, as result the
problem connected to your linux box.
Please note that qSheff tested on Suse 10 for Linux compatibility.
Baris Simsek
http://www.enderunix.org/simsek/
Jaymer wrote:
hi Baris - that is great...
but even without messing with forbidden_header_lines,
why would I get the generic error msgs:
01/03/06 02:02:14: , error=`', hint=`'
01/03/06 02:08:36: , error=`', hint=`'
i can live without the header_lines, but in my case, I
just cannot get v2 to work.
any ideas?
thx
jaymer...
--- Baris Simsek <[EMAIL PROTECTED]> wrote:
Hi Jaymer,
I just remember this issue, sorry.
But I have a great idea, I am removing subject
filter and adding a
generic header filter.
h:(^Subject: spam)
h:(alpha)
something like this. This is more flexible and
usable. You can examine
any field in the header as well as Subject field..
Good news, it is ready ;) But give me 2 week. i want
to get other
responses about 2.0.
thanks,
Baris Simsek
http://www.enderunix.org/simsek/
Jaymer wrote:
hi
thx for the release... am looking forward to
trying
new features.
i installed per the readme, but immediately got an
error at runtime after restarting qmail.
since you need to examine the conf file each time
you
install qsheff... and since I'd tried this with no
success on v1r4, i thought i'd use
forbidden_header_lines and entered 2 tokens...
"alpha|beta" and sent myself a test email.
it was incorrectly rejected with a header error:
01/03/06 02:01:41: HEADER,
queue=q-1141196501-238100-6861,
recvfrom=68.142.201.239, [EMAIL PROTECTED]',
[EMAIL PROTECTED]', subj=`test', size=1007
so i figured this wasn't fixed in this release and
took everything out leaving:
forbidden_header_lines = ""
then all i started getting was:
01/03/06 02:02:14: , error=`', hint=`'
01/03/06 02:08:36: , error=`', hint=`'
i uninstalled, and went back to 1.0r4 and all
worked
fine.
jaymer...
fedora core 2
not using qmailaueuepatch
---------------------------------------------------------------------
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]
