| View previous topic :: View next topic |
| Author |
Message |
SilverOne
Apprentice
Joined: 10 Nov 2003
Posts: 161
|
 Posted: Wed Apr 28, 2004 1:39 pm Post subject: [solved]ssmtp broke postfix |
 |
|
Hi,
I don't know why but for some reason I updated ssmtp 2 days ago, while I had an installation of postfix running.
Now postifx works fine for receiving and handling mail, but the /usr/sbin/sendmail.postfix program has dissappeared, causing mutt to throw up an error...
How can I fix this?
Was /usr/sbin/sendmail.postfix an alias I can correct?
Or am I in for more trouble (mail reception and forwarding by postfix seems to work fine)
Last edited by SilverOne on Wed Apr 28, 2004 6:22 pm; edited 1 time in total |
|
| Back to top |
|
 |
mazirian
Apprentice
Joined: 26 Jun 2003
Posts: 273
Location: Yarmouth, ME
|
| Posted: Wed Apr 28, 2004 2:48 pm Post subject: |
|
|
| I am , admitteldy, a n00b, but I didn't think those two packages could co-exist. Usually ssmpt will block an emerge of postfix. In any event, why do you need ssmtp when postfix will do smtp for you? |
|
| Back to top |
|
|
SilverOne
Apprentice
Joined: 10 Nov 2003
Posts: 161
|
| Posted: Wed Apr 28, 2004 3:07 pm Post subject: |
|
|
I don't need ssmtp but apparantly it was installed (2.48 ) and some package had it as it's dependency.
doing a emerge -uD world updated the ssmtp package to 2.60
I don't think I need ssmtp but I wonder what my best course of action is.
unmerge ssmtp (emerge -c ssmtp) or just re-emerge postfix?
p.s. a "/usr/bin/emerge -p postfix"
produces:
[ebuild R ] net-mail/postfix-2.0.19
and does not mention any blocking packages. |
|
| Back to top |
|
|
mazirian
Apprentice
Joined: 26 Jun 2003
Posts: 273
Location: Yarmouth, ME
|
| Posted: Wed Apr 28, 2004 5:12 pm Post subject: |
|
|
Well you certainly don't need ssmtp any longer if you are using postfix (like me!).
I would:
| Code: |
emerge -Cp ssmpt #and assuming there's no weirdness...
emerge -C ssmtp
|
Then, if you still don't have postfix's sendmail link:
or maybe even re-emerge postfix anyway.
Hope it all works out. |
|
| Back to top |
|
|
mikef
n00b
Joined: 02 Apr 2003
Posts: 14
|
| Posted: Wed Apr 28, 2004 5:55 pm Post subject: |
|
|
I think that when you updated ssmtp you allowed etc-config to update /etc/mailer.conf. You should be able to restore this to use postfix by simple editing.
This is part of a mechanism to overcome the problem that each agent used to overwrite sendmail.
_________________
Michael |
|
| Back to top |
|
|
SilverOne
Apprentice
Joined: 10 Nov 2003
Posts: 161
|
| Posted: Wed Apr 28, 2004 6:05 pm Post subject: |
|
|
| mikef wrote: | I think that when you updated ssmtp you allowed etc-config to update /etc/mailer.conf. You should be able to restore this to use postfix by simple editing.
|
I checked the man page for mailwrapper and the /etc/mailer.conf file.
The file seems ok to me as it refers to /usr/sbin/sendmail.postfix
But that file (sendmail.postfix) is missing.
unmerging ssmtp didn't help (as I expected), so I'll try re-emerging postfix.
EDIT: well re-emerging postfix did the trick.
funny thing though: it doesn't use the mailwrapper (/etc/mailer.conf)
before re-emerging postfix (i.e. the ssmtp was the latest mta installed) /usr/sbin/sendmail would invoke the mailwrapper, and it said look for /usr/sbin/sendmail.postfix.
Well after re-emerging postfix the wrapper still says to look for sendmail.postfix, but running /usr/sbin/sendmail no longer complains.
Apparently /usr/sbin/sendmail has been replaced by the postfix ebuild so the wrapper is no longer used.
Thanks a lot, it works fine now! |
|
| Back to top |
|
|
|
Networking & Security
