Re: [Declude.JunkMail] OT: port forwarding
Dave, Here is the latest reply I received from SmarterTools Regarding this issue: This has been verified as intended action. We do not see this as a bug. If you feel it is a security hazard, do not view HTML messages. Within SmarterMail, simply set the default view to Plain Text, and not HTML. If you feel a message is safe, view it in the HTML mode manually. Maybe you will have better lunk convincing them otherwise. Gary Original Message From: Dave Doherty [EMAIL PROTECTED] Sent: Thursday, March 23, 2006 8:49 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding I have had similar experiences with them right back to the beginning. I think the quality of the service you get varies greatly with the individual. If they get it the response is usually pretty good. It does not always seem easy to get them to get it though... I held off deploying SM in my plant for over a year because I wanted to see how the product would evolve. I was - and remain - very impressed with V3 overall. Every complicated product is going to have some issues, the real issue is how they respond when the product meets the users abnd the trouble tickets start flying. I just submitted a detailed ticket with screenshots and a good explanation as to why I think this is a major issue. It will be very interesting to see what kind of response I get. -Dave Doherty Skywaves, Inc. - Original Message - From: Gary Steiner [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Thursday, March 23, 2006 6:42 PM Subject: Re: [Declude.JunkMail] OT: port forwarding Matt, I tried all that... --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
Hi, Gary- I'm working on it. I believe they are starting to get it, and they said they are working on a fix that should be out soon. There are several ways to fix it, and they need to decide how to proceed: - Change the carets to lt; and gt; - They have some concerns about this in messages where the and do not indicate HTML tags. - Set the default to text-only if you are worried about the problem - This makes HTML messages - which are most messages these days - ugly, and requires switching manually to HTML mode to view messages. With most of my users, this would not last a day. - (My suggestion) Auto-switch the reader mode to HTML mode for HTML messages and text-only for text messages, and disable html mode entirely when a text message is being viewed. - Probably there are others, and the final solution may be something completely different. -d - Original Message - From: Gary Steiner [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Friday, March 24, 2006 12:11 PM Subject: Re: [Declude.JunkMail] OT: port forwarding Dave, Here is the latest reply I received from SmarterTools Regarding this issue: This has been verified as intended action. We do not see this as a bug. If you feel it is a security hazard, do not view HTML messages. Within SmarterMail, simply set the default view to Plain Text, and not HTML. If you feel a message is safe, view it in the HTML mode manually. Maybe you will have better lunk convincing them otherwise. Gary --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: port forwarding
This is a bug SmarterMail they need to do the replacements when displaying a plaintext email. Or switch the view automatically if there is only a plaintext portion of the email. Does the origional email have a plaintext and html portion??? If it does and the HTML portion is blank then they are doing what many clients would do. Default to the HTML view. They also may be using poor judgment and assuming that no one would ever discuss HTML tags in a plain text email and not parsing them. Kevin Bilbee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gary Steiner Sent: Thursday, March 23, 2006 8:47 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding I can't get SmarterTools to see this as a bug. Their answer is that their web mail is set to HTML by default, and you should just click on the plain text link to view it. Their support doesn't seem to be able to grasp the wider implications of this problem. Gary Original Message From: Matt [EMAIL PROTECTED] Sent: Wednesday, March 22, 2006 6:31 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding That's surely a bug. Dave sent his message as plain/text and SmarterMail should be replacing the brackets with HTML encoding before displaying it as HTML so that it should not be a functional element when displayed., i.e. lt;meta http-equiv=Refresh content=5; URL=http://www.mydomain.comgt; If Dave had sent it as an HTML message, his client would have done the replacement for him. This should probably be reported to SmarterMail. There are a lot of potential consequences, for instance, virus scanners won't generally consider code in plain/text segments to be executable, yet it can be in SmarterMail webmail if it is working the way that you reported. Matt Gary Steiner wrote: It is interesting how SmarterMail's web mail interprets Dave's message. It sees the META statement in his message as embedded code, and runs it when I read the message. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: port forwarding
The original message had no HTML part. You probably have a copy of it, it was
Dave Doherty's message to this list dated Wed, 22 Mar 2006 15:49:42 -0500
with a subject line of Re: [Declude.JunkMail] OT: port forwarding.
SmarterMail's web mail interpreted the META tag Dave illustrated in his message
as HTML.
Original Message
From: Kevin Bilbee [EMAIL PROTECTED]
Sent: Thursday, March 23, 2006 1:36 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] OT: port forwarding
This is a bug SmarterMail they need to do the replacements when displaying a
plaintext email. Or switch the view automatically if there is only a
plaintext portion of the email.
Does the origional email have a plaintext and html portion???
If it does and the HTML portion is blank then they are doing what many
clients would do. Default to the HTML view. They also may be using poor
judgment and assuming that no one would ever discuss HTML tags in a plain
text email and not parsing them.
Kevin Bilbee
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gary Steiner
Sent: Thursday, March 23, 2006 8:47 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] OT: port forwarding
I can't get SmarterTools to see this as a bug. Their answer is
that their web mail is set to HTML by default, and you should
just click on the plain text link to view it. Their support
doesn't seem to be able to grasp the wider implications of this problem.
Gary
Original Message
From: Matt [EMAIL PROTECTED]
Sent: Wednesday, March 22, 2006 6:31 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] OT: port forwarding
That's surely a bug. Dave sent his message as plain/text and
SmarterMail should be replacing the brackets with HTML encoding before
displaying it as HTML so that it should not be a functional
element when
displayed., i.e.
lt;meta http-equiv=Refresh content=5;
URL=http://www.mydomain.comgt;
If Dave had sent it as an HTML message, his client would have done the
replacement for him.
This should probably be reported to SmarterMail. There are a lot of
potential consequences, for instance, virus scanners won't generally
consider code in plain/text segments to be executable, yet it can be in
SmarterMail webmail if it is working the way that you reported.
Matt
Gary Steiner wrote:
It is interesting how SmarterMail's web mail interprets Dave's
message. It sees the META statement in his message as embedded
code, and runs it when I read the message.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
Hi Kevin- My original message was text-only. I just checked to be sure. -d - Original Message - From: Kevin Bilbee [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Thursday, March 23, 2006 1:35 PM Subject: RE: [Declude.JunkMail] OT: port forwarding This is a bug SmarterMail they need to do the replacements when displaying a plaintext email. Or switch the view automatically if there is only a plaintext portion of the email. Does the origional email have a plaintext and html portion??? If it does and the HTML portion is blank then they are doing what many clients would do. Default to the HTML view. They also may be using poor judgment and assuming that no one would ever discuss HTML tags in a plain text email and not parsing them. Kevin Bilbee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gary Steiner Sent: Thursday, March 23, 2006 8:47 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding I can't get SmarterTools to see this as a bug. Their answer is that their web mail is set to HTML by default, and you should just click on the plain text link to view it. Their support doesn't seem to be able to grasp the wider implications of this problem. Gary Original Message From: Matt [EMAIL PROTECTED] Sent: Wednesday, March 22, 2006 6:31 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding That's surely a bug. Dave sent his message as plain/text and SmarterMail should be replacing the brackets with HTML encoding before displaying it as HTML so that it should not be a functional element when displayed., i.e. lt;meta http-equiv=Refresh content=5; URL=http://www.mydomain.comgt; If Dave had sent it as an HTML message, his client would have done the replacement for him. This should probably be reported to SmarterMail. There are a lot of potential consequences, for instance, virus scanners won't generally consider code in plain/text segments to be executable, yet it can be in SmarterMail webmail if it is working the way that you reported. Matt Gary Steiner wrote: It is interesting how SmarterMail's web mail interprets Dave's message. It sees the META statement in his message as embedded code, and runs it when I read the message. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: port forwarding
Then I would suggest making a feature enhance ment to SmarterTools.
If a message has not HTML part then default to displaying the plain text.
It sounds to me that SmarterMail defaults to an HTML view of a message. They
do not see this as a bug so it must be a feature!!
Kevin Bilbee
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dave Doherty
Sent: Thursday, March 23, 2006 11:52 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] OT: port forwarding
Hi Kevin-
My original message was text-only. I just checked to be sure.
-d
- Original Message -
From: Kevin Bilbee [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, March 23, 2006 1:35 PM
Subject: RE: [Declude.JunkMail] OT: port forwarding
This is a bug SmarterMail they need to do the replacements when
displaying
a
plaintext email. Or switch the view automatically if there is only a
plaintext portion of the email.
Does the origional email have a plaintext and html portion???
If it does and the HTML portion is blank then they are doing what many
clients would do. Default to the HTML view. They also may be using poor
judgment and assuming that no one would ever discuss HTML tags
in a plain
text email and not parsing them.
Kevin Bilbee
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gary Steiner
Sent: Thursday, March 23, 2006 8:47 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] OT: port forwarding
I can't get SmarterTools to see this as a bug. Their answer is
that their web mail is set to HTML by default, and you should
just click on the plain text link to view it. Their support
doesn't seem to be able to grasp the wider implications of
this problem.
Gary
Original Message
From: Matt [EMAIL PROTECTED]
Sent: Wednesday, March 22, 2006 6:31 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] OT: port forwarding
That's surely a bug. Dave sent his message as plain/text and
SmarterMail should be replacing the brackets with HTML
encoding before
displaying it as HTML so that it should not be a functional
element when
displayed., i.e.
lt;meta http-equiv=Refresh content=5;
URL=http://www.mydomain.comgt;
If Dave had sent it as an HTML message, his client would
have done the
replacement for him.
This should probably be reported to SmarterMail. There are a lot of
potential consequences, for instance, virus scanners won't generally
consider code in plain/text segments to be executable, yet
it can be in
SmarterMail webmail if it is working the way that you reported.
Matt
Gary Steiner wrote:
It is interesting how SmarterMail's web mail interprets Dave's
message. It sees the META statement in his message as embedded
code, and runs it when I read the message.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
Gary, I've had some issues getting them past the part where they assume "user error" or something else that is outside of their immediate control so that they can actually look at the issue at hand. It may be just simply an issue of them not listening/reading carefully enough. All I can say is that you might want to go back to square one and re-explain the issue. I think that Kevin made the essence of that clear in his reply, but I would then add to it the unfortunate issues that can result from displaying plain text as HTML, and suggest that if they are displaying a plain/text only message, to do some bracket replacement in order to keep plain/text elements from becoming functional in the HTML view. Showing a message that is plain/text as HTML is fine just so long as they replace the brackets. Matt Gary Steiner wrote: I can't get SmarterTools to see this as a bug. Their answer is that their web mail is set to HTML by default, and you should just click on the "plain text" link to view it. Their support doesn't seem to be able to grasp the wider implications of this problem. Gary Original Message From: Matt [EMAIL PROTECTED] Sent: Wednesday, March 22, 2006 6:31 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding That's surely a bug. Dave sent his message as plain/text and SmarterMail should be replacing the brackets with HTML encoding before displaying it as HTML so that it should not be a functional element when displayed., i.e. lt;meta http-equiv="Refresh" content="5; URL="" class="moz-txt-link-freetext" href="http://www.mydomain.com">http://www.mydomain.com"gt; If Dave had sent it as an HTML message, his client would have done the replacement for him. This should probably be reported to SmarterMail. There are a lot of potential consequences, for instance, virus scanners won't generally consider code in plain/text segments to be executable, yet it can be in SmarterMail webmail if it is working the way that you reported. Matt Gary Steiner wrote: It is interesting how SmarterMail's web mail interprets Dave's message. It sees the META statement in his message as embedded code, and runs it when I read the message. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
Matt, I tried all that. It seemed like they didn't want to listen, or that the whole concept was just foreign to them. It's like the support people are multitasking and are unwilling to take the time to properly listen to the customer and dissect the problem. I've had very strange results dealing with their support. One day I get the perfect response to my questions, and the next day it is like I am talking to someone on another planet. Maybe their focus has changed somewhat as well. Their online forums used to be very useful. They were very well organized, and the support people participated on a daily basis. Around the time that 3.0 came out they changed the organization of their forums, lumping a lot of separate secitons together. Now you get the newbie user questions mixed together with the questions from server administrators. Also, it seems that over the past two weeks the support people have stopped posting on the forums altogether, the only ones posting now are the users. If this is an indication of a major policy shift on their part, this does not bode well for the future. Which is a shame considering that SmarterMail seems to be taking off as a product. Deja vu all over again. I've been going over another problem with them regarding Yahoo Groups. For some reason mail sent from SmarterMail to Yahoo Groups gets bounced by Yahoo as a 554 error stating that the message was sent as a BCC (which it most definitely was not). When I talked to Yahoo, they said it was a SmarterMail problem, and of course, SmarterMail insisted it was a Yahoo problem. Everyone is ready to wash their hands of the problem rather than try to get it solved. Sorry if I've gone off on a rant, but both of these problems seem to me to be indicative of potentially significant bugs, but I can't seem to get that message across. Gary Original Message From: Matt [EMAIL PROTECTED] Sent: Thursday, March 23, 2006 5:39 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding Gary, I've had some issues getting them past the part where they assume user error or something else that is outside of their immediate control so that they can actually look at the issue at hand. It may be just simply an issue of them not listening/reading carefully enough. All I can say is that you might want to go back to square one and re-explain the issue. I think that Kevin made the essence of that clear in his reply, but I would then add to it the unfortunate issues that can result from displaying plain text as HTML, and suggest that if they are displaying a plain/text only message, to do some bracket replacement in order to keep plain/text elements from becoming functional in the HTML view. Showing a message that is plain/text as HTML is fine just so long as they replace the brackets. Matt Gary Steiner wrote: I can't get SmarterTools to see this as a bug. Their answer is that their web mail is set to HTML by default, and you should just click on the plain text link to view it. Their support doesn't seem to be able to grasp the wider implications of this problem. Gary Original Message From: Matt [EMAIL PROTECTED] Sent: Wednesday, March 22, 2006 6:31 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding That's surely a bug. Dave sent his message as plain/text and SmarterMail should be replacing the brackets with HTML encoding before displaying it as HTML so that it should not be a functional element when displayed., i.e. lt;meta http-equiv=Refresh content=5; URL=http://www.mydomain.comgt; If Dave had sent it as an HTML message, his client would have done the replacement for him. This should probably be reported to SmarterMail. There are a lot of potential consequences, for instance, virus scanners won't generally consider code in plain/text segments to be executable, yet it can be in SmarterMail webmail if it is working the way that you reported. Matt Gary Steiner wrote: It is interesting how SmarterMail's web mail interprets Dave's message. It sees the META statement in his message as embedded code, and runs it when I read the message. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail
Re: [Declude.JunkMail] OT: port forwarding
I have had similar experiences with them right back to the beginning. I think the quality of the service you get varies greatly with the individual. If they get it the response is usually pretty good. It does not always seem easy to get them to get it though... I held off deploying SM in my plant for over a year because I wanted to see how the product would evolve. I was - and remain - very impressed with V3 overall. Every complicated product is going to have some issues, the real issue is how they respond when the product meets the users abnd the trouble tickets start flying. I just submitted a detailed ticket with screenshots and a good explanation as to why I think this is a major issue. It will be very interesting to see what kind of response I get. -Dave Doherty Skywaves, Inc. - Original Message - From: Gary Steiner [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Thursday, March 23, 2006 6:42 PM Subject: Re: [Declude.JunkMail] OT: port forwarding Matt, I tried all that... --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
Dave, I agree, the product is definitely continuing to evolve and they are pretty good at doing a lot of things, but they aren't good at handling support issues, especially from power users with an eye for detail. They didn't get the issues with auth-only port 587 until that exploded on this list despite repeated requests on their own message board and the fact that this was not only useful for shutting off unauthenticated access to a server, but also the standard way of implementing the submission port. I think this comes from the fact that they have a lot of control panel hosting customers using their software, and those users are typically not tweakers like we are. I don't think that there is a lot of interest on their part in getting direction from the community as a result of the general dynamic. I have seen a lot of short-sighted/impractical feature requests from users on their message list, yet I'm sure that those requesting such things feel that their requests are just as important as ours. It's likely hard for them to differentiate, or maybe because of the typical issues that they see are more on the side of the user that they don't tend to think so deeply about this stuff. It sound like they really didn't understand the nature of this bug and assumed it was a user error, or didn't bother to read deeply enough into the unintended affects. What you and Gary have done however seems like the best way to approach it. Sort of like yelling to get attention, but yelling detail and being persistent instead of just getting angry and spouting obscenities. I would understand them not fixing it immediately if it is complicated for them to do so, which it may be, but I wouldn't understand a conscious decision to leave things as is indefinitely. Matt Dave Doherty wrote: I have had similar experiences with them right back to the beginning. I think the quality of the service you get varies greatly with the individual. If they get it the response is usually pretty good. It does not always seem easy to get them to get it though... I held off deploying SM in my plant for over a year because I wanted to see how the product would evolve. I was - and remain - very impressed with V3 overall. Every complicated product is going to have some issues, the real issue is how they respond when the product meets the users abnd the trouble tickets start flying. I just submitted a detailed ticket with screenshots and a good explanation as to why I think this is a major issue. It will be very interesting to see what kind of response I get. -Dave Doherty Skywaves, Inc. - Original Message - From: Gary Steiner [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Thursday, March 23, 2006 6:42 PM Subject: Re: [Declude.JunkMail] OT: port forwarding Matt, I tried all that... --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
NATting in the firewall is what we do, though I've heard of many using gdatapipe. BTW, for searching the archives, the best bet is to google the list... much better searching than is available at mail-archive.com. Darin. - Original Message - From: John Shacklett [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Wednesday, March 22, 2006 3:34 PM Subject: [Declude.JunkMail] OT: port forwarding I'm making the jump to a new mailserver this weekend, and I've hit two snags. I know that the answers to both of these questions are in the archives, but the search feature on the list archive appears to be broken currently. My apologies to all, both for the OT question as well as for reasking. Question one: Many, many of our users have existing shortcuts and bookmarks to webmail on our old Imail machine at the webserver:8383 address. The new machine will have the same FQDN, but the webclient won't run on 8383 any more, it will run on 80. We won't have time to track down every user and update those links, so we're looking for ways to accommodate them. What are people using for port forwarding? I tried using stunnel last night to intercept an 8383 session and redirect it to 80, with dismal results. There must be a smarter and more elegant solution. Thanks, John S --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
Hi John- You may be able to do this with your firewall. Many do, many don't, but that's the first place I'd look. Failing that, set up a webserver on the IP address and port 8383 with a simple HTML forwarder. Put this in the header of the page (obviously changing the address)... meta http-equiv=Refresh content=5; URL=http://www.mydomain.com; ...and put the usual This page has moved, please adjust your bookmarks message in the body. The message will display for about five seconds and the user will be sent to wherever you specify. Note the unusual placement of the quote marks. They are correct as shown, even though they look pretty odd. -Dave Doherty Skywaves, Inc. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
If you have IIS still listening on that port, you can serve this page
html
head
META NAME=Robots CONTENT=NOINDEX
script language=JavaScript
var time = null
function redirect()
{
window.location = location.href.replace(':8383','');
}
/script
/head
body onload=timer=setTimeout('redirect()',1000)
H1Page has Moved./H1
You will redirected in 1 seconds.
/body
/html
John Shacklett wrote:
I'm making the jump to a new mailserver this weekend, and I've hit two
snags. I know that the answers to both of these questions are in the
archives, but the search feature on the list archive appears to be broken
currently. My apologies to all, both for the OT question as well as for
reasking.
Question one:
Many, many of our users have existing shortcuts and bookmarks to webmail on
our old Imail machine at the webserver:8383 address. The new machine will
have the same FQDN, but the webclient won't run on 8383 any more, it will
run on 80. We won't have time to track down every user and update those
links, so we're looking for ways to accommodate them. What are people using
for port forwarding? I tried using stunnel last night to intercept an 8383
session and redirect it to 80, with dismal results. There must be a smarter
and more elegant solution.
Thanks,
John S
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
--
Richard Lanard
Information Technology Support
University of Georgia
Business Outreach Services /SBDC
1180 East Broad Street - Chicopee Complex
Athens, Ga 30602-5412
phone: (706) 542-6774 fax: (706) 542-6776
[EMAIL PROTECTED]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. The archives can be found
at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
John, You can just set up the forwarding within IIS. Just create a site on that IP with port 8383 instead of 80, and then on the Home Directory tab choose a redirection to a URL, enter the new site's location in the box, and then check the box a permanent redirection for this resource. You don't have to create any pages for this site, it will take anything to that old URL as well as any sub-directory of it and redirect it to your new webmail site. Matt John Shacklett wrote: I'm making the jump to a new mailserver this weekend, and I've hit two snags. I know that the answers to both of these questions are in the archives, but the search feature on the list archive appears to be broken currently. My apologies to all, both for the OT question as well as for reasking. Question one: Many, many of our users have existing shortcuts and bookmarks to webmail on our old Imail machine at the webserver:8383 address. The new machine will have the same FQDN, but the webclient won't run on 8383 any more, it will run on 80. We won't have time to track down every user and update those links, so we're looking for ways to accommodate them. What are people using for port forwarding? I tried using stunnel last night to intercept an 8383 session and redirect it to 80, with dismal results. There must be a smarter and more elegant solution. Thanks, John S --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: port forwarding
If you are hosting the new webmail on the same IIS server as the old IMail machine, you may do the following to allow users to continue using port 8383: On web server 1.) Start ProgramsAdministrative ToolsInternet Services Manager 2.) Select webmailpropertiestabWeb Site Advanced 3.) tabMultiple IdentitiesAdd ipaddr=(All Unassigned), TCP Port=8383, header name=blank 4.) Click OK to exit, then stop and start webmail Webmail will answer on all ip addresses:8383 No redirection necessary - I'm making the jump to a new mailserver this weekend, and I've hit two snags. I know that the answers to both of these questions are in the archives, but the search feature on the list archive appears to be broken currently. My apologies to all, both for the OT question as well as for reasking. Question one: Many, many of our users have existing shortcuts and bookmarks to webmail on our old Imail machine at the webserver:8383 address. The new machine will have the same FQDN, but the webclient won't run on 8383 any more, it will run on 80. We won't have time to track down every user and update those links, so we're looking for ways to accommodate them. What are people using for port forwarding? I tried using stunnel last night to intercept an 8383 session and redirect it to 80, with dismal results. There must be a smarter and more elegant solution. Thanks, John S --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
Even easier! That's what I love aboutt his list. Everybody's got something to offer! -Dave Doherty Skywaves, inc. - Original Message - From: Harry Palmer [EMAIL PROTECTED] To: Declude.JunkMail@declude.com Sent: Wednesday, March 22, 2006 4:39 PM Subject: RE: [Declude.JunkMail] OT: port forwarding If you are hosting the new webmail on the same IIS server as the old IMail machine, you may do the following to allow users to continue using port 8383: On web server 1.) Start ProgramsAdministrative ToolsInternet Services Manager 2.) Select webmailpropertiestabWeb Site Advanced 3.) tabMultiple IdentitiesAdd ipaddr=(All Unassigned), TCP Port=8383, header name=blank 4.) Click OK to exit, then stop and start webmail Webmail will answer on all ip addresses:8383 No redirection necessary - I'm making the jump to a new mailserver this weekend, and I've hit two snags. I know that the answers to both of these questions are in the archives, but the search feature on the list archive appears to be broken currently. My apologies to all, both for the OT question as well as for reasking. Question one: Many, many of our users have existing shortcuts and bookmarks to webmail on our old Imail machine at the webserver:8383 address. The new machine will have the same FQDN, but the webclient won't run on 8383 any more, it will run on 80. We won't have time to track down every user and update those links, so we're looking for ways to accommodate them. What are people using for port forwarding? I tried using stunnel last night to intercept an 8383 session and redirect it to 80, with dismal results. There must be a smarter and more elegant solution. Thanks, John S --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] OT: port forwarding
That's surely a bug. Dave sent his message as plain/text and SmarterMail should be replacing the brackets with HTML encoding before displaying it as HTML so that it should not be a functional element when displayed., i.e. lt;meta http-equiv=Refresh content=5; URL=http://www.mydomain.comgt; If Dave had sent it as an HTML message, his client would have done the replacement for him. This should probably be reported to SmarterMail. There are a lot of potential consequences, for instance, virus scanners won't generally consider code in plain/text segments to be executable, yet it can be in SmarterMail webmail if it is working the way that you reported. Matt Gary Steiner wrote: It is interesting how SmarterMail's web mail interprets Dave's message. It sees the META statement in his message as embedded code, and runs it when I read the message. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
RE: [Declude.JunkMail] OT: port forwarding
I thought the meta element is only valid in the head element, thus should never be executed, even if it appears in the HTML body? Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Wednesday, March 22, 2006 06:31 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: port forwarding That's surely a bug. Dave sent his message as plain/text and SmarterMail should be replacing the brackets with HTML encoding before displaying it as HTML so that it should not be a functional element when displayed., i.e. lt;meta http-equiv=Refresh content=5; URL=http://www.mydomain.comgt; If Dave had sent it as an HTML message, his client would have done the replacement for him. This should probably be reported to SmarterMail. There are a lot of potential consequences, for instance, virus scanners won't generally consider code in plain/text segments to be executable, yet it can be in SmarterMail webmail if it is working the way that you reported. Matt Gary Steiner wrote: It is interesting how SmarterMail's web mail interprets Dave's message. It sees the META statement in his message as embedded code, and runs it when I read the message. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type unsubscribe Declude.JunkMail. The archives can be found at http://www.mail-archive.com.
