From: support@finaldraft.com
To: <netdev@oss.sgi.com>
Subject: Re: Thank you!
Date: Sun, 24 Aug 2003 00:36:50 -0700 [thread overview]
Message-ID: <B958AB0C-D605-11D7-B331-00306544FEAE@finaldraft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2201 bytes --]
***IMPORTANT! YOUR QUESTION HAS NOT YET BEEN SUBMITTED TO US! PLEASE
READ BELOW!***
THIS IS AN AUTO-REPLY FROM AN UNMONITORED E-MAIL ADDRESS
Thank you for contacting Final Draft Customer Support. You have
reached a mailbox that is no longer accepting incoming technical
support inquiries. We have made the following changes in order to
provide you with improved e-mail support.
First, please access our interactive Online Knowledge Base at
http://finaldraft.custhelp.com.
This will lead you to the "Answers" section, which has answers to over
600 Final Draft and Final Draft AV related questions. You may be able
to find your answer faster through this search.
If you have exhausted your search under "Answers" or cannot find your
answer in the Final Draft manual, you can e-mail a question to the
Customer Support team by going to "Ask A Question." Please be as
detailed as possible.
All e-mail questions should be sent through this page and will be
answered within one business day.
Please note that we no longer offer phone or e-mail support for any
Final Draft versions below version 5. If you would like information on
upgrading, please contact sales at sales@finaldraft.com or call
800-231-4055. All sales-related questions should be sent to this
address.
Any suggestions for new features to our products can be sent to
suggestions@finaldraft.com. PLEASE NOTE that no tech support questions
will be answered at this address as it goes to an incoming mailbox only.
Any other inquiries that are not tech support-related, including
company information, script contests, etc., should be directed to
info@finaldraft.com. Tech support-related questions sent to this
address will not be answered.
Thank you.
Final Draft Customer Support
On Saturday, August 23, 2003, at 10:06 PM, <netdev@oss.sgi.com> wrote:
> ******** McAfee GroupShield Exchange **********
> ******** Alert generated at: Saturday, August 23, 2003 10:06:38 PM
> Pacific Daylight Time
> **********************************************************************
>
>
> The item 262541_1061701598_netdev@oss.sgi.com-FDEXCHANGE.txt has been
> replaced because it was blocked.
[-- Attachment #2: Replaced Blocked File.txt --]
[-- Type: text/plain, Size: 302 bytes --]
******** McAfee GroupShield Exchange **********
******** Alert generated at: Saturday, August 23, 2003 10:06:38 PM Pacific Daylight Time
**********************************************************************
The item your_document.pif has been replaced because it was blocked.
next reply other threads:[~2003-08-24 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 7:36 support [this message]
[not found] <20030829124128.DUWA24095.fepZ.post.tele.dk@TESTSTAR>
2003-08-29 12:41 ` Thank you! Auto-reply from chrris@mail.dk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B958AB0C-D605-11D7-B331-00306544FEAE@finaldraft.com \
--to=support@finaldraft.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox