I have a script that runs a Java program to run some tests every night. It needs to email out the results of the tests, using JavaMail and a Google apps account.
How do I authenticate with Gmail (through the JavaMail API), without storing the password on the machine that runs the nightly tests? Can I get some sort of an Gmail authentication key that is valid for, say, a month? I don't mind refreshing the key every month, but don't want to keep the password on the test machine.
Google email accounts cost money so I would prefer not to create a new account just to email test results out.
I haven't tried that myself but you can try to send in the mail using the MX servers of googlemail. Currently these are
~ $ host -t MX googlemail.com
googlemail.com mail is handled by 40 alt4.gmail-smtp-in.l.google.com.
googlemail.com mail is handled by 10 alt1.gmail-smtp-in.l.google.com.
googlemail.com mail is handled by 20 alt2.gmail-smtp-in.l.google.com.
googlemail.com mail is handled by 5 gmail-smtp-in.l.google.com.
googlemail.com mail is handled by 30 alt3.gmail-smtp-in.l.google.com.
These are the servers responsible for inbound mails from the outside world, it's plain SMTP without the need of authentication (but you can try to start TLS to make the transfer more secure). There might be checks though, that prevent you from delivering mails to these servers (dyn-IP-checks, SFP, etc.) which is why this might fail.
If you don't want to send to a Google mail address you can try the same thing but replace the MX server of Google with the one responsible for the mail address you want to send to. Just use above call with the different domain or use one of the search results for "mx lookup" if you don't have that as command on your system.
Related
I have configured AWS SES for receiving emails to AWS S3 bucket. Followed Below Steps :-
Create Verified identities i.e. a#domain.com (using Email address so didn't setup any MX records).
Send a test mail from a#domain.com to another verified email address b#domain.com. It is working.
Setup Rule set to create rule :-
Status is Enabled
Spam and virus scanning is Enabled
Recipient condition - a#domain.com
Action - Deliver to Amazon S3 bucket (bucket created using SES so, policy is correct)
Got the file AMAZON_SES_SETUP_NOTIFICATION into the S3 bucket but whenever I receive any new mail to a#domain.com is not found in s3.
Rule set is also in active state.
Can anyone please help me why i am not receiving mail into s3.
Thank You
The error is in your setup. It is impossible for AWS SES to receive any information for the mail that you have, without specifying the MX records. Those records would point to the mail servers of Amazon, so that whenever an email is sent, it is received by them and they can process it.
The verified email addresses concept is used mostly for the sending. By approving the email address, you verify that you can use this email address to send on the behalf of it - not to receive the emails.
What is more, receiving an email works only on the domain level. So you cannot specify in the MX records the specific email addresses. The way to overcome this, is to use some subdomains for instance:
#a.domain.com to go to SES and normal emails will go to your normal email provider.
One last thing - the receipt rules in the amazon SES allow you for configuring the receiving emails on the specific address to give you the possibility to create the special address, such as no-reply/general/etc. Mostly you would prefer to have all of your emails routed in the similar way/routed based on the subdomain.
is there any REST API for roundcube?
I have this need:
I developed a software where it sends some emails to clients and we need to save the sent mails in the "sent" folder.
I searched a lot and all tutorials say that I have to use the auto_bcc but I need to simulate the client's behavoiur, I mean, when the boss access the "automatic#domain.com" mailbox by using roundcube or another email client, he can see the sent folder and the sent mails (not in the inbox), so I was thinking that if I can connect to roundcube and simulate a mail sending, roundcube will save the mail in the sent folder.
I hope I have explained myself
Thanks
You not specify coding language ... in case you use php, use PHPmailer for send the emails.
PHPmailer use resident email server of your system to operate. This means PHPmailer and Roundcube use same standard (inbox/outbox) folders of each user.
Then simply send the email using phpmailer and the email shown in Sent folder !! Look this message shows as unread in Roundcube, you need to set up a filter inside Roundcube if you want to mark as read and/or move this emails to a specific folder.
I have a fully functional Keycloak setup with verify email and then update password features enabled. I have tested multiple times and the mail sending part is working perfectly. But some clients reporting that they didn't receive the registration mail. This maybe due to their firewall, spam filter and so on, now I want way to check whether the email has sent from my system or not. Logs won't help at all, cannot find anything related to sent mails in logs.
I need to send a mail to any domains(gmail,yahoo) without configuring any mail servers in environment.rb.
Is it possible? if it's NO the how devise_invitable gem is allowing us to trigger the mail?
You can use third party email services like:
http://sendgrid.com/
http://www.mailgun.com/
http://aws.amazon.com/ses/
Though you will still need to specify those in environment files, just that you won't need to manage an email server.
We've been testing out using Embedded Signing with our Docusign integration so that clients do not receive an email with each envelope sent to them, instead they would log into a portal which contains links to documents to sign (as some clients do not have an email address, even today!). However we have noticed that the URLs generated through Embedded Signing expire after 5 minutes. Is there a way to control how long these URLs are valid for? Why do these expire when the URLs in the emails do not?
It's an account level setting. DocuSign Support or your Account Administrator can edit this for you.
By default it is set to 300 seconds (5 minutes).