I hope I can get some quick assistance because I'm kinda lost. I have a user who sent and email with a few attachments this morning. Since then, the recipients are getting the message sent to them continually. It's occurring every 11 minutes exactly. I can't find a way to remove this message from sending. Any advice?
*sigh*
\What version messaging server do you have?
What does your mail.log_current show for this message
What does imsimta qm directory show?
Is this message large? Was it sent to several folks, and is it larger than one of the people it was sent to able to receive?
Do you have your "backoff" set to 11 minutes?
In order:
Version: 1.2
Build Date: Thu Feb 21 14:42:37 PST 2002
mail.log_current just shows it being received over and over again but I know this is not the case because the computer that was sending it isn't even on.
qm directory:
Channel: ims-msSize Queued since
--
1 ZV0J1600504MZ3Q3.003 20 Jun 2006 19:37:51
2 ZV0J16000ITN8RSN.001 20 Jun 2006 19:43:39
--
Total size: 4
Channel: tcp_localSize Queued since
--
3 ZX0J160000YMHCSN.002 20 Jun 2006 19:27:12
4 ZZ0J16009PLPX4CE.00 4161 20 Jun 2006 20:41:28
5 ZZ0J16009RZPZYCE.002 20 Jun 2006 20:43:10
6 ZZ0J16009PNPXICE.00 4161 20 Jun 2006 20:41:42
7 ZZ0J16009PMPXBCE.00 4161 20 Jun 2006 20:41:35
8 ZY0J160098GOGICE.0011 20 Jun 2006 20:09:54
--
Total size: 12498
Grand total size:12502
The message has 4 megs of attachments and was sent to I believe 4 or 5 people.
I don't know what a "backoff" is.
I'm quite familiar with regular mail servers, however, I just don't have a lot of experience with this server since they bought out Netscape...
Thanks in advance again...
Version: 1.2
no such version of our server.
Where did you get this?
And where is the part of log for me to look at?
The two messages queued for ims-ms are likely addressed to a user that's over quota. It's been re-tried several times.
The six messages queued for tcp_local are outbound. Message #3 has been tried twice, unsuccessfully. Message #8 has been tried one time, unsuccessfully. The balance have not been tried, yet.
There is no evidence in this that any message in your system is looping, or in any other way being resent over and over.
backoff is a MTA channel keyword that governs how often messages are retried. You will find it in the imta.cnf file
A message with 4 megs of attachments will grow to about 5.5 or 6 megs as an e-mail message, as the binary attachment must be MIME encoded as a 7-bit stream. Likely, one of the addessees has a 5 meg maximum message size.
let's get a look at your log, please.
and also, please run
imsimta version
so we have the real version. 1.2 is not a messaging server version.
I got that from the web interface.
iPlanet Messaging Server 5.2 (built Feb 21 2002)
libimta.so 5.2 (built 15:07:23, Feb 21 2002)
SunOS mail 5.8 Generic_108528-29 sun4u sparc SUNW,Ultra-2
Maybe I didn't explain quite well enough. A user sent an email this morning: Here's a log entry:
20-Jun-2006 20:43:35.14 tcp_localD 4161 sender@domain.net rfc822;Sarah@tepesxxx.com Sarah@tepesxxx.com dns;mail04.datastreet.net (mail04.datastreet.net ESMTP Merak 8.3.8; Tu
e, 20 Jun 2006 17:41:34 -0700) smtp;250 2.1.5 <Sarah@tepesxxx.com>... Recipient ok
20-Jun-2006 20:43:35.74 tcp_localD 4161 sender@domain.net rfc822;Michael.Ruelle@exp
rexxx.com Michael.Ruelle@exprexxx.com dns;mail.expresxxx.com (S10.hq.pvt SMTP service ready) smt
p;250 Requested mail action okay, completed.
20-Jun-2006 20:43:45.40 tcp_localD 4161 sender@domain.net rfc822;leesxxx@sbcglobal.
net leesxxx@sbcglobal.net dns;sbcmx5.prodigy.net (ylpvm44.prodigy.net ESMTP Sendmail 8.13.6 inb/8.
13.6; Tue, 20 Jun 2006 17:41:00 -0700) smtp;250 2.1.5 <leesxxx@sbcglobal.net>... Recipient ok
20-Jun-2006 20:43:47.05 tcp_localD 2 ret@wow2.goods-production.com rfc822;someone@don
nell.com chad.xxx@sbcglobal.net dns;sbcmx5.prodigy.net (ylpvm44.prodigy.net ESMTP Sendmail 8.1
3.6 inb/8.13.6; Tue, 20 Jun 2006 17:41:00 -0700) smtp;250 2.1.5 <chad.xxx@sbcglobal.net>... Re
cipient ok
This is sent to I believe 4 people. They're continually receiving the same email. Every 11 minutes. Every log entry is exactly like that one I just placed in here.
Also, we have no quotas for our users nor are we out of disk space.
Well, your Messagbing Server is VERY OLD. You should at least download and apply patch 2. Immediately. There are hundreds of fixes in the 20 or so releases between what you have and patch 2.
You continue to limit my ability to help you. I see what appears to be a message being sent successfully to several users. Once.
I do not see the inital Enqueue, nor do I see any duplication.
Unless I can see the entire conversation, I cannot help you.
Seeing the channel blocks from your imta.cnf might help, too.
Thanks for you help so far. The issue has stopped. I'm still not sure as to the cause, to be honest. I did recontruct the user's directory, but that shouldn't have done anything.
As for the logging. That which I included was simply repeating dozens of times thoughout the day. It was actually receiving new copies of the email each and every time. I restarted the virus scanner and it seemed to stop. Thanks for all your help, though...
I've actually come to start suspecting our virus scanning server. It looks as though maybe IT was continually resending the message...which, really doesn't make sense to me either, but what the heck...
> Thanks for you help so far. The issue has stopped.
> I'm still not sure as to the cause, to be honest. I
> did recontruct the user's directory, but that
> shouldn't have done anything.
No, I can't imagine that it would help something in the outbound parts.
>
> As for the logging. That which I included was simply
> repeating dozens of times thoughout the day. It was
> actually receiving new copies of the email each and
> every time. I restarted the virus scanner and it
> seemed to stop. Thanks for all your help, though...
What I saw is the "dequeue" notification. That doesn't help, in that I was looking for Enqueue as well. I suspect a problem with your virus scanning, rather than with Messaging Server.
>
> I've actually come to start suspecting our virus
> scanning server. It looks as though maybe IT was
> continually resending the message...which, really
> doesn't make sense to me either, but what the heck...
You still need to apply patch 2. . . .
You should also be looking at Messaging 6.2, as 5.2 has hit the End Of Life trail. We're no longer shipping it......
