| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> (and relevant logs)
<1> Well, he's reinstalling it now.
<1> Will do it if it's still broken :)
<2> i'm here not for long
<3> mjt: aren't you going to stay up late and get drunk?
<2> i'd make a break for that rule today
<3> Hmmm, is hell freezing over? ;)
<1> On a sunday night?
<1> Alkies :)
<0> mjt is strange
<3> He's Russian, they have to drink to stay warm.
<0> he writes software and stuff
<1> hehe
<2> the last time i were drinking was last week (don't remember which day). Before, it was several months back. And no one _ever_ saw me drunk in last 10-15 years (granted, i was drunk about dozen times all those years)
<2> anyone know how to fit 1670 megs into two CDs? ;)
<3> tar and bzip2 maybe?
<1> Ok, I'm now getting this:
<2> doesn't help
<1> status=bounced (Command died with status 1: "/usr/local/bin/maildrop")
<2> is there /usr/local/bin/maildrop command?
<1> Strangely, it works for the other admin.
<1> On his account.
<2> permission prob?
<3> ~/.forward ?
<1> cds@balham:/etc/postfix$ cat ~/.forward
<1> "|/usr/local/bin/maildrop"
<3> whew
<1> Gah, I bet that's it, isn't it?
<1> rm that file, then?
<3> please do :)
<3> And then shoot it.
<2> rm: cannot remove `that': No such file or directory
<2> rm: cannot remove `file,': No such file or directory
<2> rm: cannot remove `then?': No such file or directory
<1> cds@balham:/etc/postfix$ shoot-and-stamp-on ~/.forward
<1> rob0: Thanks a lot for that :)
<1> rob0: Would that have been the cause of the problem before?
<3> f3ew, we should have told cds to try adding -v to local, I guess. :)
<0> rob0 that does not explain the qmgr error
<0> cds Feb 12 20:29:04 balham postfix/qmgr[11211]: warning: connect to transport spam******in: Connection refused
<0> rob0 or asked for full logs (which I did)
<2> some old queued email perhaps?
<1> You got everything that was in the logns.
<1> Just minus email addresses :)
<1> Cheers for solving it, guys.
<2> btw.. when this happens (qmrg can't connect to transport), mail is stuck in queue forever.
<3> But we didn't solve the qmgr one.
<0> exactly
<1> Well, reinstalling solved that error, I think.
<0> cds said that it happened even for new mail
<0> Ah
<0> so now we will never know what caused it
<2> this is the ONLY place in postfix where mail will not be returned due to maximal_queue_lifetime expiration
<0> yes
Return to
#postfix
or
Go to some related
logs:
#math
libsdl nvidia-glx gentoo
915resoulution
Graphic-sit for dinner
#fluxbox
ubuntu fdisk Unable to open /dev/hdd
_death efnet
#openzaurus
automatix mono installation in ubuntu
tivo like xwindow
|
|