Showing posts with label gmail. Show all posts
Showing posts with label gmail. Show all posts
Saturday, January 28, 2017
Attachments banned by google
Routine attachment extensions banned by Google. If the are going to be attached, they will need to be renamed and hidden. Usual method is to create either a tgz or zip file containing the files, and then rename that attachment. Usual that seems to work is to reverse the spelling of the file.
So far google doesn't seem to vet the attachment with the "file" type as well as the extension, because presumably software at the receiving or download end ignores it if the extension doesn't match.
http://www.computerworld.com/article/3161898/security/gmail-will-block-javascript-attachments-a-common-source-of-malware.html
Users will no longer be able to attach .JS files to emails in Gmail, regardless of whether they attach them directly or they include them in archives like .gz, .bz2, .zip or .tgz. For those rare cases when such files need to be shared via email, users can upload them to a storage service like Google Drive and then share the link.
The .JS file extension will be added an existing list of other banned file attachments that includes: .ADE, .ADP, .BAT, .CHM, .CMD, .COM, .CPL, .EXE, .HTA, .INS, .ISP, .JAR, .JSE, .LIB, .LNK, .MDE, .MSC, .MSP, .MST, .PIF, .SCR, .SCT, .SHB, .SYS, .VB, .VBE, .VBS, .VXD, .WSC, .WSF and .WSH. Most of these file types have long been abused by cybercriminals to send malware via email.
Friday, October 7, 2016
Setting up a google account with fetchmail
These are notes on what is required to set up pop3 fetching of gmail.
su as fetchmail id. /usr/bin/fetchmail won't run as root.
/usr/bin/fetchmail -a -k -f /etc/fetchmailrc
This will force running of all the rules in fetchmailrc
tail /var/log/mail.log will show the progress.
It wouldn't hurt to kill fetchmail with /etc/init.d/fetchmail stop
This debian doesn't support service fetchmail stop, so use the direct script to stop and start fetchmail
Verified 11/4/2014 jws
You must also log onto the gmail account, and in settings Forwarding and POP3/IMAP tab set Pop3 on.
On google mail with a newly setup account, you will get a message such as:
Review blocked sign-in attempt
By default, Google gmail will block an attempted login to their POP3 port, even with ssl and correct credentials, till you approve the access. There are ways to find these queries as third party applications, but the easiest way if you have control of the fetchmail demon is to just go ahead and launch the fetchmail (via /etc/init.d/fetchmail) and let it fail.
A failure AUTH should be logged in the /var/log/mail.info
If there are any problems that you want to see more information about, up the verbosity of fetchmail's messages by editing
/etc/default/fetchmail
and adding
OPTIONS="-v"
after a restart of fetchmail with /etc/init.d/fetchmail restart, the mail.info file will be full of all sorts of details. Remember to comment this back out and restart fetchmail once problems are solved. The increase in data in mail.info is at least 20 fold.
verified 10/7/2016 jws
***************************
setting up for imap mode fetch from gmail
http://daemonforums.org/showthread.php?t=5590
--30--
Subscribe to:
Posts (Atom)