Stephe Campbell | 3 Jun 2004 22:04

Trouble getting started

I have installed the 1.15 version RPMs on a Tao Linux server. All seemed to
go well.

I have added to the default popmap file
campbell:campbell@...

and then did a:
 makegdgm popmap.gdgm.db < popmap

I have changed what appears to be proper for the perdition.conf file,
removed POP3S and IMAP4S from the /etc/sysconfig/perdition file and then
started perdition with the /etc/rc.d/init.d script.

Return from the script indicates sucsess, but I receive this in my maillogs:

Jun  3 15:43:16 perdition perdition[9486]: version=1.15, add_domain="",
authenticate_in=off, bind_address="", capability="IMAP4 IMAP4REV1",
client_server_specification=off,
config_file="/etc/perdition/perdition.conf", connection_limit=0,
connection_logging=on, connect_relog=300, debug=on, domain_delimiter=" <at> ",
group="nobody",inetd_mode=off, listen_port="143", log_facility="mail",
login_disabled=off,
lower_case="",map_library="/usr/lib/libperditiondb_gdbm.so",
map_library_opt="/etc/perdition/popmap.gdbm.db", no_bind_banner=off,
no_daemon=off, no_lookup=off, nodename="perdition.cnpapers.net",
ok_line="You are so in", outgoing_port="143", outgoing_server="",
pid_file="/var/run/perdition.imap4/perdition.imap4.pid", protocol="IMAP4
", server_resp_line=off, strip_domain="", timeout=1800, username="nobody",
username_from_database=off, query_key="", quiet=off, ssl_mode="",
ssl_ca_file="", ssl_ca_path="/etc/perdition/perdition.ca/",
(Continue reading)

Stephe Campbell | 3 Jun 2004 23:16

Re: Trouble getting started

Sorry, I have found most of my problems. I didn't realize that I had to let
perdition do the actual binding to 110 and 143. I turned off pop3 and imap
and things look a lot better now, although I still am not connecting. At
least I'm trying to execute now.

Thanks.

Steve Campbell
campbell@...
Charleston Newspapers

----- Original Message ----- 
From: "Stephe Campbell" <campbell@...>
To: "Perdition Users" <perdition-users@...>
Sent: Thursday, June 03, 2004 4:04 PM
Subject: [PERDITION-USERS] Trouble getting started

> I have installed the 1.15 version RPMs on a Tao Linux server. All seemed
to
> go well.
>
> I have added to the default popmap file
> campbell:campbell@...
>
> and then did a:
>  makegdgm popmap.gdgm.db < popmap
>
> I have changed what appears to be proper for the perdition.conf file,
> removed POP3S and IMAP4S from the /etc/sysconfig/perdition file and then
> started perdition with the /etc/rc.d/init.d script.
(Continue reading)

Leen Besselink | 3 Jun 2004 23:42
Picon

Re: Trouble getting started

On Thu, 3 Jun 2004, Stephe Campbell wrote:

I'm guessing your running an IMAP-server and perdition on the same
address+port (0.0.0.0:143).

> I have installed the 1.15 version RPMs on a Tao Linux server. All seemed to
> go well.
> 
> I have added to the default popmap file
> campbell:campbell@...
> 
> and then did a:
>  makegdgm popmap.gdgm.db < popmap
> 
> I have changed what appears to be proper for the perdition.conf file,
> removed POP3S and IMAP4S from the /etc/sysconfig/perdition file and then
> started perdition with the /etc/rc.d/init.d script.
> 
> Return from the script indicates sucsess, but I receive this in my maillogs:
> 
> Jun  3 15:43:16 perdition perdition[9486]: version=1.15, add_domain="",
> authenticate_in=off, bind_address="", capability="IMAP4 IMAP4REV1",
> client_server_specification=off,
> config_file="/etc/perdition/perdition.conf", connection_limit=0,
> connection_logging=on, connect_relog=300, debug=on, domain_delimiter=" <at> ",
> group="nobody",inetd_mode=off, listen_port="143", log_facility="mail",
> login_disabled=off,
> lower_case="",map_library="/usr/lib/libperditiondb_gdbm.so",
> map_library_opt="/etc/perdition/popmap.gdbm.db", no_bind_banner=off,
> no_daemon=off, no_lookup=off, nodename="perdition.cnpapers.net",
(Continue reading)

Leen Besselink | 4 Jun 2004 07:09
Picon

Re: Trouble getting started

On Thu, 3 Jun 2004, Stephe Campbell wrote:

> Sorry, I have found most of my problems. I didn't realize that I had to let
> perdition do the actual binding to 110 and 143. I turned off pop3 and imap
> and things look a lot better now, although I still am not connecting. At
> least I'm trying to execute now.
> 

You will still need the pop3- and imap-server, perdition is only a proxy
(well, if your mail is sitting on that same machine anyway).

you probably want the IMAP and POP-server to bind to 127.0.0.1 and
perdition to the outside world (you IP-address(es)).

For perdition this is the -b option. And the default outgoing server (this
is used when it's unknown what server a user should be connected to) might
then be: -s 127.0.0.1

for Courier-IMAP and POP3 this is:

in etc/imapd and etc/pop3 of courier: 

ADDRESS=127.0.0.1

It might be a good idea to increase maxperip as well, as it's now all
coming from the proxy.

> Thanks.
> 
> Steve Campbell
(Continue reading)

Hubert Krause | 7 Jun 2004 12:25
Picon
Picon

Enable SSL for non SSL capable imap server with perdition?


Hello List,

is it possible to enable SSL for non SSL capable imap server with perdition? 
I've tryed with the following configuration, but with little success:

perdition.conf:

map_library /usr/lib/libperditiondb_gdbm.so.0
outgoing_server mail.domain.tld
query_str \\P

popmap:

110:mail.domain.tld:110
143:mail.domain.tld:143
995:mail.domain.tld:110
993:mail.domain.tld:143

OS is debian woody with perdition version 1.13-1woody (backport)

regards,

Hubert
--

-- 
Hubert Krause, Kassel
e-mail: 	hukrause@...
web: 		http://www.hubert-krause.de
gpg-key:	http://www.hubert-krause.de/hubert.asc
(Continue reading)

Horms | 8 Jun 2004 05:05
Picon
Gravatar

Re: Enable SSL for non SSL capable imap server with perdition?

On Mon, Jun 07, 2004 at 12:25:57PM +0200, Hubert Krause wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello List,
> 
> is it possible to enable SSL for non SSL capable imap server with perdition? 
> I've tryed with the following configuration, but with little success:

Hi Hubert,

If what you want to do is the following, then the answer is yes.

[End User]----SSL---->[Perdition]---Plain-Text--->[Real Server]

> perdition.conf:
> 
> map_library /usr/lib/libperditiondb_gdbm.so.0
> outgoing_server mail.domain.tld
> query_str \\P
> 
> popmap:
> 
> 110:mail.domain.tld:110
> 143:mail.domain.tld:143
> 995:mail.domain.tld:110
> 993:mail.domain.tld:143
> 
> OS is debian woody with perdition version 1.13-1woody (backport)

(Continue reading)

cedwards | 9 Jun 2004 18:46

segfault on 1.14

We're seeing occasional segfaults doing either pop3 or imap. It occurs
only for a specific set of users and is consistent and reliable. Other
users are able to log in just fine. The version is 1.14 using the woody
packages.

Here's a gdb backtrace. I could rebuild with debugging symbols if that
would be helpful.

Program received signal SIGSEGV, Segmentation fault.
0x401bbbb8 in free () from /lib/libc.so.6
(gdb) w
Ambiguous command "w": watch, wh, whatis, where, while, while-stepping,
winheight, ws.
(gdb) where
#0  0x401bbbb8 in free () from /lib/libc.so.6
#1  0x401bbaa3 in free () from /lib/libc.so.6
#2  0x402c5c1a in ber_memfree () from /usr/lib/liblber.so.2
#3  0x402b0746 in ldap_free_connection () from /usr/lib/libldap.so.2
#4  0x402aa7f4 in ldap_ld_free () from /usr/lib/libldap.so.2
#5  0x402aa728 in ldap_unbind_ext () from /usr/lib/libldap.so.2
#6  0x402aa9ba in ldap_unbind_s () from /usr/lib/libldap.so.2
#7  0x40015d8c in dbserver_get () from /usr/lib/libperditiondb_ldap.so.0
#8  0x402628d0 in __morecore () from /lib/libc.so.6
#9  0x402628c8 in __morecore () from /lib/libc.so.6
#10 0x402628c0 in __morecore () from /lib/libc.so.6
#11 0x08071e60 in ?? ()

I see that it dies freeing the ldap connection. Is this related to the
changes that went into 1.15? It also seems really odd that it only happens
for certain users. Could something in their LDAP results be triggering
(Continue reading)

Horms | 10 Jun 2004 04:05
Picon
Gravatar

Re: segfault on 1.14

On Wed, Jun 09, 2004 at 10:46:17AM -0600, cedwards@... wrote:
> We're seeing occasional segfaults doing either pop3 or imap. It occurs
> only for a specific set of users and is consistent and reliable. Other
> users are able to log in just fine. The version is 1.14 using the woody
> packages.
> 
> Here's a gdb backtrace. I could rebuild with debugging symbols if that
> would be helpful.
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x401bbbb8 in free () from /lib/libc.so.6
> (gdb) w
> Ambiguous command "w": watch, wh, whatis, where, while, while-stepping,
> winheight, ws.
> (gdb) where
> #0  0x401bbbb8 in free () from /lib/libc.so.6
> #1  0x401bbaa3 in free () from /lib/libc.so.6
> #2  0x402c5c1a in ber_memfree () from /usr/lib/liblber.so.2
> #3  0x402b0746 in ldap_free_connection () from /usr/lib/libldap.so.2
> #4  0x402aa7f4 in ldap_ld_free () from /usr/lib/libldap.so.2
> #5  0x402aa728 in ldap_unbind_ext () from /usr/lib/libldap.so.2
> #6  0x402aa9ba in ldap_unbind_s () from /usr/lib/libldap.so.2
> #7  0x40015d8c in dbserver_get () from /usr/lib/libperditiondb_ldap.so.0
> #8  0x402628d0 in __morecore () from /lib/libc.so.6
> #9  0x402628c8 in __morecore () from /lib/libc.so.6
> #10 0x402628c0 in __morecore () from /lib/libc.so.6
> #11 0x08071e60 in ?? ()
> 
> I see that it dies freeing the ldap connection. Is this related to the
> changes that went into 1.15? It also seems really odd that it only happens
(Continue reading)

Corey Edwards | 10 Jun 2004 17:33

Re: segfault on 1.14

On Wed, 2004-06-09 at 20:05, Horms wrote:
> On Wed, Jun 09, 2004 at 10:46:17AM -0600, cedwards@... wrote:
> > We're seeing occasional segfaults doing either pop3 or imap. It occurs
> > only for a specific set of users and is consistent and reliable. Other
> > users are able to log in just fine. The version is 1.14 using the woody
> > packages.
> > 
> > I see that it dies freeing the ldap connection. Is this related to the
> > changes that went into 1.15? It also seems really odd that it only happens
> > for certain users. Could something in their LDAP results be triggering
> > this?
> 
> Yes, I would stronly think it is related. 
> I found a few segmentation fault type bugs in the ldap module
> for 1.14. I believe these are fixed in 1.15. Actually, I believe
> these were the only code differences between the two releases.
> 
> You can see the diff here:
> 
> http://cvs.sourceforge.net/viewcvs.py/perdition/perdition/perdition/db/ldap/perditiondb_ldap.c?r1=1.42&r2=1.43

Yup. An upgrade was all it took. The only hassle was trying to schedule
time for it on a production machine. In the end it took less than a
minute with very little interruption.

Great program. Thanks to everybody who has contributed!

Corey Edwards
cedwards@...

(Continue reading)

Steve Campbell | 10 Jun 2004 18:08

clarification of popmap entries, please

I'm a little confused about what certain popmap entries could be after
reading the documentation "perdition - Mail Retrieval Proxy" written by
Simon Horman.

The document says:

"When organisations merge it may be desirable to consolidate email serving
infrastructure. Unfortunately there is often username clashes when doing
this. Perdition is able to resolve this problem by distinguishing between
users based on either a domain-name supplied by an end-user or the IP
address that the end-user connects to."

I am moving from a linuxconf box with 3 domains. Linuxconf allows something
like "real" virtual domains, and duplicate user names are allowable in
different domains. Based on what I read above, this is also allowable
through perdition if I ensure that the duplicate users (short name) are on
separate real sendmail servers.

Is this accurate?

I have users with the same shortname in different domains and Linuxconf
handles this very well, even when on the same physical server. I am now
migrating to new servers and the virtual domains will be on separate
servers, but not using Linuxconf.

Am I allowed to have popmap entries as follows:

bob@...:mail1.domain1.net
bob@...:mail1.domain2.net

(Continue reading)


Gmane