posted
And then post whatever error message you get here. My email is down, and I need meat to diagnose the problem. I can't send or recieve email. I'm now glad I haven't put pweb on that server yet and I'll probably take out a temp address there.
Depending on the problem, I know it might take a while to get an error reply.
posted
Amka, I just sent you an e-mail. I'll let you know what the error message is as asoon as I get it.
Posts: 4569 | Registered: Dec 2003
| IP: Logged |
posted
I sent one just a couple of minutes after you posted, but I have nothing back yet. I will certainly let you know if I get something before my workday is over.
Posts: 440 | Registered: Oct 2001
| IP: Logged |
posted
There is also the possibility that all the emails are being absorbed by the program, it simply refuses to spit them out at me. It shows no error when I'm downloading email, but I haven't gotten one in a week and I have several daily emails such as news headlines that I should be getting. It does show an error when I try to send.
posted
Of course this could just be a ploy on Amka's part to get a bunch of sympathetic emails sent to her... Posts: 1810 | Registered: Jan 1999
| IP: Logged |
quote:This message was created automatically by mail delivery software (Exim).
A message that you sent has not yet been delivered to one or more of its recipients after more than 24 hours on the queue on aftermath.mail.pas.earthlink.net.
The message identifier is: 1Az9J2-0003xt-00 The subject of the message is: The date of the message is: Thu, 4 Mar 2004 19:10:15 -0800
The address to which the message has not yet been delivered is:
ami@geekatplay.com Delay reason: SMTP error from remote mailer after end of data: host geekatplay.com [65.61.98.10]: 451 qq temporary problem (#4.3.0)
No action is required on your part. Delivery attempts will continue for some time, and this warning may be repeated at intervals if the message remains undelivered. Eventually the mail delivery software will give up, and when that happens, the message will be returned to you.
posted
Try to install/reinstall perl's setuidperl package.
The essential line is this: 451 qq temporary problem (#4.3.0)
I telnet'd to your SMTP server to see the direct response there. Up until the message is attempted to be sent, everything goes fine. The security restrictions are properly setup (qmail defaults to that, which is good), it just can't send the email.
It is most likely a permissions problem, which is often tied to setuidperl. You might also check your qmail logs, it should tell you more specifically where you're having problems.
Another possibility is its space related, though that's doubtful. Mail queue's just don't tend to grow beyond the space they're allocated (usually a few dozen megs) unless heavily in use.
Oh, in the future you may find it easier to diagnose your problems by telneting into your SMTP server as I did, which told me the relevant error message right off. Here' s pretty decent howto: http://www.yuki-onna.co.uk/email/smtp.htmlPosts: 15770 | Registered: Dec 2001
| IP: Logged |
posted
There are other problems that could be causing this too, however the important thing to do is check the logs. For instance, a quick google found that an out of date Kaspersky virus scan key can cause this behavior, but that would show up clearly in the logs.
Posts: 15770 | Registered: Dec 2001
| IP: Logged |
Printer-friendly view of this topic
![[Big Grin]](biggrin.gif)
![[Hail]](graemlins/hail.gif)
fugu
