Re: Clarification of file formats for recipient list, etc.

> There doesn't seem to be anything in blat's docs or associated files which
> specifies the allowed format for attached recipient lists or list of
> attachments (used with the -tf -cf -bf and -af flags). I'm successfully
> using blat to send PDF result files to a small mailing list of clubs, but
> it took a bit of experimentation to get the file formats correct. - I
> haven't programmed in C/C++ for many years, so couldn't find the
> appropriate section of source to unpick the code! :^)
>
> I use a straight list of email addresses separated by CRLF for the BCC
> file, but from experimenting with sending mail to myself at several
> addresses with blat using a bcc file it *appears* that anything on the
> address line that follows a space is ignored. If I can rely on that it,
> would be very useful to be able to add comments after each email address
> in the file (such as the name of the club).
>
> As far as the attachment list file is concerned, it looks as if the
> description in the syntax.txt file:
>
> -af <file>      : file containing list of binary file(s) to attach
>                 (comma separated)
>
> differs from what's allowed in the file because I again put the complete
> file path on a separate line for each file, rather than comma separated,
> and blat happily accepts it. Originally I assumed that any entries in that
> file with spaces in the file path would require enclosing quotes, but that
> doesn't seem to be the case.
>
> Would it be possible to clarify allowed file layouts in the docs somewhere
> please?
>
> Regards
>        John


If you want to have spaces in your email address lines, use quotation marks
(") to surround the whole of the text.  For example: "Chip
<[email protected]>".  The use of quotation marks also applies to
filenames and pathnames that have spaces.  I know that I have not published
anything about this for quite some time, but I did way back when I added
support for people's names to be associated with email addresses as shown
above.

As for comments, the default character to mark the start of comments is a
semicolon (;).  This character can be changed when using the -comment
command line option.

        -comment  <char> : use this character to mark the start of comments
in options files and recipient list files.  The default is ;

-- 
Chip