postfix no configuration resolvconf

Bug #990944 reported by loke
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postfix (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I had configured Postfix to have "no configuration." After I installed DNSMasq, and disabled dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf, and started the service, there were errors reported because of Postfix not having any configuration:

/usr/sbin/postconf: fatal: open /etc/postfix/main.cf: No such file or directory
cp: `/etc/resolv.conf' and `/etc/resolv.conf' are the same file
run-parts: /etc/resolvconf/update-libc.d/postfix exited with return code 1
run-parts: /etc/resolvconf/update.d/libc exited with return code 1
 * Restarting DNS forwarder and DHCP server dnsmasq [ OK ]
/usr/sbin/postconf: fatal: open /etc/postfix/main.cf: No such file or directory

After reconfiguring postfix for "Local Only," the problem went away. I think it should gracefully ignore, if it can't find a postfix configuration.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Please try the updated package in the precise-proposed repository. See Bug #980682 for details. Although it was based on a slightly different bug, I think it would fix this one too.

Changed in postfix (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for postfix (Ubuntu) because there has been no activity for 60 days.]

Changed in postfix (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.