I have a server with Plesk installed.
On that I've created a domain, my-domain.com, and added and e-mail account noreply#my-domain.com with access to SMTP for sending e-mails.
With PHPMailer or Swift Mailer I am able to send via the SMTP account noreply#my-domain.com whenever the from address is outside the my-domain.com, for example info#my-second-domain.com.
Whenever I'm using an e-mail address that ends on #my-domain.com it fails.
I've tried to look in the /usr/local/psa/var/log/maillog file, but it only stores the mails that doesn't fail.
Can someone help me figure out where the problems is?
You can try this:
Delete the related domain in the qmail file /var/qmail/control/virtualdomains
Then reload/restart qmail. Now it should work.
More technical background at http://forum.parallels.com/pda/index.php/t-93222.html
Benjamin answer didn't work on my installation (Plesk 11.5), but I found another solution:
just turn off the mail service itself. It might not be the solution for everyone but it was for me (my domain's mx records pointing to another server, with some scripts sending emails here and there).
You can turn off the mail service fairly easily using Plesk GUI.
Then uncheck
However, this won't turn it off for subdomains and secondary domains you might have. No problem, just log in with ssh and run this command:
/usr/local/psa/bin/domain -u mydomain.example.com -mail_service false
And if one day you decide you want to turn it back on just replace false by true.
Related
I'm setting up the SMTP server on my keycloak instance.
I tried with my Gmail account, just to see if it works. I generated applications credentials following Google documentation. It worked nicely.
Now, I want to use the SMTP relay mode on my Google Workspace account, which has a specific domain. Google recommends. It works on other apps I have, but I could not make it work with Keycloak. There is no place to put the Domain so I don't even know if it's possible.
I searched the internet. This guy encountered my issue, but I think he solved it by doing it with applications credentials as I did in the beginning.
The thing is, I'd prefer not use application credentials because that would link my app to a Google User. I could create a dedicated one, but it would be a monthly cost. The SMTP relay solution seemed the perfect way, until I could not make it work.
Is there something I miss ? Maybe another way to use Google's SMTP server ?
Thank you for reading
Antoine
I have a problem configuring Outgoing Mail Servers.
When I click "Test Connection", I see "Connection test succeeded! Everything seems properly set up!", but when I try to create user, and I click "Send reset password instructions by email", I've got a message "Cannot send email: no outgoing email server configured. You can configure it under Settings/General Settings."
I tried with various smtp servers and I got a clue when trying gmail smtp.
Google asked me:
You can switch to an app made by Google such as Gmail to access your
account (recommended) or change your settings at
https://www.google.com/settings/security/lesssecureapps so that your
account is no longer protected by modern security standards.
When I switched off the "modern security standards" I managed to send reset password instructions, however I can't use gmail for OpenERP.
I run OpenERP on my Synology NAS and there is something that smtp servers don't like. They allow to connect, but wouldn't allow to send emails.
IP is not and issue, as I tried smtp settings from account I actually have set up in my Outlook.
I will welcome any idea to solve it.
Thanks!
I found the reason.
It makes no sense to me and I can't find the logic behind it, but this is causing the problem described.
The Company email has to be the same as ERP email servers.
this actually happens when there is not email provided for the admin user. please provide the admin user the same email address used in outgoing mail server
I had the same problem, but I solved it.
Please follow the below steps.
Go to 'My Account'
Please select the 'Connected apps & sites'
Then you will see the 'Allow less secure apps: ON' Please 'ON' that button.
Please try again to Press 'Test Connection' button.
Hope this will help you.
I have successfully set up health monitoring for logging errors on my ASP.NET web page to the Windows Event Log, a SQL Server database, and through email (Microsoft Exchange) when I specify a user name and password in the web.config file. However, if I change from specifying a user name and password to defaultCredentials="true" in web.config, I get the following error message in my Windows Event Log when it tries to generate the email:
System.Web.HttpException (0x80004005): Unable to send out an e-mail to the SMTP
server. Please ensure that the server specified in the <smtpMail> section is
valid. ---> System.Net.Mail.SmtpException: Mailbox unavailable. The server
response was: 5.7.1 Client does not have permissions to send as this sender
I am running Windows Vista on a corporate domain. My Windows login is identical to my Microsoft Exchange login. Can anyone provide some insight as to why specifying my login credentials explicitly in the web.config file works, but using defaultCredentials="true" does not? Are there any known solutions so that I can have an automated email sent through healthMonitoring without having to store my user name and password in the web.config file?
Since I earned the tumbleweed badge for this question, I doubt an answer will be of much value to anyone else; but knowing that I will inevitably fall into the same trap at a later date, I thought I would post an answer to my own question...
Authentication is not necessary for sending emails within the same domain; so instead of specifying defaultCredentials="true", I removed all fields related to authentication, and the emails began working again.
Note that this is only a partial solution. I only need to send emails to addresses within the same domain for now. Sending emails outside of this domain will not work without authentication, so if/when that is needed, it will be back to the drawing board...
I've been asked to change all of our current Joomla sites from using PHP Mail to SMTP.
The background: we were recently compromised through a vulnerable component on one of our sites. We have a dedicated server, running CPanel. The hack involved a file being uploaded to one account, which had a file manager (with access to /home, ie. all other accounts). From there, another file was uploaded that began sending emails - not enough to catch with ease, but eventually enough to get our main server IP blacklisted. Because the main IP was blacklisted, many of our other sites (for which we also host email) were also blacklisted.
My argument (your comments/ideas on this are much appreciated!)
Changing to SMTP will not solve this instance
It would solve the issue of any vulnerable components where an email can be sent via a request spoof (ie. option=com_users?task=email&..., or something similar to that)
Because the hacker has access to the files in the account, they also have access to the configuration.php file, which holds the SMTP password in plain text. Access to this means they would also have access to the SMTP server.
The SMTP that we would be using is localhost, which doesn't solve the issue of our IP being blacklisted.
My first idea was to provision/setup SMTP on a separate IP (or server), but that can still be blacklisted if a site gets hacked.
The second idea was to provision each site a unique IP, so no one site can get the rest blacklisted.
So I'm a bit lost. Before we tackle the task of setting the mailing function to SMTP, testing each site (there's roughly 70, with varying components to test) I'd like to have a better idea of what's the best route, if any.
It seems that either setting in Joomla is insecure in the event of a compromised site, no?
Find where your server is blacklisted, and apply to be removed. Note: if any of the sites require payment to be de-listed, ignore them. [eg: SORBS] Nobody cares about extortionists, trust me. I was admin for several busy mail servers for the last few years.
If you're completely switching from PHP-based mail() on all sites, then disable the mail agent on the server. mail() simply submits to the MTA running on the server [usually Sendmail or Postfix] and if your server is compromised again they will still be able to spam out.
Yes, your SMTP credentials will be stored in a config file somewhere, but most instances the intruder won't even bother to look for them. They simply drop in a basic PHP script that calls mail() and that's it.
If mail service is at all important to you you should always monitor:
The reputation of your outbound server.
The abuse mail for your domain. It will either be coming to abuse#yourdomain.com, or the abuse# contact for whoever owns the IP address block.
For the life of me i cannot get this to work. I've spent almost 4 hours on this and it just does not work. I would like to start hudson job when an e-mail is sent to a specific user. I looked and followed the info mentionned here: http://wiki.hudson-ci.org/display/HUDSON/Building+a+software+project
but still cannot get it to work.
Here is a summary of what i've done so far:
Modified /etc/aliases such that any email going to usr1 trigger the build as in
usr1: "|wget http://hudson-server/hudson/job/myjob/build"
I reconstructed the aliases db after making the above changes and sent out an e-mail to usr1 but nothing happened.
Our emails run on an exchange server. My hudson server sits on a linux box. I tried to use sendmail to do my testing and cannot get it to work. All of the above changes are done on linux. So i'm not sure if the issue here is with sendmail/exchange server or is something i'm missing.
Has anyone got this to work?
I appreciate your help here guys.
Britney
A couple of things to check:
Make sure that running wget http://hudson-server/hudson/job/myjob/build from the command line successfully starts a build. You may have problems if you have security on the server (or the job).
Make sure your exchange server is forwarding the mail for the email address in question to the mail server running on your linux box. If the mail isn't being received there, the wget command in aliases won't ever get executed.
How are you sending the email to usr1? Are you sending it from the same Linux box where the /etc/aliases is located?
To test your setup, on your Linux machine, send your email like this:
mail -s "test email to usr1" usr1#localhost
If the hudson job got executed, then your /etc/aliases setup works.
I suspect your problem could be your Linux box cannot receive emails. See if this works first before you setup the redirection in /etc/aliases. To check for incoming emails, login as usr1 and run mail at the shell prompt.