Jump to content

bear

Valued Contributor
  • Content Count

    3627
  • Joined

  • Last visited

  • Days Won

    11

bear last won the day on April 4

bear had the most liked content!

Community Reputation

67 Excellent

About bear

  • Rank
    Senior Member

Recent Profile Visitors

4075 profile views
  1. That's the setting already on it, and the note "sticks" to the topmost reply when it was created. Add replies, the note moves down along with it. May be just the way I think, but I believe all notes should be in one place. Not seeing any benefit to *another* moving target (I'm looking at you, widgets, with your meaningless sort order that affects only the drop down list) in this interface aside from maybe keeping the reference that caused the note with it. As for the background color, I agree it's attention getting, but it should remain at the top (collapsed or not), rather than have the staff member have to scroll the whole ticket to accurately reply to the latest response. Things will get missed (or researched again), since they may not know about them.
  2. Actually, the notes "pane" sticks to the spot in the ticket that it was first entered, so it scrolls down with the ticket replies. That means if the note is left for the next admin, they have to review the entire ticket start to finish to be sure they missed no notes. Why isn't that at least stuck to the top like all other desk applications?
  3. Just wondering why the admin notes in a ticket are large, at the top and have an attention grabbing red background. I also wonder why there is no method to collapse it (unless I've missed it), so you don't need to scroll past a list of these to see ticket contents. Your admins add 5 notes with whois or something, and you're scrolling a really long way to see the replies. It would be appreciated if the support desk could see a little love and make notes less "in your face" until needed. Just adding a collapse section button would work, kind of like the sidebar.
  4. Touching on this again today, the built in WHMCS sync and it's inability to sync Namesilo names shows up in the sync email also. I get this for names at NS: "Sync Not Supported by Registrar Module". As I move more names there and register new ones, the emails and logs will be filled with those. WHMCS, is it so hard to reach out and see about offering sync from other registrars like this one? They have a sync script, with visible code, available over there. How hard to incorporate this that you can't seem to be bothered to do so?
  5. Bear in mind if you're using spam filtering where it checks RBLs, you might see errors using those. Many of the RBLs limit connections, and Googles DNS is used by a ton of people.
  6. I know you didn't ask me, but you might consider throwing some money at @brian! to see if you could convince him to work on one. AFAIK he isn't creating and selling things here, but he certainly has the ability to.
  7. We don't invoice suspended accounts here, since the original amount needs paying first. Any reason you're invoicing these continuously, even while suspended for non-payment?
  8. There was nothing mentioned in the WHMCS phpinfo page (at the top) about "Configuration" files anywhere?
  9. Look in that file for any additional config files? Near the top: "Configuration". There may be a stray ini or .htaccess affecting it?
  10. Possibly encoding, faulty server or even origin issues (sender error). Or it was an embedded image, and you're seeing the raw image data. 😉
  11. It was a reference specifically to this: "I'm pretty sure there aren't any server admins out there that are just waiting and watching for emails to arrive". Asking if it's safe then dismissing a potential security concern because you feel it would require an actual person carefully watching emails is too narrow a viewpoint when it comes to security and unencrypted emails with potentially exploitable content. I've never seen that, despite using STARTTLS, though get few legitimate bounces. If both connected servers are using the encryption layer, it's stripped on arrival to show the underlying email (which is stored in plain text, as explained).
  12. SSL connections and secure sockets do *not* encrypt email. STARTTLS will add an encryption layer that helps mask the contents, but there's an important caveat: "The encrypted message is revealed to, and can be altered by, intermediate email relays. In other words, the encryption takes place between individual SMTP relays, not between the sender and the recipient." To make email unreadable by third parties requires end to end encryption, which uses public and private keys at both ends. That's important. You should probably look into "bots" and "sniffers". Also, with WHMCS installations being a ripe target for stealing user and payment info (not to mention server credentials), perhaps you shouldn't be so cavalier about that.
  13. Based on what? Maybe if it's Gmail to Gmail it may be, but unless the user and WHMCS are both using encryption (in fact the same encryption, process and key), it's not. Having an HTTPS website doesn't mean it's encrypting your email; that's an entirely separate process.
  14. Mail does not go directly from the server to a remote mailbox. Along the way it typically passes through many points, which could, at least theoretically, be seen by someone else. Can something like a hash be used to do things that are unexpected? Possibly. Certainly more unsafe than having someone log in to do things, which requires a password, so more secure.
  15. In most browsers, pressing the F12 key will open developer tools. Look on the left side of that window/frame for a button you can press which will allow you to then hover over the element, then select it, showing what CSS is responsible for it. From there you can play with it until it looks right, and add that CSS into your own custom.css file.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated