Ok, if for instance you have 2 witango servers and they are both setup to
use the same mail account on the 1 mail server...

The one plus with the @email tags is that you can control the user from
within the code.

Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller 
Available for Web App. Developement


-----Original Message-----
From: Dave Machin [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 24, 2005 1:29 PM
To: [email protected]
Subject: Re: Witango-Talk: Mail Action Locks Up Server

No they're separate.

----- Original Message -----
From: "Ben Johansen" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, May 24, 2005 12:37 PM
Subject: RE: Witango-Talk: Mail Action Locks Up Server


> Along this line.
>
> Is the Mail server and Witango Server on the same computer?
>
> Ben Johansen - http://www.pcforge.com
> Authorized Witango & MDaemon Reseller
> Available for Web App. Developement
>
> -----Original Message-----
> From: Robert Shubert [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 24, 2005 11:56 AM
> To: [email protected]
> Subject: RE: Witango-Talk: Mail Action Locks Up Server
>
> If it's possible - or on your to do list anyway - upgrade to 5.5. I don't
> suspect that this will solve the problem, although it could, but I think
it
> should help the server error/crash/exception more gracefully, and should
> give you some reporting.
>
> Ben is right that the TAGS over power the ACTION, but the action, in my
> experience, is still very good. My servers create around 3 million emails
> each month using the action (from hundreds of TAF files) and I've never
seen
> the crash you are describing. I do, however, have a nearly dedicated
> connection between the Witango servers and the email server (running iMail
> 8.2), and support many threads on the server.
>
> You can wrap the email tag into a TCF to make them a little easier to use.
> I'm sure someone on the list can get you started with that. It's something
> I've been meaning to do.
>
> As for the internals, the email action can not be changed by WT without
> changing the TAF format, which will happen in the future. If you want the
> email action to have additional features - email WT. I do believe the
> underpinnings were updated slightly in 5.0 and again in 5.5, mostly to do
> with connection management. I can't sight any specific improvements that I
> recall, however.
>
> Robert
>
> PS. If there's just one action causing the problem, try deleting and
> remaking it, or moving to a TAF/TCF of its own and branching/calling it to
> separate out the logic. Sometimes this will fix something strange in a
TAF,
> or perhaps help you isolate the problem better.
>
>
> -----Original Message-----
> From: Dave Machin [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 23, 2005 4:38 PM
> To: [email protected]
> Subject: Witango-Talk: Mail Action Locks Up Server
>
> We've been having a recurring problem with Mail Actions locking up the
> Witango Server.  We've had a lockup once a week for the last couple weeks.
> WiTango probably sends out 50 to 100 emails per day and they generally
work
> fine.  The one causing the lockup seems normal - the from address is valid
> and the body is the same as the emails that work.  The mail server is
online
> and responding fine and it doesn't record any log events when this
happens.
>
> Any ideas where to look to troubleshoot this?
>
> W2K SP4, WiTango  5.0.1.065
>
> Dave Machin
>
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
>


________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf


________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to