T.R | Title | User | Personal Name | Date | Lines |
---|
2096.1 | Some workarounds | TAMARA::laceup.zko.dec.com::tamara::fitzell | It's not a bug it's functionally challenged ! | Tue Apr 01 1997 14:43 | 14 |
| Lynn,
The 32 char limit is a TeamLinks imposed limitation but
there are some ways around it. The first two probably won't help
since you're going thru a gateway but I'll put them here for
completeness. One way it to not use the full name. My local ISP
wouldn't work with reg.bah.nh.us it only works with reg as the
server name. Another way would be to use the TCP address ie
20.24.32.10. The last and probably most likely to work in your
case is to go into office.ini and change the server field in the
[POP3] section to whatever you need. Just don't modify that field
in the UI when a connect box POPs up or you'll get what you're
seeing today.
Mike
|
2096.2 | | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Tue Apr 01 1997 19:50 | 10 |
| One problem is the Server name member in the CONNECTINFO data structure
is limited to 32 characters. This is the Server field in the TL Login
dialog box displayed by the Connect.dll. I wanted to fix this in 2.7,
but was told not to. There is no way to increase this without breaking
lots of applications.
See if the work-around Mike gave you works.
Bob
|
2096.3 | Proxy Server?... | KERNEL::ANDERSONL | | Fri Apr 04 1997 09:36 | 15 |
| Hi,
thanks for the responses.
The customer has tried the office.ini workaround but is still not
having any success. He has been talking the firewall technicians they
say that for ftp and telnet connections they have a proxy server which
you connect to then you connect to destination. They can telnet to pop3
server and it responded so I guess the question now is are we missing
something in the setups that would allow teamlinks to pass thru the
firewall
Thanks
Lynn
|
2096.4 | | TAMARA::laceup.zko.dec.com::tamara::fitzell | It's not a bug it's functionally challenged ! | Fri Apr 04 1997 10:51 | 20 |
| Lynn,
Seeing how this is a customer and it's a new and interesting
problem I think you should IPMT it. Right now I have a lot more questions
than answers.
First what flavor of Windows are they using and what TCP/IP stack?
Can you have the customer turn on POP3 logging and post the logfile so I
can see what if anything happened when the office.ini workaround is tried.
Now If I understand this correctly they first have to connect to the proxy
server then they make the telnet or ftp connections. Do they just go into
to telnet and put in [email protected] and it all
magically happens or do they make a connection to the proxy server then gp
into telnet?
Have they tried another any other POP3 clients like Eudora?
Mike
|