Using Google Apps for your Domain, is it possible to set up a catch-all address to act as a proxy for various other addresses on a hypothetical virtual mailbox system and, if so, how would you go about setting this up?
Set up Google Apps so that all mail delivered to a non existant address gets sent to a certain address, log into that mailbox via POP, download all mail addressed to x#your-service.com
You might try the free service described at http://groups.google.com/group/google-appengine/browse_thread/thread/7f48e15a7cedafa6 ; I believe the ability for app engine to directly receive email is on Google's roadmap, but I don't know when it's scheduled to appear, or whether it will be available for free, etc, etc.
Related
I'm trying to find out how I can know if my application that wants to use a restricted Google API scope is exempt from the security assesment.
The documentation for the Google API Services User Data Policy states that:
Local client applications that only allow user- configured transmissions of Restricted Scope data from the device may be exempt from this requirement.
How can I find out if my app qualifies for this exemption?
If you check the OAuth API verification article here:
These applications [local client applications] may be exempt from the secure handling policy because the security assessment (and successful securement of a Letter of Assessment) primarily addresses risks associated with developers obtaining and storing data on servers.
Developers should specify in the verification application whether they believe the application is a local client application, and we will work with the developer to verify that is the case.
Therefore, when sending the verification application you should mention that the application you have is a local client one and if this is indeed the situation, you will be notified about it.
Also, please bear mind, that the local client applications can be defined as, according to Google:
Local client applications are generally applications that only run, store, and process data on the user's device (like a computer, mobile phone, or tablet). While user actions may cause data to leave a device (such as sending an email), local client applications do not transmit restricted scope data to the developer's servers (or servers specified by the developer), unless the user explicitly configured the application to do so. This would include local email clients, file managers, and calendar and contact management applications that don't utilize cloud services or only transmit restricted scope data to user-configured destinations.
Applications that send restricted scope data to a developer's or third-party's servers without explicit user-initiated action, such as setting up a backup capability, will not be considered a local client.
Reference
OAuth API Verification FAQs.
In my Laravel web application, when I send a message to all registered users, an exception occurs saying there are too many connections.
Some posts say I should change grep smtp_accept_max in the service configuration.
Where can I find that configuration in a2 hosting cpanel?
I'm on A2 too. It's not possible to change this setting through cPanel. But you can create you own php.ini as explained here.
There are couple of things to consider. A2 is not a fan of bulk email sending from their servers, as explained in their TOS. I had a warning once and was suspended.
(The mail service of your Lite Web Hosting - Singapore account with username xxxxxxxx on sgss2.a2hosting.com has been suspended. The suspension is due to large volumes of email sent from the account.)
In time, as your website grows, you will have to rely on 3th party services, as the very affordable Amazon SES functionality or mailgun. Personally I use SES in combination with the (since 5.7) Laravel Email Verification method. SES is not a fan of bouncing emails. Above a certain percentage they could suspend that service to you.
If the volume is reasonable, you could for now either loop the emails one by one in a PHP loop or create a queue.
It looks like changing the value of smpt_acceps_max could simply ignore higher volumes.
Hope it helps.
We have an application that uses a couple different Google APIs (Login, Classroom). We originally wrote end-to-end tests to make sure that these integrations worked on a very basic level. Unfortunately, it looks like our end-to-end tests have started failing because Google is detecting "suspicious" login activity from the Google accounts we created to do the integration testing and is presenting Captcha's etc..
Is there anyway to get Google to whitelist an account so that they don't run it through all their security checks? We literally only use these accounts for automated testing.
As much as Email whitelisting goes this is what I found from the docs
Email whitelist:
An email whitelist is a list of IP addresses from which your users
expect to receive legitimate mail. When you add an IP address to your
email whitelist, mails sent from this IP address will generally not be
marked spam. To instead approve specific senders based on their email
address or domain name, create an approved sender list using the Spam
setting.
Please note that email whitelist is not exclusive. If you create a
whitelist for your G Suite account, it will affect your entire domain.
There's currently no functionality in place for you or your users to
only receive mail from a self-defined list of senders.
After you configure an advanced Gmail setting, it may take up to one
hour for that configuration to propagate to individual user accounts.
You can track prior changes under Admin console audit log.
To add IP addresses to your email whitelist:
Sign in to the Google Admin console. From the dashboard, go to Apps >
G Suite > Gmail > Advanced settings. In the Organizations section,
highlight your domain. In the Email whitelist section, enter the IP
addresses of your contact's domain host to make sure any mail
originating from these IP addresses are not labeled spam. If you would
like to add more than one IP address, enter an IP range in CIDR
notation or separate each IP address with a comma. Click Save changes.
I am trying to integrate SES with Sendmail in My EC2 Server.
I looked this documents and followed steps, but didn't work out.
http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/SMTP.MTAs.Sendmail.html
I hoped to see video, but there wasn't anything about this one.
I couldn't even find a good article or blog about this.
Can you help me out? I just need to set up Sendmail via SSH.
This is now possible -- log into your AWS Console, to the SES Dashboard, and you'll see a section titled "SMTP Settings" on the lefthand nav. There you will find instructions and a mechanism to create your own SMTP credentials.
At that point you will need to set up your Postfix or Sendmail to act as a relay for outbound mail, redirecting it to the AWS SES Service API.
HOWEVER a few caveats:
You won't be able to use this as some normal SMTP gateway or outbound mail host unless you were to verify any possible sender for mail headed out of your instance. A more ideal case for this is a vendor who sends out large marketing mails to its customers, or a service that pushes out mail on a subscription or alert basis, all of which come from just one or a small handful of addresses.
Also, using SES means you'll have to live by AWS's thresholds, even once you've requested production access. An AWS engineer told me in training that they generally keep an eye on your mailflow and any bounces or rejects, as well as complaints made about your mail, and so long as things look good they will continue to throttle you up in that regard.
Good luck to you.
I am working on .net applicaton that need to send emails to clients. I am trying to figure out what would be that best solution to send emails. Here is what i have considered. Could you please suggest what would be the best way to go for?
1>Windows server 2008 in built smtp
service.
2>Exchange server hosted in our
datacenter.
3>Use google apps for sending
emails(Basically same as gmail like
for custom domain).
I have explored all options and below are findings.
1>I think would be way to go. Also
supports drop in directory to send
emails so can achieve disconnected
email activity.
2>Application would be tied up with
availability of exchange server and
we dont have any exchange server
support personal. Only developers
poke around in exchange server and
got it working. So if option 1 is as
good as 2 then would like to go with 1.
Is there any drop in directory feature in exchange server like 1?
3>Tried gmail smtp stuff didnt
work. I was receiving timeout error.
Also there is no guarantee that
gmail will send our mail
reliability. They can decide anytime
to stop sending our mails as we are
using free standard version of
google apps.
Other questions:
I installed smtp service in windows server 2008. Now to use this do i need to change any MX record and anything? What i need to do so it can send email using my domain name. Or it can send email for any domain?
I would use a hybrid of 1 and 2. Use local SMTP, but have it relay to your exchange server. Emails will queue if it can't relay to exchange and you have one server(s) that handle all of your outgoing/incoming mail. This support doc explains this setup: http://support.microsoft.com/kb/303734
You only need an MX record if you'll be receiving mail from that domain too.
I would also put in a reverse DNS entry for your domain, which will help with spam detection.