OpenSuSE 12.3, and Yast Network Services, Mail Server is adjusting files in /etc/mail, /usr/share/sendmail (as shown by ls -l and see the date). However, /etc/sendmail.cf is not being updated. [The file in place is one I copied from an OpenSuSE 11.1 machine I need to upgrade. Remove it and Yast fails to restart sendmail, does not put a file in its place.]
/etc/sysconfig/mail has MAIL_CREATE_CONFIG=“yes”
/usr/share/sendmail/README refers to config.mc and ‘./Build config.cf’ - but these are not on the machine (i.e #find / -name [config.mc | Build | config.cf] gives a null return in each case). So I am lost at the README stage!
I have two questions :
What is the top of the tree that would allow me to do m4 /somewhere/filename.mc > test.cf manually?
Have I missed installing something and causing Yast to fail?
If you change the config in YaST->Network Services->EMail, it should be run by YaST though.
And no idea about /etc/sendmail.conf. Is that even used by postfix’s sendmail? I don’t have that file on my system.
Or are you using the package “sendmail”? I don’t think you can configure that with YaST. YaST only seems to support postfix.
Hi! Thanks for the reply.
I am running the sendmail package that was included in OpenSuSE. I suspect you may be correct about only supporting postfix in Yast. Why include it but not provide full support? :\
config.postfix is not on my system … presumably removed by Yast when I opted for sendmail instead of postfix. Previous versions (11.1 was the last I used) did configure sendmail with Yast.
The release notes make no mention of sendmail - again suggesting it is not supported?
Sendmail is my comfort zone for delivery testing, etc - including some local rulesets I need - and where I have all my books and notes. My critical issue is I am trying to recover from a lightning strike that fried the motherboard on the server on my LAN. Perhaps I need to do a rebuild on SuSE 11.1 for ‘production’ then move to postfix in a test environment before going ‘live’.
11.1 is way out of support. ie no updates or fixes for several years.
Not many use sendmail any more so it is a matter of priorities and resources. But sendmail can be fully supported from the command line. If you would like to volunteer to support a Yast module to configure sendmail I’m sure the developers would be happy to include it.
I haven’t really looked at it in detail, but config.sendmail does seem to read the same /etc/sysconfig/ variables as config.postfix.
So the existing module might work even with sendmail. But again, you have to run config.sendmail manually to create the configuration, just like you have to run config.postfix for creating postfix’s configuration…
On 2014-03-15 18:36, gogalthorp wrote:
>
> 11.1 is way out of support. ie no updates or fixes for several years.
>
> Not many use sendmail any more so it is a matter of priorities and
> resources. But sendmail can be fully supported from the command line. If
> you would like to volunteer to support a Yast module to configure
> sendmail I’m sure the developers would be happy to include it.
No, no, there is something wrong here.
YaST has always configured sendmail out of the box, for decades. Later
postfix was added, but sendmail was not removed. You could choose
anyone, just that postfix was the default and recommended. But of
course, people that already had a sendmail setup, or were just familiar
with it, did not need to migrate.
There has been no official notification in the releases notes, as far as
I remember, about YaST stopping to support the automatic configuration
of sendmail. If this has stopped working, or has been removed, I would
report it immediately in Bugzilla, and let the maintainers say what they
have to say, officially.
The fact that the functionality in SuSEconfig has been moved to
config.sendmail hints that this is a Bug, or some configuration problem
local to the OP.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I just had a look at the 13.1 YaST module (/usr/share/YaST2/modules/Mail.rb), and sendmail apparently is still supported.
At least it distinguishes between sendmail and postfix in several places and writes /etc/sysconfig/sendmail.
I have no idea whether that works though. (I don’t even have sendmail installed)
While it does run config.postfix, I cannot find any reference to config.sendmail anywhere in /usr/share/YaST2/.
So maybe that has been forgotten to add when SuSEconfig was removed?
The fact that the functionality in SuSEconfig has been moved to
config.sendmail hints that this is a Bug
SuSEconfig was removed intentionally, its functionality was moved to scripts like config.postfix and config.sendmail where necessary.
I don’t see a bug here (or do I misunderstand you?).
Of course, if the YaST module does not call config.sendmail (which indeed it doesn’t, unless I missed something) although it’s needed, that would be a bug (IMHO) that should be reported.
On 2014-03-15 20:46, wolfi323 wrote:
>
> robin_listas;2630674 Wrote:
> While it does run config.postfix, I cannot find any reference to
> config.sendmail anywhere in /usr/share/YaST2/.
> So maybe that has been forgotten to add when SuSEconfig was removed?
>
>> The fact that the functionality in SuSEconfig has been moved to
>> config.sendmail hints that this is a Bug
> SuSEconfig was removed intentionally, its functionality was moved to
> scripts like config.postfix and config.sendmail where necessary.
> I don’t see a bug here (or do I misunderstand you?).
I mean that if the intention was to not support automatic configuration
of sendmail, when SuSEconfig was removed from the distribution, they
would not have created config.sendmail at all.
Thus, as they created config.sendmail (with the old functionality of
SuSEconfig sendmail module), it was their intention to keep supporting
sendmail.
Thus, YaST failing to create a complete configuration for sendmail is a Bug.
Is that clearer?
> Of course, if the YaST module does not call config.sendmail (which
> indeed it doesn’t, unless I missed something) although it’s needed, that
> would be a bug (IMHO) that should be reported.
Seems to me that Yast does not fully support sendmail - unintentionally?
I found the ‘top of the tree’ to build the sendmail.cf file. Just run /usr/lib/sendmail.d/update and it picks up all the variables input via Yast, restart sendmail and it does what I expect it to do.
A bit messy, but works for me.
I can now focus on getting back operationally, then learn postfix on a test machine and play ‘catchup’ with the rest of the world!
>On 2014-03-15 18:36, gogalthorp wrote:
>>
>> 11.1 is way out of support. ie no updates or fixes for several years.
>>
>> Not many use sendmail any more so it is a matter of priorities and
>> resources. But sendmail can be fully supported from the command line. If
>> you would like to volunteer to support a Yast module to configure
>> sendmail I’m sure the developers would be happy to include it.
>
>No, no, there is something wrong here.
>
>YaST has always configured sendmail out of the box, for decades. Later
>postfix was added, but sendmail was not removed. You could choose
>anyone, just that postfix was the default and recommended. But of
>course, people that already had a sendmail setup, or were just familiar
>with it, did not need to migrate.
>
>There has been no official notification in the releases notes, as far as
>I remember, about YaST stopping to support the automatic configuration
>of sendmail. If this has stopped working, or has been removed, I would
>report it immediately in Bugzilla, and let the maintainers say what they
>have to say, officially.
>
>The fact that the functionality in SuSEconfig has been moved to
>config.sendmail hints that this is a Bug, or some configuration problem
>local to the OP.
I am a tad late to the party here, but a lot of yast modules are optional.
Perhaps all that is needed is to install all yast modules?
Well, if he didn’t have the YaST mail module installed, how would he be able to use it?
Another note to the OP:
Up to now I didn’t realize that config.sendmail is missing in 12.3. It does exist in the 13.1 package. But I don’t know whether it would be called by YaST or not. (as I said, I couldn’t really find a reference to it in the YaST module, but maybe I just overlooked it)
>
>josephkk;2632810 Wrote:
>> I am a tad late to the party here, but a lot of yast modules are
>> optional.
>> Perhaps all that is needed is to install all yast modules?
>>
>Well, if he didn’t have the YaST mail module installed, how would he be
>able to use it?
We both wish that the yast modules were that cleanly defined. Too often
you can install something and not get all the relevant yast configuration
modules with it.
>
>Another note to the OP:
>wolfi323;2630800 Wrote:
>> Well, that’s exactly what config.sendmail does. It’s just a small
>> wrapper script that calls /usr/lib/sendmail.d/update.
>Up to now I didn’t realize that config.sendmail is missing in 12.3. It
>does exist in the 13.1 package. But I don’t know whether it would be
>called by YaST or not. (as I said, I couldn’t really find a reference to
>it in the YaST module, but maybe I just overlooked it)
>On 2014-03-25 11:26, josephkk wrote:
>> On Sat, 15 Mar 2014 19:08:08 GMT, “Carlos E. R.” <> wrote:
>
>> I am a tad late to the party here, but a lot of yast modules are optional.
>> Perhaps all that is needed is to install all yast modules?
>>
>> ?-)
>
>Er… yes, but there is no sendmail module, just a mail module that must
>include all possible implementations.
Please take a look at installing ALL yast modules.
yast2-mail is the only thing needed to configure a mail server. (no matter whether it’s postfix or sendmail)
And if you install a module and don’t get other stuff with it that’s needed to use it, it would be a packaging bug and should be reported.
On 2014-03-26 06:52, josephkk wrote:
> On Tue, 25 Mar 2014 13:38:09 GMT, “Carlos E. R.” <> wrote:
>> Er… yes, but there is no sendmail module, just a mail module that must
>> include all possible implementations.
>
> Please take a look at installing ALL yast modules.
There is no yast-sendmail module, nor yast-postfix.
Telcontar:~ # zypper se yast | grep -i sendmail
Telcontar:~ # zypper se yast | grep -i postfix
Telcontar:~ #
There are only generic yast-mail modules.
> Telcontar:~ # zypper se yast | grep -i mail
> | rubygem-webyast-mailsetting | WebYaST - system mail settings | package
> | rubygem-webyast-mailsetting-doc | RDoc documentation for webyast-mailsetting | package
> | rubygem-webyast-mailsetting-testsuite | Test suite for webyast-mailsetting | package
> i | yast2-mail | YaST2 - Mail Configuration | package
> i | yast2-mail-plugins | YaST2 - Users/Group Plugins for the mail delivery configuration | package
> Telcontar:~ #
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
>
>josephkk;2633094 Wrote:
>> We both wish that the yast modules were that cleanly defined. Too often
>> you can install something and not get all the relevant yast
>> configuration
>> modules with it.
>>
>yast2-mail is the only thing needed to configure a mail server. (no
>matter whether it’s postfix or sendmail)
>And if you install a module and don’t get other stuff with it that’s
>needed to use it, it would be a packaging bug and should be reported.
Yep. Yet if no one knows that the yast modules exist, it won’t get
reported.
