Hi Gordon, 2014.09.23 10:52, Gordon Dickens wrote:
You mentioned Vexim in the attached post and, in a post on the exim-users(a)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?
to be fair, I use Vexim, but only on one server, which still runs Debian Squeeze. Hence, I'm not directly suffering from this problem. The reason why I follow this list and sometimes participate in it is because I also happen to be the current maintainer/reviewer of Vexim (although I've been quite passive in that regard recently, and I don't expect this to change back anytime soon). This particular problem we're discussing here was registered as Vexim issue #21 almost four weeks ago ( https://github.com/avleen/vexim2/issues/21 ), and I would like to fix it on our side, hoping that somebody will find a solution rather sooner than later. By the way, do you think it would be possible to have a working cooperation between Vexim and Exim4U? After all, we do share a lot of common code, and it doesn't seem very feasible to work on two copies of it independently. Rimas