gmane.mail.squirrelmail.imapproxy

Re: request info on SquirrelMail

Paul Lesniewski — 2012-03-03T23:41:09

You found the mailing lists for SquirrelMail, but failed to use the
right one.  Please try the squirrelmail-users mailing list in the
future.


I think it'd be quite possible to implement it in your own skin for
version 1.5.2, possibly in tandem with a plugin that handles the
multiple simultaneous uploads from the compose page template.

For the 1.4.x series, I don't believe this is currently supported by
any plugins, so I decided to see if I could throw together a proof of
concept, which was successful.  I don't really have time to finish it
and can't give you an ETA (unless someone wants to sponsor the time
needed to finish it off).  Otherwise, just keep an eye on the new
plugin releases every once in a while and it'll get published
eventually.

request info on SquirrelMail

La Principessa customer service ITALIA — 2012-02-16T21:55:05

Hi,

My name is Francesco, I do not know if this is the right place to ask this kind of information,
but I didn't find other way to ask information and support on SquirrelMail.

We use SqurrelMail as email addresses for our firm and we work a lot with emails, we have a question:

Is't possible to add to email message more attached files in 1 time, and not just one by one?
Should we use some plug-in, or could You please suggest some other way to do it?

Really Thank You, and sorry if this is not the right place to ask it.

Francesco





------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

Re: SSL initialization logic error

Paul Lesniewski — 2011-12-31T18:15:16

You're right.  Thanks for contributing to more clarity for the users
of this tool.

Thanks,

  Paul

Re: SSL initialization logic error

Orion Poplawski — 2011-12-31T15:24:50

Looks like that would work as well.  However, after thinking about it 
some more I think something like this would be better:

int r;
if (PC_Struct.tls_ca_file != NULL || PC_Struct.tls_ca_path != NULL ) {
   r = SSL_CTX_load_verify_locations( tls_ctx, PC_Struct.tls_ca_file, 
PC_Struct.tls_ca_path );
} else {
   r = SSL_CTX_set_default_verify_paths( tls_ctx );
}
if (r == 0) {
      syslog(LOG_ERR, "%s: Failed to load CA data. exiting.", fn);
      exit( 1 );
}

That way if someone specifies a path and it fails to initialize 
imapproxy fails to start rather than silently reverting to the ssl defaults.

Re: SSL initialization logic error

Paul Lesniewski — 2011-12-31T06:17:30

Nice catch.  I think I prefer just changing the || to && as follows instead:

        if ( ! SSL_CTX_load_verify_locations( tls_ctx,
                                                PC_Struct.tls_ca_file,
                                                PC_Struct.tls_ca_path ) &&
            ! SSL_CTX_set_default_verify_paths( tls_ctx ) )

Seem OK with you?

SSL initialization logic error

Orion Poplawski — 2011-12-31T03:38:00

in main.c the logic for for SSL CA init is incorrect:

--- squirrelmail-imap_proxy-1.2.7/src/main.c.sslinit    2010-07-26 
01:21:19.000000000 -0600
+++ squirrelmail-imap_proxy-1.2.7/src/main.c    2011-12-30 
20:25:31.495721931 -0700
< at >< at > -490,10 +490,10 < at >< at > int main( int argc, char *argv[] )
             /* Work around all known bugs */
             SSL_CTX_set_options( tls_ctx, SSL_OP_ALL );

-           if ( ! SSL_CTX_load_verify_locations( tls_ctx,
+           if ( ! ( SSL_CTX_load_verify_locations( tls_ctx,
                                                   PC_Struct.tls_ca_file,
                                                   PC_Struct.tls_ca_path 
) ||
-                ! SSL_CTX_set_default_verify_paths( tls_ctx ) )
+                    SSL_CTX_set_default_verify_paths( tls_ctx ) ) )
             {
                 syslog(LOG_ERR, "%s: Failed to load CA data. 
Exiting.", fn);
                 exit( 1 );


If SSL_CTX_load_verify_locations fails (returns 0) you want to try 
SSL_CTX_set_default_verify_paths.  Then if both fail you want to error 
out.  In the current code, if no tls_ca_file or tls_ca_path is specified 
it never calls SSL_CTX_set_default because one half of the or succeeded.

Re: [PATCH] header fix for config.h

Paul Lesniewski — 2011-12-16T17:58:26

Committed.  Thanks so very much for your attention to detail.  We
really appreciate your help.

Re: [PATCH] Makefile cleanup

Paul Lesniewski — 2011-12-16T17:57:26

Hi Brad,

On Fri, Dec 2, 2011 at 1:14 AM, Brad <brad< at >comstyle.com> wrote:

Committed.  Thanks once again!

  - Paul

[PATCH] Makefile cleanup

Brad — 2011-12-02T09:14:03

Here is a small diff to cleanup the Makefile variables handling a bit.
I noticed because of the current CFLAGS handling CFLAGS was picked up
from both autoconf and make instead of just autoconf as expected.


Index: Makefile.in
===================================================================
--- Makefile.in(revision 14153)
+++ Makefile.in(working copy)
< at >< at > -23,11 +23,12 < at >< at >
 mandir = $(prefix)/man/man3
 
 CC = < at >CC< at >
-CPPFLAGS = < at >CPPFLAGS< at > 
+CPPFLAGS = < at >CPPFLAGS< at >
+CFLAGS = < at >CFLAGS< at >
 LDFLAGS = < at >LDFLAGS< at >
 LIBS = < at >LIBS< at >
 DEFINES = < at >DEFINES< at >
-FLAGS = $(CPPFLAGS) < at >CFLAGS< at > -I. -I./include
+FLAGS = -I. -I./include
 
 INSTALL = < at >INSTALL< at >
 EBIN = $(sbindir)
< at >< at > -63,7 +64,7 < at >< at >
 $(XYD_OBJ) $(TAT_OBJ): $(MAKEFILE) ./include/common.h ./include/imapproxy.h
 
 .c.o:
-$(CC) $(CFLAGS) $(FLAGS) -c -o $< at > $<
+$(CC) $(CFLAGS) $(FLAGS) $(CPPFLAGS) -c -o $< at > $<
 
 $(XYD_BIN): $(XYD_OBJ)
 $(CC) -o $< at > $(XYD_OBJ) $(LDFLAGS) $(XYD_LIB)

[PATCH] header fix for config.h

Brad — 2011-12-02T09:11:34

Here is a header fix for config.h which includes sys/mman.h and on OpenBSD
you have to include sys/types.h before sys/mman.h


Index: config.h.in
===================================================================
--- config.h.in(revision 14153)
+++ config.h.in(working copy)
< at >< at > -89,6 +89,10 < at >< at >
 /* Define to empty if `const' does not conform to ANSI C. */
 #undef const
 
+#if HAVE_SYS_TYPES_H
+#include <sys/types.h>
+#endif
+
 #if HAVE_SYS_MMAN_H
 #include <sys/mman.h>
 #endif

Re: [PATCH] Add DESTDIR support for Makefile

Paul Lesniewski — 2011-11-23T20:53:48

Committed to SVN.  Thank you.

Re: [PATCH] Add DESTDIR support for Makefile

Brad — 2011-11-23T18:29:34

Yes, Brad Smith.

Re: [PATCH] Add DESTDIR support for Makefile

Paul Lesniewski — 2011-11-23T11:27:46

Looks good.  Thank you.  Do you have a full name for attribution?  :)

Cheers,

Paul

[PATCH] Add DESTDIR support for Makefile

Brad — 2011-11-20T02:26:53

The following diff adds DESTDIR support to imapproxy's Makefile.


Index: imapproxy.spec
===================================================================
--- imapproxy.spec(revision 14151)
+++ imapproxy.spec(working copy)
< at >< at > -50,7 +50,7 < at >< at >
 install -d $RPM_BUILD_ROOT/etc/init.d
 install -d $RPM_BUILD_ROOT/%{prefix}/sbin
 
-make prefix=$RPM_BUILD_ROOT%{prefix} rpm_prefix=$RPM_BUILD_ROOT  rpm-install
+make DESTDIR=$RPM_BUILD_ROOT rpm-install
 
 %clean
 rm -rf $RPM_BUILD_ROOT
Index: Makefile.in
===================================================================
--- Makefile.in(revision 14151)
+++ Makefile.in(working copy)
< at >< at > -21,7 +21,6 < at >< at >
 infodir = $(prefix)/info
 libdir = $(prefix)/lib/gnudl
 mandir = $(prefix)/man/man3
-rpm_prefix = < at >rpm_prefix< at >
 
 CC = < at >CC< at >
 CPPFLAGS = < at >CPPFLAGS< at > 
< at >< at > -79,21 +78,21 < at >< at >
 rm -f config.cache config.log config.h Makefile
 
 install: $(XYD_BIN) $(TAT_BIN)
-mkdir -p $(EBIN)
-$(INSTALL) -o bin -g bin -m 0755 $(XYD_BIN) $(EBIN)
-$(INSTALL) -o bin -g bin -m 0755 $(TAT_BIN) $(EBIN)
+mkdir -p $(DESTDIR)$(EBIN)
+$(INSTALL) -o bin -g bin -m 0755 $(XYD_BIN) $(DESTDIR)$(EBIN)
+$(INSTALL) -o bin -g bin -m 0755 $(TAT_BIN) $(DESTDIR)$(EBIN)
 
 install-init-linux:
-$(INSTALL) -o root -g sys -m 0755 ./scripts/imapproxy-linux.init $(ETC)/init.d/imapproxy
-ln -s ../init.d/imapproxy /etc/rc2.d/S99imapproxy
-ln -s ../init.d/imapproxy /etc/rc0.d/K10imapproxy
+$(INSTALL) -o root -g sys -m 0755 ./scripts/imapproxy-linux.init $(DESTDIR)$(ETC)/init.d/imapproxy
+ln -s ../init.d/imapproxy $(DESTDIR)/etc/rc2.d/S99imapproxy
+ln -s ../init.d/imapproxy $(DESTDIR)/etc/rc0.d/K10imapproxy
 
 install-conf:
-$(INSTALL) -o root -g bin -m 0644 ./scripts/imapproxy.conf $(ETC)
+$(INSTALL) -o root -g bin -m 0644 ./scripts/imapproxy.conf $(DESTDIR)$(ETC)
 
 rpm-install: install 
-$(INSTALL) -o root -g sys -m 0644 ./scripts/imapproxy.conf $(rpm_prefix)/etc
-$(INSTALL) -o root -g sys -m 0755 ./scripts/imapproxy-linux.init $(rpm_prefix)/etc/init.d/imapproxy
+$(INSTALL) -o root -g sys -m 0644 ./scripts/imapproxy.conf $(DESTDIR)/etc
+$(INSTALL) -o root -g sys -m 0755 ./scripts/imapproxy-linux.init $(DESTDIR)/etc/init.d/imapproxy
 
 pkg:
 pkgmk -o -r .

Re: imap proxy working?

Laura McCord — 2011-11-10T20:10:48

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:


------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1

Re: imap proxy working?

Paul Lesniewski — 2011-11-09T19:15:11

Looks like it's working, then, right?  Did you have any other question?

You can also run pimpstat to see imapproxy's live statistics to verify
that it's working, or just telnet to the port you have it listening
on, and the CAPABILITY reply you should see will include "XIMAPPROXY"
which verifies that you are using imapproxy.

Re: imap proxy working?

Ken D'Ambrosio — 2011-11-08T16:16:39

What happens when you do an 'lsof -i -P | egrep "imap|143" '?  Have you changed
your IMAP daemon to be on a different port, to which the proxy points?

-Ken

On Tue, 08 Nov 2011 10:05:17 -0600 Laura McCord <mccordl< at >southwestern.edu>
wrote







------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1

Re: imap proxy working?

Laura McCord — 2011-11-08T16:27:44

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:


------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1

imap proxy working?

Laura McCord — 2011-11-08T16:05:17

Hi,

I installed imap proxy and I am testing it and I just can't tell what I 
am supposed to be looking for or if I need to start troubleshooting. I 
have the following in my /var/log/maillog and anytime I login to my 
webmail client I don't see any transactions it only displays the 
following when I start up imapproxy.

Nov  8 09:44:26 webmail  in.imapproxyd[1459]: No syslog priority mask 
specified.
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: main(): SELECT caching is 
disabled
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: main(): Internal admin 
commands are disabled
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: main(): Allocating 3072 
IMAP connection structures.
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: ServerInit(): Using 
'/var/log/imapproxy_protocol.log' for global protocol logging file.
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: ServerInit(): proxying to 
IMAP server 'imap.server.com'.
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: ServerInit(): Proxying to 
IMAP port 143
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: main(): Binding to tcp 
127.0.0.1:143
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: main(): Using global 
statistics file '/var/run/pimpstats'
Nov  8 09:44:26 webmail  in.imapproxyd[1459]: Daemonize(): Configured to 
run in background mode.
Nov  8 09:44:26 webmail  in.imapproxyd[1462]: BecomeNonRoot(): Process 
will run as uid 99 (nobody) and gid 99 (nobody).
Nov  8 09:44:26 webmail  in.imapproxyd[1462]: main(): Launched ICC 
recycle thread with id -1376848128
Nov  8 09:44:26 webmail  in.imapproxyd[1462]: main(): imapproxy version 
1.2.7 normal server startup.

Thanks.



------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1

Re: IMAPTalk: error parsing atom in IMAP responsefrom up-imapproxy

Paul Lesniewski — 2011-11-01T15:28:53

Perfect.  Thanks, Dave, for taking the time to do what I should have
done before replying.  We'll remove the space.

Re: IMAPTalk: error parsing atom in IMAP response from up-imapproxy

Dave McMurtrie — 2011-11-01T13:21:49


I'd say the extra space in 1081/1082 is a bug.  If you read the formal 
syntax section in RFC 3501 (Section 9), it seems to clarify that the 
CAPABILITY response should be single-space separated.

First, the RFC clarifies exactly what SP means in the BNF.

"(2) In all cases, SP refers to exactly one space.  It is NOT permitted 
to substitute TAB, insert additional spaces, or otherwise treat SP as 
being equivalent to LWSP."

Then where capability-data is later defined we can see that it is SP 
separated tokens.

capability-data = "CAPABILITY" *(SP capability) SP "IMAP4rev1"
                   *(SP capability)
                     ; Servers MUST implement the STARTTLS, AUTH=PLAIN,
                     ; and LOGINDISABLED capabilities
                     ; Servers which offer RFC 1730 compatibility MUST
                     ; list "IMAP4" as the first capability.


If you look at the imapproxy code before the XIMAPPROXY patch was added, 
it would always output a CAPABILITY string with single spaces between 
each token.  Further, you'll notice that imapproxy itself expects the 
CAPABILITY string to be SP separated tokens in the code that has to 
parse the CAPABILITY response to strip out things that can't be supported.

hth!

Dave

------------------------------------------------------------------------------
RSA&reg; Conference 2012
Save &#36;700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1