On Thu, 2 Apr 2020 15:57:17 +0800
Stephan Chedlivili wrote:
> Is there a way to achieve that? And more generally, is that a good
> idea?
You could have a list with valid receivers and redirect the rest to your
user X with a catchall rule. Something like this (untested, partial):
table aliases
Hi,
Let' s assume I have 3 virtual users A, B and X on my domain
I want to receive mail for all of them. No problem, that's easy to set up.
But now, suppose some one (locally or non-locally) sends a mail to user
C that does not exist (nor virtual nor as a account). I want my set-up
to be
Hey,
thank you for your response. I have a question to your workaround. In
the userinfo table, did you specify every email address in there that is
a virtual address? Or did you define the user that does the LMTP deliver
to dovecot?
Also, would you mind pasting an example from your
> It is possible to use some variables in .forward files, so you can write
> a small script [...]
> Then in ~mailman/.forward, use:
>
> |/path/to/that/wrapper "%{dest.user}"
Thanks! Is there an overview of the possible variables? It doesn't seem
to be documented in the man pages.
In case anyone
Hi Leo,
the userinfo table contains all "virtual users" (respectively usernames
of dovecot imap-accounts).
See example tables:
== userinfo table
virtualuser1 1010:1010:/home/vmail
virtualuser2 1010:1010:/home/vmail
virtualuser3 1010:1010:/home/vmail
==
== virtuals table
i...@mydomain.de
Hi Leo,
Would you mind sharing your full configuration file? Without this, I am
stuck on how to help you. I have done a lot with virtual users and domains
so I think I can help. You could also see Gilles Chehade's article,
April 5, 2020 2:47 AM, "grmat" wrote:
> Hi there,
>
Hello,
> I'd like to setup GNU Mailman with OpenSMTPD. In #1040[1], poolpOrg told
> me command processing is to be done with a .forward file instead of
> aliases:
>
>> I think aliases should not support command processing at all as
Hey,
thank you for your help. I am going to describe my goal a little bit
different, maybe it gets clearer when i do.
I am trying to have a list of email accounts that OpenSMTPD recieves
emails for and sends to Dovecot via lmtp without having the email
accounts as real system accounts on
Hi all,
i have the same problem. My current workaround is to use a userbase-table:
action "inbound" lmtp 127.0.0.1:24 virtual userbase
Instead of:
action "inbound" lmtp 127.0.0.1:24 virtual user "vmail"
== userinfo table
virtualuser1 1010:1010:/home/vmail
virtualuser2
I might be misunderstanding what you are trying to achieve, but it
sounds to me that you need mail aliases.
Check the "alias" option of "action", and also the section "Aliasing
tables" in table(5).
hth
On Sun, Apr 05, 2020 at 02:24:01PM +0200, Leo Unglaub wrote:
Hey,
first of all i want to
Hey,
of course i can share my entire config. Its from a fresh start and i
keept it as simple as possible.
##
## Queue
##
queue compression
queue encryption <32 char passphrase>
##
## Tables
##
table aliases file:/etc/mail/aliases
table passwd file:/etc/mail/yace-passwd
##
## PKI
##
pki
I'm looking to dive into an LDAP setup for OpenSMTPd. Gilles says there is a
third party extension, which I presume is the Opensmtpd-extras-* packages that
no longer appear in ports.
I would just like some clarification on what I'm actually looking for, there
doesn't appear to be any other
> On Apr 5, 2020, at 08:20, Thomas Bohl wrote:
>
> Hi,
>
>> Let' s assume I have 3 virtual users A, B and X on my domain
>> I want to receive mail for all of them. No problem, that's easy to set up.
>> But now, suppose some one (locally or non-locally) sends a mail to user C
>> that does not
13 matches
Mail list logo
