Poke a Shell Variable with xTalk?

[Sivakatirswami]

Aloha, David:

Thanks for that tip... but the "(text file + shelling to sendmail)"

cat someFoo.txt | sendmail etc.

is what we use now, and honestly we are shooting in the dark as to  
when and why a CRLF is inserted into a line that is longer than 1024  
characters. The attempt to use echo makes a big assumption (possibly  
wrong) that it would handle long lines without that CRLF being  
introduced... but without *any* line delimiters at all from echo,  
it's a futile attempt to test for an unknown result.

I'll look at postalias... but as often happens with such things,-- 
where lo-level programming eats so much time for so little result,  
and you end up going back to find an xTalk solution-- I am about  
ready to "move up" and use Shao's SMTP libs... If I had started this  
whole foray with that and ditched the shell thing completely last  
week, I would probably be home free already...and I would have a grip  
on a nice tool box I can use for other projects...

Anyway, I think we can let this thread die for now..

Thanks

Sivakatirswami



On Sep 15, 2005, at 4:40 AM, david bovill wrote:

> My suggestion would be to go with the (text file + shelling to  
> sendmail) combination,  and not the (shell + echo + pipe)  
> combination to get variables into anything but the simplest stuff.
>
> I have not done this with sendmail but looking at the man page,  
> would indicate that you need to use the :
>
>        Postfix sendmail relies on the postdrop(1) command to create
>        a queue file in the maildrop directory.
>
> Which you can find at:
>
>         /var/spool/postfix, mail queue
>
> However as this says use postdrop which in return takes input from  
> STDIN you are back to square one.
>
>        newaliases
>               Initialize the alias database.  If no input  file   
> is  specified
>               (with  the  -oA  option,  see  below), the program  
> processes the
>               file(s) specified with the alias_database  
> configuration  parame-
>               ter.   If  no alias database type is specified, the  
> program uses
>               the type specified with the default_database_type   
> configuration
>               parameter.  This mode of operation is implemented by  
> running the
>               postalias(1) command.
>
> Where:
>
>       -oAalias_database
>               Non-default  alias  database. Specify pathname or  
> type:pathname.
>               See postalias(1) for details.
>
> So this is not looking simple:) The postalias command seems to be  
> the thing you need to create the queue files in the maildrop  
> directory (from files):
>
> POSTALIAS(1)                                                       
> POSTALIAS(1)
>
> NAME
>        postalias - Postfix alias database maintenance
>
> SYNOPSIS
>        postalias [-Nfinoprvw] [-c config_dir] [-d key] [-q key]
>                [file_type:]file_name ...
>
> So by issuing a series of simple commands passing the right  
> fileNames you should get the result you want? NB ie use merge() to  
> create the right shell commands...
>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>