Menu
▾
▴
squirrelmail-imapproxy — SquirrelMail IMAP Proxy Mailing List
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(6) |
Oct
(5) |
Nov
(6) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(6) |
Feb
(1) |
Mar
|
Apr
(9) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(14) |
Dec
(8) |
| 2012 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(3) |
Oct
|
Nov
|
Dec
(5) |
| 2013 |
Jan
(2) |
Feb
(6) |
Mar
|
Apr
(4) |
May
|
Jun
(2) |
Jul
|
Aug
(7) |
Sep
|
Oct
|
Nov
(9) |
Dec
|
| 2014 |
Jan
(10) |
Feb
|
Mar
(5) |
Apr
(1) |
May
(2) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(6) |
Sep
(15) |
Oct
|
Nov
|
Dec
(4) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jorge L. P. <jor...@us...> - 2012-12-19 07:31:35
|
Hi everybody, we've been running imapproxy for several months with great success, but we're having some trouble trying to understand the pimpstat output. Are there any docs about the meaning of each metric? We've been unable to find them. Specifically we'd like to know the meaning of "Client connections", "Active server connections" and "Cached server connections". Thank you very much! Regards. -- Jorge López Pérez jabber: jor...@im... |
|
From: ANANT S A. <as...@is...> - 2012-09-05 13:18:08
|
Dear Paul Lesniewski,
Thank you very much for clarifying my doubts.
Regards,
Anant.
----- Message from Paul Lesniewski <pa...@sq...> ---------
Date: Mon, 3 Sep 2012 23:58:29 -0700
From: Paul Lesniewski <pa...@sq...>
Reply-To: pa...@sq..., SquirrelMail IMAP Proxy Mailing List
<squ...@li...>
Subject: Re: [SM-imapproxy] Clarification on number of IMAP proxies
To: SquirrelMail IMAP Proxy Mailing List
<squ...@li...>
> On Mon, Sep 3, 2012 at 8:09 PM, ANANT S ATHAVALE <as...@is...> wrote:
>> Dear List,
>>
>> I have one Cyrus IMAP server running on server 1. I also run,
>> imapproxy on the same server and connect the IMAP server using this.
>>
>> Now that one IMAPproxy is already connecting to Cyrus IMAP server, is
>> it advisable to run one more IMAP proxy on server 2 (different server)
>> and connect to Cyrus IMAP server running on Server1?
>
> Nothing stopping you from doing that. It really depends on your
> network as well as what the usage of the servers is. I'd probably use
> a separate proxy instance on each server unless the same users could
> be connecting to either server at any time, during their same usage
> session.
>
> --
> Paul Lesniewski
> SquirrelMail Team
> Please support Open Source Software by donating to SquirrelMail!
> http://squirrelmail.org/donate_paul_lesniewski.php
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> -----
> squirrelmail-imapproxy mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.imapproxy
> List info (subscribe/unsubscribe/change options):
> https://lists.sourceforge.net/lists/listinfo/squirrelmail-imapproxy
----- End message from Paul Lesniewski <pa...@sq...> -----
Anant
------------------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
------------------------------------------------------------------------------
|
|
From: Paul L. <pa...@sq...> - 2012-09-04 06:59:03
|
On Mon, Sep 3, 2012 at 8:09 PM, ANANT S ATHAVALE <as...@is...> wrote: > Dear List, > > I have one Cyrus IMAP server running on server 1. I also run, > imapproxy on the same server and connect the IMAP server using this. > > Now that one IMAPproxy is already connecting to Cyrus IMAP server, is > it advisable to run one more IMAP proxy on server 2 (different server) > and connect to Cyrus IMAP server running on Server1? Nothing stopping you from doing that. It really depends on your network as well as what the usage of the servers is. I'd probably use a separate proxy instance on each server unless the same users could be connecting to either server at any time, during their same usage session. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: ANANT S A. <as...@is...> - 2012-09-04 03:09:21
|
Dear List,
I have one Cyrus IMAP server running on server 1. I also run,
imapproxy on the same server and connect the IMAP server using this.
Now that one IMAPproxy is already connecting to Cyrus IMAP server, is
it advisable to run one more IMAP proxy on server 2 (different server)
and connect to Cyrus IMAP server running on Server1?
Anant
------------------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
------------------------------------------------------------------------------
|
|
From: Paul L. <pa...@sq...> - 2012-08-13 00:40:42
|
Hi Tim, > I maintain the IMAP Proxy package in EPEL[1], and I was prompted to look at a > patch guarding against a possible buffer overflow that is checked into the > source tree, but has not yet made it into a release: > > http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/trunk/imap_proxy/src/request.c?r1=14069&r2=14071 > > Is this just a crash bug or does it have security implications? I don't know as there are any real world implications of this issue - it's just one of correct semantics. That is, the size given is much larger than what was allocated, however, the static string being assigned is also significantly within the allocated memory. The commit comments are probably misleading. Again, there was no bug here. The change just clarifies the code so no one makes a mistake about the size of that variable in the future. > Looking at the ChangeLog, I see that there are also quite a few improvements > that have been made over time since the l.2.7 release. Are there any plans for > a new release? Yes, it's on the radar, but we're not yet at the point where we can commit to a firm ETA. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Tim J. <li...@ti...> - 2012-08-11 08:49:22
|
Hi I maintain the IMAP Proxy package in EPEL[1], and I was prompted to look at a patch guarding against a possible buffer overflow that is checked into the source tree, but has not yet made it into a release: http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/trunk/imap_proxy/src/request.c?r1=14069&r2=14071 Is this just a crash bug or does it have security implications? Looking at the ChangeLog, I see that there are also quite a few improvements that have been made over time since the l.2.7 release. Are there any plans for a new release? Thanks Tim [1] http://fedoraproject.org/wiki/EPEL |
|
From: Federico B. <f.b...@ar...> - 2012-07-18 09:53:20
|
On Tue, 17 Jul 2012, Paul Lesniewski wrote: > On Tue, Jul 17, 2012 at 4:53 AM, Federico Bianchi > <f.b...@ar...> wrote: >> On Tue, 17 Jul 2012, Federico Bianchi wrote: >> >> We have a vintage SquirrelMail setup still defaulting to ISO-8859-1; after inserting imapproxy >> some filters stopped working because of its UTF-8 default. >> >> While our specific problem was tamed and fixed in a matter of minutes by means of iconv, I >> assume other people might stumble into it (much more so, because their contexts might not >> be so trivial to handle): do you think it may be worth a specific workaround? If so, can you >> think of a reliable one since the simple solution (streaming to iconv via a configuration >> setting) is likely a bad one? > > You don't say what your "solution" was, and I can't say as I > understand exactly what your problem was. You can also change the > default character set in SquirrelMail webmail by making a single > change in its configuration file. The trivial fix for us was converting to UTF-8 all the SquirrelMail user preferences files from ISO-8859-1; much in a similar way, the simple (and, IMHO, wrong) general solution I could think of would be a configuration setting. > More generally speaking, one of my primary goals for SquirrelMail > webmail right now is to encourage all the translators to resubmit > their translations converted to UTF-8, so we can ship it with its > character set defaulting to UTF-8. I've not had the time I thought I > would in the past 6 months to work on this, but it's coming.... OK. Generally speaking, however, I think everything coming from imapproxy should be normalised to a common encoding. Best regards Federico Bianchi Dipartimento di Storia delle Arti Universita` di Pisa via Trieste, 38 - I-56126 Pisa (Italy) tel.(+39) 050 221 6 024; fax (+39) 050 221 6 001 e-mail: <f.b...@ar...> =================================================== !DISCLAIMER!: my e-mail reflects _my_own_ opinions! =================================================== |
|
From: Paul L. <pa...@sq...> - 2012-07-18 06:46:17
|
On Tue, Jul 17, 2012 at 4:53 AM, Federico Bianchi <f.b...@ar...> wrote: > On Tue, 17 Jul 2012, Federico Bianchi wrote: > > We have a vintage SquirrelMail setup still defaulting to ISO-8859-1; after inserting imapproxy > some filters stopped working because of its UTF-8 default. > > While our specific problem was tamed and fixed in a matter of minutes by means of iconv, I > assume other people might stumble into it (much more so, because their contexts might not > be so trivial to handle): do you think it may be worth a specific workaround? If so, can you > think of a reliable one since the simple solution (streaming to iconv via a configuration > setting) is likely a bad one? You don't say what your "solution" was, and I can't say as I understand exactly what your problem was. You can also change the default character set in SquirrelMail webmail by making a single change in its configuration file. More generally speaking, one of my primary goals for SquirrelMail webmail right now is to encourage all the translators to resubmit their translations converted to UTF-8, so we can ship it with its character set defaulting to UTF-8. I've not had the time I thought I would in the past 6 months to work on this, but it's coming.... -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Federico B. <f.b...@ar...> - 2012-07-17 13:17:26
|
On Tue, 17 Jul 2012, Federico Bianchi wrote: We have a vintage SquirrelMail setup still defaulting to ISO-8859-1; after inserting imapproxy some filters stopped working because of its UTF-8 default. While our specific problem was tamed and fixed in a matter of minutes by means of iconv, I assume other people might stumble into it (much more so, because their contexts might not be so trivial to handle): do you think it may be worth a specific workaround? If so, can you think of a reliable one since the simple solution (streaming to iconv via a configuration setting) is likely a bad one? Best regards Federico Bianchi Dipartimento di Storia delle Arti Universita` di Pisa via Trieste, 38 - I-56126 Pisa (Italy) tel.(+39) 050 221 6 024; fax (+39) 050 221 6 001 e-mail: <f.b...@ar...> =================================================== !DISCLAIMER!: my e-mail reflects _my_own_ opinions! =================================================== |
|
From: Paul L. <pa...@sq...> - 2012-03-03 23:41:35
|
> 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. You found the mailing lists for SquirrelMail, but failed to use the right one. Please try the squirrelmail-users mailing list in the future. > 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? 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. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: La P. c. s. I. <cus...@la...> - 2012-02-16 22:15:26
|
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 |
|
From: Paul L. <pa...@sq...> - 2011-12-31 18:15:44
|
On Sat, Dec 31, 2011 at 7:24 AM, Orion Poplawski <or...@co...> wrote:
> On 12/30/2011 11:17 PM, Paul Lesniewski wrote:
>>
>> On Fri, Dec 30, 2011 at 7:38 PM, Orion Poplawski<or...@co...>
>> wrote:
>>>
>>> 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
>>> @@ -490,10 +490,10 @@ 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.
>>
>>
>> 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?
>>
>
> 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.
You're right. Thanks for contributing to more clarity for the users
of this tool.
Thanks,
Paul
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
|
|
From: Orion P. <or...@co...> - 2011-12-31 15:25:01
|
On 12/30/2011 11:17 PM, Paul Lesniewski wrote:
> On Fri, Dec 30, 2011 at 7:38 PM, Orion Poplawski<or...@co...> wrote:
>> 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
>> @@ -490,10 +490,10 @@ 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.
>
> 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?
>
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.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane or...@co...
Boulder, CO 80301 http://www.cora.nwra.com
|
|
From: Paul L. <pa...@sq...> - 2011-12-31 06:18:00
|
On Fri, Dec 30, 2011 at 7:38 PM, Orion Poplawski <or...@co...> wrote:
> 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
> @@ -490,10 +490,10 @@ 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.
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?
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
|
|
From: Orion P. <or...@co...> - 2011-12-31 03:38:17
|
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
@@ -490,10 +490,10 @@ 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.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane or...@co...
Boulder, CO 80301 http://www.cora.nwra.com
|
|
From: Paul L. <pa...@sq...> - 2011-12-16 17:58:56
|
On Fri, Dec 2, 2011 at 1:11 AM, Brad <br...@co...> wrote: > 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 Committed. Thanks so very much for your attention to detail. We really appreciate your help. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Paul L. <pa...@sq...> - 2011-12-16 17:57:54
|
Hi Brad, On Fri, Dec 2, 2011 at 1:14 AM, Brad <br...@co...> wrote: > 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. Committed. Thanks once again! - Paul -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Brad <br...@co...> - 2011-12-02 09:14:16
|
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) @@ -23,11 +23,12 @@ mandir = $(prefix)/man/man3 CC = @CC@ -CPPFLAGS = @CPPFLAGS@ +CPPFLAGS = @CPPFLAGS@ +CFLAGS = @CFLAGS@ LDFLAGS = @LDFLAGS@ LIBS = @LIBS@ DEFINES = @DEFINES@ -FLAGS = $(CPPFLAGS) @CFLAGS@ -I. -I./include +FLAGS = -I. -I./include INSTALL = @INSTALL@ EBIN = $(sbindir) @@ -63,7 +64,7 @@ $(XYD_OBJ) $(TAT_OBJ): $(MAKEFILE) ./include/common.h ./include/imapproxy.h .c.o: - $(CC) $(CFLAGS) $(FLAGS) -c -o $@ $< + $(CC) $(CFLAGS) $(FLAGS) $(CPPFLAGS) -c -o $@ $< $(XYD_BIN): $(XYD_OBJ) $(CC) -o $@ $(XYD_OBJ) $(LDFLAGS) $(XYD_LIB) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Brad <br...@co...> - 2011-12-02 09:11:48
|
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) @@ -89,6 +89,10 @@ /* 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 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Paul L. <pa...@sq...> - 2011-11-23 20:54:16
|
On Wed, Nov 23, 2011 at 10:29 AM, Brad <br...@co...> wrote: > On 23/11/11 6:27 AM, Paul Lesniewski wrote: >> >> On Sat, Nov 19, 2011 at 6:26 PM, Brad<br...@co...> wrote: >>> >>> The following diff adds DESTDIR support to imapproxy's Makefile. >> >> Looks good. Thank you. Do you have a full name for attribution? :) >> > Yes, Brad Smith. Committed to SVN. Thank you. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Brad <br...@co...> - 2011-11-23 18:29:47
|
On 23/11/11 6:27 AM, Paul Lesniewski wrote: > On Sat, Nov 19, 2011 at 6:26 PM, Brad<br...@co...> wrote: >> The following diff adds DESTDIR support to imapproxy's Makefile. > > Looks good. Thank you. Do you have a full name for attribution? :) > > Cheers, > > Paul Yes, Brad Smith. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Paul L. <pa...@sq...> - 2011-11-23 11:28:14
|
On Sat, Nov 19, 2011 at 6:26 PM, Brad <br...@co...> wrote: > The following diff adds DESTDIR support to imapproxy's Makefile. Looks good. Thank you. Do you have a full name for attribution? :) Cheers, Paul -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Brad <br...@co...> - 2011-11-20 02:46:21
|
The following diff adds DESTDIR support to imapproxy's Makefile.
Index: imapproxy.spec
===================================================================
--- imapproxy.spec (revision 14151)
+++ imapproxy.spec (working copy)
@@ -50,7 +50,7 @@
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)
@@ -21,7 +21,6 @@
infodir = $(prefix)/info
libdir = $(prefix)/lib/gnudl
mandir = $(prefix)/man/man3
-rpm_prefix = @rpm_prefix@
CC = @CC@
CPPFLAGS = @CPPFLAGS@
@@ -79,21 +78,21 @@
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 .
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
|
|
From: Laura M. <mc...@so...> - 2011-11-10 20:10:58
|
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<mc...@so...>
> 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<mc...@so...>
>>> 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<mc...@so...>
>>>>> 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"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
>
|
|
From: Paul L. <pa...@sq...> - 2011-11-09 19:15:38
|
On Tue, Nov 8, 2011 at 8:27 AM, Laura McCord <mc...@so...> 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. 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. > On 11/8/11 10:16 AM, Ken D'Ambrosio wrote: >> lsof -i -P | egrep "imap|143" -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
1 message has been excluded from this view by a project administrator.