ah ha! So I changed my webmail configuration to point to localhost 
(where imapproxy is installed) instead of my remote imap server and now 
I see stuff in my maillog

in.imapproxyd[12714]: LOGIN: 'mccordl' (127.0.0.1:48529) on new sd [9]
in.imapproxyd[12714]: LOGOUT: 'mccordl' from server sd [9]

Plus, my webmail login and mail access is still working so I'm guessing 
that it's truly working now.

Thanks,
Laura


On 11/8/11 12:00 PM, Ken D'Ambrosio wrote:
> Irksome.  Nothing looks obviously wrong.  I might take a look at your
> /var/log/imapproxy_protocol.log file and see if there's anything there that
> might be of use.  I also might try changing foreground_mode to "yes", and see
> if you can see it throw any errors when it's run.  (If you're not at the
> console, you'd have to run the executable directly.)  I'd also, for the Hell 
> of
> it, try to do a "telnet localhost 143"...
> Waitaminute.
> Where is your webmail going for IMAP?  Is it hitting the localhost IP
> (127.0.0.1), or the host's public IP/hostname?  It either needs to reference
> the localhost IP, or we need to re-configure your imapproxy.  I suddenly
> suspect this is your issue.
>
> -Ken
>
> On Tue, 08 Nov 2011 11:51:00 -0600 Laura McCord<mcco...@southwestern.edu>
> wrote
>
>    
>> Thanks Ken!
>>
>> Here's my sanitized imapproxy.conf file, though I am not allowed to send
>> anyone my server/ip even if it's harmless or I'll get in trouble :)
>>
>> It's mainly using the defaults so I am wondering if I need to configure
>> something on my horde webmail client to use imapproxy
>>
>> Also,  thanks for sharing the lsof command this is something I can stow
>> away for future use
>>
>> server_hostname my.imap.server
>> connect_retries 10
>> connect_delay 5
>> cache_size 3072
>> listen_port 143
>> server_port 143
>> cache_expiration_time 300
>> proc_username nobody
>> proc_groupname nobody
>> stat_filename /var/run/pimpstats
>> protocol_log_filename /var/log/imapproxy_protocol.log
>> syslog_facility LOG_MAIL
>> #syslog_prioritymask LOG_WARNING
>> send_tcp_keepalives no
>> enable_select_cache no
>> foreground_mode no
>> force_tls no
>> #chroot_directory /var/empty
>> enable_admin_commands no
>> #tls_ca_file /usr/share/ssl/certs/ca-bundle.crt
>> #tls_ca_path /usr/share/ssl/certs/
>> #tls_cert_file /usr/share/ssl/certs/mycert.crt
>> #tls_key_file /usr/share/ssl/certs/mycert.key
>>
>>
>> On 11/8/11 10:41 AM, Ken D'Ambrosio wrote:
>>      
>>> On Tue, 08 Nov 2011 10:35:39 -0600 Laura McCord<mcco...@southwestern.edu>
>>> wrote
>>>
>>>
>>>        
>>>> I guess because it was one of the prerequisites to doing Horde and CAS
>>>> (central authentication service) SSO authentication, that's my overall
>>>> goal.  Also, I keep reading that it's for better performance. I am
>>>> totally new to doing email administration and I am learning on the way
>>>> so I am very confused as to what's REALLY needed and what's just extra
>>>> stuff :D
>>>>
>>>>          
>>> Ah.  Okay; that makes some sense.  It does help with a performance boost --
>>> it keeps from having to re-open TCP connections, and re-authenticate the
>>> IMAP sessions, each time something is done.  If you don't mind, could you
>>> send me your configuration file for imapproxy?  It would also be helpful if
>>> you included the name or IP of your IMAP server.  (I don't think there's
>>> anything potentially harmful in there -- e.g., passwords -- but take a
>>> quick scan, first.)
>>>
>>> I'm guessing your newness has led you down the wrong path; don't worry --
>>> we were all new to this at one point or another.
>>>
>>> -Ken
>>>
>>> P.S. The "lsof" command shows -- or, rather, LiSts -- Open Files.  The "-i"
>>> parameter says "show open ports, instead" and the "-P" says "don't try to
>>> name the port (e.g., "imap"), just return the port number ("143")".
>>>
>>>
>>>        
>>>> Laura
>>>>
>>>>
>>>> On 11/8/11 10:28 AM, Ken D'Ambrosio wrote:
>>>>
>>>>          
>>>>> I'm somewhat confused, then.  Why bother with a proxy?  Why not just
>>>>> point your webmail client straight to the remote host's port 143?
>>>>>
>>>>> -K
>>>>>
>>>>> On Tue, 08 Nov 2011 10:27:44 -0600 Laura McCord<mcco...@southwestern.edu>
>>>>> wrote
>>>>>
>>>>>
>>>>>
>>>>>            
>>>>>> Hi Ken,
>>>>>>
>>>>>> I get the following when executing that line:
>>>>>>
>>>>>> in.imappr 1462 nobody    5u  IPv4 1486723      0t0  TCP
>>>>>> localhost.localdomain:143 (LISTEN)
>>>>>>
>>>>>> I haven't configured anything on my imap server....I don't have admin
>>>>>> access to that server yet.   I do know that when I setup imp I can login
>>>>>> without a secure connection using port 143,  if that answers anything.
>>>>>>
>>>>>> Thanks,
>>>>>> Laura
>>>>>>
>>>>>> On 11/8/11 10:16 AM, Ken D'Ambrosio wrote:
>>>>>>
>>>>>>
>>>>>>              
>>>>>>> lsof -i -P | egrep "imap|143"
>>>>>>>
>>>>>>>
>>>>>>>                
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>            
>>>
>>>
>>>
>>>
>>>        
>
>
>
>
>    


------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
-----
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

Reply via email to