Outlook Mail attachment BUG!

[aps]

I have a MS Outlook 2000 SR-1 installed on my Windows2000
PC. I am facing bit strange problem. The problem is, I am
trying to send a mail from Unix Box to Outlook mail but it
got truncated at one perticular line. Let say I am typing
the following command on unix
$mailx -s "test mail" (e-mail address removed) <dbareport.log

here dbareport.log file has following lines in it
------
this is a test mail to all DBA users (line1)

begin declare (line 2)

end of report (line 3)
-------

when I received this mail in outlook it got truncated at
line 2, that begin statement. See the begin stmt, there is
a more then one space between 'begin' and 'declare'.

After this analysis I tried to remove the extra space
between 'begin' and 'declare' then it went fine. a full
mail recd. Or if you put a single space before 'begin',
again it worked fine. So I found that outlook has a
special meaning for line starts with 'begin'.

If anyone have the same problem, please let me know. You
can also try the same thing in your env.

Thanks in advance

aps_

 

[Brian Tillman]

I have a MS Outlook 2000 SR-1 installed on my Windows2000
PC. I am facing bit strange problem. The problem is, I am
trying to send a mail from Unix Box to Outlook mail but it
got truncated at one perticular line. Let say I am typing
the following command on unix
$mailx -s "test mail" (e-mail address removed) <dbareport.log

here dbareport.log file has following lines in it

I'd say the problem is on the Unix end.

 

[Sue]

If the original post was sent from unix, I'd have to
agree - seems there's a lot missing.

Aside from that, it looks like you're using a < (here
doc?) as the message input. Is that supposed to work?
Most command line mailers I've seen expect an argument
for including text in one form or another. For example,
mailto uses -MF filename (to use the contents of filename
as the message text) or -AT textfile (to attach a text
file to the message). Admittedly, though, I'm not
familiar with mailx, so I can't say for sure if that's
what the problem is.

 

[Brian Tillman]

If the original post was sent from unix, I'd have to
agree - seems there's a lot missing.

Aside from that, it looks like you're using a < (here
doc?) as the message input. Is that supposed to work?

The mailx command in most Unixes takes the body of the message from the
standard input until a CTRL-D (EOF) in encountered or, if from a terminal,
until a line containing a single period is encountered. The "<" redirects
the standard input to a file so that a file can be mailed without prompting
for input.

 

[Guest]

aps -
yes '<' this sign works perfectly fine under most of the
unix. you can read the message contents from a file by
this sign. it like taking input. if you have a unix access
you can try this thing.
and this problem comes when there is a special line comes
(here in this case 'begin anytext') and pluse there are
more than single space between 'begin' and the next
word.and there is no unix setting for such special things.
it must be a problem with Outlook.

 

[Brian Tillman]

and this problem comes when there is a special line comes
(here in this case 'begin anytext') and pluse there are
more than single space between 'begin' and the next
word.and there is no unix setting for such special things.
it must be a problem with Outlook.

Ah! "begin something" is being interpreted by Outlook as the indication of
a UUENCODEd attachment. Outlook doesn't require any headers to tell it an
attachment is included that's UUENCODEd. I dont know if you can address
this with Outlook 2000. In Outlook 2002 and 2003, you can tell outlook to
interpret all messages as plain text, which *might* address the issue. I
can't test it.