while looking at past questions, it seems like if I wanted to mail from localhost I would be able to use a gmail account through google's smtp service. However as of may 2022 it is no longer possible for external apps to use my google account: 1
Seemed like all information online was focused on using google's smtp on xampp, so I was wondering if anyone had a updated method they used for emailing from localhost?
Thanks in advance!
Related
I created a video downloading bot using python and hosted it on heroku. The bot is working perfectly. But the problem is I have some video urls which were issued only to my ip address in computor.
When I try to download the video with the bot running locally it works fine. But when downloading with the bot hosted in heroku it gets 403 forbidden error.
So is there a way to use these ip issued urls on an another server or a pc. I tried using same proxy server in heroku and in my pc. But they are blocked to the country also.
I can't move on to paid servers because the bot is used only by me and it is waste of money to use a paid service for an small task.I know there is some way to do this. I saw some guy is doing this with Napsterntv.
So can anyone suggest a way to do this. Any help would be appreciated.
As the title mentions, I've got a question regarding the possibility of implementing the on send event functionality on the outlook PC client.
I current got an add-in running that blocks sending emails on the outlook WEB variant properly and allows sending them when the criteria is met. I've used the examples the microsoft documentation provides to get it to work. This example however doesn't work on the outlook PC (windows) client. Other functionality works just fine on the outlook PC client, it's just the on send not functioning. All I get on the outlook PC client is the error "[add-in name] couldn't complete. Please try sending this message later" upon pressing send.
Been looking at this for the past few days and based on all the microsoft documentation it gives me the impression that it should be possible, but I can't find any examples online or anyone really verifying it either. Which bring us to my question as I mentioned at the start;
Is it possible to make the outlook on send event work on the outlook PC client as well? And if so, does anyone have an example of how to do so?
Thanks in advance!
Yes, the on-send feature for Outlook add-ins is supported in certain versions of Outlook win-32. There is documentation here about which versions are supported and some code examples.
I managed to fix my issue.
So to recap; when running the nodejs server locally, the on send didn't appear to work for the outlook pc client. (It did for outlook web)
What I did was put the code on an external server and ran the nodejs. Then I created an IIS website with https and redirecred it towards the localhost port of the nodejs server.
After doing this and installing the manifest through the URL the issue no longer persisted for the pc client and worked exactly the same as the outlook web variant.
I am new, so I cannot add comments - but keep in mind that if you plan to put your add-in into AppSource - the doc says it will be banned: you are not allowed to use the OnSend event for anything in there.
I hope this helps you avoid some pain if you had those plans!
" Important. Add-ins that use the on-send feature aren't allowed in AppSource. "
( https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/outlook-on-send-addins?tabs=classic )
I've been following Microsoft's Teams C# tutorials found here, and have been successful for the most part. However, I cannot seem to get my app to work when I host the messaging endpoint myself rather than via their Azure service, which is not an option for me ultimately as the pricing is outrageous for what we need it to do.
I'm hosting the endpoint myself by publishing the sample project and ensuring it's externally available via HTTPS. I can access a custom tab within Teams, so I know that it's online, it's just the messaging endpoint that seems to fail with an "unable to reach app" error when I try and use the messaging extension via a chat window.
When debugging using dev tools, I get 502 error: Bot returned unsuccessful status code Forbidden, error code 1008. Every potential solution I've seen for similar issues hasn't worked for me thus far, though I still feel like it's something incredibly obvious. Are there special steps that need taking when hosting the endpoint yourself? The docs do a very lousy job of explaining the process, probably because Microsoft want you to pay to host the app on Azure.
This is usually caused by the app id / app key not being registered or used correctly in your app, so it's not authenticating to the bot framework service properly. Where/how you do that depends a bit on what sample code / project template you started with, but it's usually somewhere in a .config file (or previously in a .bot file).
The information that you need will be in:
App Id: The Bot Settings page in Azure
App Key: from the Bot settings page, where you got the AppId above, it links to the App registration itself - within there you'll find the section on keys, and you can create a new key (if you've lost the original one)
I know it's generally an error when AppID validation fails. The bot app requests Azure AD to verify the identity.Could your web server access to Azure AD? If you deny to access to outbound with firewall, you should allow Azure IP range.
Turns out it was purely a network issue, that as of yet we still haven't actually figured out. But we tried hosting the app elsewhere and it was fine. That's my recommendation if anyone else has the same problem!
I have my work email set up on an iPhone using the instructions given to me by my IT department. It works a treat.
I'd really like to be able to use in on my Mac. I have webmail (owa) access but it's a terrible webmail client. I use Airmail as my email client.
I've been reading online and I understand there are different issues with accessing Exchange email from a Mac, but I'm hoping they are surmountable.
The info from my IT people for iOS set up includes
My username
My password
A server - mobile.xxx.xxx.xx
A domain - live.xxxx.xxx.xx
I don't seem to be able to make any combination of these work for mac email setup.
Is there a solution?
Thanks
Try to enter username with the domain:
domain\username
username#domain.fullname.com
If nothing works, maybe you can ask your IT dept for help?
Also, your server administrator should check that EWS protocol is enabled for your mailbox (most MacOS clients works through this protocol)
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.