Hello Tbbeta,
When trying to send mail to a server with an expired Cert Mail send
fails with no explanation: https://www.ritlabs.com/bt/view.php?id=6856
Quote:
The Bat! gives the explanation in the account log, but we won't make
an option to bypass this error.
No way to send an email with TB!
The Bat! gives the explanation in the account log, but we won't make
an option to bypass this error.
No way to send an email with TB! if the sysad at the other end is a
dimwit. Good night then.
I am actually quite taken aback by this unexpected reply. I have
absolutely no understanding for
Am 27.09.2010 17:10, schrieb Thomas Fernandez:
When trying to send mail to a server with an expired Cert Mail send
fails with no explanation:https://www.ritlabs.com/bt/view.php?id=6856
This will not help you actually, but i recognized, that they have been
working on this, because Bugtracker
Hello all,
Monday, September 27, 2010, Jens Franik wrote:
This will not help you actually, but i recognized, that they have been
working on this, because Bugtracker Entry gave me Feedback about Status
Change...
nobody is working on this, report was closed
--
Bye
Marek Mikus
Czech
Sveiki,
Monday, September 27, 2010, 6:10:47 PM, you wrote:
Hello Tbbeta,
When trying to send mail to a server with an expired Cert Mail send
fails with no explanation: https://www.ritlabs.com/bt/view.php?id=6856
Quote:
The Bat! gives the explanation in the account log, but we won't make
Hello Vilius!
On Monday, September 27, 2010 at 6:17:05 PM you wrote:
You can always choose a company with does provide services as they are
supposed to be served.
Yeah, especially when your reliable service just once hiccups for a
few days ...
Bad cert is not The Bat!'s fault. And
Hello Vilius,
On Mon, 27 Sep 2010 19:17:05 +0300 GMT (27/Sep/10, 23:17 PM +0700 GMT),
Vilius Šumskas wrote:
I am actually quite taken aback by this unexpected reply. I have
absolutely no understanding for this policy which will certainly hurt
my company. If I cannot send a mail to my customer
VŠ Bad cert is not The Bat!'s fault. And providing an option to bypass
VŠ that, is a security risk as explained numerious times on this list.
Right. So I'll lose the customer because TB! doesn't allow me to
override the security issue.
You must be quite unaware of business reality to say
On Monday, September 27, 2010, 12:50:28 PM, Vili wrote:
I totally agree with Thomas. TB is not user friendly when reporting
errors, warnings. The error should be put into the face of the user,
suggest him a solution and allow him to bypass this kind of
certificate security issues if he
You have to remember that theBAT is always looking out for us. I see
this issue as very similar to the refusal to enable inserting notes or
other useful information into the body of messages in your data base,
or doing things like removing '[SPAM]' from headers for some imagined
reason of
Guten Morgen,
TF The Bat! gives the explanation in the account log, but we won't make
TF an option to bypass this error.
TF I am actually quite taken aback by this unexpected reply. I have
TF absolutely no understanding for this policy which will certainly hurt
TF my company.
Actually, it's
On Monday, September 27, 2010, 3:25:31 PM, Rick wrote:
You have to remember that theBAT is always looking out for us. I see
this issue as very similar to the refusal to enable inserting notes or
other useful information into the body of messages in your data base,
or doing things like
lunes, 27 sep 2010 at 22:07, it seems you wrote:
I see
this issue as very similar to the refusal to enable inserting notes or
other useful information into the body of messages in your data base,
or doing things like removing '[SPAM]' from headers for some imagined
reason of morality.
On Monday, September 27, 2010, 7:04:13 PM, NetVicious wrote:
What's the problem with It. I can export the mail and modify it and
later import it to The Bat!. I have the same result. What's the
diference
if you can't see the difference, I'm not sure I could explain it.
--
lunes, 27 sep 2010 at 22:07, it seems you wrote:
I see
this issue as very similar to the refusal to enable inserting notes or
other useful information into the body of messages in your data base,
or doing things like removing '[SPAM]' from headers for some imagined
reason of morality.
Hello Dwight,
On Mon, 27 Sep 2010 15:07:11 -0500 GMT (28/Sep/10, 3:07 AM +0700 GMT),
Dwight Corrin wrote:
I totally agree with Thomas. TB is not user friendly when reporting
errors, warnings. The error should be put into the face of the user,
suggest him a solution and allow him to bypass
Hello Vili,
On Mon, 27 Sep 2010 13:50:28 -0400 GMT (28/Sep/10, 0:50 AM +0700 GMT),
Vili wrote:
VŠ Bad cert is not The Bat!'s fault. And providing an option to bypass
VŠ that, is a security risk as explained numerious times on this list.
Right. So I'll lose the customer because TB!
17 matches
Mail list logo
