http://permalink.gmane.org/gmane.mail.perdition.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.mail.perdition.user/1840 <pre> Is perdition affected by this Red Hat kernel bug? [dovecot.org] Red Hat/CentOS users: A recent kernel update [1] causes Dovecot to start failing after it has reached 1000 child processes. To fix this, downgrade your kernel until Red Hat releases a fixed kernel. Regards Javier Links: ------ [1] https://bugzilla.redhat.com/show_bug.cgi?id=681578 ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> Javier Miguel Rodríguez 2012-05-02T21:41:02 http://permalink.gmane.org/gmane.mail.perdition.user/1839 <pre> I'm using perdition quite successfully to present a unified interface for users whose mail resides on various back-end servers, using LDAP routing. But I foresee trouble ahead. A gmail backend, for example, requires an imaps connection, regardless of how the user reached the perdition proxy. gmail also requires the full email address (foobar&lt; at &gt;gmail.com), but other services just want the user id -- i.e. the part before the '&lt; at &gt;'. There will probably be cases where the user id on the backend is quite different from the user id the user knows about and logs in with. In short -- maybe it's a good idea to start thinking about having more stuff be LDAP-driven than the current three elements. Has there ever been a discussion of some scriptable or extensible facility for driving more back-end parameters from LDAP -- maybe including even parameters that are normally driven by command-line or config file parameters, on a per- connection basis? If this sounds like a good idea at all I'd be happy t</pre> Michael Smith 2012-04-16T21:29:02 http://permalink.gmane.org/gmane.mail.perdition.user/1838 <pre>Hi, I'm happy to announce the release of perdition 1.19-rc5 Key changes since 1.19-rc4: * ldap: fix segmentation fault in dbserver_get2() * Manage-sieve: Fix handling of plain login which would segmentation fault in some cases * Manage-sieve: Fix handling of long authentication hashes * Enhance --bind_address option parsing to handle IPv6 addresses * Fix 8/4byte integer type miss-matches which may lead to undefined behaviour A full change log is provided by the Mercurial repository http://hg.vergenet.net/perdition/perdition/ Perdition 1.19-rc5 and the vanessa libraries that it depends on are available from: http://horms.net/linux/perdition/download/1.19-rc5/ Debian unstable packages have been uploaded to Debian.Org and should be available in the Debian archive within 24 hours. http://packages.debian.org/source/unstable/perdition ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> Simon Horman 2012-03-20T12:23:21 http://permalink.gmane.org/gmane.mail.perdition.user/1837 <pre>Try setting the outgoing_port for each protocol. For instance, in /etc/sysconfig/perdition: FLAGS="${FLAGS:=}" POP3="${POP3:=yes}" POP3_FLAGS="${POP3_FLAGS:=}" POP3S="${POP3S:=yes}" POP3S_FLAGS="${POP3S_FLAGS:=--outgoing_port 110}" IMAP4="${IMAP4:=yes}" IMAP4_FLAGS="${IMAP4_FLAGS:=}" IMAP4S="${IMAP4S:=yes}" IMAP4S_FLAGS="${IMAP4S_FLAGS:=--outgoing_port 143}" Todd -----Original Message----- From: perdition-users-bounces&lt; at &gt;vergenet.net [mailto:perdition-users-bounces&lt; at &gt;vergenet.net] On Behalf Of Jean-Christophe PAROLA Sent: Monday, March 12, 2012 10:54 AM To: perdition-users&lt; at &gt;vergenet.net Subject: [PERDITION-USERS] Problem bridging IMAPS to IMAP real server hi, I use Perdition perdition-1.17.1_6 on FreeBSD 8.2 witch mysql option. I want bridging IMAPS connection (993) to Perdition on IMAP (143) to real server and POPS (995) connection on Perdition on POP(110) to real serveur. All ports is setting to NULL in database I activate SSL with: ssl_mode ssl_listen I generate certificat thanks to man documenta</pre> Todd Taylor 2012-03-12T18:19:39 http://permalink.gmane.org/gmane.mail.perdition.user/1836 <pre>hi, I use Perdition perdition-1.17.1_6 on FreeBSD 8.2 witch mysql option. I want bridging IMAPS connection (993) to Perdition on IMAP (143) to real server and POPS (995) connection on Perdition on POP(110) to real serveur. All ports is setting to NULL in database I activate SSL with: ssl_mode ssl_listen I generate certificat thanks to man documentation 993 port is open but Perdition call with real server on port 993 instead of 143. The bridging works fine if i set "port=143' in database but the POP proxy don't work. Could you help me to find my mistake ? thanks a lot (i'm french and bad english...sorry) ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> Jean-Christophe PAROLA 2012-03-12T17:53:40 http://permalink.gmane.org/gmane.mail.perdition.user/1835 <pre>Am 03.03.2012 16:11, schrieb Matthias Hunstock: good arguments. I did not think it through I guess :-) thats how I do it with my mailboxes. I use getmail to collect my external accounts thanks for your explanation. Makes sense that this is not possible Cheers tobi ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> jahlives< at >gmx.ch 2012-03-03T17:05:07 http://permalink.gmane.org/gmane.mail.perdition.user/1834 <pre>Am 03.03.2012 15:07, schrieb jahlives&lt; at &gt;gmx.ch: I wouldn't say that it is impossible, but I don't think perdition was made for such a scenario. It just talks to the client until authentication starts, then bridges the connection to the real server based on the authentication data. In order to proxy between IMAP and POP, a software needs to understand/implement IMAP to a certain extent, not just authentication, and then do some really clever things: what to do on the POP3 side when: -IMAP client is searching for mails -IMAP client wants to move messages between folders -IMAP client wants to mark messages -... If you have a local server under your control, the conventional solution would be to use something like fetchmail to suck the mails from that POP3 account into your IMAP mailbox. Matthias ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> Matthias Hunstock 2012-03-03T15:11:05 http://permalink.gmane.org/gmane.mail.perdition.user/1833 <pre>Am 02.03.2012 22:15, schrieb Matthias Hunstock: Hi yes this is what I tried to achieve: My client connects via IMAP4S to my server (which runs perdition and dovecot). The connection from perdition to my local dovecot works like charm. But now I have a "stupid" webmail client which only talks IMAP4(S). I want to connect this "stupid" client through perdition to an external server of my provider. Unfortunately the provider does not offer IMAP4S on the mailbox. Only POP3S as secured transport. So I try to connect this client to my perdition and perdition should connect to the external POP3S service of my provider. The connection to perdition works but perdition cannot connect to the external service. Although I can connect from my Thunderbird to the external POP3S-service without any problem. Is it maybe not possible to change the protocols on perdition? The connection comes in as IMAPS and should go out as POP3S. Do I want to achieve something which simply is not possible? Thanks for any input t</pre> jahlives< at >gmx.ch 2012-03-03T14:07:40 http://permalink.gmane.org/gmane.mail.perdition.user/1832 <pre>Am 02.03.2012 17:20, schrieb jahlives&lt; at &gt;gmx.ch: Just to get this right, you want to connect to perdition via IMAP4(S) and have perdition make a connection using POP3(S)? Matthias ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> Matthias Hunstock 2012-03-02T21:15:57 http://permalink.gmane.org/gmane.mail.perdition.user/1831 <pre>Am 28.02.2012 16:09, schrieb tobi: Nobody an idea where I could check? Or was my description too weird (sorry english is not my first language)? Or do you need excerpts from configfiles? ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> jahlives< at >gmx.ch 2012-03-02T16:20:59 http://permalink.gmane.org/gmane.mail.perdition.user/1830 <pre> It was quite snowy (for Tokyo) and nicely bracketed by several noticeable quakes. ^o^ That works for me, thanks! Chibi </pre> Christian Balzer 2012-03-01T08:53:16 http://permalink.gmane.org/gmane.mail.perdition.user/1829 <pre>Am 29.02.2012 12:02, schrieb N V: Is it possible that you restartet the real server your perdition tries to connect to? I got the same msg yesterday because I restarted my dovecot and forgot to restart perdition as well ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> tobi 2012-02-29T13:46:42 http://permalink.gmane.org/gmane.mail.perdition.user/1828 <pre>Hi, last night i get the following error in the log perdition.imaps[2686]: Fatal error accepting child connection. Exiting. I checked Google but didn't find anything Does anybody see the same error? My setup: Debian 6.0.3 i386 Perdition 1.19-rc4 Sorry about my English... Thanks in advance! Nix ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> N V 2012-02-29T11:02:01 http://permalink.gmane.org/gmane.mail.perdition.user/1827 <pre> I'm in Kobe these days, but I heard there is rather a lot of snow in Tokyo today. Sure, how about mail.info? ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> Simon Horman 2012-02-29T07:07:39 http://permalink.gmane.org/gmane.mail.perdition.user/1826 <pre> Hello Simon, if you're still/again in Tokyo, how did you like the snow this morning? ^o^ Debian Squeeze, thus Perdition 1.19~rc4-2. This version will log any and all session close activities to mail.warn and mail.err. Aside from wasting disk space (not really an issue here) and making the files pretty unreadable (I'd expect to find only a few lines of actual problems if any happened in there) the logging to mail.err is particular troublesome as this log file by default will be synced after each entry. And I'm dealing with 20-50 sessions per second here. Would be nice if this could be remedied. Looking at older (1.17) logs I'd suggest that "Closing NULL session" doesn't belong into mail.err, probably not even into mail.warn. Regards, Christian </pre> Christian Balzer 2012-02-29T05:40:35 http://permalink.gmane.org/gmane.mail.perdition.user/1825 <pre>Hi all together my first post, so hopefully I do not ask something that has already been asked several times :-) I installed perdition on my server and it works very well for my local dovecot. clients can connect and perdition connects to the local server. So far perfect :-) Now I thought that I could connect from perdition to other external servers as well. So I set an entry in popmap for user&lt; at &gt;domain.tld to point to server imap.domain.tld:995 But when I check the logfiles I can see that perdition cannot connect to the external server. Although I can ping the server without problems. One strange thing in the logs is that as protocol always IMAP4S is used, even if port 995 would demand for POP3S. How can I achieve that perdition connects via POP3S to a real server, although the initial connection to perdition by client is based on IMAP4S. I tried to setup the real server as well with port 993 in popmap so port and protocol should match. but that did not work either. Thanks for any idea on how to solve that </pre> tobi 2012-02-28T15:09:33 http://permalink.gmane.org/gmane.mail.perdition.user/1824 <pre> Hi Todd, I have taken a closer look into this but unfortunately I have drawn a blank, the sequence below seems to work for me. Could you let me know which version of Courier IMAP you are using. My test environment was: Debian Testing (amd64) * From the courier 0.66.3-2 source package + courier-base 0.66.3-2 + courier-imap 4.9.3-2 * From the courier-authlib 0.63.0-4 source package + courier-authdaemon 0.63.0-4 + courier-authlib 0.63.0-4 + courier-authlib-userdb 0.63.0-4 ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> Simon Horman 2012-02-16T08:32:22 http://permalink.gmane.org/gmane.mail.perdition.user/1823 <pre> Hi Todd, what you are seeing does look a lot like the bug at the URL above. Unfortunately I don't remember the details of how I (claimed to have) fixed it before not does the patch jump out of the changelog. I will take a closer look into this. ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> Simon Horman 2012-02-13T09:08:24 http://permalink.gmane.org/gmane.mail.perdition.user/1822 <pre>Hello, We have deployed Perdition 1.19rc4 to proxy user requests during a migration with popmap via LDAP. While POP works fine, we are seeing authentication failures through Perdition to the Courier IMAP, as shown below. I see there was a similar issue reported in build 1.18, in early 2011, but it was thought to be fixed since then. That post is at: http://lists.vergenet.net/pipermail/perdition-users/2011-January/002468.html Am I missing an IMAP configuration setting or is this still a bug? Any help you can offer is much appreciated. Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: CLIENT: ". login hemigtest5&lt; at &gt;unix.local&lt;mailto:hemigtest5&lt; at &gt;unix.local&gt; password\r\n" Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: username_add_domain: username_add_domain 0 1 Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: do_getserver: dbserver_get returned empty string Feb 9 14:53:44 dp-perdition-01 perdition.imap4[5904]: username_add_domain: username_add_domain 0 4 Feb 9 14:53:44 dp-perdition-01 per</pre> Todd Taylor 2012-02-09T19:39:42 http://permalink.gmane.org/gmane.mail.perdition.user/1821 <pre>LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - tjilik tjilik lim Consultant at Personal Greater Jakarta Area, Indonesia Confirm that you know tjilik lim: https://www.linkedin.com/e/361uxm-gxvfypn5-16/isd/5665175492/DdDOLmg2/?hs=false&amp;tok=08_sZnslbcDl41 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/361uxm-gxvfypn5-16/Vk41amNYjQLYiF4bGFlW6J-0MjI1jEDRykcYPjLJ7_7/goo/perdition-users%40vergenet%2Enet/20061/I1971360256_1/?hs=false&amp;tok=3i0H8CpbncDl41 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. ______________________________________________ Perdition-users mailing list Perdition-users&lt; at &gt;vergenet.net http://lists.vergenet.net/listinfo/perdition-users </pre> tjilik lim 2012-01-26T07:08:27 http://permalink.gmane.org/gmane.mail.perdition.user/1820 <pre>Hi Steven, On Mon, Jan 16, 2012 at 11:59:53AM -0500, Steven Stillaway wrote: I believe that the problem is that a) The connection has been made from 127.0.0.1 b) 127.0.0.1 has been resolved as localhost c) Stripping away the host portion of local host has left the empty string d) Perdition has skipped appending the empty string as the domain name You configuration should work if end-users connect from 64.147.109.53. But I suspect that may not be what you are after. If you want realnet.com to be appended to user sammy then I suggest the following popmap. sammy:sammy&lt; at &gt;realnet.com&lt; at &gt;zimbra.realnet.com And the following perdition option --username_from_database If you want realnet.com to be appended if users connect to 64.147.109.53 then I suggest the following popmap.re. (.*)&lt; at &gt;64.147.109.53: $1&lt; at &gt;realnet.com&lt; at &gt;zimbra.realnet.com And the following perdition options -M /usr/lib/libperditiondb_posix_regex.so --query_key '\U&lt; at &gt;\I' --username_from_database ______________________________________________ Perdition-us</pre> Simon Horman 2012-01-17T13:17:56 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.mail.perdition.user