I want to develop an email sending application like www.formget.com or similar.
Can anyone will help how to integrate OpenDKIM with my email sending application?
Any idea from anyone would be highly appreciated
I think the first question is how you send your mails? Via your own mailserver postfix, sendmail, ... or you use a smtp relay sendgrid, mailgun, emailsocket,...
The easiest way is using a smtp relay Service, this company create the dns records (SPF, DKIM, DMARC) and you must only set this records on your domain.
Related
I have Postfix setup on my VPS to relay all outgoing mail through AmazonSES and deal with all my incoming mail myself. I have recently setup DMARC and when analyzing my dmarc reports I find that everything passes except for my SPF Alignment. I'm a bit concerned that if I follow Amazons instructions to setup a MAIL_FROM domain that I will lose the ability to deal with my own incoming mail through Postfix, is that correct?
To answer my own question, no, I don't lose the ability to deal with my own incoming email just by setting up a MAIL_FROM (sub) domain.
Best regards
I have an instance configured in Google Cloud, where I installed cPanel to manage more easily my web project. Everything runs fine, but as much a problem to use email accounts.
I set all MX records in the Network section of the console Google, and have also done the same in cPanel. Then I created email accounts in cPanel, and I can access the accounts (I use RoundCube as an email client), but when sending an email, this is going, but does not arrive to destination, or conversely, sent from another account (such as a Gmail) email, and this is sent but not up to my new personal email account.
I realized that what happens is that Google does not allow use ports 25 and 587, so must perform other configuration.
Someone could help me to know how I can create and use email accounts, from a "normal" way, without using Google Apps (because it is paid) or services like Mailgun.
Thanks so much for any help.
You will have to use any third party email service for mail. Please check following URL,
https://cloud.google.com/compute/docs/tutorials/sending-mail/
You cannot use ports 25 and 587 since GCP block all outbound traffic from those ports, I suggest you use port 2525 since that's the only smtp port that GCP does not block and most major vendors use.
I'm accessing my email address via imap protocol using Java Mail.
The server name I'm using is something like impa.somename.secureserver.net
Dose this mean I'm consuming messages using a secure channel? how can I verify this?
If your program is using the "imaps" protocol, has set the "mail.imap.ssl.enable" property, or has set the "mail.imap.starttls.required" property, then you're using a secure channel.
You can verify what JavaMail thinks it's doing by enabling JavaMail session debugging and examining the debug output. It's possible to configure things so that it looks like it's using a secure channel, but it really isn't, but that's not likely to be done by accident. For complete verification, you'll need to get a packet sniffer.
I'm coding an SMTP Server here and wondering an issue which I don't know how to proceed.
You know that when you using Outlook, ThunderBird or any email client to send email, we need (the most of times) username and password to authenticate with the SMTP Server. In this case, SMTP Server requires an "AUTH LOGIN" before other commands such as MAIL, DATA...
I completed this stub in my project. But I'm wondering about a case, when another SMTP Client send directly to my SMTP Server. I mean our server is the final destination of the email. In this case, the authentication with AUTH LOGIN should not be required.
How can I organize my code for 2 cases above. How does the professional MTA such as Postfix, PowerMTA, Exim organize for these.
I hope you will help me
Most outgoing SMTP servers do one of the following:
1) Require SMTP Authentication
2) Alllow relaying without SMTP Authentication only from clients within a certain IP range
If you are doing neither of the above, then that means that your SMTP server is basically operating as an 'open relay', meaning that spammers can abuse your server to send outgoing spam mail.
Many ISP-hosted SMTP servers do #2 above, to allow their clients (and only their clients) to send mail through their SMTP server - as long as the client is on their network.
First of all sorry for my English, its not my native language. I will try to describe my problem as much as I can.
I searched for a long time on the Internet for a solution where I can create a wcf service that can respond to requests of my clients with username and password required but without creating a certificate, using https or anything else that require a special configuration on the machine where my windows service will be installed.
Here is my point: I want to deploy an application to a lot of my customers. This application will have mobile devices and a server which will give some information to mobile device with the help of wcf. Each customer will have a server and many devices. I don't want that anyone on the web can have access to these information and for this reason, I must implement an authentication procedure with username and password for each request but I don't want to be forced to install a certificate, activate some https port on each machine when I sell a new copy of my application.
I've read that with wcf 4.0, there is a built-in system that can encrypt data and for this reason, I don't want the overhead of implementing anything else if possible.
My question is: Is that possible to have a secure solution considering my requirements and if yes, how can I do that?
If I really must create a certificate and use IIS, https or any other secure solution, it is possible to automate these things in a package that will be installed in a single click wizard into each server machine of my customers?
Thank you in advance for your time.
By default WCF doesnt allow transport of username credentials over http and hence have to use certificates to secure your transport layer. But if you are sure that you are fine with sending username credentials over the http channel then you can have a look at ClearUsernameBinding which gives you the flexibility of sending username credentials over http channel (consider the fact that someone can intercept your transport channel to get access to the credentials)
Also if you want to use certificates that have to be installed you can achieve that writing some code in c# and include that as part of your installation from your package. You can also configure everything from an msi like creating a virtual directory, deploying the application,etc..
what you are probably looking for is one of the wcf bindings that has message level security. You can put the user name and password into this message and not worry about them going across an http wire unencrypted(ie custom authentication). The defaults for WCF send user name and password as part of the http request in the header this is why it wants https.