[opensuse] Can't use mail - 12.1 - openSUSE Users

newer
[opensuse] 11.4 FireFox 8.0 - how...

[opensuse] Can't use mail - 12.1

James Knott

23 Nov 2011 23 Nov '11

20:53

In attempting to set up Thunderbird to use a system email account, I discovered a problem with mail. Thunderbird complained it couldn't find the mail spool. I then tried running mail from the command prompt. After trying to send a message, I got an error "postdrop: warning: unable to look up public/pickup: No such file or directory". This is on 12.1. I also tried creating another user, to make sure the problem wasn't caused by something in my home directory, but got the same result. Any ideas? This is the first time I've ever seen mail fail. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

Per Jessen

24 Nov 24 Nov

07:07

James Knott wrote:

...

In attempting to set up Thunderbird to use a system email account, I discovered a problem with mail. Thunderbird complained it couldn't find the mail spool. I then tried running mail from the command prompt. After trying to send a message, I got an error "postdrop: warning: unable to look up public/pickup: No such file or directory". This is on 12.1. I also tried creating another user, to make sure the problem wasn't caused by something in my home directory, but got the same result.

Any ideas? This is the first time I've ever seen mail fail.

Possibly: https://bugzilla.novell.com/show_bug.cgi?id=730787 iow, make sure that postfix is running. -- Per Jessen, Zürich (2.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

James Knott

13:39

Per Jessen wrote:

...

James Knott wrote:

...
In attempting to set up Thunderbird to use a system email account, I discovered a problem with mail. Thunderbird complained it couldn't find the mail spool. I then tried running mail from the command prompt. After trying to send a message, I got an error "postdrop: warning: unable to look up public/pickup: No such file or directory". This is on 12.1. I also tried creating another user, to make sure the problem wasn't caused by something in my home directory, but got the same result.

Any ideas? This is the first time I've ever seen mail fail.

Possibly: https://bugzilla.novell.com/show_bug.cgi?id=730787

iow, make sure that postfix is running.

That's the problem. It's enabled for run levels 3 & 5, but not running. After manually starting, mail works. I guess I'll have to start it in after.local. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

James Knott

15:29

James Knott wrote:

...

That's the problem. It's enabled for run levels 3 & 5, but not running. After manually starting, mail works. I guess I'll have to start it in after.local.

Starting postfix in after.local doesn't work either. So, postfix is definitely broken in 12.1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

phanisvara das

15:41

On Thu, 24 Nov 2011 20:59:50 +0530, James Knott wrote:

...

James Knott wrote:

...
That's the problem. It's enabled for run levels 3 & 5, but not running. After manually starting, mail works. I guess I'll have to start it in after.local.

Starting postfix in after.local doesn't work either. So, postfix is definitely broken in 12.1.

i'm not convinced that's due to postfix. in my case, when using systemd, none of the network services start (sshd, smb, nmb, postfix) unless i manually restart "systemctl restart network.service" after booting. for some reason the loopback interface comes up, but nothing else. i think it's got something to do with having a bridge connection for virtualbox, but i'm not sure about that. once i (manually) restart network service, everything else falls into place quickly. if i do nothing, it takes some 15 min for all services to come up, but without working network (eth0, br0). i don't have time at the moment to try to debug this; i just restart the network, and everything's fine. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

James Knott

15:49

phanisvara das wrote:

...

On Thu, 24 Nov 2011 20:59:50 +0530, James Knott wrote:

...
James Knott wrote:

...
That's the problem. It's enabled for run levels 3 & 5, but not running. After manually starting, mail works. I guess I'll have to start it in after.local.

Starting postfix in after.local doesn't work either. So, postfix is definitely broken in 12.1.

i'm not convinced that's due to postfix. in my case, when using systemd, none of the network services start (sshd, smb, nmb, postfix) unless i manually restart "systemctl restart network.service" after booting. for some reason the loopback interface comes up, but nothing else. i think it's got something to do with having a bridge connection for virtualbox, but i'm not sure about that. once i (manually) restart network service, everything else falls into place quickly. if i do nothing, it takes some 15 min for all services to come up, but without working network (eth0, br0).

i don't have time at the moment to try to debug this; i just restart the network, and everything's fine.

Sshd works for me, so I don't think our problems are identical. /etc/init.d/after.local is supposed to run after everything else, but it appears not to work. Manually starting System Services does. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

phanisvara das

16:13

On Thu, 24 Nov 2011 21:19:31 +0530, James Knott wrote:

...

Sshd works for me, so I don't think our problems are identical. /etc/init.d/after.local is supposed to run after everything else, but it appears not to work. Manually starting System Services does.

yes, seems to be a different variation of the same theme: systemd boot process doesn't work yet. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

16:42

phanisvara das said the following on 11/24/2011 11:13 AM:

...

On Thu, 24 Nov 2011 21:19:31 +0530, James Knott wrote:

...
Sshd works for me, so I don't think our problems are identical. /etc/init.d/after.local is supposed to run after everything else, but it appears not to work. Manually starting System Services does.

yes, seems to be a different variation of the same theme: systemd boot process doesn't work yet.

Gee WOW! I've run systemadm on my Fedora-15 and it tells me that the postfix process is dead! It tells me what it dependent on and that there is a list of conflicts. So perhaps its not just a openSuse problme! There is a "wants: mail-transfer-agent.target" (in /lib/systemd/system/mail-transfer-agent.target but which has an empty body) which conflicts with shutdown.target. I don't know how to interpret all this... -- Over the last few centuries, mathematicians have demonstrated a remarkable tendency to underestimate the cryptanalytic powers of blunt and heavy objects. -- Jamie Reid, CISSP -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

lynn

15:51

...

On Thu, 24 Nov 2011 20:59:50 +0530, James Knott wrote:

...
James Knott wrote:

...
That's the problem. It's enabled for run levels 3 & 5, but not running. After manually starting, mail works. I guess I'll haveto start it in after.local.

Starting postfix in after.local doesn't work either. So, postfix is definitely broken in 12.1.

None of the items you mention are broken I don't think. It's what starts

On 24/11/11 16:41, phanisvara das wrote: the processes that is.

...

i'm not convinced that's due to postfix. in my case, when using systemd, none of the network services start (sshd, smb, nmb, postfix) unless i manually restart "systemctl restart network.service" after booting. for some reason the loopback interface comes up, but nothing else. i think it's got something to do with having a bridge connection for virtualbox, but i'm not sure about that. once i (manually) restart network service, everything else falls into place quickly. if i do nothing, it takes some 15 min for all services to come up, but without working network (eth0, br0).

i don't have time at the moment to try to debug this; i just restart the network, and everything's fine.

I had the same problem. It seems to be to do with the new systemd in 12.1. If you boot using system V, the services are enabled fine. I have a bug open on it: https://bugzilla.novell.com/show_bug.cgi?id=732395 Meanwhile, I'm either booting using sysV or enabling the services manually if I forget to hit f5. HTH L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

phanisvara das

16:07

On Thu, 24 Nov 2011 21:21:45 +0530, lynn wrote:

...

I had the same problem. It seems to be to do with the new systemd in 12.1. If you boot using system V, the services are enabled fine. I have a bug open on it: https://bugzilla.novell.com/show_bug.cgi?id=732395

very good; was feeling guilty for not posting one myself.

...

Meanwhile, I'm either booting using sysV or enabling the services manually if I forget to hit f5.

i had "init=/sbin/sysvinit" added to my menu.lst, but was afraid that sysV might be pulled out from under me eventually, so i rather manage to live with systemd and get used to it. i hope i'll be able to figure out what exactly goes on during systemd boot some time soon. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

16:33

phanisvara das said the following on 11/24/2011 10:41 AM:

...

none of the network services start (sshd, smb, nmb, postfix) unless i manually restart "systemctl restart network.service" after booting

I'm staying away from 12.1 until its stabilized :-( However I do have a running Redhat Fedora 15 and SystemD is stable and working there. All the network services start OK "out of the box" I mention this since the reason for network services no starting at book might be a missing dependency. Just a though. Logs ought to show this. Perhaps someone with time and machine to spare could do a side-by-side of F15 and 12.1 in this respect... I don't understand systemD fully yet, but I do recall reading that the start scripts need to be in the right directory and that the dependencies need to be correct. Perhaps one or the other is absent. There a systemd.config somewhere under /etc and you can turn on/up logging and stuff. There is a tool, systemadm, a GUI, which makes it easy to navigate all this. I don't grok that yet, but its there. Is it available for 12.1? There is also a PAM for postfix on F-15. Do check that on 12.1 For me, grub2 and SystemD, in so far as I've ventured into them on F-15 have been successful and delightful. I look forward to openSuse 12.4 -- Tortoise: 'How many talking tortoises have you met?' Brutha: 'I don't know.' Tortoise: 'What d'you mean, you don't know?' Brutha: 'Well, they might all talk. They just might not say anything when I'm there.' -- "Small Gods", Terry Pratchett -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

phanisvara das

16:52

On Thu, 24 Nov 2011 22:03:47 +0530, Anton Aylward wrote:

...

I'm staying away from 12.1 until its stabilized

for the time being you could use 12.1 with sysV. as far as i've seen, all these problems disappear when the user switches to the old init process. i'm not sure how long sysV will remain available, but looking at the various problems, it's not likely to go away soon. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

lynn

18:14

On 24/11/11 17:52, phanisvara das wrote:

...

On Thu, 24 Nov 2011 22:03:47 +0530, Anton Aylward wrote:

...
I'm staying away from 12.1 until its stabilized

for the time being you could use 12.1 with sysV. as far as i've seen, all these problems disappear when the user switches to the old init process. i'm not sure how long sysV will remain available, but looking at the various problems, it's not likely to go away soon.

+ 1 System V works. systemd as in 12.1 is just not ready. Please vote: https://bugzilla.novell.com/show_bug.cgi?id=732395 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Ken Schneider - openSUSE

18:24

On 11/24/2011 01:14 PM, lynn pecked at the keyboard and wrote:

...

On 24/11/11 17:52, phanisvara das wrote:

...
On Thu, 24 Nov 2011 22:03:47 +0530, Anton Aylward wrote:

...
I'm staying away from 12.1 until its stabilized

for the time being you could use 12.1 with sysV. as far as i've seen, all these problems disappear when the user switches to the old init process. i'm not sure how long sysV will remain available, but looking at the various problems, it's not likely to go away soon.

+ 1

System V works. systemd as in 12.1 is just not ready. Please vote:

https://bugzilla.novell.com/show_bug.cgi?id=732395

Any vote will not matter. SystemD is the way forward as far as the devs are concerned. For now there is a choice at install/upgrade time and that is to install sysvinit-init which will prompt you to uninstall systemd-init. You will then end up with a system that boots sysvinit by default. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

lynn

18:28

On 24/11/11 19:24, Ken Schneider - openSUSE wrote:

...

On 11/24/2011 01:14 PM, lynn pecked at the keyboard and wrote:

...
On 24/11/11 17:52, phanisvara das wrote:

...
On Thu, 24 Nov 2011 22:03:47 +0530, Anton Aylward wrote:

...
I'm staying away from 12.1 until its stabilized

for the time being you could use 12.1 with sysV. as far as i've seen, all these problems disappear when the user switches to the old init process. i'm not sure how long sysV will remain available, but looking at the various problems, it's not likely to go away soon.

+ 1

System V works. systemd as in 12.1 is just not ready. Please vote:

https://bugzilla.novell.com/show_bug.cgi?id=732395

Any vote will not matter.

How then can we tell the devs that systemd is not ready yet? L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Ken Schneider - openSUSE

18:32

On 11/24/2011 01:28 PM, lynn pecked at the keyboard and wrote:

...

On 24/11/11 19:24, Ken Schneider - openSUSE wrote:

...
On 11/24/2011 01:14 PM, lynn pecked at the keyboard and wrote:

...
On 24/11/11 17:52, phanisvara das wrote:

...
On Thu, 24 Nov 2011 22:03:47 +0530, Anton Aylward wrote:

...
I'm staying away from 12.1 until its stabilized

for the time being you could use 12.1 with sysV. as far as i've seen, all these problems disappear when the user switches to the old init process. i'm not sure how long sysV will remain available, but looking at the various problems, it's not likely to go away soon.

+ 1

System V works. systemd as in 12.1 is just not ready. Please vote:

https://bugzilla.novell.com/show_bug.cgi?id=732395

Any vote will not matter.

How then can we tell the devs that systemd is not ready yet? L x

By filling bug reports and including a note about your displeasure with the forced change. We do have a voice on this list but no right to dictate what happens, that is up to the devs and their vote. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan

18:35

* lynn [11-24-11 13:30]:

...

On 24/11/11 19:24, Ken Schneider - openSUSE wrote:

...
On 11/24/2011 01:14 PM, lynn pecked at the keyboard and wrote:

...
System V works. systemd as in 12.1 is just not ready. Please vote:

https://bugzilla.novell.com/show_bug.cgi?id=732395

Any vote will not matter.

How then can we tell the devs that systemd is not ready yet?

Bug-reports, but then the problems will be solved :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

18:44

lynn said the following on 11/24/2011 01:14 PM:

...

On 24/11/11 17:52, phanisvara das wrote:

...
On Thu, 24 Nov 2011 22:03:47 +0530, Anton Aylward wrote:

...
I'm staying away from 12.1 until its stabilized

for the time being you could use 12.1 with sysV. as far as i've seen, all these problems disappear when the user switches to the old init process. i'm not sure how long sysV will remain available, but looking at the various problems, it's not likely to go away soon.

+ 1

System V works. systemd as in 12.1 is just not ready. Please vote:

https://bugzilla.novell.com/show_bug.cgi?id=732395

"systemd takes 5 minutes to start processes " The something *IS* seriously wrong. My Fedora-15 desktop boots faster than my neighour's SSD-powered Ubuntu netbook! -- "Obscurity is the refuge of incompetence." -- Robert Heinlein, -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

lynn

19:00

On 24/11/11 19:44, Anton Aylward wrote:

...

lynn said the following on 11/24/2011 01:14 PM:

...
On 24/11/11 17:52, phanisvara das wrote:

...
On Thu, 24 Nov 2011 22:03:47 +0530, Anton Aylward wrote:

...
I'm staying away from 12.1 until its stabilized

for the time being you could use 12.1 with sysV. as far as i've seen, all these problems disappear when the user switches to the old init. process. i'm not sure how long sysV will remain available, but looking at the various problems, it's not likely to go away soon.

+ 1

System V works. systemd as in 12.1 is just not ready. Please vote:

https://bugzilla.novell.com/show_bug.cgi?id=732395

"systemd takes 5 minutes to start processes"

The something *IS* seriously wrong. My Fedora-15 desktop boots faster than my neighour's SSD-powered Ubuntu netbook!

Yeah don't I know. It's making openSUSE look ridiculous. It reminds me of Intel's Pentium bug in the 1990's. 'We know it's wrong but we are not going to do anything about it.' It took the might of IBM to make them change their minds. Golden days! L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

deabru

26 Nov 26 Nov

09:47

On Jueves, 24 de noviembre de 2011 08:39:19 James Knott escribió:

...

Per Jessen wrote:

...
James Knott wrote:

...
In attempting to set up Thunderbird to use a system email account, I discovered a problem with mail. Thunderbird complained it couldn't find the mail spool. I then tried running mail from the command prompt. After trying to send a message, I got an error "postdrop: warning: unable to look up public/pickup: No such file or directory". This is on 12.1. I also tried creating another user, to make sure the problem wasn't caused by something in my home directory, but got the same result.

Any ideas? This is the first time I've ever seen mail fail.

Possibly: https://bugzilla.novell.com/show_bug.cgi?id=730787

iow, make sure that postfix is running.

That's the problem. It's enabled for run levels 3 & 5, but not running. After manually starting, mail works. I guess I'll have to start it in after.local.

"dmesg | less" and see what failed. Maybe there are some dependencies that haven't started. In my case, was remote-fs. Regards. -- deabru, bai deabrunaiz... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen

27 Nov 27 Nov

09:04

deabru wrote:

...

On Jueves, 24 de noviembre de 2011 08:39:19 James Knott escribió:

...
Per Jessen wrote:

...
James Knott wrote:

...
In attempting to set up Thunderbird to use a system email account, I discovered a problem with mail. Thunderbird complained it couldn't find the mail spool. I then tried running mail from the command prompt. After trying to send a message, I got an error "postdrop: warning: unable to look up public/pickup: No such file or directory". This is on 12.1. I also tried creating another user, to make sure the problem wasn't caused by something in my home directory, but got the same result.

Any ideas? This is the first time I've ever seen mail fail.

Possibly: https://bugzilla.novell.com/show_bug.cgi?id=730787

iow, make sure that postfix is running.

That's the problem. It's enabled for run levels 3 & 5, but not running. After manually starting, mail works. I guess I'll have to start it in after.local.

"dmesg | less" and see what failed. Maybe there are some dependencies that haven't started.

I get very little systemd output in dmesg - certainly nothing about postfix, do I need to enable debug output or some such? -- Per Jessen, Zürich (3.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

lynn

09:42

On 27/11/11 10:04, Per Jessen wrote:

...

deabru wrote:

...
On Jueves, 24 de noviembre de 2011 08:39:19 James Knott escribió:

...
Per Jessen wrote:

...
James Knott wrote:

...
In attempting to set up Thunderbird to use a system email account, I discovered a problem with mail. Thunderbird complained it couldn't find the mail spool. I then tried running mail from the command prompt. After trying to send a message, I got an error "postdrop: warning: unable to look up public/pickup: No such file or directory". This is on 12.1. I also tried creating another user, to make sure the problem wasn't caused by something in my home directory, but got the same result.

Any ideas? This is the first time I've ever seen mail fail.

Possibly: https://bugzilla.novell.com/show_bug.cgi?id=730787

iow, make sure that postfix is running.

That's the problem. It's enabled for run levels 3& 5, but not running. After manually starting, mail works. I guess I'll have to start it in after.local.

"dmesg | less" and see what failed. Maybe there are some dependencies that haven't started.

I get very little systemd output in dmesg - certainly nothing about postfix, do I need to enable debug output or some such?

It's not just postfix that isn't started. systemd doesn't start many other processes either: https://bugzilla.novell.com/show_bug.cgi?id=732395 The only workaround I found is to use system V init or wait until the system is up (you can tell when you get a login prompt on console 1), login as root and start the services manually. For me, the latter involves a wait of over 5 minutes. HTH L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

4551

Age (days ago)

4555

Last active (days ago)

List overview

Download

21 comments

8 participants

participants (8)

Anton Aylward
deabru
James Knott
Ken Schneider - openSUSE
lynn
Patrick Shanahan
Per Jessen
phanisvara das