Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About oompahloompah

  • Rank
    Distant Family
  1. Mm I could be wrong but I would have thought regexping the mail logs would be possible, thus filtering out the logs that belong to you and those that don't. Perhaps it would be helpful to take it up with the help desk again as it seems they have the key to the answer you wish for.
  2. You could set an autodelay that sends off emails at a prespecified interval. If Squirrelmail does not do it, most third-party email clients do.
  3. What is the difference between superglobal and global variables? I think I understand how they work when it comes to passing data between a form and another output page but I don't know how to implement a superglobal in this case. The reason why I'm asking is because I read up somewhere on the PHP manual which says that globals would soon be deprecated? In this case, which superglobal array should I use? Environment, session, server, request, post, get, cookies or?
  4. I would like to have two files using the heredoc syntax, one handling the user interface and the other handling the headers and footers of a page. The one handling the UI is a function accepting parameters to set the attributes of the UI for example, a button would have the title and href link attributes which would be set via a function. The function handling the headers and footers has buttons inside them and I would like to somehow get the output of the earlier-mentioned function at various places within the heredoc text output of this function. I have tried using a return instead of an echo for the UI function in one file. Then I called the UI function from the other file containing the header/footer function. I plugged the output of the UI function to a variable and I inserted the variable into the header/footer heredoc text. The error I get is a parse error stating something about an unexpected $ sign. I've checked my brackets and they all match. I've checked my variable names and they all have their corresponding $ signs. I've also checked that when the UI function accepts a parameter, it has '' delimiting the parameters. Would be grateful to see a working implementation of this idea.
  5. Ahhh.. Is there a way of storing the heredoc text in a variable in one particular function in a file and call it up again within another heredoc text in another function on another file?
  6. How do I call a function from within the heredoc syntax in PHP? I would like to use a function to display parts of the entire text within the heredoc syntax repeatedly throughout itself. For example, the text that I would like to display is: Mary had a little lamb, little lamb, little lamb. The entire sentence is contained within the heredoc syntax and I would like to use a function to repeat little lamb three times instead of having to type it in full within the syntax. Can this be done? I'm tearing my hair out on this. Edit: I could probably use a variable to store little lamb but unfortunately the piece of text that I wish to repeat has slight variations that makes a function more suitable instead.
  7. worse (for better or for worse)
  8. Crater 160. What's the last possible number?
  9. You're welcome, Weezy. Insert it into the subject line. I haven't personally tried it yet but do let me know if it works.
  10. I totally agree with Robert. At the same time, it would be great to see how the new site looks like. At the moment, things does feel a little scattered and hopefully the new design would make navigation a breeze.
  11. Spamkey is associated with SpamAssassin. It's on everybody's accounts I reckon. It's a key that if used can bypass your spam filters such that whoever uses it will be able to send email without worry about it getting filtered.
  12. Thank you very much for the port numbers. They've helped me configure my email clients successfully. If I may, may I ask which authentication system does TCH POP3 servers support, if any? This has boggled me for awhile and is in my email client settings. Regular - this is a simple authentication mechanism that requires an e-mail client to send a username and password to the server. Username/password data is sent in cleartext form, which could be easily intercepted in transit. This authentication mechanism is supported by most RFC-1081 compliant mail servers, e.g. mail servers that support basic POP3 features. MD5 &APOP Challenge/Response (RFC-1939) - this authentication mechanism avoids passing a cleartext password over a network. Instead of sending the password as cleartext, the e-mail client sends a non-reversible digest (produced by the MD5 cryptographic hash function) of the password concatenated with a unique random string (Challenge String) received from the server. Any exposure of the digest that is sent during the APOP authentication cycle does not introduce a risk, even for e-mail clients that connect frequently to POP3 servers to check for new mail, e.g. every five minutes. Please note that this authentication mechanism may not be supported by all POP3 servers. MD5 &CRAM-HMAC Challenge/Response (RFC-2095) - this authentication mechanism is an improvement over the APOP standard. It also follows a Challenge/Response scheme, but uses HMAC (Keyed-Hashing) instead of the simpler digest method. While APOP requires that both the client and server systems have access to the password in cleartext form, HMAC offers a method for avoiding such cleartext storage while retaining the algorithmic simplicity of APOP in using only MD5, though in a "keyed" mode. Another reason to choose Keyed Hashing is the greater security imparted to the authentication of short passwords. Please note that this authentication mechanism may not be supported by all POP3 servers. Token MD-5 CRAM-HMAC Challenge/Response - this is a hardware implementation of the CRAM-HMAC Challenge/Response (RFC-2095) authentication. A special non-replicable hardware token is used to store the password and to produce the Keyed Hashing. When this authentication mechanism is used, the password will never be exposed at the client side. Once stored, the password cannot be extracted from the token and it is never transferred into the computer where the e-mail client is running. This way, no software (including Spies / Trojan Horses / Viruses) can intercept or otherwise retrieve the password. A mail server administrator may give the user a token that has already had the required password stored on it, so the user won't know and won't need to know the actual password. Utilising the feature that tokens can not be replicated, only the physical owner of the token will have access to the mail server, provided that he or she knows the token's PIN. All POP3 servers that support the MD5 &CRAM-HMAC Challenge/Response (RFC-2095) authentication method support this authentication mechanism. Also, one of my earlier difficulties made me wonder if it's possible for a symlink creation feature to be added in Cpanel. Rock Sign
  • Create New...