-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use? #8
Comments
You can use it as usual SMTP server if you program can send emails directly to SMTP server. For sending mails from command line and for old programs that calls Any of sendmail, postfix or exim will provide Then you can use config
And test configuration with |
Awesome, got it working with ssmtp! The two snags I had were figuring out
the rules array in the yaml was required, so I created a catch all rule.
And the second was figuring out slacks confusing interface for creating an
API key. (And scopes)
…On Tue, Jun 2, 2020, 12:35 PM ont ***@***.***> wrote:
You can use it as usual SMTP server if you program can send emails
directly to SMTP server.
For sending mails from command line and for old programs that calls
/usr/bin/sendmail you must install one of the MTA (mail transfer agent).
Any of sendmail, postfix or exim will provide /usr/bin/sendmail command.
but if you only need to redirect all emails to the slacker, then just
install ssmtp.
Then you can use config /etc/ssmtp/ssmtp.conf that looks like this:
root=postmaster
mailhub=localhost:8025
hostname=localhost.localdomain
And test configuration with sendmail -s "Test subject" ***@***.*** <
test.txt
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHQ6OVE3VSB6GPYJZS6UTRUUS37ANCNFSM4NQ23KOQ>
.
|
Actually, a little help on the rule. How do I create a catch all rule? I want every single message sent through the server, regardless of where it comes from, to be pushed to slack. I tried changing the from to |
@Sparticuz can you post error message of the crash and config? |
I tried from: * as well as |
Oh, you probably use this form in config: rules:
- name: Catch them all
from: *@* Yes, this will not work. Values in yaml must start with alphanumeric values. You must surround value with quotes: Correct "catch them all" rule must be: rules:
- name: "Catch them all"
from: ".*" |
Great, It looks like I'm getting some messages. (Sorry it's taken so long, working on this on the side). Some of my messages are coming through odd though. What's this? |
It is probably multipart email message with additional content. For example some email has two variants: |
Can you please provide a bit more details on how to make it work ? I have a running container, and it is open and working
I installed ssmtp, and configured it exactly as per above (which is : ) /etc/ssmtp/ssmtp.conf looks like this:
when I run Is there anything else I need to do , |
@hycday you probably have
|
I indeed forgot to comment out that line, so now I only have the 3 lines from my previous post
and test.txt has the following:
I get
|
Very strange. Do you have any logs from server in docker container? |
this is what i have with
so i guess it comes from my config.yml... I am not sure i got the slack_token correctly |
Nevermind... just did it all works perfectly well. Once you create your slack workspace go to https://api.slack.com/ |
I've got the image up and running on docker, but do you have instructions on how to use it? What's the best program to install to take advantage of this smtp server? Thanks!
The text was updated successfully, but these errors were encountered: