On Sunday, Jan 08 2006 04:36 Daniel Henninger wrote: > =D What format is that in? File gives me: > katana:~ daniel$ file ~/Desktop/winmail.dat > /Users/daniel/Desktop/winmail.dat: Transport Neutral Encapsulation > Format > > =D He uses either Outlook Express or MS Outlook. I know - we should kill him for this but for sake of making PyAIMt here is version decoded with tneff.
Small text is really _very_ small - actually it was very hard to me to found it. Blue nickname writes it. > Daniel > > On Jan 7, 2006, at 6:02 PM, Parish, Ray wrote: > > Here is a screen shot. You can see the small text! :) > > > > > > ________________________________ > > > > From: [EMAIL PROTECTED] on behalf of Daniel > > Henninger > > Sent: Thu 1/5/2006 10:41 AM > > To: PyAIM-t/PyICQ-t/PyMSN-t Discussion > > Subject: Re: [py-transports] PyAIMt > > > > > > > > OPN? =) When you say legit AOL clients, do you mean those using the > > official AIM client, or those not only using the official AIM client, > > but also using AOL "as a whole". (the service or whatever you'd call > > it) I have no way of testing the AOL "as a whole" service, but there > > shouldn't be any reason why it doesn't come through correctly based > > off PyAIM's code. (simply because it never ever references italics, > > blue, or any type of font really. =/ I can't imagine what else > > would cause it. Does anyone happen to have a screenshot of this > > behavior so that I can look and see if I notice anything unusual? > > > > Daniel > > > > On Jan 5, 2006, at 9:16 AM, Parish, Ray wrote: > >> The only reports I have heard are from legit AOL clients. If other > >> aim > >> users are using Trillian or someother IM Client, the font comes > >> over as > >> it should. > >> > >> More info on our environment: > >> > >> We are using OPN Server client 4.5 sp1. The OPN server talks to our > >> jabber 1.4.4 server to access the gateways. > >> We only transitioned from the old c transport because the process > >> would > >> die several times a day. We switched to the PyAIMt and it has been > >> running solid for over a week with no problems. > >> > >> > >> Thanks > >> > >> > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] On Behalf Of Daniel > >> Henninger > >> Sent: Thursday, January 05, 2006 9:07 AM > >> To: PyAIM-t/PyICQ-t/PyMSN-t Discussion > >> Subject: Re: [py-transports] PyAIMt > >> > >> Say -what-? Ack! The default handling of text in PyAIM is to be > >> simple "black text on white background"... nothing special about it. > >> If your Jabber client is providing XHTML, then I tried to pass that > >> on if I can. All I can think of is that either: > >> > >> A. The person on the other end has something configured poorly in > >> their AIM client > >> B. The jabber client is set to be small blue italicized > >> > >> I can't imagine where else this would be coming from! =/ Anyone > >> else seen this before? > >> > >> Daniel > >> > >> On Jan 5, 2006, at 8:56 AM, Parish, Ray wrote: > >>> Sorry if this has been covered before, I just transitioned from the > >>> old aim c transport to the new Python AIM. > >>> > >>> Very stable compared to the old c transport, thanks guys. > >>> > >>> > >>> > >>> PyAIMt-0.7b version > >>> > >>> > >>> > >>> I am getting reports that when a user uses the PyAIMt transport to > >>> communicate to an AIM client (legit download client) the font is > >>> seen to the AIM client as small blue italicized font. > >>> > >>> > >>> > >>> Any fix? > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> py-transports mailing list > >>> py-transports@blathersource.org > >>> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > >> > >> _______________________________________________ > >> py-transports mailing list > >> py-transports@blathersource.org > >> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > >> _______________________________________________ > >> py-transports mailing list > >> py-transports@blathersource.org > >> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > > > > _______________________________________________ > > py-transports mailing list > > py-transports@blathersource.org > > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > > > > > > <winmail.dat> > > _______________________________________________ > > py-transports mailing list > > py-transports@blathersource.org > > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports -- Respectfully Alexey Nezhdanov -------------- next part -------------- A non-text attachment was scrubbed... Name: smallt~1.png Type: image/png Size: 80937 bytes Desc: not available Url : http://modevia.com/pipermail/py-transports/attachments/20060108/5d29aa6c/smallt1-0001.png From [EMAIL PROTECTED] Sun Jan 8 13:12:11 2006 From: [EMAIL PROTECTED] (James Bunton) Date: Sun Jan 8 13:12:27 2006 Subject: [py-transports] Log file in PyMSNt In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> You could set it to log to STDOUT (give - as the log filename), and then redirect to a file. I don't know if twistd actually provides this option. It might be worth looking around though :) --- James On 08/01/2006, at 10:50 AM, Daniel D?az wrote: > Hello! > > With PyMSNt SVN (rev 88) I'm seeing the log file being kind of rotated > as soon as it reaches 1000000 bytes (or so). Is that an option? How > can I change it back to the other behaviour of not checking and > letting the log file grow? > > Thanks in advance! > > Daniel D?az > [EMAIL PROTECTED] > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >
