Hi Shah,
You mentioned Vexim in the attached post and, in a post on the�
exim-users@exim.org mailing list, you said that you were using
Vexim.� So, please clarify; Are you using Exim4U or Vexim?
Also, others have mentioned Vexim too.� So, I ask the same
question of Rimas Kudelis, Harald Valkanover and anyone else
having this problem;� Are you using Exim4U or Vexim?
Thanks,
Gordon
On 09/22/2014 08:00 PM, Shamim Shahriar wrote:
On 23/09/2014 00:32, Gordon Dickens
wrote:
I have not tested exim4u with exim
4.84 and I may not have the resources or time to test it for
quite a while, maybe for several months.� Harald Valkanover's
suggestion to comment out the headers_remove statements that
are causing problems may fix the problem. Other things to try
would be:
- Disable subject tagging as described in
exim4u_global_spam_virus.� Subject tagging may be disabled by
setting the tag score in the web interface to be equal to or
greater than the discard score for each user and domain.� This
may or may not solve the problem but is worth a try.
- Disable Spamassassin by setting SpamRejectScore = 100 in
exim4u_global_spam_virus.� I think that this would definitely
solve the problem.
- Anybody that has the inclination is welcome to debug this
problem.� Please post your solution so that it can be added to
the stock exim4u config.
Otherwise, you need to run an exim version prior to 4.84 until
someone has the time to study this further.
FYI,
Gordon
Hi Gordon
Thank you for the suggestions. The process of disabling features
or removing global options, IMHO, is not a "fix", these are
workarounds; and these workarounds are nothing but compromising
the much needed features/functionalities that the users
need/expect. Otherwise people would have used some other
combination rather than Exim with exim4u or vexim. But as you
stated, Exim v4.82 seem to be the last known functional setup, and
hopefully people can still get by with that.
As for testing and sending feedbacks, I think the people who are
suffering the most are not really "programmers" in the classical
sense and are merely end users with functional knowledge of what
is supposed to do happen at different configuration changes --
much of the v4.84 is implying that their knowledge, may be
gathered over many years, are uselss -- irrespective of whether
that is intended or a software glitch, and that is what got
everyone befuddled. I for example am not happy with the defunct
headers_remove section which, despite the non-effective solutions
suggested so far, works flawlessly with v4.82, and the same lookup
mysql works elsewhere except for the headers_remove section. This,
as I understand, is inconsistency -- which needs "fixing" as
opposed to taking a detour.
Please don't get me wrong, I do appreciate your suggestions and
comments, and understand your lack of time for testing and
debugging -- but that does not change the fact that both the vexim
and exim4u community members (and users) are left with systems
that they cannot patch, even if there is a major security issue,
simply because that would make their setup disfunctional and
useless. And I sincerely hope that proper solution will not take
so long that by that time both the vexim and exim4u users will be
forced to look for an alternate.
Just my 2p
Best regards
Shah
_______________________________________________
users mailing list
users@exim4u.org
https://exim4u.org/mailman/listinfo/users