Does not work on systems where python 3.4 is the default environment

[code-chicken]

As already written in the subject: I had to set the default environment to python2.7 to make this brilliant scanner work.

[ercpe]

Hi,

I'm glad to hear that AmavisVT is useful to you.
What problem did you encounter with Python 3.4? The test suite is passing on Python 3.4 so this should work (although I haven't tested it on a production server).

[code-chicken]

Unfortunately I don't get many messages. To answer your question I just set my environment back to python3.4:

centaur ~ # eselect python list
Available Python interpreters:
[1] python2.7 *
[2] python3.4
centaur ~ # eselect python set 2
centaur ~ # eselect python list
Available Python interpreters:
[1] python2.7
[2] python3.4 *

When I now start the amavisvt daemon and send any messages to the server I get the following messages:

Jan 21 17:04:28 centaur amavisvt[13771]: MainThread - Starting up
Jan 21 17:04:28 centaur amavisvt[13771]: MainThread - loading new configuration
Jan 21 17:04:28 centaur amavisvt[13771]: MainThread - Read configuration files: ['/etc/amavisvt.cfg']
Jan 21 17:06:22 centaur amavis[8665]: (08665-18) (!)AmavisVTd: Empty result from /var/amavis/amavisvtd.sock, retrying (2)
Jan 21 17:06:28 centaur amavis[8665]: (08665-18) (!)AmavisVTd av-scanner FAILED: run_av error: Too many retries to talk to /var/amavis/amavisvtd.sock (Empty result from /var/amavis/amavisvtd.sock) at (eval 99) line 600.\n

If I switch back to python2.7 everything is fine again after I restart the amavisvt daemon.

Hope this helps. Let me know if I can do something which will give you more information. Unfortunately with python3.4 the daemon doesn't write much information to the syslog even with -vvvvv in /etc/conf.d/amavisvt. Actually it writes tons of information to the syslog when my Gentoo box is set to python2.7.