 Thread: Major email problem |
|
|
Have you ever tried to access the account with another client, e.g. Outlook or Thunderbird?
|
|
| Thread: Windows batch file .bat parameters |
|
|
Use the "set" command (without any parameters) and you will see all the information that is available from the server.
In the output you will find one (and probably more) environment variables that contain the actually called URL (like "http://yourdomain/this.bat?bla=xy").
You'll "simply" have to parse these variables to obtain your request parameters.
|
|
 Thread: problem |
|
|
Do not misuse the report button!
"This function should only be used for one of the following reasons: spam, advertisement or other problems (like racism, vulgarity, agressiveness, discrimination or sexism)."
Please take a deep breath and rethink about your problem. Then start a new thread and tell us everything that is relevant. This includes Jana version, system environment and accurate failure descriptions.
Closed.
|
|
| Thread: http proxy and chain proxies |
|
|
@1: Probably you cannot. Isn't this the reason why there is the corporate proxy?!
@2: Of course this is possible: You can set this option in Jana's RAS options page.
|
|
| Thread: SMTP Proxy |
|
|
At this point, I think, it is a good idea to emphasize the dangers of a public proxy.
As we've seen in David's Proxy.log, a public proxy can be (ab)used to connect anonymously to other Internet ressources reachable by the proxy. Remember, that any addressed server will only see the IP address of your proxy and not the abuser's IP, which raises the suspicion that you where the abuser.
But what is not mentioned here is the other way round: Making the proxy public simply exposes your LAN to the Internet! Be aware, that also all services running only locally on the proxy (i.e. any Jana services only bound to 127.0.0.1, or some typical Windows services) are visible to the Internet in this case.
|
|
| Thread: e-mail address standard |
|
|
Although my company also is keen on using the forename.surname@domain.tld layout, I'm not so convinced this is really a good idea.
The dot "." between forename and surname would imply a hierarchy (like in the Domain Name System) where there is none. Therefore, I tend to prefer the "writeitallinoneword"-Solution:
LudwigVanBeethoven@componist.music.net
Wherever appropriate you could apply "camelcaps" as I did in the example above (but of course the technical parts in an email system won't care about capitalization!)
|
|
| Thread: Extra Gateways cause me some problems |
|
|
| quote: | | Sitalk Proxy.log shows no errors and an unloaded image appears exactly like a loaded one... |
|
Are you definitely sure about this?! It would mean that both, the correctly shown and the missing image produce an HTTP status code of 200 in the proxy.log.
=> Jana did her job and fetched the images. So we can concentrate on the connection proxy <=> client for further debugging.
By the way: You didn't mention the server.log!
My first and most obvious suspect is ZoneAlarm.
I would consider to completely uninstall ZoneAlarm (sorry, switching it off does generally not suffice, since its network driver level parts stay active): Even more than other firewalls it influences network traffic and has too often been the cause of "obscure" network misbehaviour. Generally, I would not consider ZoneAlarm to be a suitable server firewall.
Alternatives exist: e.g. free Sygate Personal Firewall.
|
|
| Thread: Extra Gateways cause me some problems |
|
|
You should provide some background on your system configuration:
Operating system on server and clients? Any firewalls or virus scanners? Errors in server.log?
Which errors (status lines) appear in the proxy.log in case images fail to load?
Additionally, please tell us exactly all your Extra-Gateway parameters!
|
|
|
) 
