Good morning. Afan <[email protected]> wrote: |Am fine thanks - hope you are too!
Great. Well. Yes, thanks. |> It seems you set the $USER environment variable to this address, |> and i wondered wether the script doesn't use $USER directly and |> you were just gentle enough to show us the expansion? | |Ah - yes this was the issue. Changing this solved the problem immediately. Fine. |> If you use the -u command line option or set the $USER environment |> variable, then we fetch that specified user identity, instead of |> deducing the one that is implied by "you" as the person who is |> running the script. | |I tested -u and got this error: | | The -u option cannot be used in send mode Oh! Indeed we yet follow the POSIX standard which defines -u only for receive mode (as «Read the system mailbox of the login name user»), which is of course wrong. (It was always more in the BSD Mail codebase.) I'll fix that in a minute! |> Hope this helps a bit. | |Helps tremendously! Thanks! | |> I think i have to extend the manual a bit regarding user identity |> and accounts, somewhere early, too. Be warned you will be |> credited for that. | |That's fine, but no credit is necessary. Seems to me it's really due now, though. Sorry for that ^_^ Ciao! --steffen ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e __________________________________ [email protected]
