How to eschew transmission errors? Re: Error-finding program

[Antti Karttunen]

franktaw at netscape.net wrote:

> I have had exactly this error occur; and as Paul says, it occurs when 
> emailing Neil directly.  Note that the problem is not usually in 
> composiing the message, but in transmission; there is email software 
> that decides that lines are too long and wraps them for you.

Exactly for this reason I am nowadays sending all my e-mail submissions 
(whether renumbered new sequences
or edits of existing ones) as tarred attachments (Note: AT&T's 
mail-server rejects mails with ZIP-attachments!)
Seems to work well, and at the same time one can include b-files and 
other associated extra files
in the same tarball.

-- Antti

>   When you submit from the submissions page, the email is sent from 
> AT&T's server, and they don't have this problem internally.
>
> There is a very simple solution for the submitter: use spaces instead 
> of commas in the sequence.  This will take care of the problem unless 
> your sequence has a very long number in it - in which case, add a note 
> for Neil to check that it didn't get split.
>
> Franklin T. Adams-Watters
>
>
> -----Original Message-----
> From: pauldhanna at juno.com
>  
> Seqfans,
>      The splitting of an element can occur when a submission is made via
> direct e-mail to Neil by cut and paste of a line that word-wraps to 
> another. 
>  
> Example, if I cut and paste the following line into an e-mail message:
> 1,4,6,8,11,13,16,18,21,23,25,28,30,33,35,37,40,42,45,47,49,52,54,57,59,6
> 2,
> clearly I mean it to be '62' for the last element, but it becomes '6,2'
> since spaces are interpretted as delimiters along with commas.
> ...
> ________________________________________________________________________
> Check Out the new free AIM(R) Mail -- 2 GB of storage and 
> industry-leading spam and email virus protection.
>
>