we upgraded a R6.5.5FP1 server first to R7.0.1FP1 and 2 days later to 7.0.2. since using R7 our mail server has crashed lots of times. we found the router task to be responsible for the crashes. i have a mail in 1 of our mail.boxes that makes the router crash immediately and today we have some hundred mails waiting that cannot be delivered because a server is not reachable and this seems to crash the router also.
has anyone out there the same problems with the router in r7?
for now after each crash i have to remove the old mail.boxes, let the server create new ones and then copy the old mails into the new boxes. and believe me this is no fun. we had 6 crashes yesterday!
Hi, thanks fpr your response. i doesn’t seem to be this problem. for me this is the way to get my server back up. but it is not the reason for a crash.
we found out problem to be MIME mails without a body item. pasting such a mail in one of mail boxes crashes the server, receiving one crashes the server.
we now block all mail for one recipient that has received these e-mails…
i really hoped it was just the error converting MIME mails and deliverung them to r4.6 that made our server crash but it wasn’t this one alone. routing the mail over a r6.5 server reduced the number of crashes but it didn’t stop them entirely.
we spent another 1gig ram to the server having now 4gig of memory. but the server still crashed with “not enough memory” and similar errors although it was only using about 2gig.
but after reading the fixlist of the upcoming 7.0.2 FP1 i found the reason for the crashes we have encountered since.
we stopped all reports in the reports.nsf!
i really didn’t find this one as a solution for crash problems with r7, only some references to a BLK_OPEN*** error which i didn’t link to the reports.nsf. we had not a single crash after stopping all reports in the reports.nsf.
we have found out that we are receiving mails that have no body item and that this makes the server crash. whenever i copy a document in one of the mailboxes and this document has no body item it makes the router crash.
In our case it seems to be related to the new TNEF feature (at least there is a lot about it in the nsd crash log).
-Be sure the TNEF conversion is disabled (details in the release notes for 7.0.2)
-We added to server notes.ini (or configurations document):
MailBoxDisableTXNLogging=1
-Recreated the mailboxes, so they stay with transactional logging disabled.
-Also had to delete some messages from mailboxes with an attachment saying it was not able to decode mime body, which it was making the router to crash.
We have blocked in configuration connections from IP addresses of these messages and they have not appeared again.
We started getting crashes in 7.0.2 after enabling the TNEF converter as well. I just disabled it a short while ago, so it is still too soon to be absolutely sure. But setting “TNEFEnableConversion=1” was the only change prior to the crashes occurring.
I hope it is the TNEF converter, because I can live without that until they get it right. But it would have been nice to have. And why wasn’t it right in the first place?
Problem completely identified and work around installed.
the problem happens in this constellation: an R7 server running SMTP and router, a R4.6 server just running router. incoming MIME message with no BODY item is converted on r7 server and when r7 router tries to transfer the mail to r4.6 router r7 router crashes the complete r7 server.
this hast to be an new error in r7. we have a r6.5.5 server running. we route any mail that is destined to the r4.6 server via r6.5.5 and this is running.