Hm. Usually ^M is created by DOS/Windows systems and given that your server is Linux I can't see why would something like that happen. Perhaps your mail server is playing tricks with you adding strange encoding to message. Do you get this only for Windows backups or all backups? Or even only SQL backups? You may easily check if NW is guilty by changing notification - instead of sending it to email send it for a file on disk and see if you get ^M again.

Hi,
The savegroup completion notification I'm using is absolutely the default one. I can check sending the standard output message generated on the Linux server on a file, to see if the "^M" is not due to mailx. Anyway I see "^M" also in the /var/spool/mail file.

It sounds to be a bug. I think it is generated on the client side, so by the SQL module itself; do you agree ?

Thanks for any ideas.

Pierpa

Hrvoje,
oops ... I forgot to tell that this "^M" appears ONLY after SQL module backup. Backing up the same W2K server's filesystem I see a normal ascii mail message. Mmhh...

Pierpa

That may indicate that part of the notification is parsed from client and since client is Windows based i guess that is how the whole thing slips in. I do not see that as bug as ^M is not a bug at all, however if earlier releases did not perform that way you may request support to look into that. Nevertheless, handling this at local sendmail or whatever you use mail daemon should be the way to go.

Hi,
this is a bug, temporary resolved using the LISTSERV networker mail archive.

Solution: dos2unix | mailx -s "Backup completion message" root

dos2unix is typical on LInux. If not available, sed is always usable ...

Pierpa

Was that confirmed as bug? If not then it's not Also, sed and dos2unix (or ed) are just removing ^M are just removing this while real solution should be implemented on your mail system.