dcron fails to send emails, as it is trying to run /usr/lib/sendmail, which is not provided by recent? exim - I am almost sure that I used to receive mails from my cron. fix: cd /usr/lib ln -s ../sbin/sendmail maybe this link should be created by mailbase. Reproducible: Always
*** This bug has been marked as a duplicate of bug 82772 ***
Florian, can you tell me what emerge --info|grep USE outputs?
sorry for the bug spam.
(In reply to comment #2) > Florian, can you tell me what emerge --info|grep USE outputs? I dont have mailwrapper set. USE="acl amd64 apache2 bash-completion berkdb bitmap-fonts caps cli cracklib crypt dri fortran gdbm gpm iconv isdnlog ldap midi mmx mudflap ncurses nls nptl nptlonly ogg openmp pam pcre perl pppd python readline reflection session spl sse sse2 ssl tcpd threads truetype-fonts type1-fonts unicode vhosts vim-syntax vorbis xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i810 mach64 mga neomagic nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo"
very odd, what are the permissions on /usr/lib ? does the ebuild show >>> /usr/lib/sendmail -> /usr/sbin/sendmail when you build it?
(In reply to comment #5) > very odd, what are the permissions on /usr/lib ? # ls -dl /usr/lib lrwxrwxrwx 1 root root 5 2006-12-22 03:35 /usr/lib -> lib64 # ls -dl /usr/lib64 drwxr-xr-x 38 root root 25440 2007-08-21 14:29 /usr/lib64 > does the ebuild show > > >>> /usr/lib/sendmail -> /usr/sbin/sendmail > > when you build it? no, only links listed are: >>> /usr/bin/mailq -> exim >>> /usr/bin/newaliases -> exim
(In reply to comment #6) > (In reply to comment #5) > > very odd, what are the permissions on /usr/lib ? > > # ls -dl /usr/lib > lrwxrwxrwx 1 root root 5 2006-12-22 03:35 /usr/lib -> lib64 > # ls -dl /usr/lib64 > drwxr-xr-x 38 root root 25440 2007-08-21 14:29 /usr/lib64 > Same permissions here, > > does the ebuild show > > > > >>> /usr/lib/sendmail -> /usr/sbin/sendmail > > > > when you build it? > > no, only links listed are: > >>> /usr/bin/mailq -> exim > >>> /usr/bin/newaliases -> exim > What profile and arch are you building on? I think i've replicated it in a very specific sequence, if I build exim fresh, then i get the symlink, if I rebuild exim the link is removed, I'm guessing by the un-merge of the previous version. I'm going to be away on work business this week, so I may not be able to work on this any more until next weekend, hopefully i'll still be able to read my email and access bugzie, but I can't promise. could you try emerge -C exim && emerge exim and check to see if the link appears for you? if so i think we have the problem diagnosed, but i have no idea what the fix would be, excepting to blindly force that link.
What I expect to happen is the following, this is assuming no mailwrapper a) if the symlink already exists, to leave it alone b) if the symlink doesn't exist to create it. if exim is unmerged, then the symlink state should be the same, if it existed, it should still exist and point to whereever, if it didn't, then there should be no symlink. This is what appears to not be working, I'm not going to delay the release of 4.68 because of it, but will hopefully have it in an -r release.
(In reply to comment #8) > What I expect to happen is the following, this is assuming no mailwrapper > > a) if the symlink already exists, to leave it alone If the symlink exists, you have a missing blocker and broken ebuild, as explained numerous times to no avail on bug 82772. The mailwrapper logic in the ebuild is broken, is broken, is broken... I give up, doesn't go anywhere.
(In reply to comment #9) > (In reply to comment #8) > > What I expect to happen is the following, this is assuming no mailwrapper > > > > a) if the symlink already exists, to leave it alone > > If the symlink exists, you have a missing blocker and broken ebuild, as > explained numerous times to no avail on bug 82772. The mailwrapper logic in the > ebuild is broken, is broken, is broken... I give up, doesn't go anywhere. > Jakub: perhaps you're forgetting that a user can add the symlink themselvs, most of them know how to use ln. Ive had enough of your attitude, go and boil your head, as it is, i'll be retiring at the end of the month as I've had enough of attempting to deal with you. If I thought it would do any good, i'd have raised this issue with dev-rel again.
*** Bug 236371 has been marked as a duplicate of this bug. ***
Reassign to net-mail herd as peitolm retires
fixed in exim-4.69-r3
