assume the behaviour is the
same in 2.6.
(This is not a serious problem for me: the addresses that are rewritten
in my installation are in practice local addresses and it is extremely
unlikely that they will bounce. But it surprised me.)
--
Jesper Dybdal, Denmark.
http://www.dybdal.dk (in Danish).
tedly many others, very much appreciate about Postfix
- and miss in many many other software products.
--
Jesper Dybdal, Denmark.
http://www.dybdal.dk (in Danish).
On Mon, 29 Dec 2008 22:30:53 +0100, mouss wrote:
>Jesper Dybdal a écrit :
>> Since mailing list software using XVERP needs to recognize the address
>> from the envelope return path as being equal to the subscribed address,
>
>Really? AFAIK, most list managers use the From:
On Tue, 30 Dec 2008 01:10:16 +0100, I wrote:
>Since my first mail, I have tried an experiment where the rewriting of
>the sender address is done by a .forward file instead of by
>virtual_regexp; in that case, VERP actually uses the recipient address
>before it has been changed by .forward, as I wo
On Mon, 29 Dec 2008 21:54:52 +0100, I wrote:
>... I was surprised to see that when the recipient address
>provided by Mailman is rewritten by Postfix' virtual_regexp, then the
>recipient address that Postfix encodes in the envelope return path is
>the rewritten address, rather than the original su
On Fri, 2 Jan 2009 15:25:14 -0500 (EST), wie...@porcupine.org (Wietse
Venema) wrote:
>Fortunately, Postfix has original recipient
>information at hand. Unfortunately, the information is not guaranteed
>to be in the canonical u...@domain form. However, in the special
>case of VERP this is OK.
I'm
On Sat, 06 Mar 2010 22:01:14 +0100, mouss wrote:
>- OP's reverse DNS is borked:
>$ host 188.183.91.18
>18.91.183.188.in-addr.arpa domain name pointer
>0xbcb75b12.cpe.ge-1-1-0-1112.hcnqu2.customer.tele.dk.
>$ host 0xbcb75b12.cpe.ge-1-1-0-1112.hcnqu2.customer.tele.dk.
>Host 0xbcb75b12.cpe.ge-1-1-0-
mail to
be held until I am sure that the new address has a proper reverse DNS
and is not in any problematic DNSBLs. I could also just block outgoing
port 25 with a firewall rule, but using HOLD will give me better
control: I can then release individual mails if I want to.
--
Jesper Dybdal, Den
I wrote:
>Is there a simple way to put all outgoing mail (i.e., everything that
>would normally be processed by the default "smtp" instance) into the
>HOLD queue?
Thanks for the responses.
Considering the disadvantages of using the HOLD state that Noel
describes, I think I'll use Wietse's sugges
still having a milter_header_checks
parameter active for mail received by that stanza?
--
Jesper Dybdal
https://www.dybdal.dk
On 2022-03-18 13:07, Matus UHLAR - fantomas wrote:
On 18.03.22 12:35, Jesper Dybdal wrote:
I run postfix 3.4.14 (Debian Buster) with Amavisd-new as a pre-queue
filter.
I would now like to add DMARC validation, done by the opendmarc
milter in the after-Amavis smtpd instance.
This
better if it also supported PREPEND.)
And thanks to Matus and PGNet Dev for interesting suggestions of
alternative solutions that I may need if my requirements change.
--
Jesper Dybdal
https://www.dybdal.dk
have p=reject in their DMARC policy but still send mail that does not
pass DMARC - in some cases even with neither SPF nor DKIM. I'm
beginning to fear that it will be a while before DMARC can be really
useful...)
--
Jesper Dybdal
https://www.dybdal.dk
Versions, all from Debian 10.12 (Buster): postfix 3.4.14,
amavisd-new-2.11.0 (20160426), opendmarc 1.3.2.
Thanks,
Jesper
--
Jesper Dybdal
https://www.dybdal.dk
On 2022-04-08 16:22, Wietse Venema wrote:
Jesper Dybdal:
I run Amavis as a before-queue filter, and opendmarc in the after-Amavis
smtpd instance.
Why not use Amavis as a before-queue MILTER? Then there is no need
to propagate remote SMTP client info through non-Postfix programs.
That might
headers) made by a
policy service?
--
Jesper Dybdal
https://www.dybdal.dk
mine, but I might have overlooked something.
(For unauthenticated mail from the outside, it will be a pre-queue
amavisd-milter setup.)
Thanks,
Jesper
--
Jesper Dybdal
https://www.dybdal.dk
On 2022-04-13 15:24, Wietse Venema wrote:
Jesper Dybdal:
I use amavisd-new for the smtpd instances that receive authenticated
submission.
Are there any significant pros and cons in doing this as a pre-queue
filter (proxy) compared to doing it as a post-queue content filter?
Doing what as a
On 2022-04-13 16:06, Dominic Raferd wrote:
On 13/04/2022 13:29, Jesper Dybdal wrote:
I use amavisd-new for the smtpd instances that receive authenticated
submission.
Are there any significant pros and cons in doing this as a pre-queue
filter (proxy) compared to doing it as a post-queue content
On 2022-04-08 16:22, Wietse Venema wrote:
Jesper Dybdal:
I run Amavis as a before-queue filter, and opendmarc in the after-Amavis
smtpd instance.
Why not use Amavis as a before-queue MILTER? Then there is no need
to propagate remote SMTP client info through non-Postfix programs.
Thanks for the
.0.1:10029,inet:127.0.0.1:10030
--
Jesper Dybdal
https://www.dybdal.dk
On 2022-11-05 11:57, Paul Kudla wrote:
...
# nslookup 10.220.0.6
6.0.220.10.in-addr.arpa name = syslog-local.scom.ca.
...
Name: syslog-local.scom.ca
Address: 10.228.0.6
Ought that 228 not to be 220?
--
Jesper Dybdal
https://www.dybdal.dk
ail(1) submission.
Or perhaps I've overlooked some good reason why it would be a bad idea
to control sendmail(1) submission in such detail?
--
Jesper Dybdal
https://www.dybdal.dk
On 2023-01-01 19:54, Wietse Venema wrote:
Viktor Dukhovni:
On Sun, Jan 01, 2023 at 05:03:27PM +0100, Jesper Dybdal wrote:
...
(I seem to remember that there was a thread here about a similar subject
some time ago, but I can't find it now.)
Did you mean https://www.postfix.org/postc
somebody can tell me what is going on
- and what opendmarc means with that error message.
--
Jesper Dybdal
https://www.dybdal.dk
ck all possible case.
An alternative solution might be to use the milter variant of amsvis:
policyd-spf, amavis-milter (doing DKIM), openDMARC milter. Would that
work? (I hesitate to do major changes, since this is a production system.)
Any help would be greatly appreciated.
--
Jesper Dybdal
https://www.dybdal.dk
im. I
just prefer the way it handles it.
Yes, I also like the Amavis DKIM-setup, and would prefer to keep it.
--
Jesper Dybdal
https://www.dybdal.dk
pport metacpan Mail::DMARC
with imho could help simplify it very much
Yes - if Amavis could do DMARC check, that would be a very nice solution.
--
Jesper Dybdal
https://www.dybdal.dk
en a trouble-free success.
And with the excellent documentation and the excellent support provided
here, Postfix is a true model of high quality software.
Thanks!
--
Jesper Dybdal
http://www.dybdal.dk
makes no connection to port 10030.
I normally have an iptables rule that allows only user "amavis" to
connect to port 10030, but I've tried removing that restriction and that
did not help.
Have I completely misunderstood something?
--
Jesper Dybdal
http://www.dybdal.dk
I always helps to ask for help - you then immediately see what you've
missed. I've suddenly seen the word "no_milters" in my mail below,
which probably explains the problem.
I expect it will help to remove that word - sorry for the inconvenience.
Jesper
On 2017-11-26
not warn me about this problem.
Jesper Dybdal
--
Jesper Dybdal
http://www.dybdal.dk
time I
increment compatibility_level.
--
Jesper Dybdal
http://www.dybdal.dk
hanged with the file permissions and there is lots of room on the disk.
Postfix 3.1.12 (Debian Stretch).
A slightly edited session transcript is shown below.
Thanks,
Jesper Dybdal
Transcript of session follows.
Out: 220 nuser.dybdal.dk ESMTP Postfix (Debian/GNU)
In: EHLO mail-oi1-f178.g
On 2019-09-17 13:02, Wietse Venema wrote:
Jesper Dybdal:
Can "Error: queue file write error" mean anything other than a problem
with the queue file?
Yes. LOOK IN THE LOGS. Postfix will not reveal internal error details
in its responses to random SMTP clients.
You're right
ers = check_sender_access
regexp:/etc/postfix/regexp_spamblock_senders
unknown_address_reject_code = 550
virtual_alias_domains = regexp:/etc/postfix/virtual_regexp
virtual_alias_maps = regexp:/etc/postfix/virtual_regexp
root@nuser:~#
--
Jesper Dybdal
http://www.dybdal.dk
On 2019-09-23 22:04, Viktor Dukhovni wrote:
As documented in transport(5), when a transport table entry does not
specify an explicit nexthop, it uses the extant (default) nexthop
for the recipient. In your case that's specified via "relayhost".
Of course! Thank you very m
ocess?
Will I get the desired effect if I ensure that
_destination_concurrency_limit for the post-queue amavis smtp plus the
process limit for the port 25 smtpd does not exceed the number of amavis
processes?
Thanks,
Jesper
--
Jesper Dybdal
https://www.dybd
somehow make Debian not copy
/etc/resolv.conf into the chroot jail.
Thanks,
Jesper
--
Jesper Dybdal
https://www.dybdal.dk
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
On 2023-11-05 15:41, Matus UHLAR - fantomas via Postfix-users wrote:
Jesper Dybdal via Postfix-users skrev den 2023-11-05 13:48:
To avoid using a public name server for DNSBL lookups, I would like
the DNSBL checks to be done using only the name server running on
localhost.
But I would like the
On 2023-11-05 17:51, Wietse Venema via Postfix-users wrote:
Jesper Dybdal via Postfix-users:
To avoid using a public name server for DNSBL lookups, I would like the
DNSBL checks to be done using only the name server running on localhost.
But I would like the rest of the system to have for
and support of the highest quality.
Among all the many excellent aspects of Postfix, I would like to
especially mention the care taken to ensure backwards compatibility.
I've never had to fear breaking things by upgrading Postfix, and I
appreciate that very much.
--
Jesper Dybdal
h
"local_login_sender_maps" looks up a username
to find allowed addresses, while "smtpd_sender_login_maps" looks up an
address to find users that may use that address. I have no doubt that
there is a good reason, but it escapes me for the moment - and I am curious.
Thanks,
Jesper
-
43 matches
Mail list logo
