thanks for your help, migration to spamc/spamd wouldn't be the problem -> it's even
planned within the next half year. there is only one reason this hasn't been done so far:
there is no desicion from the company management if the want to use only spamc/spamd
or if they want to use amavis-new in combination with spamc/spamd and a virusscan (e.g. clamav-new).
so i have to wait for their decision - that's the problem.
Yeah, so? Why should this inhibit you from using spamd now?
so my idea to reduce the load/ramusage of the mailserver was to just modifiy
the filter.sh that it only passes mails smaller then 100kb to spamassassin (as a fast solution/hack).
why are the modifications in the filter.sh harder then the migration to spamc/spamd?
The main reason is that conversion to spamc is completely trivial.... It's so absurdly trival that doing nearly anything else is going to be harder:
1) start spamd
2) make sure you have an init script to start spamd on boot (there's plenty around for the taking)
3) modify filter.sh so that SPAMASSIN is now spamc not spamassassin
That's it.. you're done.
if [ "$SIZE" <= "100" ]
but this doesn't work that way.
Exactly, because there's no easy way from a shell script to know how big your input stream is until you've already read it.
This is why modifying filter.sh is going to be harder than converting to spamd. Converting to spamd is easy. Doing a really strange hack to a shell script is difficult.
