update from a previous 11.1 install to 11.2 RC2 seems to have left a previous working internal maildelivery broken. After update, yast2 mail server was no longer an active process and setup thru yast2 was run again using standard mode with no connection… problem solved… not!
no mail delivery with sent mail trapped in maildrop folder.
mail.err log:
Nov 9 16:24:49 blkdragon postfix/qmgr[29978]: fatal: open database /etc/postfix/relay.db: No such file or directory
Nov 9 16:24:53 blkdragon postfix/cleanup[30005]: fatal: open database /etc/postfix/relay.db: No such file or directory
i can see no glaring errors in /etc/postfix/main.cf, and i’m a bit mystified why it would look for available relays (relay.db does not exist in /etc/postfix) on a standard setup, hoping someone has been through this before.
the suggestion did indeed eliminate the previous error msg, but now i have others:
Nov 10 10:08:49 blkdragon postfix/pickup[10252]: B1D571FA6E: uid=1000 from=<blkdragon@localhost>
Nov 10 10:08:49 blkdragon postfix/cleanup[12792]: B1D571FA6E: message-id=<200911101008.49479.blkdragon@localhost>
Nov 10 10:08:49 blkdragon postfix/qmgr[10254]: B1D571FA6E: from=<blkdragon@localhost.localdomain>, size=495, nrcpt=1 (queue active)
Nov 10 10:08:50 blkdragon postfix/smtp[12258]: connect to blkdragon.site[208.69.36.132]:25: No route to host
Nov 10 10:08:50 blkdragon postfix/smtp[12258]: B1D571FA6E: to=<root@blkdragon.site>, relay=none, delay=0.51, delays=0.22/0/0.28/0, dsn=4.4.1, status=deferred (connect to blkdragon.site[208.69.36.132]:25: No route to host)
then in the other log file:
Nov 10 10:28:49 blkdragon postfix/local[20894]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled
i believe i need to find the reason it was looking for a relay (unneeded) in the first place, if all i’m looking to accomplish is local machine messaging.
It thinks blkdragon.site is an external host so it’s trying to send the mail outside your LAN. I don’t know how your email got addressed to root@blkdragon.site. Did you enter that explicitly or did it get rewritten from root@localdomain or what? I have no idea, not knowing how you set your system up.
thanks for the feedback, Ken… actually my paste was second try at directing mail to root… (root@localhost then root@sitename).
I’ll dig deeper into this, my concern was that somehow the existing config files were not upgraded properly when postfix was updated because it worked perfectly before.
This does appear to be an upgrade bug. Yesterday, I upgraded from 11.1 to 11.2. Today, I discovered the same problem as reported above – no local mail delivery and relay.db errors in the mail.err log. After applying your workaround, local mail started working again.
ah, just revisited this thread to convey my eventual solution and i see that some others had the same result.
my haste to fix made me err in opening the Yast2 Mail Server module and starting a Standard server (which i didn’t need), therefore ken_yap’s solution didn’t immediately work.
when the lightbulb came on, i went to Yast2>SysConfigEditor>Network>Mail>General>Config_Type and changed it back to “undef” (revoking the Standard Mail server i had initiated previously)…and then did the “postmap…etc” command that ken previously gave to generate the relay.db file. then “postfix reload” and it was fixed.
thanks again ken
guess all that upgraded from 11.1 will run into this.
Perhaps one of you might be so kind to enter it into Novell’s bugzilla so that something will be done about it? Just say that relay.db was not found but relay was there and the workaround. Perhaps point them to this thread. The devs will figure out what needs to be fixed.
I haven’t upgraded yet so I don’t have firsthand experience of this bug. But it’s good to know ahead of time.
I have been testing as Root, but when I test as User, the result is the same:
“No mail for tabanna”
I am totally ignorant : Imagine that Passwords are handled by /etc/passwd . . . I do not even know what NIS is !!
/var/log/mail.info says:
Dec 6 10:17:01 AIG postfix/pickup[10080]: D92E6714F: uid=1000 from=<tabanna>
Dec 6 10:17:01 AIG postfix/cleanup[10312]: D92E6714F: message-id=<20091206081701.D92E6714F@AIG.loca
Dec 6 10:17:01 AIG postfix/qmgr[29682]: D92E6714F: from=<tabanna@AIG.localdomain>, size=613, nrcpt=
Dec 6 10:17:02 AIG postfix/local[10314]: warning: dict_nis_init: NIS domain name not set - NIS look
Dec 6 10:17:02 AIG postfix/local[10314]: D92E6714F: to=<tabanna@AIG.localdomain>, orig_to=<root>, r
Dec 6 10:17:02 AIG postfix/cleanup[10312]: 0F2277151: message-id=<20091206081702.0F2277151@AIG.loca
Dec 6 10:17:02 AIG postfix/qmgr[29682]: 0F2277151: from=<>, size=2544, nrcpt=1 (queue active)
Dec 6 10:17:02 AIG postfix/bounce[10315]: D92E6714F: sender non-delivery notification: 0F2277151
Dec 6 10:17:02 AIG postfix/qmgr[29682]: D92E6714F: removed
Dec 6 10:17:02 AIG postfix/local[10314]: 0F2277151: to=<tabanna@AIG.localdomain>, relay=local, dela
Dec 6 10:17:02 AIG postfix/qmgr[29682]: 0F2277151: removed
…
my /var/log/ says :
Dec 6 09:11:59 AIG postfix/local[9212]: warning: dict_nis_init: NIS domain name not set - NIS looku
Dec 6 09:17:01 AIG postfix/local[9358]: warning: dict_nis_init: NIS domain name not set - NIS looku
Dec 6 09:26:15 AIG postfix/local[9515]: warning: dict_nis_init: NIS domain name not set - NIS looku
Dec 6 10:17:02 AIG postfix/local[10314]: warning: dict_nis_init: NIS domain name not set - NIS look