NTISP: X-Originally-To Header and full domain mail in NTMail

------=_NextPart_000_0015_01BD6465.93ECB500
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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.

----------------------------------------------------------------------------
----

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)

----------------------------------------------------------------------------
----

------=_NextPart_000_0015_01BD6465.93ECB500
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

In=20order to deal with NTMail's inability to restrict incoming message sizes =on a=20POP domain, I thought I had figured out the solution. I created a full =domain=20for the customer. Had all "unknown user" mail transfered to =the root=20account, and then had the pullmail.exe file on the remote Exchange =server pull=20mail down from the root account.

Guess=20what. NTMail does not seem to include the X-Originally-To header with =non-POP=20domain mail. In other words. if the mail account is full domain, it does =not=20include the X-Originally-To header, which pullmail.exe=20requires.

Anyone=20know either a) how to work around this or b) when a version of NTMail =will be=20coming out that is not inconsistent in how it handles mail? I am getting =really=20tired of having to delete large attachement mailfiles for this customer =EVERY=20DAY...you would think that something as simple as limiting incoming file =attachments would not cause such problems.

Matt Stratton, MCP
Systems=20 Integrator
AIS Network
A Microsoft Solution = Provider

matts@aisnetwork.net
http://www.aisnetwork.net
847.=882.0493=20 x124 (Vox)
847.882.0201 =(Fax)