Eclectica Daybreak over Colburne Passage near Sidney, BC, Canada filler
shim shim shim shim
shim Home shim Software shim Avocations shim Services  
shim shim shim shim
Software
shim
shim
Documentation
 SSL Certificates
 OpenBSD RAID
 Self-Check Digits
 Bare Metal Reload
shim
Linux
 popbsmtpd
      Reference
      Installation
      Changelog
      FAQ
      Mailing Lists
      Download
shim
 Postfix
shim
 EnGarde
shim
iSeries
 CPYTOIFSF
 FTP Backup
shim
Windows
shim
shim

popbsmtpd-users

Re: popbsmtpd

From: Marcus Redivo (mredivo_at_<censored>)
Date: 2002-12-22 22:51:11


Now we are getting somewhere. First, I want to make sure nothing changed.
In your previous mail, you had this line:

popbsmtpd: Expiry tests: Current time 2002/12/22 10:14:25 (1040573665),
Cutoff time 2002/12/22 09:44:25 (1040571865)

This time, you have this line:

popbsmtpd: Expiry tests: Current time 2002/12/22 22:58:00 (1040619480),
Cutoff time 2002/12/22 23:28:00 (1040621280)

First message, the cutoff time is earlier than the current time; second
message, it is later. Did you make the auth_duration negative? If so,
change it back to positive. I know the terminology is misleading, but the
cutoff time is the oldest login time that is not considered expired, so it
needs to be earlier than the current time.

Now, here is the problem:

> popbsmtpd: Login by user rhs from IP 24.153.136.148 at 2002/12/22
> 21:58:00 (001040615880)

Notice that according to syslog, the current time is 21:58:00.

> popbsmtpd: Relaying ENABLED (started) for user rhs at 24.153.136.148
> popbsmtpd: KEY "IP:24.153.136.148" DATA "001040615880" recorded
> popbsmtpd: KEY "001040615880_24.153.136.148" DATA "24.153.136.148"
> recorded popbsmtpd: No data ready.
> popbsmtpd: Expiry tests: Current time 2002/12/22 22:58:00 (1040619480),
> Cutoff time 2002/12/22 23:28:00 (1040621280)

Ooops! popbsmtpd thinks the current time is 22:58:00. Also, note that the
expiry should be earlier than the current time.

> popbsmtpd: Inspecting 001040615880_24.153.136.148 (24.153.136.148)
> cutoff=1040621280 logintime=1040615880

Here, the problem is obvious. Login was at ...15880, entries before
....21280 get expired and deleted. This entry is expired.

> popbsmtpd: Entry 001040615880_24.153.136.148 (24.153.136.148) EXPIRED
> popbsmtpd: Relaying DISABLED for 24.153.136.148
> popbsmtpd: Timestamp 001040615880_24.153.136.148 for 24.153.136.148
> deleted from login DB

> I did make sure both my /etc/localtime and
> /var/spool/postfix/etc/localtime are the same.

That's good. Here is where I am stumped; maybe you need to stop and
restart syslog so that everything has the same idea of the current time.
If you can get to the bottom of this, please let me know how you fixed it,
so I can learn from it.

But if you can't get all the times the same, that's OK. Just adjust the
auth_duration by one hour and set it to 90 (one and a half hours, and make
sure it is not negative), and you will get a 30-minute expiry. With this,
you should be good to go. (If you want longer expiries, just add 60 to
what you want to specify.)

Let me know if this works.

Regards,
Marcus


This archive was generated by hypermail 2.1.6 on 2005-11-05 00:15:06 PST


shim