* jk-exim via Exim-users (exim-users@exim.org) [220322 08:24]:
> So it works now for me now but I still have a feeling there is something
> wrong.
Please see /usr/share/doc/exim4-base/README.Debian.gz 'Enabling TLS
support for Exim as server' on how it is supposed to work.
You need to activate
* Julian Bradfield via Exim-users (exim-users@exim.org) [220108 16:36]:
> However, I also don't like fiddling with systems more than necessary -
> sysadmin is not my job, it's just what I have to do to make things
> work. If I have to go the trouble of building my own Debian package, I
> might as
* Julian Bradfield via Exim-users (exim-users@exim.org) [220108 15:18]:
> The pain of dealing with Debian's antiquated versions (4.92) and
> gratuitous messing around with upstream's configuration (most recent
> annoyance, not supporting built-in SPF) is prompting me to think about
> switching to
* Jeremy Harris via Exim-users (exim-users@exim.org) [210920 13:43]:
> On 18/09/2021 11:17, Andreas Barth via Exim-users wrote:
> >What would be the most appropriate way to set the envelope from
> >address in this situation
>
> Does the return_path transport option do what
Hi,
I'd like to run a filter per recipient (however filters are managed by
the admin), basically something like
filter:
driver = redirect
domains = ${if exists{CONFDIR/virtual.d/}{dsearch;CONFDIR/virtual.d}{}}
file = CONFDIR/virtual.d/$domain/$local_part
user = Debian-exim
allow_filter
