| 1 |
Am Tue, 28 Mar 2017 23:24:15 -0600 |
| 2 |
schrieb thelma@×××××××××××.com: |
| 3 |
|
| 4 |
> On 03/28/2017 10:57 PM, thelma@×××××××××××.com wrote: |
| 5 |
> [snip |
| 6 |
> [...] |
| 7 |
> >> |
| 8 |
> >> "man aliases" will probably give you the answer. |
| 9 |
> >> |
| 10 |
> >> -- |
| 11 |
> >> Regards |
| 12 |
> >> wabe |
| 13 |
> > |
| 14 |
> > No, it will not! |
| 15 |
|
| 16 |
Well, actually it will. But the resulting behavior is obviously not |
| 17 |
what you wanted. Maybe you should explain better what you try to |
| 18 |
achieve. Your original request was just looking for a solution to the |
| 19 |
error message which was provided properly. You didn't say you wanted to |
| 20 |
keep the mail local. |
| 21 |
|
| 22 |
Actually you asked this: |
| 23 |
|
| 24 |
| My system mail is not going out via my system provider |
| 25 |
|
| 26 |
|
| 27 |
> > The explanation is here: |
| 28 |
> > https://www.experts-exchange.com/questions/21895287/SMTP-550-Too-many-invalid-recipients.html |
| 29 |
> > |
| 30 |
> > -- |
| 31 |
> > Thelma |
| 32 |
> |
| 33 |
> I don't run an internal mail server but was wondering is there an easy |
| 34 |
> way to configure the postfix so it will keep local mail (portage |
| 35 |
> notifications, hylafax etc) away from system provider. |
| 36 |
> My boxes are connected over VPN. |
| 37 |
> |
| 38 |
> When I was setting up a new box today, something happen to cron email |
| 39 |
> notification I started receiving bunch of emails like: |
| 40 |
> Cron <root@i5> root test -x /usr/sbin/run-crons |
| 41 |
> && /usr/sbin/run-crons |
| 42 |
> |
| 43 |
> So provide mail server block my internal system emails from passing |
| 44 |
> through their server. |
| 45 |
|
| 46 |
Still, "man aliases" is your friend. You need to provide proper aliases |
| 47 |
for "root" and "operator", maybe more. Give a local alias, e.g. your |
| 48 |
username, without "@" and without domain. |
| 49 |
|
| 50 |
Now, properly configure the LDA in postfix. Your transport |
| 51 |
configuration probably excludes local delivery and instead passes |
| 52 |
everything to the relay. I can recommend Dovecot as LDA, it will allow |
| 53 |
you to use IMAP and Sieve locally which is probably what you want |
| 54 |
anyway in your setup: |
| 55 |
|
| 56 |
https://wiki.dovecot.org/LDA/Postfix |
| 57 |
|
| 58 |
Tho, handling a full blown IMAP server for local mail is it's own |
| 59 |
beast. If you don't want to use Dovecot, you can use procmail to |
| 60 |
directly deliver to files in your $HOME: |
| 61 |
|
| 62 |
http://wiki.kartbuilding.net/index.php/Procmail_-_setup_with_postfix |
| 63 |
|
| 64 |
This requires a mail app that can work with local maildirs or mbox |
| 65 |
files. Usually every mail software can do that (tho, I'm not sure for |
| 66 |
Thunderbird). I recommend sticking to maildir as mbox can become very |
| 67 |
slow. |
| 68 |
|
| 69 |
You should get to know how postfix works. Postfix only delivers and |
| 70 |
relays mails. You need to define agents to store mails - which is what |
| 71 |
you are looking for. |
| 72 |
|
| 73 |
Also, you can use "aliases" to define processes to deliver mail: Just |
| 74 |
start an alias definition with "|" followed by a process, instead of |
| 75 |
mail addresses. |
| 76 |
|
| 77 |
Procmail supports filtering by simple rule definition, similar to |
| 78 |
sieve. Maildrop is also an alternative. |
| 79 |
|
| 80 |
Don't forget to run newaliases and maybe "postfix reload" after |
| 81 |
modifications. Changes to *.db files are usually picked up by postfix |
| 82 |
automatically, tho. |
| 83 |
|
| 84 |
-- |
| 85 |
Regards, |
| 86 |
Kai |
| 87 |
|
| 88 |
Replies to list-only preferred. |
Archives