Create a Mail Importer without a validation hash
Permalink
I'd like to create a mail importer that would do the following:
* Capture the 'from' address and verify the email is associated with a user and that the user is part of a 'can use mail importer' group.
* Capture the subject and body to use as a title and content.
* Capture any attachments, add them to the file manager, and associate them with the content.
* Post the content to the site.
All of the above I'm okay with doing. It's the actual email import that I'm having trouble wrapping my head around.
* As I review the MailImporter object and 'Process Email' job functionality, it seems that the default is to check a 'validation hash' before proceeding.
* Is there any way around this without creating a replacement 'Process Email' job that doesn't check for the hash?
Any other help from people who have worked with the Mail Importer before would be greatly appreciated. Thanks in advance.
* Capture the 'from' address and verify the email is associated with a user and that the user is part of a 'can use mail importer' group.
* Capture the subject and body to use as a title and content.
* Capture any attachments, add them to the file manager, and associate them with the content.
* Post the content to the site.
All of the above I'm okay with doing. It's the actual email import that I'm having trouble wrapping my head around.
* As I review the MailImporter object and 'Process Email' job functionality, it seems that the default is to check a 'validation hash' before proceeding.
* Is there any way around this without creating a replacement 'Process Email' job that doesn't check for the hash?
Any other help from people who have worked with the Mail Importer before would be greatly appreciated. Thanks in advance.
If you don't have such validation and the spammers catch on .......
It's really more of an internal thing: I get emails all the time asking 'Can you post this file or add this to the site?' While it only takes 10-15 minutes to do the task, I'd rather spend that time doing something else. :D
Maybe create an override that replaces the validation hash check with a whitelist.
Something in this post has blanked it?
As of right now there isn’t any way to override the class. It is not in the new core ‘Concrete5_Library_****’ format that is then extended at the root level. I think I’m going to test an IMAP class (https://github.com/barbushin/php-imap) to do it instead.
