Mixpost
-
@humptydumpty just to double check credentials, you can try the swaks CLI tool in the web terminal. See https://docs.cloudron.io/packaging/addons/#sendmail for an example
-
@andreasdueren said in Mixpost:
Mail server location is mail. Also shows mail in the credentials.
The mail server location is for the "external facing" domain name. So, it would be
mail.domain.com
for the external world. Themail
that you use in the env variables is the internal DNS i.e the mail container is namedmail
internally. Both these are totally different!mail
containers name will not change in the foreseeable future butmail.domain.com
could be changed by user to whatever they want. -
@humptydumpty I'm not using my Cloudron for incoming mail either. So I don't think this is an issue.
-
I'm not sure if I'm using the swaks command right. In the app's terminal, I typed
swaks
it saidTo
, I pasted the >swaks bla bla (first line), it said connection refused on port 25. Did the same for the second line and got the same result.Anyway, I think there's a mistake in the docs: https://docs.cloudron.io/packaging/addons/#sendmail where it says
CLOUDRON_MAIL_DOMAIN= # the domain name to use for email sending (i.e username@domain)
shouldn't it be mydomain.com and not username@domain? -
All this just makes it clear to me that this app needs packaging so everything Just Works, as is the Cloudron way.
-
@humptydumpty you should be able to cut and paste the command as-is and it will work. The port is not 25, it's 2525
I will fix the typo in the docs, but it's trying to say the "i.e the domain part of username@domain"
-
@humptydumpty here is my complete .env file in case there is something else in there that's useful:
Did you activateMIXPOST_FORGOT_PASSWORD=true
for example?# You app name. It is usually equal to the name of your project. APP_NAME='tld.ld' # Your application environment. If you are ready for production, set 'production' APP_ENV=production # Is used to encrypt and decrypt sensitive data. Generate it with: 'php artisan key:generate' APP_KEY=base64:yfWnd+DKiAnIPluqqzkREDlLGdqXoxibScsdyFjmIwo= # Debug mode. If the environment is in production, we recommend setting it to 'false' APP_DEBUG=false # URL of your application. Important: it is not allowed to be a slash at the end of the url. APP_URL=https://app.tld.ld APP_DOMAIN=app.tld.ld # Mysql connection setup DB_CONNECTION=mysql # Change this only if you know what you are doing DB_HOST=mysql DB_PORT=3306 DB_DATABASE="250d30918200a8b2" DB_USERNAME="250d30918200a8b2" DB_PASSWORD="06c15ecba68b9e77baf5f6ab246dff2dfd6a2676479c46a1" # Redis connection setup REDIS_HOST=redis-ef2a63d9-1366-42fe-a555-87818d6f1633 REDIS_PASSWORD=683300f802ec17947a4a1c9fbe0951c7aed452106c00c257 REDIS_PORT=6379 # Default Queue Connection Name QUEUE_CONNECTION=redis # Default Cache Store CACHE_DRIVER=redis # Default Session Driver SESSION_DRIVER=redis # Default log channel for Mixpost MIXPOST_LOG_CHANNEL=mixpost # change URL prefix "/mixpost" MIXPOST_CORE_PATH="a" # The disk on which to store added files. Disks: "public", "s3". For "s3" you should fill in the AWS_* credentials below. MIXPOST_DISK=public # AWS Credentials These are filled in but not in use. # SMTP MAIL_MAILER="smtp" MAIL_HOST="mail" MAIL_PORT="2525" MAIL_USERNAME="app@tld.ld" MAIL_PASSWORD="9b7e07a5419758685560d4741270044e4a846a1e1211b5a6" MAIL_ENCRYPTION="ssl" MAIL_FROM_ADDRESS="app@tld.ld" MAIL_FROM_NAME="${APP_NAME}" # Sentry SENTRY_LARAVEL_DSN=null MIXPOST_FORGOT_PASSWORD=true MIXPOST_TWO_FACTOR_AUTH=true MIXPOST_DEFAULT_LOCALE=de-DE
-
Thanks @andreasdueren I have a lot of missing entries compared to yours. Somehow none of these got set up on a fresh Mixpost install, but adding them didn't resolve the issue
* APP_ENV=production * APP_DOMAIN=app.tld.ld (adjusted to same value as APP_URL) * QUEUE_CONNECTION=redis * CACHE_DRIVER=redis * SESSION_DRIVER=redis * MIXPOST_FORGOT_PASSWORD=true * MIXPOST_TWO_FACTOR_AUTH=true * MIXPOST_DEFAULT_LOCALE=de-DE (adjusted to en-US)
-
@humptydumpty said in Mixpost:
Thanks @andreasdueren I have a lot of missing entries compared to yours. Somehow none of these got set up on a fresh Mixpost install, but adding them didn't resolve the issue
* APP_ENV=production * APP_DOMAIN=app.tld.ld (adjusted to same value as APP_URL) * QUEUE_CONNECTION=redis * CACHE_DRIVER=redis * SESSION_DRIVER=redis * MIXPOST_FORGOT_PASSWORD=true * MIXPOST_TWO_FACTOR_AUTH=true * MIXPOST_DEFAULT_LOCALE=de-DE (adjusted to en-US)
I remember pulling some of these off here. Sorry that didn't help.
-
@humptydumpty If you care, I can offer to take a look at your installation and compare to what I'm running to try to troubleshoot.
-
@andreasdueren I'll take you up on that if I can't figure this out after a fresh install attempt. I won't follow the guide we have on here and will follow the upstream docs this time. It's not a CR issue for sure. I have a ticket opened on Mixpost's Discord, and other non-CR users can't receive emails either.