Hello,
We have a virtual_alias_maps entry like this
handled@by.exchange handled@by.dovecot,handled@by.exchange
The problem is that the address handled@by.dovecot receives every email
sent to handled@by.exchange twice: handled@by.exchange is expanded before
amavisd is called, and also after
On 10.06.20 12:48, Jozsef Kadlecsik wrote:
handled@by.exchange handled@by.dovecot,handled@by.exchange
The problem is that the address handled@by.dovecot receives every email
sent to handled@by.exchange twice: handled@by.exchange is expanded before
amavisd is called, and also after receiving
On 10.06.20 12:48, Jozsef Kadlecsik wrote:
handled@by.exchange handled@by.dovecot,handled@by.exchange
The problem is that the address handled@by.dovecot receives every email
sent to handled@by.exchange twice: handled@by.exchange is expanded before
amavisd is called, and also after receiving
On Wed, 10 Jun 2020, Matus UHLAR - fantomas wrote:
> On 10.06.20 12:48, Jozsef Kadlecsik wrote:
> > handled@by.exchange handled@by.dovecot,handled@by.exchange
> >
> > The problem is that the address handled@by.dovecot receives every email
> > sent to handled@by.exchange twice: handled@by.exchange
Noel Jones:
> On 6/9/2020 8:46 PM, PGNet Dev wrote:
> > does dnsblog have a log map/filter/somesuch?
> >
> > or does the capability exist elsewhere in postfix?
> >
> > currently, with spamhaus dqs in the rbl/dnsbl mix, dnsblog spits out, e.g.
> >
> > /var/log/postfix/postfix.log:Jun 9 13:27
Hi Noel,
Thanks very much for your reply. For some reason, I had assumed that the
service name was dictated by convention, not the contents of /etc/services. I
DID have a nagging question about how Postfix knew to listen on 25 and 587, but
I assumed it was a system default and I had just never
On 6/9/20 5:40 AM, Marvin Renich wrote:
>> https://savannah.nongnu.org/projects/spamass-milt/
>> https://github.com/mpaperno/spampd
>> https://gitlab.com/glts/spamassassin-milter
>>
>> anyone have any current experience with any of these?
>
> I also use the first one (Debian package sp
Hi Doug,
Very much appreciate your response. In combination with Noel’s email, I think I
get what’s going on now.
All of this was, of course, in the service type section of
http://www.postfix.org/master.5.html. Once I had an idea what I was looking for
and gave it a slow re-read, it’s all th
I’ve been using my own spamassassin-milter (your third option) with
Postfix 3.3.0 for a few months and am happy with it. This project is
‘done’, the initial development phase is through, but it is active.
(I wrote about the why in these places:)
https://mail-archives.apache.org/mod_mbox/spamassass
On 10 Jun 2020, at 14:37, PGNet Dev wrote:
spampd worked well enough, when listening on tcp host:port.
listening on socket, i couldn't get past postfix permissions issues,
despite similar setup to other policy daemons in use.
that makes me a bit antsy. as does not using 'native', up-to-date
sp
On 6/10/20 2:05 PM, Bill Cole wrote:
> It uses the installed SpamAssasssin Perl modules directly, just as spamd does.
fact noted. details admittedly i'll have to poke around in.
> The socket permissions issues are probably solvable, but if running on the
> loopback interface works,
> there's no
/commit/851b525c5c09405c48b8cd697d14cb0d2edbb68b
>
> Raw patch:
>
>
> https://github.com/vdukhovni/postfix/commit/851b525c5c09405c48b8cd697d14cb0d2edbb68b.patch
>
> This applies to Postfix 3.4, 3.5 and 3.6 snapshots.
Released in postfix-3.6-20200610. Stable releases will be updated
after the code has been running for a few days.
Wietse
12 matches
Mail list logo
