headers
Ged Haywood | 6 Feb 2004 22:55
Picon

daemon doesn't start, no debug messages

Hello all,

Linux (RH9.0 with kernel upgraded to 2.4.24) and ssl 0.9.7c.

Compiled perdition this evening for the first time.

It doesn't start, and it doesn't give me much information in logs or
other output even with the --debug option.  I'm trying to run the
daemon (that is inetd mode is disabled in the config) but when I run

/usr/local/sbin/perdition.pop3s -P POP3S -u root --debug \
  --pid_file /usr/local/etc/perdition/perdition.run      \
  >perdition.out 2>&1

There's nothing in /var/log/maillog (I did get a couple of messages in
there before I put my self-signed X509 certificate in the right place)
and this is all I get in 'perdition.out':

perdition[17800]: Reading configuration file: "/usr/local/etc/perdition/perdition.conf"
perdition[17800]: options: trailing argument: on
perdition[17800]: options: trailing argument: no
perdition version 1.13 Copyright Horms

perdition is an mail retrieval proxy daemon

Usage: perdition [options]
...
(rest of 'usage' text snipped)
...
(Continue reading)

Permalink | Reply | 5 comments |
headers
Horms | 9 Feb 2004 02:00
Picon
Gravatar

Re: daemon doesn't start, no debug messages

On Fri, Feb 06, 2004 at 09:55:50PM +0000, Ged Haywood wrote:
> Hello all,
> 
> Linux (RH9.0 with kernel upgraded to 2.4.24) and ssl 0.9.7c.
> 
> Compiled perdition this evening for the first time.
> 
> It doesn't start, and it doesn't give me much information in logs or
> other output even with the --debug option.  I'm trying to run the
> daemon (that is inetd mode is disabled in the config) but when I run
> 
> /usr/local/sbin/perdition.pop3s -P POP3S -u root --debug \
>   --pid_file /usr/local/etc/perdition/perdition.run      \
>   >perdition.out 2>&1
> 
> There's nothing in /var/log/maillog (I did get a couple of messages in
> there before I put my self-signed X509 certificate in the right place)
> and this is all I get in 'perdition.out':
> 
> perdition[17800]: Reading configuration file: "/usr/local/etc/perdition/perdition.conf"

It is reading the configuration file /usr/local/etc/perdition/perdition.conf
> perdition[17800]: options: trailing argument: on
> perdition[17800]: options: trailing argument: no

It has found some trailing (extra, uneeded, spurious) argements
"on" and "no", while parsing that file.

> perdition version 1.13 Copyright Horms
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Ged Haywood | 9 Feb 2004 14:44
Picon

Re: daemon doesn't start, no debug messages

Hi there,

On Mon, 9 Feb 2004, Horms wrote:

> On Fri, Feb 06, 2004 at 09:55:50PM +0000, Ged Haywood wrote:
> 
> > perdition[17800]: options: trailing argument: on
> > perdition[17800]: options: trailing argument: no
> 
> It has found some trailing (extra, uneeded, spurious) argements
> "on" and "no", while parsing that file.

I finally figured that out - I was confused, especially by the bit in
the documentation that says:

# Sample configuration file for perdition. Format of a line is:
#
# <key> <value>

That's not quite true, is it?  I was also confused by the use of the
words 'key' to mean 'option' and 'argument' to mean 'value'...

> Contributions are welcome.

...so I propose a new introduction to the 'perdition.conf' file. :)

######################################################################
# perdition.conf
#
# Sample configuration file for perdition.  The file consists of two
(Continue reading)

Permalink | Reply | 3 comments |
headers
Horms | 10 Feb 2004 03:52
Picon
Gravatar

Re: daemon doesn't start, no debug messages

Hi,

your changes seem reasonable, please turn them into a patch.

--

-- 
Horms
Permalink | Reply | 2 comments |
headers
Ged Haywood | 10 Feb 2004 12:37
Picon

Re: daemon doesn't start, no debug messages

Hi there,

On Tue, 10 Feb 2004, Horms wrote:

> your changes seem reasonable, please turn them into a patch.

Attached.

73,
Ged.
Attachment (perdition-conf-docs.patch.gz): application/x-gzip, 1818 bytes
Permalink | Reply | 1 comment |
headers
Cruzio Research | 13 Feb 2004 21:43
Picon
Favicon

Best way to implement perdition

Hi, I'm new here...

I've looked through the last two years or so worth of messages, but 
didn't find anything that would point me in the right direction.

I want to split my mail server in two to increase availability and 
capacity, while using a front end server to direct traffic to the 
correct server, almost exactly like what is described in the 'High 
Capacity Email' paper.

Because of the number of mailboxes on the current server, we use a 
perl-script that contains a hashing algorithm that both qpopper and 
lmail call to determine where to find a mailbox (/var/mail/am/a, 
/var/mail/am/b, /var/mail/nz/x, etc) based on the username.  In other 
words, we don't have a file that lists where each mailbox is located.  
Instead the map is created "on the fly".

The hashing isn't done via a simple regular expression, but instead is 
based on a formula that randomizes the mailboxes so that they spread 
evenly across directories.

What I was thinking of doing was splitting things so that all mail that 
is currently in the /var/mail/am directory goes to one server (and 
therefore would be popped from that server), and /var/mail/nz to the 
other.  Is there a way to get perdition to call a perl script to 
determine which server to pop from, instead of using a map file?

While I could use the perl script to create a map file each time a user 
is added or deleted, I'd rather not go that route if there is a better way.
(Continue reading)

Permalink | Reply | 8 comments |
headers
Ken McKittrick | 14 Feb 2004 03:28

Re: Best way to implement perdition

Mark

I'm using qpopper with the mysql patch to do user mailbox lookups from 
a database. Works fine for 60K mailboxes. The POP3 servers are FreeBSD 
4.9. Perdition is Debian Linux, Database is Solaris.

HTH
Ken McKittrick
Senior Internet Engineer
USADatanet

On Feb 13, 2004, at 3:43 PM, Cruzio Research wrote:

> Hi, I'm new here...
>
> I've looked through the last two years or so worth of messages, but 
> didn't find anything that would point me in the right direction.
>
> I want to split my mail server in two to increase availability and 
> capacity, while using a front end server to direct traffic to the 
> correct server, almost exactly like what is described in the 'High 
> Capacity Email' paper.
>
> Because of the number of mailboxes on the current server, we use a 
> perl-script that contains a hashing algorithm that both qpopper and 
> lmail call to determine where to find a mailbox (/var/mail/am/a, 
> /var/mail/am/b, /var/mail/nz/x, etc) based on the username.  In other 
> words, we don't have a file that lists where each mailbox is located.  
> Instead the map is created "on the fly".
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Philipp Sacha | 14 Feb 2004 15:29
Favicon

perdition-ldap seg faults

Hi,

when my perdition 1.13 installation is configured to get the mailhost 
from an LDAP server (OpenLDAP 2.2.5) it exits with signal 11, when the 
mailhost attribute is absent.

In the log i can find entries like
"perdition[<pid>]: Exiting on signal 11".

After adding the mailhost attribute to the LDAP entry no more seg faults 
are encountered.
Is this perhaps a bug? I think perdition shoul print out an error 
message concerning the missing mailhost attribute.

Regards,
Philipp

--

-- 
Philipp Sacha mailto:psacha@...
Permalink | Reply | 3 comments |
headers
Jeremy Rumpf | 14 Feb 2004 23:38

Re: Best way to implement perdition

On Friday 13 February 2004 03:43 pm, Cruzio Research wrote:
> Hi, I'm new here...
>
> I've looked through the last two years or so worth of messages, but
> didn't find anything that would point me in the right direction.
>
> I want to split my mail server in two to increase availability and
> capacity, while using a front end server to direct traffic to the
> correct server, almost exactly like what is described in the 'High
> Capacity Email' paper.
>
> Because of the number of mailboxes on the current server, we use a
> perl-script that contains a hashing algorithm that both qpopper and
> lmail call to determine where to find a mailbox (/var/mail/am/a,
> /var/mail/am/b, /var/mail/nz/x, etc) based on the username.  In other
> words, we don't have a file that lists where each mailbox is located.
> Instead the map is created "on the fly".
>
> The hashing isn't done via a simple regular expression, but instead is
> based on a formula that randomizes the mailboxes so that they spread
> evenly across directories.
>
> What I was thinking of doing was splitting things so that all mail that
> is currently in the /var/mail/am directory goes to one server (and
> therefore would be popped from that server), and /var/mail/nz to the
> other.  Is there a way to get perdition to call a perl script to
> determine which server to pop from, instead of using a map file?
>
> While I could use the perl script to create a map file each time a user
> is added or deleted, I'd rather not go that route if there is a better way.
(Continue reading)

Permalink | Reply | 6 comments |
headers
Horms | 10 Feb 2004 13:03
Picon
Gravatar

Re: daemon doesn't start, no debug messages

On Tue, Feb 10, 2004 at 11:37:22AM +0000, Ged Haywood wrote:
> Hi there,
> 
> On Tue, 10 Feb 2004, Horms wrote:
> 
> > your changes seem reasonable, please turn them into a patch.
> 
> Attached.

Thanks, I will put this into the CVS tree.

--

-- 
Horms
Permalink | Reply | 0 comments |

Gmane