Sponsored Content
Full Discussion: bourne mail script problem
Top Forums Shell Programming and Scripting bourne mail script problem Post 11774 by Cameron on Wednesday 12th of December 2001 12:41:04 AM
Old 12-12-2001
Sorry, my example may not have been entirely understandable.


3. To send a file to another user, enter:
mail fran < proposal

This command sends the contents of the file proposal to fran.

Hope that helps. Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

mail problem (NOT Mail or Mail.app)

When I try to use the CLI mail, I get the following error. What's wrong? Welcome to Darwin! % mail root Subject: test test . EOT % /etc/mail/sendmail.cf: line 81: fileclass: cannot open /etc/mail/local-host-names: Group writable directory Do I just need to change the... (1 Reply)
Discussion started by: chenly
1 Replies

2. Shell Programming and Scripting

simple Bourne problem

Hi, I'm a newer for this languages, and I have a log file, which is something like this: 35.75.253.207 - - "GET /products/orgonizer/title.png HTTP/1.1" 200 1555 "-" "Mozilla 1.4" Now, I want to write a shell code to accoplish like ./XXX.sh -N n n is a number by user input, the code should... (5 Replies)
Discussion started by: pnxi
5 Replies

3. Shell Programming and Scripting

bourne script help

I need to make a small script that figures out if a filename that the user enters is a file or a directory. and if it is a directory, how many files are in it. please point me to the right direction, I am a newbie at this. (1 Reply)
Discussion started by: Heedunk
1 Replies

4. UNIX for Dummies Questions & Answers

mail script problem using cgi

dear all i've try several scripts and i think this is the simplest scripts that i can understand. please see below:- if ($num >= 4000000001) { #use CGI; #my $query = new CGI; #my $sendmail = "/usr/sbin/sendmail -t"; #my $reply_to = "bla@bla.com"; #my $subject =... (1 Reply)
Discussion started by: unknown2205
1 Replies

5. Shell Programming and Scripting

please give a bourne script to this problem

Hello all, I am new to unix and having the below problem.Any help will be appreciated. Write a Bourn shell script dTOe which takes as an input any number between 0 and 999 and prints the English value for this number. The program should display an error message when a NOT digit value entered.... (1 Reply)
Discussion started by: raj1811
1 Replies

6. Shell Programming and Scripting

Sh, Bourne Problem with getting lines in a file

This is a new exercise for me 1.) Create a bourne shell script that can accept 2 arguments/parameters. Name your script as housekeep_files.sh. 2.) The script will delete the files specified in the input file (1st parameter) and will send a notification through email (2nd parameter) the... (1 Reply)
Discussion started by: kdyzsa
1 Replies

7. Shell Programming and Scripting

if loop problem in bourne shell

how to use if-loop in bourne shell with multiple conditions like follows if then commands fi it gives me an error test: ] missing then i put if ] it gives me an error [[ not found kindly i need the syntex for the bourne shell (5 Replies)
Discussion started by: ahmad.diab
5 Replies

8. Shell Programming and Scripting

help with bourne script

Hey guys not sure why but when i execute the script i get the correct result but then it says command not found not sure why can anyone see anything wrong with my code below? I just want to print how much quota i have used in my home directory #!bin/sh `quota -v | grep ^/home | awk... (2 Replies)
Discussion started by: musicmancanora4
2 Replies

9. Shell Programming and Scripting

Bourne Shell - Problem with while loop variable scope.

Hello I am having issues with a script I'm working on developing on a Solaris machine. The script is intended to find out how many times a particular user (by given userid) has logged into the local system for more than one hour today. Here is my while loop: last $user | grep -v 'sshd'... (7 Replies)
Discussion started by: DaveRich
7 Replies

10. UNIX for Dummies Questions & Answers

bourne script problem

I've got an NTFS file system mounted on my Linux box, which means I can have multi-word directory names. I want to recurse through the directory structure copying stuff from /A to /B when it does not already exist on /B. Here is the chunk of code, and the output of a set -x run on that chunk of... (8 Replies)
Discussion started by: esmith92000
8 Replies
SIEVE-TEST(1)						      General Commands Manual						     SIEVE-TEST(1)

NAME
sieve-test - Sieve script tester for the Dovecot secure IMAP server SYNOPSIS
sieve-test [-c] [-d dump-file] [-e] [-f envelope-sender] [-l mail-location] [-m default-mailbox] [-r recipient-address] [-S script-file] [-t] [-x "extension extension ..."] script-file mail-file DESCRIPTION
The sieve-test command is part of the Sieve implementation for the Dovecot secure IMAP server. Sieve (RFC 5228) is a simple and highly extensible language for filtering e-mail messages. It can be implemented for any type of mail access protocol, mail architecture and oper- ating system. The language cannot execute external programs and in its basic form it does not provide the means to cause infinite loops, making it suitable for running securely on mail servers where mail users have no permission run arbitrary programs. Using the sieve-test command, the execution of Sieve scripts can be tested. This evaluates the script for the provided message, yielding a set of Sieve actions. Unless the -e option is specified, it does not actually execute these actions, meaning that it does not store or for- ward the message anywere. In stead, it prints a detailed list of what actions would normally take place. Note that, even when -e is speci- fied, no messages are ever transmitted to remote SMTP recipients. The outgoing messages are printed to stdout in stead. This is a very useful tool to debug the execution of Sieve scripts. It can be used to verify newly installed scripts for the intended be- haviour and it can provide more detailed information about script execution problems that are reported by the Sieve plugin. The command has two mandatory arguments: the script-file argument, which specifies the script to (compile and) execute, and the mail-file argument, which specifies the file containing the e-mail message to filter. Note that this tool looks for a pre-compiled binary file with a .svbin extension and with basename and path identical to the specified script. Use the -c option to disable this behavior by forcing the script to be compiled into a new binary. OPTIONS
-c Force compilation. By default, the compiled binary is stored on disk. When this binary is found during the next execution of sieve-test and its modification time is more recent than the script file, it is used and the script is not compiled again. This option forces the script to be compiled, thus ignoring any present binary. Refer to sievec(1) for more information about Sieve com- pilation. -d dump-file Causes a dump of the generated code to be written to the specified file. This is identical to the dump produced by sieved(1). Using '-' as filename causes the dump to be written to stdout. -e Turns on true execution of the set of actions that results from running the script. In combination with the -l parameter, the actual delivery of messages can be tested. Note that this will not transmit any messages to remote SMTP recipients. Such actions only print the outgoing message to stdout. -f envelope-sender The envelope sender or return path. This is what Sieve's envelope test will compare to when the "from" envelope part is requested. Also, this is where response messages are sent to. -l mail-location The location of the user's mail store. The syntax of this option's mail-location parameter is identical to what is used for the mail_location setting in the Dovecot config file. This parameter is typically used in combination with -e to test the actual deliv- ery of messages. If -l is omitted when -e is specified, mail store actions like fileinto and keep are skipped. -m default-mailbox The mailbox where the keep action stores the message. This is "INBOX" by default. -r recipient-address The envelope recipient address. This is what Sieve's envelope test will compare to when the "to" envelope part is requested. Some tests and actions will also use this as the owner's e-mail address. -S script-file Specify additional scripts to be executed before the main script. Multiple -S arguments are allowed and the specified scripts are executed sequentially in the order specified at the command line. -t Enable simple trace debugging; prints all encountered byte code instructions to stdout. This is currently only intelligible for developers. -x "extension extension ..." Set the available extensions. The parameter is a space-separated list of the active extensions. By prepending the extension identi- fiers with + or -, extensions can be included or excluded relative to the default set of extensions. If no extensions have a + or - prefix, only those extensions that are explicitly listed will be enabled. Unknown extensions are ignored and a warning is produced. By default, all supported extensions are available, except for deprecated extensions or those that are still under development. For example -x "+imapflags -enotify" will enable the deprecated imapflags extension along with all extensions that are available by default, except for the enotify extension. DEBUG SUPPORT
To improve script debugging, the Sieve command line tools such as sieve-test support a custom Sieve language extension called 'vnd.dove- cot.debug'. It adds the debug_print command that allows printing debug messages to stdout. Example: require "vnd.dovecot.debug"; if header :contains "subject" "hello" { debug_print "Subject header contains hello!"; } Other tools like sievec and sieved also recognize the vnd.dovecot.debug extension. In contrast, the actual Sieve plugin for the Dovecot LDA does not allow the use of the debug extension. So, keep in mind that scripts and compiled binaries that refer to de debug extension will fail to be run by the Sieve plugin itself. Note that it is not necessary to enable nor possible to disable the availability of the debug extension with the -x option. AUTHOR
The Sieve implementation for Dovecot was written by Stephan Bosch <stephan@rename-it.nl>. Dovecot was written by Timo Sirainen <tss@iki.fi>. SEE ALSO
sievec(1), sieved(1) 4 July 2009 SIEVE-TEST(1)
All times are GMT -4. The time now is 01:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy