I run setlock to lock qmail-pop3d sessions on a per-user basis. Setlock
runs the poplogger script to log POP activity.
After two days of running smoothly, setlock fails with something close to:
setlock:... poplogger.sh: permission denied
P. Pirn - Sys Admin - see complete headers for more
Sorry for the preceding mispost!
I run the poplogger script with setlock for my qmail-pop3d invocation.
After running fine for two days, I get an error similar to:
setlock:... poplogger.sh: permission denied
and popping fails.
What's strange is that poplogger.sh is set to 755:
-rwxr-xr-x
I'm normally a digest subscriber and I saw this come through the digest.
We have approx 15,000 accounts on our server.
I solved the "unable to fork" problem using sh's limit (not the bash(?),
csh(?) ulimit) and by increasing the value of the -c option in tcpserver.
I have the following lines
Check the mailing list archives for more detail. Qmailaserializes(?)
message delivery from the queue if thereaare too many messages waiting to
be processed into the queuea(listed as "still to be processed" in
qmail-qstat).a Can someone tell me what the big-todo-patch is? What does
is change/makea
I am running fastforward against /etc/aliases.cdb. I want to force the
default sendmail-type behavior that an entry in /etc/aliases will have
delivery priority over a user's mailbox, e.g., an alias exists for "bobo"
and so does the user account for "bobo" but mail will get delivered
according to
Heads up. If you have a reasonably high-volume server (10,000+), you may be
facing the "big todo" queue issue (See mailing list archives.). And even
with the big-todo patch installed, the disk controller for the separate
filesystem may not keep up with the volume of local deliveries.
I ran into
retrieve the record.
------
Peeter Pirn - [EMAIL PROTECTED] - Sys Admin - FWI Internet
uplicate !" tag.
------
Peeter Pirn - [EMAIL PROTECTED] - Sys Admin - FWI Internet
attempts will get a password
authentication error.
--
Peeter Pirn - [EMAIL PROTECTED] - Sys Admin - FWI Internet
According to the FAQ:
2.5. How do I deal with ``CNAME lookup failed temporarily''? The log
showed that a message was deferred for this reason. Why is qmail doing
CNAME lookups, anyway?
Answer: The SMTP standard does not permit aliased hostnames, so qmail
has to do a CNAME lookup in DNS for
I figure it might help to put this one in the archive.
Having applied the AOL DNS patch (According to a previous post, AOL may
have corrected the problem by now.), I'm wary of any DNS error messages
when our customers send mail to AOL.
Here's one not to worry about, other than informing the
11 matches
Mail list logo
