cc:Mail Link to SMTP Undeliverable Message: Unknown user: CNET T221C
administrator@smtp.cnet.navy.mil
Fri, 10 Apr 98 10:26:37 -0600
--simple boundary
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Another NTMail question...
In order to deal with NTMail's inability to restrict incoming message sizes
on a POP domain, I thought I had figured out the solution. I created a full
domain for the customer. Had all "unknown user" mail transfered to the root
account, and then had the pullmail.exe file on the remote Exchange server
pull mail down from the root account.
Guess what. NTMail does not seem to include the X-Originally-To header with
non-POP domain mail. In other words. if the mail account is full domain, it
does not include the X-Originally-To header, which pullmail.exe requires.
Anyone know either a) how to work around this or b) when a version of NTMail
will be coming out that is not inconsistent in how it handles mail? I am
getting really tired of having to delete large attachement mailfiles for
this customer EVERY DAY...you would think that something as simple as
limiting incoming file attachments would not cause such problems.
m.
----------------------------------------------------------------------------
----
Matt Stratton, MCP
Systems Integrator
AIS Network
A Microsoft Solution Provider matts@aisnetwork.net
http://www.aisnetwork.net
847.882.0493 x124 (Vox)
847.882.0201 (Fax)
----------------------------------------------------------------------------
----
--simple boundary
Content-Type: text/plain; charset=US-ASCII; name="FileItem.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="FileItem.txt"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
Another NTMail question...
In order to deal with NTMail's inability to restrict incoming message sizes on a POP domain, I thought I had figured out the solution. I created a full domain for the customer. Had all "unknown user" mail transfered to the root account, and then had the pullmail.exe file on the remote Exchange server pull mail down from the root account.
Guess what. NTMail does not seem to include the X-Originally-To header with non-POP domain mail. In other words. if the mail account is full domain, it does not include the X-Originally-To header, which pullmail.exe requires.
Anyone know either a) how to work around this or b) when a version of NTMail will be coming out that is not inconsistent in how it handles mail? I am getting really tired of having to delete large attachement mailfiles for this customer EVERY DAY...you would think that something as simple as limiting incoming file attachments would not cause such problems.
m.
--simple boundaryContent-Type: text/plain; charset=US-ASCII; name="RFC822.TXT"Content-Transfer-Encoding: 7bitContent-Disposition: attachment; filename="RFC822.TXT"Received: from netpmsa.cnet.navy.mil by pens3646.cnet.navy.mil (ccMail Link to SMTP R8.00.01) ; Fri, 10 Apr 98 10:01:49 -0600Return-Path: Received: from twistersec.iea.com by netpmsa.cnet.navy.mil with SMTP (1.38.193.4/16.2) id AA04509; Fri, 10 Apr 1998 09:54:27 -0500Received: from mail.aisnetwork.net by twister.emerald.iea.com (NTList 3.02.13) id ta255131; Fri, 10 Apr 1998 07:43:33 -0700Received: from www.aldenskennels.com (www.aldenskennels.com [208.195.199.250]) by mail.aisnetwork.net (NTMail 3.03.0017/1.aaoz) with ESMTP id ca786866 for ; Fri, 10 Apr 1998 09:46:41 -0500Reply-To: ntisp@emerald.iea.comFrom: "Matthew Stratton" To: "NT-ISP (E-mail)" Subject: X-Originally-To Header and full domain mail in NTMailDate: Fri, 10 Apr 1998 09:46:43 -0500Message-Id: <001401bd648f$7cbfafc0$fac7c3d0@tripoli.AISNETWORK>Mime-Version: 1.0Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01BD6465.93ECB500"X-Priority: 3 (Normal)X-Msmail-Priority: NormalX-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4Importance: NormalX-Listmember: cnet.t221c@smtp.cnet.navy.mil [ntisp@emerald.iea.com]--simple boundary--