Hi,
what could be the reason for such an error message???:
2001-08-09 16:55:10.524490500 new msg 365071
2001-08-09 16:55:10.525218500 info msg 365071: bytes 234 from qp 2344 uid 8001
2001-08-09 16:55:10.612899500 starting delivery 7: msg 365071 to remote
[EMAIL PROTECTED]
2001-08-09 16:55
Martin Hasenbein [EMAIL PROTECTED] wrote:
what could be the reason for such an error message???:
[...]
2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./
[...]
I've patched qmail with a few patches, [...]
There's your answer -- your patches are buggy. Remove the
delivery 7: msg 365071 to remote
[EMAIL PROTECTED]
2001-08-09 16:55:10.613655500 status: local 0/100 remote 1/100
2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./
2001-08-09 16:55:10.618697500 status: local 0/100 remote 0/100
I've patched qmail with a few patches
On Tue, Aug 07, 2001 at 12:04:50PM +1200, Jason Haar wrote:
We have exactly the same issue here. Exchange goes down. Mail backs up on
Qmail servers. Exchange comes back up. USERS ARE TOLD ITS WORKING AGAIN.
Users then wonder why it takes up to 2 hours for queued mail to get to them.
USERS
Jason Haar [EMAIL PROTECTED] wrote:
It is absolutely necessary.
Why can't you just run qmail-tcpok and send qmail-send an ALRM?
-Dave
try a couple of dozen connections to the same remote host
at the same time.
(This is an issue in itself!)
Why is this an issue? If the remote host can handle 100 inbound
connections, you should be able to open 100 connections to
them, inject
your messages, and close the connections
. Again, 2 messages get through, and the process repeats. This simply
isn't efficient.
This isn't qmails fault but the fault of the remote host. There is room for
improvement - just not on qmail's side. The remote host MUST NOT accept more
connections than it can handle. If it does the remote
, but unfortunately they tend to get retried at much the same
time. Again, 2 messages get through, and the process repeats. This
simply
isn't efficient.
This isn't qmails fault but the fault of the remote host. There is room
for
improvement - just not on qmail's side. The remote host MUST NOT accept
more
On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
[snip]
Read what I wrote again. It IS qmail's fault. One role I use qmail
for is to accept mail which is then passed on to an exchange server on the
same network. Here's an example of what can happen ...
If the
, perhaps 2 will get through. The rest
will
be retried, but unfortunately they tend to get retried at much the same
time. Again, 2 messages get through, and the process repeats. This
simply
isn't efficient.
This isn't qmails fault but the fault of the remote host. There is room
From: Peter van Dijk [mailto:[EMAIL PROTECTED]]
On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
When the exchange server comes back up, I kick the qmail-send
process to get it to deliver the queue. At this point I should be able
to go
off and do other things.
On Mon, Aug 06, 2001 at 02:17:22PM +0100, Richard Underwood allegedly wrote:
And if you don't like this behaviour: write a patch (or find one), or
stop using qmail. Nobody is forcing you to use qmail.
Perhaps, but using this list to tell people (often quite forcefully)
that the
and then suggest/do something beyond what has been
already been discussed ad nauseum.
I would have, if I had been investigating that problem. I was
looking at a completely different problem at the time. If you look at the
title of this thread, you'll see that it's about qmail-remote
On Mon, 6 Aug 2001, Peter van Dijk wrote:
Why are you kicking qmail-send? That should never be necessary in a
production environment.
Apparently, your production environment does not involve situations when
you need to convince qmail-send to retry some of the queued messages
quickly in order
On Mon, Aug 06, 2001 at 10:02:10PM +0200, Pavel Kankovsky wrote:
On Mon, 6 Aug 2001, Peter van Dijk wrote:
Why are you kicking qmail-send? That should never be necessary in a
production environment.
Apparently, your production environment does not involve situations when
you need to
On Mon, Aug 06, 2001 at 02:16:00PM +0200, Peter van Dijk wrote:
On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
When the exchange server comes back up, I kick the qmail-send
process to get it to deliver the queue. At this point I should be able to go
off and do other
On Tue, Aug 07, 2001 at 12:05:12PM +1200, Jason Haar allegedly wrote:
On Mon, Aug 06, 2001 at 02:16:00PM +0200, Peter van Dijk wrote:
On Mon, Aug 06, 2001 at 01:07:36PM +0100, Richard Underwood wrote:
When the exchange server comes back up, I kick the qmail-send
process to get it to
On Fri, Aug 03, 2001 at 03:07:57PM +0100, Richard Underwood wrote:
Hi,
I asked about qmail-remote processes hanging in read() on this list
a few days ago. It appears that this has been reported before, but no
conclusion seemed to have been made.
I just looked at the server I had
Richard Underwood [EMAIL PROTECTED] wrote:
My other suspicion is that there's a chance that my one server will
try a couple of dozen connections to the same remote host at the same time.
(This is an issue in itself!)
Why is this an issue? If the remote host can handle 100 inbound
Hi,
I asked about qmail-remote processes hanging in read() on this list
a few days ago. It appears that this has been reported before, but no
conclusion seemed to have been made.
The problem appears to be in timeoutread() which uses select() to
prevent read() from blocking
) servers ran Linux.
It's weird...
It is. I didn't spot a pattern in the remote hosts, but then I
didn't try to. I suspect it's something to do with stateful firewalls
dropping a session after a period of inactivity, it doesn't explain why the
code is affected by it all, though.
My
Richard Underwood writes:
My other suspicion is that there's a chance that my one server will
try a couple of dozen connections to the same remote host at the same time.
(This is an issue in itself!)
Not really. It used to be an issue back in 1996 when qmail was first
introduced
I've hit an odd problem with qmail-remote.
With one of our ISP's DNS servers set as primary, qmail-remote will hang
indefinitely on some addresses. The DNS server in question responds fine
to dig queries.
Example:
First DNS server in resolv.conf is 205.152.0.20
Run the following command
on this and the simplest
solution is to put a large-value alarm() handler in qmail-remote. No
one as yet seems to be able to narrow down which OSes do this and
under what circumstances.
Mark,
Thanks for the reply. I only seem to experience the problem with
large mail-outs. One
Setting an alarm is a nasty hack in my opinion, but I have to admit
that it's something I considered.
Well, the qmail-remote connection is well and truly wedged once it's
in this state and if the select() timed out as it's meant to,
qmail-remote would exit with a delivery failure
Hi,
I've been running qmail on a number of platforms quite happily for a
while - until now I've had no problems at all. However, I am now
experiencing a problem with qmail-remote hanging.
I'm running qmail on this server for sending mails from websites and
bulk mail-outs (up
I've been running qmail on a number of platforms quite happily for a
while - until now I've had no problems at all. However, I am now
experiencing a problem with qmail-remote hanging.
The problem I see is with qmail-remote failing to terminate when a
connection times-out
Hi,
I have just installed qmail as my mail server.but its giving some random
problem , qmail-remote make a no of connections and do nothing just hang on for a long
time and after some time it works for a few minutes and again hangs on and my queue
size goes on increasing local mails
Please wrap your lines at 72 characters or so.
On Mon, Jul 30, 2001 at 05:58:48AM +0100, Naveen Dhankhar wrote:
Hi,
I have just installed qmail as my mail server.but its giving some random
problem , qmail-remote make a no of connections and do nothing just hang on for a
long time
the request of those who
complained and asked to never receive another email from us.
Because I anticipate other users breaking their TOS at some point in the
future, I'd like to be able to block certain outbound addresses at the
qmail-send or qmail-remote level. Ideally, I would have a control
-remote level. Ideally, I would have a control file that
listed addresses and wildcards that this box would refuse to send mail to.
That is, if [EMAIL PROTECTED] requests that our service not allow
sending to his domain, I could put that restriction on the box, regardless
of whether [EMAIL PROTECTED
Try the badrcptto patch or the spamcontrol patch, either of which
will check against the envelope recipient and refuse to accept the
message. Alternately, nullroute all of the MX's for the domain in
question.
Once again, these messages are not being received via qmail-smtpd. They are
another email from us.
Because I anticipate other users breaking their TOS at some point in the
future, I'd like to be able to block certain outbound addresses at the
qmail-send or qmail-remote level. Ideally, I would have a control file that
listed addresses and wildcards that this box would refuse
On Fri, Jul 20, 2001 at 11:38:31AM -0500, Joshua Nichols wrote:
I'd like to be able to block certain outbound addresses at the
qmail-send or qmail-remote level.
virtualdomains should do it for you. Something like:
unwanted.dom.ain:trashcan
where ~alias/.qmail-trashcan contains
On Sat, Jul 21, 2001 at 02:08:50AM +0800, Adrian Ho wrote:
where ~alias/.qmail-trashcan contains:
Sorry, I meant ~alias/.qmail-trashcan-default, of course. 8-)
--
Adrian HoTinker, Drifter, Fixer, Bum [EMAIL PROTECTED]
Archived @: http://marc.theaimsgroup.com/?l=qmail
Useful URLs:
Hi Guys,
Anyone aware of a remote DoS against qmail?
We we're attacked this weekend and attackers were able to crash SMTP without
affecting any others services in the machine.
This was _not_ the multiple RCPT TO: problem.
I run qmail 1.03 + qmailqueue patch + qmailscanner under tcpserver
[EMAIL PROTECTED] wrote:
We we're attacked this weekend and attackers were able to crash SMTP without
affecting any others services in the machine.
What does crash SMTP mean?
-Dave
Charles Cazabon [EMAIL PROTECTED] wrote:
This is the way to do it. What you could do is make a domain virtual,
and create a couple of .qmail files to handle it. In virtual domains,
do
defaultdomain:alias-defaultdomain
then have ~alias/.qmail-defaultdomain-jim, which forwards to two
On Thu, Jul 12, 2001 at 10:58:33AM +0930, Greg Elliott wrote:
Next I would like to offer every user in the organization a mail address
[EMAIL PROTECTED]
(Regardless of where they reside in the organization).
[...]
qmail-ldap may be your favorite here. It has builtin cluster support letting
the
master accepts modifications. Mail authentication is pointed to the
local LDAP server on the mail server, so imap/pop passwords never fly in
the clear. If you have failover LDAP and the local server dies for some
reason, it will pick up a remote server and you will be in the clear
unless you are on a vpn
-BEGIN PGP SIGNED MESSAGE-
Mike Jackson wrote:
If you have failover LDAP and the local server dies for some
reason, it will pick up a remote server and you will be in the clear
unless you are on a vpn. I have asked Sam Varshavchik to implement SSL
in Courier's authldap module.
I use
Im trying to setup mutliple forwarding for only ONE user account in the
domain (ie. jim@defaultdomain forwards to jim@domain1 to jim@domain2) on
a qmail server that just does inbound/outbound relaying, only remote
deliverys no local ones. I've been reading the life with qmail guide
~darkage [EMAIL PROTECTED] wrote:
Im trying to setup mutliple forwarding for only ONE user account in
the domain (ie. jim@defaultdomain forwards to jim@domain1 to
jim@domain2) on a qmail server that just does inbound/outbound
relaying, only remote deliverys no local ones.
If you're
achievable?
You may wanna take a look at http://untroubled.org for qmail-qfilter.
how to read the parameters from stdinput in a shell script, manipulate
them,
and then how to pass control back to qmail-remote.)
man qmail-control
--
Grtz,
Arjen.
Greg Elliott [EMAIL PROTECTED] wrote:
[The effect would be to 'hijack' (for legitimate reasons) mail for a
subset of an upstream domain, and deliver it locally. (Attempting to
cut down on WAN traffic)].
You're asking us to confirm your proposed solution as being a good (or
possibly the
Greg Elliott [EMAIL PROTECTED] wrote:
b) The script would look at the domain of the intended recipient and if
it matched maildomain.com (for example) it would then look at the
username being sent to.
A small(ish) text file would be kept on the mail server with a list of
usernames.
Thankyou to those who have already replied to my first posting.
However, as Charles Cazabon pointed out, I probably should have backed up a
step
to describe exactly what I am trying to achieve; and in doing so see if that
makes the
advice offered by Arjen van Drie and Dave Sill change in any
From: Greg Elliott [EMAIL PROTECTED]
Date: Thu, 12 Jul 2001 10:58:33 +0930
The problem I am trying to resolve is where user3 mails user4 at the
address [EMAIL PROTECTED]
I do not want the mail to be sent back to the central mail server and then
returned to the address
[EMAIL PROTECTED].
Greg Elliott [EMAIL PROTECTED] wrote:
I want to put in a single machine that acts as a central mail gateway
for an organization. All mail for every domain related to the
organization will initially arrive there and be farmed out to the
various branch mail servers (each which have one or
to execute the changes and
was wondering if anyone had some advice or ideas on the following:
a) I would like to rename the program qmail-remote to qmail-remote.real
and insert another program in its place. (Likely to be a shell script).
b) The script would look at the domain of the intended recipient
9:11 AM
To: Charles Cazabon
Cc: qmail-list.cr.yp.to
Subject: Re: stopping delivery to remote domain
We had the same problem with this domain, but of course it
was 'remote'
mail that was hanging, not local. Our solution was to add this domain
to our local DNS so it would be delivered
Hey all,
I have a slight problem. I got some calls that the mail server was taking 5
hours to send email, so I checked out the mail server. I had 3 connections to
some mail server (all the same) and all the other qmail-remotes were enclosed in
brackets [qmail-remote]. Not knowing what
We had the same problem with this domain, but of course it was 'remote'
mail that was hanging, not local. Our solution was to add this domain
to our local DNS so it would be delivered locally and then dumped.
We have also blocked smtp connections from the many IPs that these
hosts resolved
qmail-remotes were enclosed in
brackets [qmail-remote]. Not knowing what this was, I did a 'killall
-HUP qmail-remote'. The 'unclogged' the remote process and it started
delivering the messages that were on hold. Can anyone tell me what might have
cause this
Not now that you've destroyed
Me again...
Now we're getting this in the log files:
@40003b44845219ec0e14 status: local 0/10 remote 3/20 exitasap
@40003b44845219ec73a4 delivery 760867: deferral: qmail-remote_crashed./
@40003b44845219ece8d4 status: local 0/10 remote 2/20 exitasap
@40003b44845219ed524c delivery
432 ??
I 7:09PM 0:00.00 /var/qmail/bin/qmail-popup
mybox.org /usr/local/vpopmail/bin/vchkpw /vvpopmail 1255
0.0 0.3 864 432 ?? S
7:09PM 0:00.09 /var/qmail/bin/qmail-pop3d
Maildirqmailr 1434 0.0 0.5
884 568 ?? I 7:23PM
0:00.03 qmail-remote graycastle.com [EMAIL PROTECTED]qmailr
1446 0.0 0.5
and receiving mail
Possibly the mode/etc of the trigger is incorrect. Stop qmail, do make setup
check from the qmail source directory again.
Mail sent from machine does not seem to arrive at destination, even though
an 'accepted' message can be seen in /var/log/qmail/qmail-send/current
If the remote
- Original Message -
From: Charles Cazabon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 04, 2001 11:26 PM
Subject: Re: qmail-remote
GIC MLs [EMAIL PROTECTED] wrote:
I'm having a problem which started after having to hard-reboot my
machine
due to monitor
as well.
Don't re-type any of this; copy and paste it.
@40003b432fbd3b1d04bc delivery 900: success:
210.228.3.165_accepted_message./Remote_host_said:_250_ok_994259680_qp_76967/
@40003b432fbd3b3353ac status: local 0/10 remote 19/20
That's fine (although you didn't show the line which
Thanks for the help.
Possibly the mode/etc of the trigger is incorrect. Stop qmail, do
make
setup check from the qmail source directory again.
Actually, I am glad you mentioned this, because I have been looking
for
the correct way to stop qmail. I can't find stop in the index
GIC MLs [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]: Sorry. Although I'm listed as a best-preference
MX or A for that host, it isn't in my control/locals file, so I don't
treat it as local. (#5.4.6)
It looks like somehow a Maildir delivery instruction is being confused for
a
]
To: [EMAIL PROTECTED]
Sent: Thursday, July 05, 2001 3:05 AM
Subject: Re: qmail-remote
Thanks for the help.
Possibly the mode/etc of the trigger is incorrect. Stop qmail, do
make
setup check from the qmail source directory again.
Actually, I am glad you mentioned this, because I
GIC MLs [EMAIL PROTECTED] wrote:
For what its worth, I am now receiving (and able to send mail).
The make setup check fixed your problems. You had to stop and restart qmail
for those changes to take effect.
Now mail I send is sent out immediately. However, I had been using vpopmail
with
Hello again,
- Original Message -
From: Charles Cazabon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 05, 2001 4:00 AM
Subject: Re: qmail-remote
Post an exact copy of the script you use to start qmail -- the one
that
actually calls qmail-start. We need to see what
- Original Message -
From: Charles Cazabon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 05, 2001 4:00 AM
Subject: Re: qmail-remote
Post an exact copy of the script you use to start qmail -- the one
that
actually calls qmail-start. We need to see what you're
lists [EMAIL PROTECTED] wrote:
chicken# cat /var/qmail/control/defaultdelivery
./Maildir/
Okay, that looks fine.
Last night I had messed up my queue by removing messages without bringing
down qmail-send and qmail-smtpd first (DOH!!). I fixed the queue with
queue-fix (found on the
wrap your lines at 72 chars.
On Thu, Jun 28, 2001 at 10:57:09AM +0530, D Rajesh wrote:
Whenever a qmail-remote tries to send a mail to hotmail.com. it hangs for
sometime. As I had 8000 out of 30,000 mails as hotmail ID's the number of
occurrence's of hotmail were more. So, the 300 qmail
D Rajesh wrote:
Hi there,
Firstly, sorry for a long mail.
I have sent 30,000 mails to different domains like yahoo, hotmail,
rediff etc...
Before mentioning the problem the configuration that I have used in
qmail is as follows:-
qmail config
--
1.) Two qmails running at
Are you saying that qmail cannot send mail to a hotmail account?
Dave.
-Original Message-
From: Henning Brauer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 28, 2001 5:47 AM
To: [EMAIL PROTECTED]
Subject: Re: Problem with qmail-remote during Delivery
wrap your lines at 72 chars
On Thu, Jun 28, 2001 at 10:57:09AM +0530, D Rajesh wrote:
Whenever a qmail-remote tries to send a mail to hotmail.com. it hangs for
sometime. As I had 8000 out of 30,000 mails as hotmail ID's the number of
occurrence's of hotmail were more. So, the 300 qmail-remote processes were just
On Thu, Jun 28, 2001 at 09:25:16AM -, [EMAIL PROTECTED] wrote:
[snip]
Try running a real MTA like Iplanet messaging server, Sendmail, Notes or Exchange
server. Even Exchange 4.0 is more advanced than qmail. Qmail was an attractive option
when we had less than 300 users, because it was
On Thu, Jun 28, 2001 at 09:25:16AM -, [EMAIL PROTECTED] wrote:
Try running a real MTA like Iplanet messaging server, Sendmail, Notes or Ex
[lots of nonsense deleted]
*plonk*
ignore this guy.
--
* Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de *
* Roedingsmarkt 14, 20459 Hamburg,
Peter van Dijk wrote:
On Thu, Jun 28, 2001 at 09:25:16AM -, [EMAIL PROTECTED] wrote:
[snip]
Try running a real MTA like Iplanet messaging server, Sendmail, Notes or Exchange
server. Even Exchange 4.0 is more advanced than qmail. Qmail was an attractive option
when we had less than
mails, using qmail-inject of both qmail directories on
rotation. All the 30,000 mails were put in queue with in 7 minutes and
qmail-remote was also running parallelly to send mails.
Now,as in the parameter concurrencyremote totally 300 ( 150from
/var/qmail and 150 from /var/qmail1 ) qmail-remote
Hi Everyone
I'm keep getting this error and I'm not able to receive any emails to my
server.
@40003b36734d34995adc status: local 0/10 remote 0/500
@40003b36738c3629a384 starting delivery 26: msg 1425658 to local
[EMAIL PROTECTED]
@40003b36738c362a246c status: local 1/10 remote 0
newbieportal [EMAIL PROTECTED] wrote:
I'm keep getting this error and I'm not able to receive any emails to my
server.
[...]
@40003b36738d03e0f15c delivery 26: deferral:
procmail:_Couldn't_create_/var/spool/mail/admin/procmail:_Lock_failure_on_
not being zero.
I also put a debugging version of qmail-remote on my system, so if it
ever decides to hang again I can fling gdb at it.
yes, that is what I should do too.
James.
Hi,
[Summary: Some systems leave the fd_sets alone when select times out.]
I think it isn't relevant. qmail-remote doesn't seem to use select,
It does. timeoutread.c:
int timeoutread(t,fd,buf,len) int t; int fd; char *buf; int len;
{
fd_set rfds;
struct timeval tv;
tv.tv_sec = t
On Mon, Jun 18, 2001 at 11:05:34PM +0200, Claudio Nieder allegedly wrote:
On Solaris the above code would work without flaws.
whereas SunOS 4.1.4 (my usual 'old bsd system' benchmark) says:
descriptor sets. 0 indicates that the time limit referred
to by timeout expired.
On Sun, Jun 17, 2001 at 08:56:13PM +0100, James R Grinter wrote:
% I think it isn't relevant. qmail-remote doesn't seem to use select,
% or at least it's nowhere in the path where my qmail-remote wedges.
Go look at timeoutread(), which *is* in your path. The select is in
the line right before
Mark,
How would I need to go about building a dubug version of qmail-remote?
Also, how to terminate the process so that I can 'fling' gdb at it?
With a little I can probably have output from gdb within a couple hours.
--
Troy Settle
Pulaski Networks
540.994.4254
** -Original
On Mon, Jun 18, 2001 at 11:20:36PM -0400, Troy Settle wrote:
% How would I need to go about building a dubug version of qmail-remote?
I set conf-cc and conf-ld to 'gcc -g', edited timeoutread.c slightly
to save the return value of the select in a variable, then built
qmail-remote and put
to posting the evidence I collected here,
so here (finally) it is:
Here's my example stuck qmail-remote, with a backtrace from gdb and
also lsof output. Unfortunately I didn't keep truss output for this
one. (I should point out that this output was collected on Jan 11th...)
qmailr 4322 211 0 Nov 03
I came across the following, which *might* explain some of these
deadlocking problems:
http://kt.zork.net/kernel-traffic/kt20010611_121.html#6
[Summary: Some systems leave the fd_sets alone when select times out.]
If I read this right, timeoutconn/read/write (and anything else that
uses
(explicitly checking for a
result of 0) may be worthwhile.
Or this may just be a red herring...
I think it isn't relevant. qmail-remote doesn't seem to use select,
or at least it's nowhere in the path where my qmail-remote wedges.
As to different OS behaviour, Solaris 2.6 (and 7) both say:
C
of qmail-remote that were sitting
doing nothing. In fact, they had been sitting doing nothing for so long,
they were swapped out. The first few times, I just killed the qmail-remote
processes and watched as qmail again started sending messages across the
Internet. After a while though, I noticed
for that virtual
user.
-K
Do not meddle in the affairs of dragons, because you are crunchy and taste
good with ketchup.
From: David U. [EMAIL PROTECTED]
Date: Thu, 14 Jun 2001 08:04:36 -0700
To: Qmail@List. Cr. Yp. To [EMAIL PROTECTED]
Subject: RE: URGENT: Qmail-remote gone nuts
Here's an update
]]
Sent: Friday, June 15, 2001 3:52 PM
To: Qmail
Subject: Re: URGENT: Qmail-remote gone nuts
I have had this problem qmail+vpopmail if there is an error in a .qmail file
in vpopmail's file system. I had this occur (infinite sending loop) when a
.qmail file had a single blank line at the top. Qmail
forwarded about 6000 times.
Now in my logs I have these just constantly appearing:
== /var/log/qmail/qmail-send/current ==
2001-06-14 08:02:02.460824500 starting delivery 6231: msg 562568 to remote
[EMAIL PROTECTED]
2001-06-14 08:02:02.460830500 status: local 0/10 remote 73/120
2001-06-14 08:02
David U. [EMAIL PROTECTED] wrote:
this morning I awoke to find some 6000 emails in my inbox from
[EMAIL PROTECTED] -- they were the same exact 6000 emails.
Perhaps their MTA isn't finishing the SMTP converstation properly, so they
think they need to try delivery again?
You said you don't
[EMAIL PROTECTED] wrote:
So I got rid of the support forward and now support seems to be
reiceving mail
fine -- but how I do clear my queue when qmail-qstat reports:
messages in queue: 5046
messages in queue but not yet preprocessed: 0
Delete the queue and rebuild it. A good tool for that
Russell Nelson [EMAIL PROTECTED] wrote:
If you're running qmail configured as per
http://www.lifewithqmail.org, then the following commands will fix the
problem:
svc -dx /service/qmail
setlock /service/qmail/supervise/lock sh -c
'/var/qmail/queue/*/0/{348381,348335,348013}'
For LWQ, the
Niles Rowland [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
So I got rid of the support forward and now support seems to be
reiceving mail
fine -- but how I do clear my queue when qmail-qstat reports:
messages in queue: 5046
messages in queue but not yet preprocessed: 0
Delete the
actually queue-fix will do the job right... I know I have done it.
just delete de subfolders in the queue and run the queue-fix
Terius
- Original Message -
From: Dave Sill [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 14, 2001 10:11 AM
Subject: Re: URGENT: Qmail-remote
-Original Message-
From: Dave Sill [mailto:[EMAIL PROTECTED]]
Yeah, he probably won't lose any important messages...
heh, yeah, I *would* want to do that.
No, queue-fix fixes corrupt queues. To delete and rebuild, you should
rm -rf /var/qmail/queue and make setup check from the qmail
Guillermo Villasana Cardoza [EMAIL PROTECTED] wrote:
actually queue-fix will do the job right... I know I have done it.
I didn't mean to imply that it wouldn't work, just that it's
preferable to use the rm/make method since it's definitive and doesn't
require downloading/installing a
David U. [EMAIL PROTECTED] wrote:
now I just want to know why [EMAIL PROTECTED] forwarded to
[EMAIL PROTECTED] 6000 times (until /var filled I assume) instead
of just once. this is all via localhost, no other machines involved.
I'd look at the logs, from the beginning of the incident.
-Dave
My qmail log always say:
Jun 14 08:24:16 seic8 qmail: 992478256.893320 warning: trouble opening
remote/0/348381; will try again later
Jun 14 08:24:16 seic8 qmail: 992478256.894017 warning: trouble opening
remote/0/348335; will try again later
Jun 14 08:24:16 seic8 qmail: 992478256.894706
dgrer writes:
Jun 14 08:28:24 seic8 qmail: 992478504.218230 warning: trouble opening
remote/0/348013; will try again later
...
When I enter /var/qmail/queue/remote/0/, I con not find file 348381,348335 and
348013,
What I showld do to deal with this problem? thx!
This might
delivery down.
If you're talking about SMTP deliveries to remote systems, some MTAs do SMTP
connection caching for multiple messages to the same host or MX -- however, as
SMTP on the 'net at large is mostly latency bound, it's usually faster to just
fire up multiple parallel qmail-remotes each
1 - 100 of 570 matches
Mail list logo
