Please reply to the list, not to me and please don't top post, thank you. >> > Fist time poster here. Just needed bit of more info with imapprxy >> > server. I >> > just installed the imapproxy on my redhat 6 by following README doc .. >> > configure, make and make install. That all worked. >> > >> > I have a webclient on test0 >> > then imapproxy is installed on test0 too >> > >> > then imapserver is on test1 >> > >> > here is the /etc/imapproxy.conf looks like : >> > ## imapproxy.conf >> > ## >> > server_hostname test1 >> > #connect_retries 10 >> > #connect_delay 5 >> > cache_size 80 >> > listen_port 143 >> > listen_address 127.0.0.1 >> > server_port 143 >> > cache_expiration_time 300 >> > proc_username imapproxy >> > proc_groupname imapproxy >> > stat_filename /var/run/pimpstats >> > protocol_log_filename /var/log/imapproxy_protocol.log >> > syslog_facility LOG_MAIL >> > send_tcp_keepalives no >> > enable_select_cache no >> > foreground_mode no >> > force_tls no >> > enable_admin_commands no >> > >> > port 143 is opened on test0 so as on test1 then here is the netstat >> > output >> > tcp 0 0 127.0.0.1:143 0.0.0.0:* >> > LISTEN >> > >> > how can I make sure my imappoxy server is caching or is there a way to >> > see >> > if my imapproxy is in effect ? >> >> * Simple - if the webmail client is logging into port 143 on test0 >> (and there's no conflict on that port/machine), then it's working. >> >> * You can also log in by hand and watch some of the server responses, >> which will be slightly different than your normal IMAP server >> >> * Your /var/log/maillog on test0 will show imapproxy entries when users >> log in >> >> * Use pimpstat (should be in /usr/local/sbin) > > Thanks for your reply and hint. now my imapproxy looks working, I can see > log in /var/log/maillog as : > > Apr 19 13:29:26 test0 in.imapproxyd[29344]: LOGOUT: '"skytest"' from server > sd [9] > Apr 19 13:29:26 test0 in.imapproxyd[29344]: LOGIN: '"skytest"' > (127.0.0.1:49125) on ex > > I can also see statistics on pimpstat. but it says SELECT CACHE NOT ENABLED, > in order to cache the imap connectin do I need to enable this option on > /etc/imapproxy.conf ?
Yes, exactly. Note that the SELECT cache is not widely used yet, or at least I don't know if there's been a lot of feedback on how well it works or how useful it is. There's some information in the documentation about this I believe. >> > I do not see any logs in /var/log/imapproxy_protocol.log >> >> Wrong file. Try the mail log. >> >> > but >> > /var/log/messages I see : >> > Apr 18 14:27:48 test0 in.imapproxyd: main(): Using default configuration >> > file '/etc/imapproxy.conf'. >> > Apr 18 14:27:48 test0 in.imapproxyd: Using syslog facility 'LOG_MAIL' >> > for >> > logging. >> >> Wrong file again. /var/log/maillog is what you want. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ----- squirrelmail-imapproxy mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-imapproxy@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.imapproxy List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-imapproxy
