Ken

While Google and Rackspace don't have piping they do have routing options. So you can route mail to your ticketing server which would then be piped. That's what I have done since we use Google Apps.

They've asked us to post one request per thread which is why I included the thread to the client side two-factor authentication.

+1 for this request

http://www.blesta.com/forums/index.php?/topic/819-client-two-factor-authentication/?hl=authentication

Though I don't have an immediate need, I would like to see this.

I hear your concerns and they will too, electric. But I think you're overthinking their intentions with free modules. You're worried about a monopoly so to speak even though you're not directly saying it. But that's not consistent with them giving away 93% of their code and implementing an open marketplace. This discussion could go on forever. But the fact that we have such a diverse opinion and needs to me proves that there will be plenty of opportunity for 3rd party modules. Blesta can't keep up with the development of several companies on several products. I just don't see it. Don't worry so much. Take it day by day, and if you're worried about Blesta charging for modules in the future then just expect it. The worst that'll happen is you'll have been right.

I'm against this completely. If I update a ticket I want it going out immediately because I work in a mission critical environment where seconds count. As far as editing I'm going with Paul on this one... the email would be sent out via email so even if you edited the ticket that would be inconsistent. Unless an "Edit" email want out to them but then why not just update the ticket again with the correction. The ticketing system is nothing other an a fancy email client. I treat them like emails because you can't edit emails either. There's my input.

Yea but you're comparing apples and oranges. Blesta has been for a while and a lot longer than Hostbill unless I'm mistaken? But if you look at Blesta's track record I think you'll find it very consistent, careful, and complete. Unlike Hostbill who has been sporadic since day one. So I don't think CubicWebs is trying to push his opinion on you but rather instill some confidence from their core users that they haven't really displayed that kind of behavior. As far as you wanting an indefinite price guarantee I want you to show me what company would do or say that? If they have any pricing model changes they will let you know well in the advance. Unlike HostBill who is focused on selling modules and not doing much with the billing system, Blesta is billing system focused and their modules are a part of it's evolution. Then there are 3rd party modules on the marketplace. Of course these things will need some maturity as v3 just came out. But I'm personally glad that I'm ahead of the curve as I like the simplicity at the moment. It's made transitioning very easy for many.

I don't use Blesta on cPanel but I'm going to give this a shot until someone else has a better solution. If it's only occurring after a Blesta upgrade then you probably are not getting an email bounce message when you send an email to the piped address right? Have you checked logs for PHP errors? I'm not sure cPanel stores them but if you can produce those that's where I would start. Also when you're placing the files and upgrading does it by any chance change any file permissions or ownership? Unless it's something internal to Blesta that is the only thing that immediately comes to mind.

Says a little bit about how the brain reads and processes words. Similarly, Did aonnye ncitoe how aanizmg Btelsa's new safwtore is? I cnduo’t bvleiee taht I culod aulaclty uesdtannrd waht I was rdnaieg. Unisg the icndeblire pweor of the hmuan mnid, it dseno’t mttaer in waht oderr the lterets in a wrod are, the olny irpoamtnt tihng is taht the frsit and lsat ltteer be in the rhgit pclae. The rset can be a taotl mses and you can sitll raed it whoutit a pboerlm. Tihs is bucseae the huamn mnid deos not raed ervey ltteer by istlef, but the wrod as a wlohe.

What is it's intended purpose if nobody knows what it is? I know I can make one up but the point of password generators is to quickly randomize a complex password for quicker work flow.

I see. What is it's current function? Since neither the client or the admin have any way of knowing what the password is. Is it just a place holder until they do a password reset?

Yea, I wanted to find out if it's the intended function before I submit bug report or feature request. Paul?

Looks like the ones from the Arachnophobia movie. haha

Not on my system. It just generates a new password then save the client and send mail attempts. There is a password reset tool at the login screen that works though.

If you open up a client as a staff and hit the generate password button the password stays hidden. Is that it's intended functionality? Because I'm not sure what good it'd do if so.

Hmm... are you trolling us? lol because that's a gnarly spider.

When you say purchased does this include monthly subscriptions?

I'm sorry. I completely overlooked this. That's exactly what I'm after... and a far better method than my original request. I will test this out and report back if I have any issues.

So if debug were to produce:[department_name] => Billing Can we make an if statement out of this?

components/gateways/nonmerchant/paypal_payments_standard/language/en_us/paypal_payments_standard.php

If you create a recurring invoice and set it to 1 month indefinitely why does it need a renewal date -- what is it renewing exactly? It forces you to select one. If you setup a set amount of payments, let's say 12 months, what does setting a renewal date do exactly -- wouldn't the renewal date be at the end of the term?

Is it possible to add a tag in the email field of the templates that calls the department's configured email?

Tickets are being routed properly so it's not a problem from the Staff side but rather the client side. If the department's email address is billing@ then updates should come from that email. As a client, what if I wanted to setup a folder in my email client that routed all emails from Billing into a folder -- or an organization who wants to route incoming emails from billing to their billing staff? And of course that's aside from the fact that custom email templates per department. For example if Support is 24 hours but Billing is 9-5... it'd be nice to let the client know in the ticket opener of brief information for that department such as operating hours, alerts, etc that pertain to that department.

We can set the incoming mail per department but not outgoing. If you have a department called Billing and set the email to billing@yourcompany.com the client can open a ticket by sending an email to billing@yourcompany.com. Then the Billing department will use the universal set of templates for all departments. Even though the client started the ticket with billing@yourcompany.com all updates will come back as support@yourcompany.com (or as specified in your template). Now the client is sending replys back to support@yourcompany.com instead of billing@yourcompany.com -- make sense?