After installing Postfix on my Ubuntu server and getting my Symfony application running, I'm attempting to have the system send emails via Postfix. I tested it out in the terminal to make sure that it sends properly and it does, but I'm confused as to what the Symfony configurations are to have SwiftMailer send email through Postfix.
In the .env file, there is a MAILER_URL attribute. What do I input there? My hostname? One of the destinations? Something else entirely? Help would be appreciated.
Related
I have a site in digitalocean hosting and I have some problems sending email from this site.
My site built at wordpress and I'm trying to submit an application to email. It worked on my localhost and my on my server https://cp.beget.com/ but as soon as I transferred it on https://www.digitalocean.com/ it immediately stopped working.
I have a small php script for send emails and it works correctly also I tried change admin email in main wp settings but I havу not received confirm letter on my email.
Server using ubuntu and i set everything up on it for email send and tested this through postfix and it worked correctly.
Maybe someone had this problem and know how it fix
It is better to use SMTP instead of relying php's sendmail which may get blocked on some hosting companies.
You can use the Post SMTP Mailer plugin to overcome this problem.
Just create a new email account at digitalocean and use its smtp server as the outgoing server address at the SMTP plugin. Usually it will be mail.yourdomain.com. Outgoing port can be 25 or 587.
I use Symfony and SwiftMailer as post manager. I can send post using console command, but when I send using browser client the post is not sent and there is nothing in log files. What can be the reason of such strange behavior?
CLI - Command Line Interface
CGI - Common Gateway Interface
You probably mean CGI php that deals with browser routine.
I faced the same problem using nginx. Swiftmailer refuse to send any e-mails triggered by CGI PHP, but nevertheless it successfully sends e-mails by swiftmailer:email:send command in console.
I found that the cause of this problem is function stream_socket_client in disabled_functions of my nginx config. Just remove stream_socket_client from disabled functions, reboot your server and try again, it should help.
I use cyberduck for SFTP my website files to the server. Dreamhost is the server.
In setting up a new bookmark in cyberduck I received this error "Connection failed - EOF while reading packet." [end of file]
The website is up and working fine, http://ce-t.org
Initially I thought this error had to do with the connection opening with cyberduck. So I setup a different bookmark to test and was able to do without a problem.
I have also deleted my first attempt to setup and reset up. This did not alter anything.
Now after doing more reading, may be in one of the website files?
As you can see i am a novice.
Help appreciated.
Usually when I run into this issue, its because my pw has expired.
Try SSHing into the server and change/update your pw. After I change it, I can FTP in.
This is 3 years too late for the OP. But I had this error when trying to make an SFTP connection to hosting on a Plesk server and the solution was to:
Enable the 'Access to the server over SSH' setting for the ftp user via the Plesk Control panel.
Of course you might need to contact your hosting service to get this done if you are not managing your own server.
In my case the same error occurred due to a syntax error in the .bashrc file on the remote server.
Also note that the default account setting for an FTP user at Dreamhost might specify an FTP connection. If so, trying to use Cyberduck to connect via SFTP will generate this error message. You can use the Dreamhost control panel to edit the user's record to specify SFTP.
In my case I have used dropbear ssh server.
I replace this server with openssh server, and now i can open the sftp connection without any issues.
I followed the instructions at https://developers.google.com/compute/docs/sending-mail to setup postfix to send via sendgrid. I believe I have it all setup correctly, but mail is failing. The bounce is not very helpful other than status: 5.0.0 and Action: failed.
Any ideas?
As a wild guess, you might not have run postmap from step 5, or reloaded postfix after updating your /etc/postfix/main.cf. Can you post the log messages from postfix from /var/log/syslog along with your postfix main.cf?
One other question: are you running on Debian, CentOS or something else? I think that the SendGrid instructions you linked to assume Debian, and file locations may be different in CentOS.
I've run into an issue configuring a Yum repository which I'm serving up with HTTP/Apache.
I want to use http basic authentication, and set the listening port to something other than 80, because this repo is in my DMZ. I was trying to do that by setting up my baseurl as follows (from my repo file):
baseurl=http://user:password#<my-ip>:<my-non-80-port>/yum/RHEL/7/base/$basearch/
The documentation for yum.conf indicates you can do basic http authentication by adding the username/password to the URL as I did above. I get the following error when I try to do a yum search mysql from a client:
[Errno 14] HTTP Error 401: Authorization Required
This indicated to me that the extra ":" specifying the port was confusing yum's parsing of my url. I removed the port, set the server back to port 80, and it works.
So it appears you cannot do basic http authentication AND change the port number that the web server listens on. I noticed that there are username and password directives in newer version of Yum, but my version doesn't appear to have this directives (I am running yum-3.2.22-37.0.1.el5). Is there any workaround for this?
I worked around this by turning off plugins by adding the following line to my yum configuration.
plugins=0
I think the workaround worked because the base yum updater was working fine with the authorization information from baseurl, but some of the plugins (such as the fastmirror plugin) didn't remember the authorization properly. So the behaviour I had without plugins enabled is that initially an update would work, then subsequently it would start to fail with the authorization error in the question. Once I disabled plugins, everything started to work fine.