sparkpost - Routing mail through SMTP and also using API -


i have app (saas – laravel/php) built , goal send transactional mails through app , send general emails out through app. transactional mail working via sending domain (configured using spark post’s api-php).

now, want configure system user logging in can send out emails via his/her own email address (which his/her username used log in); i’m thinking message route through sending domain (the ”from header” users email via sending domain).

do set smtp relay in addition job class i’ve created sparkpost’s api ? configure sparkpost’s api; not sure how approach problem. has 1 encountered same issue/found solution?

offering general email sending service broad topic. here basic observations based on question.

full disclosure: work sparkpost.

in summary, use sparkpost or own smtp relay send user mail caveats. imo, using api-driven service simpler manage smtp relay server.

from addresses

first it's important recognise risk of sending mail from customer domains without explicit authorisation domain owners. modern email domains use several mechanisms (spf, dkim, dmarc, ...) ensure authorised parties can send mail on behalf. without these mechanisms, impersonate else on email.

for reason, recommend don't send mail customer email addresses. instead use own domain either generic address usermail@yourdomain.com or user email addresses embedded.

sending general mail

the messages users send through service impact reputation email sender. recommend considering ways provide service while not presenting easy, automatable, sending service spammers. might include limiting types of message, speed or volume people can send, including recaptcha on mailing forms or possibly vetting users before letting them use mailing services.

sparkpost details

the mail send through sparkpost must using sending domain control. since sparkpost manages delivery, mail sent through sparkpost account impact account's reputation unwanted mail cause account suspended. might consider using subaccounts separate each of users' email traffic , understanding how suppression lists protects sparkpost accounts useful.

 smtp relay details

that same caveats in sparkpost details notes apply here you'll have manage relationship each receiving domain (live.com, gmail, etc) directly. app have include usual unsubscribe , bounce handling features.


Comments

Post a Comment

Popular posts from this blog

Command prompt result in label. Python 2.7 -

i want put result(output) of shell command label. command works, label shows "0", however, in command prompt, result shown correctly, need showed in label. doing ubuntu. myg1 = button(root, text="rodyti informacija", command=lambda: gauti()) myg1.pack(side=bottom) def gauti(): imti = tekstas.get("1.0", "end-1c") info = subprocess.call("id '{imti}' ".format(imti=imti), shell=true) w = label(root, text= info) w.pack(side = bottom) subprocess.call() returns exit code of process created (in case 0 success). if want text output of process, should instead call subprocess.check_output() .
Read more

javascript - How do I use URL parameters to change link href on page? -

i change href value of link using url parameters. example: default <a id="dlink" href="link-1">link</a> but, when user goes https://url.com/?dlink=link-2 it swaps out link new link <a id="dlink" href="link-2">link</a> first need value url. if you're not using javascript framework can create function using jquery. please check get url parameter jquery or how query string values in js it. after that, element "a" id , set value there. $("#dlink").attr("href", hreffromparam);
Read more

amazon web services - AWS Route53 Trying To Get Site To Resolve To www -

so have domain nameservers pointed aws route 53. site hosted on ec2 instance , reachable resolves site.com, if input www.site.com. i'm curious how site resolve www.site.com. have under route53 domains hosted zone 2 additional record sets outside of ns , soa: a site.com ec2 elastic ip cname www.site.com ec2 public dns i can reach site using both site.com , www.site.com, resolve site.com. there way make if enter either, resolves www.site.com? at first, both should record set. a site.com ec2 elastic ip www.site.com ec2 elastic ip and need redirect setting in web server (nginx, apache, ..) following. (source: how redirect www non-www nginx on centos 7 ) redirect non-www www if want redirect users plain, non-www domain www domain, add server block: server { server_name example.com; return 301 $scheme://www.example.com$request_uri; } save , exit. configures nginx redirect requests "example.com" "www.example.com". not...
Read more