Sorry to include the whole thread, but I think this is needed to "get the 
whole picture"....


I finally found a way to solve this problem with CC's and FtGate (problem 
wich indeed seems to have started since Imail 5.08).

I will not tell the list how I did it. Not because I don't want to....

But because:

-I think Ipswitch should tell us the "how and why".
But as they seem to be sure "there is no problem" so far...
I'm rather curious if they will. Let's hope.

-Solving this involded some "reverse ingeneering" and yes, I know, one 
should not do this and the license says one is "guilty"... ;-)

All I can tell is: it took only 1 change of 1 character in 1 "Imail-related 
file".

"Et voila", our customers can send CC's trough the nobody account again and 
FtGate will happily re-distribute those messages amongst the CC-ed people 
at their location.

I will NOT answer mails about "how did you do it" for the reasons mentioned.

Perhaps I will tell Ipswitch where exactly things go wrong and perhaps (?) 
they will bring a nicer fix then the "brute force attack" (although very 
nice and completely harmless) I used...

But as long the 2 paries involved (Imail and FtGate) tell us "ask the 
other" I saw no other way then to solve it myself.

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


Date: Wed,  2 Feb 2000 16:12:48 +0100
From: "Hostmaster Zitech NET" <[EMAIL PROTECTED]>
Subject: Re: [IMail Forum] X-Recipient and CarbonCopy and.. Imail 6.02
Reply-To: [EMAIL PROTECTED]

Yep we've had the same problem with verison 5.08, prior version 6.0 & 6.02
I'm having the exact same problem with a customer using FTGate, so I'd be h=
appy if anyone has ideas, comments or even solutions to this.



---------- Original Message ----------------------------------
From: Luk Van de Heyning <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Tue, 01 Feb 2000 20:27:37 +0100

 >We (our customers, to be correct) have problems with CC (Carbon Copy) ...
 >
 >Seems this trouble started with Imail 6.02.
 >
 >I'll try to explain very brief:
 >
 >-use a 'nobody' account, let it forward all mail for a domain to one
 >mailbox (for that domain).
 >
 >-No other users exist for that domain.
 >
 >-Send mail to i.e. [EMAIL PROTECTED]
 >
 >-Send a CC (Carbon Copy) in that same mesage to i.e.
 >[EMAIL PROTECTED],[EMAIL PROTECTED] etc etc
 >
 >-Look at the 'main.mbx' for the mailbox the 'nobody' alias points to:
 >
 >-You will see ONLY ONE message, with ONLY ONCE a X-Recipient:...@....
 >
 >My question: anyone noticed this, anyone noticed this BEFORE 6.02 ?
 >
 >The trouble is: our customers mainly use a product called FtGate (not
 >really competition for Imail, so I "dare" to mention it here).
 >
 >FtGate has NO MEANS to know, after fetching the mail via POP3, that this
 >message has to be dropped in the user1 and user2 mailboxes at the FtGate
 >system.
 >
 >And: THIS ALL WORKED NICE before we updated to Imail 6.02 (or before
 >"something else happened but I haven't got a clue what...").
 >
 >Does anyone has an idea what's going on ?
 >
 >And.... does anyone think, in the case / setup I described here, that Imai=
l
 >should always have multiple messages with one 'X-Recipient:' per message, =

 >AND that it's Imail that should handle the CC's ????
 >
 >As far I know the RFC's say it's the POP3-server that should take care of =

 >CC's, not the mailclient.
 >
 >In this case (with use of the 'nobody') Imail seems not to take care of
 >CC's, does it ?
 >
 >Rather urgent, this one....
 >
 >Thanks !
-------------------------------------------------------------
                        Luk Van de Heyning
                            "Zeb-master"
                      E-mail: [EMAIL PROTECTED]
         ZEB Electronics, Dorp 1A, 2288 Bouwel, Belgium.
            Tel:+32-(0)14-512865 Fax:+32-(0)14-517703

 >>>>Hobby-home-page:<<<<               >>>>Business homepages:<<<<
  http://www.zeb.be/luk/                 http://www.zeb.com/
-------------------------------------------------------------

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

Reply via email to