Jim Shupert, Jr. wrote:
Friends,
I have a blckberry user who has the complaint of
5.1.0 - Unknown address error 571-'sorry, sender address has invalid
format (#5.7.1 - chkuser)'
I find this in the wiki - ok , that sounds dead on
1.Is it generally agreed that disabling the check for all
Roxanne Sandesara wrote:
Jake, how do I individually stop qmailtoaster services? Will qmailctl
accept a second argument with the name of a service? Or do I need to
'kill' the processes? Is there a way to start up only selected services?
You can stop individual processes with the svc -d
Thank you.
I've run the script to repair the queue, and started up just send.
I'm going to leave it to run for an hour or so, to see if it can
manage to make the deliveries it needs to make. If not, I'll shut
down send, check to see if the queue is corrupted again. If it is,
I'll have to
OK. Send is still not delivering, clearing up the queue at all.
However, the queue is not re-corrupting itself. I'm not really sure /
what/ to try next. Any suggestions? Should I just leave send running
by itself for a while longer? (I tried forcing the issue with
qmHandle -a to no avail).
Roxanne Sandesara wrote:
OK. Send is still not delivering, clearing up the queue at all.
However, the queue is not re-corrupting itself. I'm not really sure
/what/ to try next. Any suggestions? Should I just leave send running
by itself for a while longer? (I tried forcing the issue with
50% free on the disk is good - But, how about the partition holding the
queue? Do any of the partitions themselves show full?
Thank You
Kevin Katz
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Friday, October 05, 2007 6:00 PM
To:
OK. I had queue-repair create a whole new queue, in case it was
something niggling. However, in test mode it hadn't found anything
wrong.
Having built a new queue, I have restarted qmail-send, and only send,
to see if it will process through the queue. I assume I should let it
sit for an
Roxanne Sandesara wrote:
OK. I had queue-repair create a whole new queue, in case it was
something niggling. However, in test mode it hadn't found anything wrong.
Having built a new queue, I have restarted qmail-send, and only send,
to see if it will process through the queue. I assume I
OK. I tried 'recordio svc -u /var/qmail/supervise/send', but that
clearly doesn't work, as that is just a service script. All I get is
an EOF and a hanging process. What program(s) should I call with
recordio to try to get some meaningful information?
Obviously, I'd prefer to fix this, as
Roxanne Sandesara wrote:
OK. I tried 'recordio svc -u /var/qmail/supervise/send', but that
clearly doesn't work, as that is just a service script. All I get is
an EOF and a hanging process. What program(s) should I call with
recordio to try to get some meaningful information?
Obviously, I'd
Roxanne Sandesara wrote:
OK. I put recordio at the start of the command line within the run
file within /var/qmail/supervise/send and started up just the send
service. What follows is the log /var/log/qmail/send/current:
[EMAIL PROTECTED] ~]# cat /var/log/qmail/send/current
Yeah. It was huge. Sorry about that. But I really wasn't sure what to
keep and what to clip. :(
My /var/log/maildrop/maildrop.log was ... gigantinormous. I don't
feel like doing byte math, but I'm pretty sure it was at least close
to 2gb. So, I moved that to .log.old-date and created a new
Well, I believe we have some good news. Thank you again for your
help, Jake.
With the latest changes (detailed below), the restart of /send wasn't
throwing the errors it was before. So I removed the recordio from the
run file for send, ran Jake's qfixq script again (it found several
13 matches
Mail list logo
