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

popbsmtpd - Sorry about the bounce

From: Marcus Redivo (mredivo_at_<censored>)
Date: 2002-09-08 11:59:08


Hi James,

Sorry about the bounce; your mail server has no reverse DNS, so mine refused
the connection. I have added you to my whitelist, so you should have no
problems mailing me now.

Now, to the pop-before-smtpd problem:

After the obvious has been checked, there are a couple of things that can go
wrong.

- No pop/imap login entries are being written to the named pipe
- popbsmtpd is not correctly parsing the logged entries

Both can be tested at the same time. Stop the daemon, and run popbsmtpd on
the command line as follows:

popbsmtpd --loglevel=4

This will show you what configuration it is using, and also describe what it
is doing with each log entry it processes. While it is still running, pop
some mail from the server and check the log information. You should have
something that looks like the attachment (the lines would wrap if I included
it inline here).

(Ctrl+C will gracefully exit.)

You can see what is going into the log by scanning for lines that look like
this:
popbsmtpd: INPUT DATA: "Sep 8 11:37:50 spruce stunnel[21373]: spop3
connected from 192.168.1.13:1233"

If your login log entries are arriving, you should see how they are
processed. In my case, I came in from a local address, so I got the
following:
popbsmtpd: Login by user marcus from IP 192.168.1.13 at 2002/09/08 11:37:51
(001031510271)
popbsmtpd: Local address 192.168.1.13 not recorded

Try this, and let me know the results. If it is seeing the log entries but
not extracting the login information correctly, then the parser
configuration needs to be updated. With a couple of sample log entries, I
can fix that up for you.

Good luck,
Marcus Redivo


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


shim