How to fix Blat email having wrong timestamp? - smtp

The email I sent using blat is showing wrong time at the receivers end. The time is shown one hour earlier than actual sent time. I verified it by sending to my own email. I saw this thread where another user faced similar issue but no fix.
My guess is that you are in US Eastern Timezone, your system is configured
to GMT, while your managers' systems are all configured for Easter Time.
Blat tries to get the local time in your system, plus the time zone
difference from GMT, and put the correction into the outgoing header
from link
If Anybody know how to properly give timezone details to blat or fix this please let me know how.

Related

How can I send HTML emails using PHP through a diffrent server to avoid Shared-hosting delays

I am currently using SiteGround shared hosting to host my website. Through SiteGround I send an HTML email using PHP to my customers when they register to confirm their email address.
I am currently having issues with receiving email, with it taking over 4 hours to appear in my inbox.
Contacting Siteground they tell me SpamExperts who run their MX recorders are having some issues. I am currently still having these issues after 24 hours despite Siteground telling me it has been fixed.
I am unsure about how to fix this, it may just need time. Either way, I was wondering if there is any way of having an alternative server to send my emails through incase it happens again?
I have limited knowledge on how emails send, but I know that it helps if the from the domain name is the same one I have set up through the shared hosting. I thought about just having shared hosting with another company but then my domain wouldn't match up.
I'd appreciate any insight into this.

A website tells me my password is compromised, does this imply the website is also insecure?

I recently logged into a website (student run club website which stores event and participant information).
After successfully logging in the following message appears and follows me around for the rest of my time on the site:
You are using an insecure password. The password that you entered has
been exposed in at least one data breach.
How do you know my password is insecure? This password appears in a
database of known passwords. Hackers may use this password to try to
break into your accounts.
While I appreciate the notification that my password was compromised (and should know better and will change and stop reusing passwords etc etc) I now worry about the overall security of this site.
I don't know a terrible lot about web dev but my naive assumption, given this message and the fact that it appears after log in, is that my password must have been stored in plain text for them to be able to check it against a database. Is this correct? Or is there some clever secure way this could be done?
Just because you are receiving a notification from the site doesn't mean that your passwords are being stored in plaintext. Whatever website you are using can use your password in the "Have I Been Pwned" API before encrypting them. This of course doesn't necessarily mean that they are encrypting them as there isn't really a surefire way to know how they are storing your passwords without possibly contacting the owner or if you were to receive an email at a later date with your password in it.
You can read up on the API for password checking here haveibeenpwned.com/API or you can check for the website you are using in this list here haveibeenpwned.com/API/Consumers.

Is this the right way to store tracking information for a website?

I need to store the IP address, the User-Agent of the client who is requesting a particular web page, the name of the webpage being requested and the request time. I am planning to store the information in a table in the database(MySQL). But, the problem I can for-see is that every time the page is requested there will be a database entry, and in time it would take up a huge amount of space.
Does analytics tools like Google Analytics already store these information (IP-Address, User-Agent, Requested-Webpage-Name, Time) that I can access anytime in future (Say, i need to check the client's IP and User-Agent who viewed a particular page within a particular timeframe)? If not, is my approach the right way to do it? If not, what is the right way?
I found that nginx does this out of the box with it's access logs, which are stored in /var/logs/nginx/access.log. So, i just need to pare the access log data, using various tools available online.

OBIEE Scheduling reports

I am having a problem trying to schedule a report in OBIEE. After some research I found that, if we want to do scheduling in OBIEE we have to install SMTP server on our system. Is that true?
I just installed the Hmail server on my system, and gave it the necessary information about port number, domain name, sender and receiver mail Id's. However, when I am running my report I get the following error.
Global Error: [nQSError: 77030] Oracle BI Presentation Server Connection Error: Unable to resolve the address for miracle_PC.
Error Codes: AXSBMN8D:
The operation completed successfully.
Here miracle_pc is my system name.
How can I resolve this problem to deliver a report through email in OBIEE.
If you want to send email from OBIEE, then yes you need access to an SMTP server. This might be one within your company, from your internet service provider, from your webmail provider -- or you can host your own.
Looking at the error you've posted it looks like miracle_PC isn't a valid DNS entry so OBIEE can't find the SMTP server you've given it.
Which version of OBIEE are you using? The configuration for 10.x.x.x and 11.x.x.x varies slightly, however take a look at the below url for ibot configuration in 11g.
https://praveenobd.wordpress.com/2013/01/23/setting-up-ibots-in-obiee-11g-2/
According to your question, you seem wanted to use OBIEE report schedule.
In my experience, there is two different type of schedule.
Sending scheduled reports via email
Seeding scheduled reports (it is more likely run the report regarding
your schedule and save cache on the memory)
You can use both of them if you want.
Regarding this error, I would like to recommend that you need to test your email server first. The testing email server is not related to OBIEE.
The reason behind I am recommending to test your SMTP email server is that
it looks like OBIEE is not able to find DNS of your server or the
configuration might be invalid if the SMTP email server was working.
I understand that it does not look like a solution, but I hope it will help.
I know it's too late but for people still searching for a solution.
I faced the same problem and solve it by editing /etc/hosts file.
The hosts file contains lines of text consisting of an IP address in the first text field followed by one or more host names
if you want to read more you can go to this link.
in your case it should be <Your_IP> <host_name> <miracle_PC>

Extract mail from Exchange and load into Mysql. Perl Win32::OLE or Perl Net::POP3, or try it in Ruby

My problem is this: I need determine the timestamp of the first and last email sent from an Exchange account for every day that mail exists for. Also, for each day I need to rank the words that appear in each email so that I can report trend words for each day.
I have two approaches to this I'm considering, and would welcome comments and suggestions relating to either these approaches or something entirely different.
I've discounted exporting the file from Outlook as a CSV file as it does include the time stamp fields in the output, which is a crucial factor for me.
Approach #1 is:
Use Perl and Net::POP3 to pull the messages out of the inbox, mung them and then insert them into a MySQL database.
Approach #2 is:
Use Win32:OLE to attempt to act like a proper Exchange client, to the same end.
If you use Win32::OLE you'll have to either use Outlook automation or the CDO libraries. I've done both in a previous life, and it works, but it's a bit painful.
I'd suggest approach #1 except that I can't imagine that Exchange would actually allow you to fetch sent mail through POP. Rather, though, Exchange can be enabled to expose an IMAP interface, and IMAP should certainly let you get at the Sent mail without running into any of the problems associated with POP (for example, replacing deleted messages on the server). I haven't used it but Mail::IMAPClient appears to be the recommended module for this.