| View previous topic :: View next topic |
| Author |
Message |
vcihon
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 107
|
 Posted: Tue Sep 14, 2004 5:05 pm Post subject: email not delivered after emerge world |
 |
|
I emerged world and am having two problems:
First of all, I am not able to recieve email. My /var/log/qmail/qmail-smtpd/current reads:
| Quote: | @40000000414723973a4cc824 X-Qmail-Scanner-1.23st:[tolkien10951811976607503] cannot open /var/spool/qmailscan/qmail-scanner-queue-version.txt - did you initialise the system by running "qmail-scanner-queue.pl -z"? - Permission denied
@40000000414723973a7f74cc /bin/rm: cannot remove `/var/spool/qmailscan/tmp/tolkien10951811976607503/': Permission denied
@40000000414723973a818fdc /bin/rm: cannot remove `/var/spool/qmailscan/working/new/tolkien10951811976607503': Permission denied
@40000000414723973b2c79c4 tcpserver: end 7502 status 0
@40000000414723973b2d509c tcpserver: status: 0/40
|
Qmailscanner and courier-imap was one of the proggies emerged.
Secondly - after updating the authdaemon during the email, now my user gets prompted for a password so auth is apparently not working.
Can someone help me troubleshoot. I realize I will have to provide more information.
Thanks! |
|
| Back to top |
|
 |
wastrel
n00b
Joined: 12 Dec 2003
Posts: 7
|
| Posted: Tue Sep 14, 2004 9:54 pm Post subject: |
|
|
I had a problem with courier-imap after i emerged it recently. You
probably need to do an etc-update and replace the appropriate
config files for courier. This fixed me, may fix your prob too.
-david |
|
| Back to top |
|
|
vcihon
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 107
|
| Posted: Tue Sep 14, 2004 10:53 pm Post subject: |
|
|
I did that. It did solve a problem where the authdaemond wouldn't even start however that is when my users couldn't log in (kept prompting them for the password).
Right now, our email (including a company who hosts their email with us) is down so any help would be greatly appreciated!
I've scoured Blubbi's doc and everything seems to be setup fine . .
Thanks! |
|
| Back to top |
|
|
tecknojunky
Veteran
Joined: 19 Oct 2002
Posts: 1937
Location: Montréal
|
| Posted: Tue Sep 14, 2004 11:38 pm Post subject: |
|
|
I'm too looking for the answer.
I did run /var/qmail/bin/qmail-scanner-queue.pl -z, but it did not fixed anything. Evolution always return some DATA error.
That's what I hate with portage. If their is more than one ebuild emerged at once, their might be messages (einfo) that are printed but you don't see them. It would seem that Gentoo expect you to to watch the screen scrolling all the time.
In the past, I had something similar happening when updating openldap. The new version was incompatible with the current shemas, and the author printed the einfo at the end of the merge!!!
Who is responsable for QA at Gentoo? Shoot him! 
_________________
(7 of 9) Installing star-trek/species-8.4.7.2::talax. |
|
| Back to top |
|
|
vcihon
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 107
|
| Posted: Wed Sep 15, 2004 11:52 am Post subject: |
|
|
I'll bump it once because I really need the help on this one. In particular, how to troubleshoot it.
Thanks. |
|
| Back to top |
|
|
vcihon
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 107
|
| Posted: Wed Sep 15, 2004 1:28 pm Post subject: |
|
|
I figured out the login problem - for some reason - i had to reset the passwords using vchangepw. Then the clients could login. However we still can't recieve email with the errors above.
I have a feeling that permissions were changed when qmail was upgraded.
How can I find out what the correct ownership should be for the queue dirs? |
|
| Back to top |
|
|
vcihon
Tux's lil' helper
Joined: 19 Aug 2003
Posts: 107
|
| Posted: Wed Sep 15, 2004 2:21 pm Post subject: |
|
|
Posting this in case anyone else has the problem:
It was a combination of things.
I used:
http://www.infocopter.com/know-how/courier-imap/debugging.html
to debug the auth problme and then turned of qmail-scanner-queue.pl in my tcprules becuase I am no longer doing server side scanning.
From what I could find, it was a permissions issue with qmail-scanner however as this was down, I did not have time to trouble shoot it. |
|
| Back to top |
|
|
|
Networking & Security
