Topic: email address for updates

[rgmhtt]

What email address is used to notify about updates?

The whole update information is rather vague.  I suppose having it under software installer makes sense but in a rather indirect way.

My Astaro firewall has the update status in the main page so you know as soon as you log in (besides a configurable email notification).

Based on the answer to what the email address for notification is, I have a bug report or two to submit...

[janet]

rgmhtt

admin-yum@yoursmeserverdomain
which effectively goes to
admin@yoursmeserverdomain

That by the way is a design "feature" of sme
for user
you can send to
user-anything@yourdomain
and it wil be delivered to the user account

ie where user-anything can be user-yum or user-contribs or user-hotmail etc
It helps to identify the source & filter stuff in your email client
You can use or hand out addresses like user-contribs@yourdomain to register at contribs and so on for other websites etc, without needing to setup all those email addresses seperately.

[janet]

rgmhtt

The whole update information is rather vague.

Of course it's vague if you do not yet understand it, but in fact it is not vague, it is well structured and thought out with a lot of work having gone into the yum implementation to get it to where it is now in sme server.

You are new to sme and making quite a bit of criticism in this and other posts.

I would suggest that you would be far better off to hold on to your comments until you get more familiar with sme and learn how it works and what it is doing, before jumping to conclusions and deciding that it's a bug or needs a NFR (New Feature Request).

Please learn & understand how sme works, before wanting (others) to rewrite code for your perceived issues !

Have you read
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Yum_Updates

I suggest you read everything on the contribs.org and related websites as it may bring your knowledge "up to speed".

[rgmhtt]

rgmhtt

admin-yum@yoursmeserverdomain
which effectively goes to
admin@yoursmeserverdomain

That by the way is a design "feature" of sme
for user
you can send to
user-anything@yourdomain
and it wil be delivered to the user account

ie where user-anything can be user-yum or user-contribs or user-hotmail etc
It helps to identify the source & filter stuff in your email client
You can use or hand out addresses like user-contribs@yourdomain to register at contribs and so on for other websites etc, without needing to setup all those email addresses seperately.

I suspected it was something like that.  I read through ch 13 where the Software Installer is.  I read the FAQ where yum update is mentioned.  I searched the wiki for both 'yum' and 'update' (separately).  I searched this forum for 'yum'.  I did not find any information of the address where update announcements went to.

Also you indicate that I can change where these announcements go to.  I assume this is via the 'pseudonyms' option?  Again, I have searched the wiki and have found this information.  Maybe my problem is I am just not enough of a newbie and am looking at the documents the wrong way...

And, Mary, I really appreciate your help.

[janet]

rgmhtt

That feature has been mentioned a good few times in the forums, devinfo list and bugzilla, I don't recall if it is documented elsewhere. A read of the code would surely find it.

Also you indicate that I can change where these announcements go to. 

Be careful what you think you read. I never said that.
That address is hard coded.

If you create a seperate user account for admin-yum, then mail will be delivered there, in preference to admin.
Then you can redirect where those emails will go.

[rgmhtt]

rgmhtt

Of course it's vague if you do not yet understand it, but in fact it is not vague, it is well structured and thought out with a lot of work having gone into the yum implementation to get it to where it is now in sme server.

You are new to sme and making quite a bit of criticism in this and other posts.

I have had the pleasure of reading many systems documentation and have written some myself.  One thing I have learned is that a community develops a way to document their technology and can be a little near-sighted on how others handle it.  I have been quite guilty of this myself,  RFC2510 really bit us; too many us-centric jokes which are now historic.  A number of vendors where English was not their first language implemented ESP-NULL wrong because of those jokes.

I would suggest that you would be far better off to hold on to your comments until you get more familiar with sme and learn how it works and what it is doing, before jumping to conclusions and deciding that it's a bug or needs a NFR (New Feature Request).

If the documentation is missing or it takes extensive wiki searching to find it, that MIGHT be considered a bug in the documentation, or might be the style of the documenters. I was asked to submit bug reports on documentation 'problems'.  It is up to the sme community to decide if I am correct, or 'just did not get it'.  The fact that Chapter 6 starts out with "When installation is complete and if you set server console mode to "auto", the opening screen of the SME Server server console will appear: " but this panel now apparently no longer a part of the install is either a bug in the install or in the documentation.  The choice is up to the sme developer community.  This is NOT a criticism, but a report on a fact.  Perhaps I could lighten my tone; I am a bit rushed to get something up before I head to IETF in SF tomorrow....

Please learn & understand how sme works, before wanting (others) to rewrite code for your perceived issues !

I report my observations as a newbie to sme, but far from a newbie to Samba, SMB, Centos, etc.  So I AM trying to lean how sme works; I have to if I am going to use it.

Have you read
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Yum_Updates

I suggest you read everything on the contribs.org and related websites as it may bring your knowledge "up to speed".

I read the whole FAQ before reading the manual.  Then I read, probably too quickly, the whole manual before starting the install (probably why I missed the information linkage problem between the end of CH 5 and start of Ch 6).  I DID miss a number of wiki pages which have since been pointed out.  Ones that are not directly linked to from the manual or FAQ,,,

I will not be able to do too much this week, being at the IETF.  I believe I have a tunnel setup back to the sme server so I can try things out IF I have the time...

[rgmhtt]

rgmhtt

That feature has been mentioned a good few times in the forums, devinfo list and bugzilla, I don't recall if it is documented elsewhere. A read of the code would surely find it.

But not in the wiki as to where they go.

Be careful what you think you read. I never said that.
That address is hard coded.

A poorly worded response on my part.  Sorry.  In too much of a hurry.

I assumed the address was hard coded, a shame, but as you said there is a way to get it to someplace else.

If you create a separate user account for admin-yum, then mail will be delivered there, in preference to admin.
Then you can redirect where those emails will go.

Think I got it.  So I create a user admin-yum and in my case this is in domain test.htt-consult.com.  I can then create a pseudonym to me@htt-consult.com.

A howto would be nice.  I AM starting a doc file for sme notes, and a doc file != wiki page.  And it is a busy month for me: IETF, Passover, Son #2's wedding...  But then I suspect spare time is not a common commodity here...

[janet]

rgmhtt

So I create a user admin-yum and in my case this is in domain test.htt-consult.com.  I can then create a pseudonym to me@htt-consult.com.

No need to create a pseudonym.
Just edit the admin-yum user account to forward mail to whatever user or email address you wish.

A howto would be nice.

Perhaps a read of all the other chapters instead.

Your questions are basic setup, most of which is obvious if you open up the server manager panels, read the descriptions provided, and try out the options.

I don't think a seperate howto is required, but if you wish to make one, then feel free. I'd suggest it would be better that you use your time to make submissions to improve the text of the manuals. The manual maintainers will implement your suggested changes if they think them worthy.

[rgmhtt]

rgmhtt

Perhaps a read of all the other chapters instead.

Your questions are basic setup, most of which is obvious if you open up the server manager panels, read the descriptions provided, and try out the options.

I HAVE read all the other chapters.  I am carefully reviewing the ibay chapter before creating any ibays.

No where is the information of where the email on available updates sent provided.  A good example (IMNSHO) is Astaro.  One of the basic setup items is where to send update notifications.

At least I have not found it.  It is not in the manual or the faq.

I am making a note of this in my sme docs, and will submit something in the future.

[janet]

rgmhtt

The short & quick answer is that every system related message is sent to admin.

I suggest you use and get to know sme, rather than comparing it to something else and expecting sme to behave like "something else".

If you had waited for a yum update email, then you would see it arrives in the admin users mailbox.

Use sme for what it is, it works.

[rgmhtt]

rgmhtt

The short & quick answer is that every system related message is sent to admin.

If you had waited for a yum update email, then you would see it arrives in the admin users mailbox.

Providing that I had the email set up in time, and known to check emails to user admin.  I have missed this instruction in the manual.

But I am out of time.  I was hoping to get a number of things working still today.  I will have to hope I have everything setup right for remote config, as I have to devote the rest of today to other things.

Mary, thanks for your help.

[uniqsys]

Providing that I had the email set up in time, and known to check emails to user admin.  I have missed this instruction in the manual.

Your expertise is clouding your simple vision.

There is NO NEED to "email set up".  SME is so simple that the admin account is set up for you and the update services send email notifications to the admin account.  That is simple and straight forward and normally expected as a default by network administrators.  So, everyone commonly KNOWS to check that account. 

IF you want notifications to go somewhere else, then as Mary said, edit the admin user in the server manager users account panel and redirect it to any email account in the world that you want.  What could be simpler?