Is anyone running v 1.2.3 and have clients with AVG email scanning?
I upgraded a server a few weeks ago (which ran Dovecot and the Maildir
mail store), and all of a sudden clients with AVG were unable to use
POP. Essentially, AVG freezes. The server upgrade was from FreeBSD 7
to OpenSolaris 2009.06, and I did upgrade the Dovecot version from
1.1.17 to 1.2.3, but kept the same config. When I point those users
to a port running qmail-popup on another machine (NFS mounting the new
server), they work fine. I'm sure I reverted to 1.1.17 during the
initial hectic days, with no change. Of course, I'm also sure I had a
few of the users test the alternate qmail-popup server, maybe they did
it wrong. :(
Any thoughts? Should I attach compile configs?
#/usr/local/sbin/dovecot -n
# 1.2.3: /usr/local/etc/dovecot.conf
# OS: SunOS 5.11 i86pc
base_dir: /opt/csw/dovecot/
protocols: imap imaps pop3s pop3
ssl_cert_file: /etc/ssl/mail.rapid.pem
ssl_key_file: /etc/ssl/mail.rapid.key
ssl_key_password: password
disable_plaintext_auth: no
shutdown_clients: no
login_dir: /opt/csw/dovecot//login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
login_greeting: VFEmail.net ready.
login_process_per_connection: no
login_process_size: 256
login_processes_count: 6
login_max_processes_count: 512
login_max_connections: 384
mail_max_userip_connections: 25
verbose_proctitle: yes
first_valid_uid: 89
last_valid_uid: 89
first_valid_gid: 89
last_valid_gid: 89
mail_privileged_group: mail
fsync_disable: yes
mail_executable(default): /usr/local/libexec/dovecot/rawlog
/usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/rawlog
/usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/rawlog
/usr/local/libexec/dovecot/pop3
mail_plugins(default): quota imap_quota
mail_plugins(imap): quota imap_quota
mail_plugins(pop3): quota
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
imap_client_workarounds(default): delay-newmail outlook-idle
netscape-eoh tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(pop3):
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
namespace:
type: private
separator: .
prefix: INBOX.
inbox: yes
list: yes
subscriptions: yes
lda:
postmaster_address: postmaster@vfemail.net
mail_plugin_dir: /usr/local/lib/dovecot/lda
sendmail_path: /var/qmail/bin/sendmail
auth_socket_path: /opt/csw/dovecot/auth-master
auth default:
mechanisms: plain login digest-md5 cram-md5
user: vpopmail
username_translation: %@
passdb:
driver: vpopmail
userdb:
driver: passwd
userdb:
driver: vpopmail
socket:
type: listen
master:
path: /opt/csw/dovecot/auth-master
mode: 384
user: vpopmail
plugin:
quota: maildir
On Wed, 2009-09-02 at 10:33 -0500, Rick Romero wrote:
Is anyone running v 1.2.3 and have clients with AVG email scanning? I upgraded a server a few weeks ago (which ran Dovecot and the Maildir
mail store), and all of a sudden clients with AVG were unable to use
POP. Essentially, AVG freezes.
Rawlog might be helpful. http://wiki.dovecot.org/Debugging/Rawlog
The server upgrade was from FreeBSD 7
to OpenSolaris 2009.06, and I did upgrade the Dovecot version from
1.1.17 to 1.2.3, but kept the same config. When I point those users
to a port running qmail-popup on another machine (NFS mounting the new
server), they work fine. I'm sure I reverted to 1.1.17 during the
initial hectic days, with no change.
You mean 1.1.17 also didn't help? So the problem might not even be related to Dovecot at all, but related to OS or hardware or network?
Quoting "Thomas Leuxner" <tlx@leuxner.net>:
Am 02.09.2009 um 17:33 schrieb Rick Romero:
Any thoughts? Should I attach compile configs?
If I remember correctly AVG uses a client-side proxy to scan the
mails. This could as well be broken with a recent update...
That was the original 'solution' and I thought it was coincidental to
my server change, but apparently if the user changes to hitting a
qmail-popd instance instead of Dovecot, it works.
I'm not convinced it's a pure dovecot issue, because before I switched
to OpenSolaris it worked fine on FreeBSD.
I had installed AVG, but haven't had a supported client to properly
test with (AVG hooked into my Bat! install, but it had expired).
Rick
Am 02.09.2009 um 18:28 schrieb Rick Romero:
I had installed AVG, but haven't had a supported client to properly
test with (AVG hooked into my Bat! install, but it had expired).
Think I had something in the past where it suddenly stopped to work
for encrypted sessions after an AVG update. Did you try with pure
unsecured POP3 too?
Yep, POP on port 110. If I have them change to port 113 (which
directs to qmail-pop3 on another server) I'm told it works fine.
IMAP works without any issues.
Rick
Quoting "Thomas Leuxner" <tlx@leuxner.net>:
Am 02.09.2009 um 18:28 schrieb Rick Romero:
I had installed AVG, but haven't had a supported client to properly
test with (AVG hooked into my Bat! install, but it had expired).Think I had something in the past where it suddenly stopped to work
for encrypted sessions after an AVG update. Did you try with pure
unsecured POP3 too?
On Wed, 2009-09-02 at 11:41 -0500, Rick Romero wrote:
Yep, POP on port 110. If I have them change to port 113 (which
directs to qmail-pop3 on another server) I'm told it works fine.
What if you make Dovecot listen on non-110 port? Because I'd guess non-110 port could just bypass AVG's checks..
Quoting "Timo Sirainen" <tss@iki.fi>:
On Wed, 2009-09-02 at 11:41 -0500, Rick Romero wrote:
Yep, POP on port 110. If I have them change to port 113 (which directs to qmail-pop3 on another server) I'm told it works fine.
What if you make Dovecot listen on non-110 port? Because I'd guess non-110 port could just bypass AVG's checks..
Hmm that's a thought. But what I want to achieve is no change to the
client. I already have port 112 point to Dovecot.
It would definitely be a good test to see if the port # change
disables AVG, cause then moving 110 back to the qmail-pop3 server
wouldn't have any affect, which with that new insight, I'm now even
more confident I already tried.
So now I'm leaning back towards AVG being an issue :(
Rick
participants (3)
-
Rick Romero
-
Thomas Leuxner
-
Timo Sirainen