Koozali.org: home of the SME Server
Obsolete Releases => SME Server 6.x => Topic started by: christian on December 28, 2006, 02:41:58 PM
-
Q: Does anyone know what steps (and log files to look in; services to check) an incoming email follows once it enters the 6.1 system until it is in the user's inbox?
per below I'm open to any other suggestions.
Back ground:
Well in preparing to upgrade to 7.0, I ran into some problems removing some standard blades on my 6.1 based system (Mitel distro). Hard to say what exactly happened but my guess is that I often have Beta blades on my system and the blade removal didn't work gracefully. Regardless, I'm trying to get my email back up again but I'm a little stuck.
I can send a test email (from external user aaa@bbb.com) and see it come into the 6.1 system (xxx@yyy.com). I have appended the logs below to see what is going on. The logs seem to show all is ok (from what I know) but then the email doesn't seem to show up up in the inbox when viewed from Webmail or going directly to the user (xxx)'s account and looking at the Maildir.
qmailscan/current
@400000004593c3f030235b4c clean|Recips|xxx@yyy.com|Returnpath|aaa@bbb.com|ScanTime|0.323687|Size|2586|Subject|Test 122801
qmail/current
@400000004593c3f032391804 new msg 3588123
@400000004593c3f03239335c info msg 3588123: bytes 2903 from <aaa@bbb.com> qp 13469 uid 400
@400000004593c3f0326ffeb4 starting delivery 441: msg 3588123 to local xxx@zzz.yyy.com
@400000004593c3f032701df4 status: local 2/10 remote 0/20
@400000004593c3f0327025c4 delivery 440: success: forward:_qp_13469/did_0+0+1/
@400000004593c3f032702d94 status: local 1/10 remote 0/20
@400000004593c3f032703564 end msg 3588114
@400000004593c3f032e4a9e4 delivery 441: success: did_0+0+1/
@400000004593c3f032e4c924 status: local 0/10 remote 0/20
@400000004593c3f032e4d0f4 end msg 3588123
smtpfront-qmail/current
@400000004593c36009a4393c tcpserver: status: 0/40
@400000004593c3ec38b38e6c tcpserver: status: 1/40
@400000004593c3ec38b3a9c4 tcpserver: pid 13455 from 216.191.234.102
@400000004593c3f00b7b914c tcpserver: ok 13455 0:192.168.9.11:25 smtp.mitel.com:216.191.234.102::42556
@400000004593c3f0116e6cdc smtpfront-qmail[13455]: MAIL FROM:<aaa@bbb.com>
@400000004593c3f011708404 smtpfront-qmail[13455]: RCPT TO:<xxx@yyy.com>
@400000004593c3f030b22214 smtpfront-qmail[13455]: Accepted message qp 13456 bytes 2397
@400000004593c3f030b6544c smtpfront-qmail[13455]: bytes in: 2436 bytes out: 205
@400000004593c3f030bca194 tcpserver: end 13455 status 0
@400000004593c3f030bcb134 tcpserver: status: 0/40
-
Help. I've exausted my knowledge and tried many things. I'm afraid I will carry this into my 7.1rc1 upgrade if I don't fix it now. It may be a database setting.
I've removed all the blades on this server except for 6040 and ServiceLink. Cleared the blade cache and then did re-installs on both remaining blades.
If I can at least understand the incoming email steps, processes, and logs, I may be able to figure the rest out myself.
Any thoughts are appreciated.
-
One more piece of information now. I've noticed SPAM that is getting caught by the spam filter is getting to my junkmail box. Anything not caught in the filter doesn't appear to get delivered.
-
One more piece of information now. I've noticed SPAM that is getting caught by the spam filter is getting to my junkmail box. Anything not caught in the filter doesn't appear to get delivered.
Check your .qmail files. It sounds like you don't have an instruction to deliver to ./Maildir/
-
hmmm. I double checked another 6.1 server to compare. they both have the following in the users directory of both .qmail and .qmail-default (linked).
# more .qmail
#------------------------------------------------------------
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# SME Server software. Instead, modify the source template in
# an /etc/e-smith/templates-custom directory. For more
# information, see http://www.e-smith.org/custom/
#
# copyright (C) 1999-2003 Mitel Networks Corporation
#------------------------------------------------------------
| sortspam
-
hmmm. I double checked another 6.1 server to compare. they both have the following in the users directory of both .qmail and .qmail-default (linked).
Yep. sortspam was rewritten and the interface changed. You need an upgrade to the relevant management package. We don't use sortspam in the SME Server.
-
I've removed all the blades on this server except for 6040 and ServiceLink. Cleared the blade cache and then did re-installs on both remaining blades.
None of those things mean anything to non-Mitel customers. You'll really need to get support from Mitel's commercial support network.
Happy New Year!
-
thanks Gents. that does help.
Charlie, point taken. I know there was a lot in common up until 6 and assumed I was likely in common space. As it turns out. not!
Cheers.
-
for info. I copied "sortspam" over from a clean install of the commercial package. For some reason, I ended up with a "newer" version on my problem server. Once I copied it over. all seems right again.
Thanks again for the tip.
-
hmmm. I double checked another 6.1 server to compare. they both have the following in the users directory of both .qmail and .qmail-default (linked).
# more .qmail
#------------------------------------------------------------
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# SME Server software. Instead, modify the source template in
# an /etc/e-smith/templates-custom directory. For more
# information, see http://www.e-smith.org/custom/
#
# copyright (C) 1999-2003 Mitel Networks Corporation
#------------------------------------------------------------
| sortspam
With the original version of sortspam, that will deliver spam to your junkmail folder and all other mail to your INBOX. With a later version of sortspam, that will redirect spam to your junkmail folder, and *do nothing else*.
Moral of the story is that it is very important that you don't 'upgrade' sortspam without also updating the package which provides the templates for ~/.qmail.
Another moral of the story would be that it is rather danger to make such a substantial change to the semantics of a program.