I have a problem with postfix + mailman3. Mailman creates the necessary aliases
of the mailing lists and they are added as follows in postfix:
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
owner_request_special = no
transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp
use external service
El 13/1/2022 a las 15:44, Benny Pedersen escribió:
On 2022-01-13 15:37, Francesc Peñalvez wrote:
I have a postfix server both inbound and outbound in my own home, that
is, my isp does not block traffic on port 25, it blocks it on 53
perfect, so basicly your isp is
I have a postfix server both inbound and outbound in my own home, that
is, my isp does not block traffic on port 25, it blocks it on 53
El 13/1/2022 a las 15:24, Benny Pedersen escribió:
On 2022-01-13 04:00, Yamadaえりな wrote:
Hello list,
I have got a DSL from the ISP, having a static IP.
Can I
I had soft_bounce = yes. Thanks
El 24/9/2021 a las 13:59, Wietse Venema escribió:
> Wietse Venema:
>> Francesc Pe?alvez:
>>> I re-ask again since my postscreen responds to connections with dnsbl
>>> code 450 instead of a 5xx, with which those servers are trying to resend
>>> the mail again and aga
postscreen_dnsbl_whitelist_threshold = -1
postscreen_dnsbl_ttl = 10m
cat /etc/postfix/postscreen_dnsbl_reply
# Secret DNSBL name Name in postscreen(8) replies
El 8/6/2021 a las 14:42, Francesc Peñalvez escribió:
> The question may have been answered, but I don't see it. Is there a way
> to
Thanks Wietse
El 8/6/2021 a les 15:18, Wietse Venema ha escrit:
> Francesc Pe?alvez:
>> The question may have been answered, but I don't see it. Is there a way
>> to change the 4xx error from postscreen to error 5xx so that it doesn't
>> retry to send the mail blocked by dnsbl
> There is no '4xx'
The question may have been answered, but I don't see it. Is there a way
to change the 4xx error from postscreen to error 5xx so that it doesn't
retry to send the mail blocked by dnsbl
smime.p7s
Description: Signatura criptogràfica S/MIME
1 (in main.cf)
Yassine.
Le 4/18/21 à 2:13 PM, Yassine Chaouche a écrit :
Le 4/18/21 à 12:21 PM, Francesc Peñalvez a écrit :
I can only see TO connections but not FROM connections and I would
like to see both
Can you show us how your logs look like when you make
a TLS connection to your s
I can only see TO connections but not FROM connections and I would like
to see both
El 18/04/2021 a las 12:59, Jaroslaw Rafa escribió:
Dnia 18.04.2021 o godz. 12:44:41 Francesc Peñalvez pisze:
I have postfix configured to log outgoing tls connections:
Untrusted TLS connection established to
I have postfix configured to log outgoing tls connections:
Untrusted TLS connection established to smtp-mx.x
but is it possible to log in the same way the incoming connections?
smime.p7s
Description: Firma criptográfica S/MIME
Is it possible to identify which password smtp is trying to use? if so I
would like to know how
El 17/04/2021 a las 14:13, Wietse Venema escribió:
li...@lazygranch.com:
I am getting a lot of these:
Apr 17 07:27:10 mydomain postfix/smtpd[21897]: connect from
mone183.secundiarourous.com[141.98
there is a space of more entity unix: and private, remove it. should be
unix:private/clamav/clamav-milter.ctl
El 30/03/2021 a las 17:32, Francesc Peñalvez escribió:
do you have the postfix with chroot? if you have it, the path in
main.cf should be unix: private/clamav/clamav-milter.ctl
El 30
-Ursprüngliche Nachricht-
Von: Francesc Peñalvez
Gesendet: Sonntag, 28. März 2021 12:25
An: mauri...@caloro.ch; postfix-users@postfix.org
Betreff: Re: AW: Postfix - ClamAvMilter refused
If you have deleted that line then you want to do it by sockets with
which in the main.cf of postfix it
357
telnet: Unable to connect to remote host: Connection refused
-Ursprüngliche Nachricht-
Von: owner-postfix-us...@postfix.org Im
Auftrag von Francesc Peñalvez
Gesendet: Sonntag, 28. März 2021 11:34
An: postfix-users@postfix.org
Betreff: Re: Postfix - ClamAvMilter refused
At a first glance
At a first glance, I see that you have ClamdSocket configured 2 times,
one per socket and one per tcp, delete the one you do not want to
execute and restart, to check if it is listening on the correct port you
can run netstat -tupan | grep 7357
El 28/03/2021 a las 11:26, Maurizio Caloro escrib
thanks Viktor
El 28/03/2021 a las 1:21, Viktor Dukhovni escribió:
On Sun, Mar 28, 2021 at 01:08:44AM +0100, Francesc Peñalvez wrote:
Right now dnssec is activated in the external manager zoneedit.com, in
which I cannot modify the type of encryption or the length of the key.
If there are no
01:59:56PM +0100, Francesc Peñalvez wrote:
I have a connection of the domestic type, with 7 computers in an
internal network, in which I do not have access to make any changes to
the ip. I use external dns service to manage the bind9 service,
although I have another installed and running locally
escribió:
On Sat, Mar 27, 2021 at 12:51:36PM +0100, Francesc Peñalvez wrote:
I have the dns of the domain managed externally, configured with
dnssec, and another host running postfix. How could I integrate that
postfix use the dnssec configuration? Would it be enough to add the
dns of the external
I have the dns of the domain managed externally, configured with dnssec,
and another host running postfix. How could I integrate that postfix use
the dnssec configuration? Would it be enough to add the dns of the
external service to the postfix resolv.conf?
--
smime.p7s
Description: Firma cr
:58 PM Francesc Peñalvez
<naz...@almogavers.net> wrote:
I was looking in the
postfix manual for the waiting parameter by which
an email is tried to send after receiving a 4xx code. I am
interested in
I was looking in the postfix manual for the waiting parameter by which
an email is tried to send after receiving a 4xx code. I am interested in
adapting it correctly for the servers that use postgrey,but i dont find
it or i dont understand it
--
smime.p7s
Description: Firma criptográfica S
Thanks Wietse
El 08/11/2020 a las 21:31, Wietse Venema escribió:
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.5.8.html]
Fixed in Postfix version 3.5.8:
* [Postfix 3.5 and later] The Postfix SMTP client inserted
into messa
n/opendmarc
>>Restart=on-failure
>>ExecReload=/bin/kill -USR1 $MAINPID
---
*Von:*owner-postfix-us...@postfix.org
*Im Auftrag von *Francesc Peñalvez
*Gesendet:* Samstag, 16. Mai 2020 11:56
*An:* postfix-users@postfix.org
*Betreff:* Re: Permission failed opendkim.sock
in the /lib/systemd/
in the /lib/systemd/system/opendmarc.service file add Group = postfix
under User =
that will correctly create the sock with correct permissions
El 16/05/2020 a las 11:35, mauri...@caloro.ch escribió:
Hello
Here i’am running with Debian Stretch and i have a littel undestanding
mismatch, pleas
I don't have the correct dkim entry in the domain?
El 26/4/2020 a les 13:18, Christian ha escrit:
Sorry if this has been tested before, but I joined the list only
lately.
Have you tried the google postmaster-tools for postfix.org and
especially adding the google-site-verification TXT?
Am Sonnt
Surely, but it has coincided just with the new version and above with a
test of mtpolicytd I no longer knew what to think. Thanks to those who
have answered
El 25/4/2020 a les 15:37, Wietse Venema ha escrit:
Francesc Pe?alvez:
For days, 4 specifically, I have only received 2 emails from the P
For days, 4 specifically, I have only received 2 emails from the Postfix
list. Is there a problem?
Url is broken
El 22/09/2019 a las 16:47, Wietse Venema escribió:
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.4.7.html]
Fixed in Postfix 3.4:
* Robustness: the tlsproxy(8) daemon could go into a loop, logging
a flood of er
:/etc/postfix/access
On 4/2/2019 1:49 PM, Francesc Peñalvez wrote:
the problem that I have already described
I have several rules against spamers and one of them is to reject the
ips that are not resolved.
So when the resolution of the dns fails those ips are rejected for
not having an
Jones escribió:
On 4/2/2019 12:15 PM, Francesc Peñalvez wrote:
the problem is with the directive
reject_unknown_reverse_client_hostname when there is a failure in the
resolution of the ip blocks the connection with this ip, to avoid
adding the access file the ip as indicated in the first mail, but
the ip of my last mail does not match the first, but it is from the same
company that uses several ips and all of them are added to the access file
El 02/04/2019 a las 19:15, Francesc Peñalvez escribió:
the problem is with the directive
reject_unknown_reverse_client_hostname when there is a
the problem is with the directive reject_unknown_reverse_client_hostname
when there is a failure in the resolution of the ip blocks the
connection with this ip, to avoid adding the access file the ip as
indicated in the first mail, but still blocking that ip by not
resolving. activate the debug
following the instructions given to me place the access in front of the
rule that is not supported ips unresolved, and as I still have the same
problems I added a debug to that ip that interests me and among other
things in this debug I find this:
16:43:05 ns postfix / smtpd [28258]: generic_che
u can check dnsbl list here https://hetrixtools.com/blacklist-check/
El 17/03/2019 a las 20:10, Johannes Bauer escribió:
Hi Wesley,
On 17.03.19 13:44, Czarek wrote:
Check if you are not an open relay. Configure SPF, DKIM, DMARC
and Reverse DNS.
Except for DMARC I have all of the above.
Th
thank you I had not thought that postfix followed the order of the list
El 15/03/2019 a las 20:45, Matus UHLAR - fantomas escribió:
On 15.03.19 20:37, Francesc Peñalvez wrote:
I have this directive active reject_unknown_client_hostname and in some
ips when it does not solve at the moment of
I have this directive active reject_unknown_client_hostname and in some
ips when it does not solve at the moment of doing the RCPT it does not
solve correctly, as it is logical send code 450 blocking the mail. Well
my question is how could I put some ips in particular that I know are
reliable for
The correct way is this i think
make makefiles CCARGS="-DUSE_TLS -DUSE_SASL_AUTH -DUSE_CYRUS_SASL \
-I/usr/include/sasl" AUXLIBS="-L/usr/lib -lsasl2 -lssl -lcrypto"
El 13/03/2019 a las 18:08, Francesc Peñalvez escribió:
is this correct
make makefiles CCA
is this correct
make makefiles CCARGS="-DUSE_SASL_AUTH -DUSE_CYRUS_SASL \
-I/usr/include/sasl" AUXLIBS="-L/usr/lib -lsasl2 -lssl -lcrypto"
i compile with this options but when mail arriving i get this in log
warning: TLS has been selected, but TLS support is not compiled in
smime.p7s
Sorry its my firm,i erease when send mail to this list
smime.p7s
Description: Firma criptográfica S/MIME
sure i use it thanks!!
the question of whether there is a simple way to make a deb package, is
that I have a somewhat complicated configuration and I would not like to
lose it or run two postfix one in the local directory and the deb
package in normal sbin, so I asked if there is some simple w
or disseminated without authorization.
***
El 11/03/2019 a las 0:21, Francesc Peñalvez escribió:
there is an error in that web if i choose the link of wietse own site
the link download is this
ftp
there is an error in that web if i choose the link of wietse own site
the link download is this
ftp://ftp.porcupine.org/mirrors/postfix-release/index.html
*
Este mensaje y todos los archivos adjuntos
when will this version be published? on the web is not yet the source or
the change list
*
Este mensaje y todos los archivos adjuntos son confidenciales y de uso
exclusivo por parte
de su/sus destina
thanks i had permit and dont work noi use PERMIT and work corretly
*
Este mensaje y todos los archivos adjuntos son confidenciales y de uso
exclusivo por parte
de su/sus destinatario/s. Si usted ha re
/03/2019 a las 11:03, Francesc Peñalvez escribió:
i use postscreen
postscreen_dnsbl_sites = cbl.abuseat.org=127.0.0.2*3
b.barracudacentral.org=127.0.0.2*3 bl.spamcop.net=127.0.0.2*2
hostkarma.junkemailfilter.com=127.0.0.2*2
hostkarma.junkemailfilter.com=127.0.0.4*1
dnsbl.sorbs.net=127.0.0
even edited or disseminated without authorization.
***
El 04/03/2019 a las 10:59, Matus UHLAR - fantomas escribió:
On 04.03.19 10:55, Francesc Peñalvez wrote:
Subject: Is there any way to add whitelist to rang
Gmail has its ips stuck in almost all dnsbl spam and for that reason I
do not receive any mail from gmail, I see the rebounds that postfix
sends to the administration mail according to the failures of those ips,
but no mail arrives from that domain
--
**
Add smtpd_sender_restrictions =
permit_mynetworks
check_client_access cidr: /etc/postfix/trusted_ips.cidr
permit_sasl_authenticated
check_sender_access inline: {
{almogavers.net = Local REJECT sender from unauthorized
client}
}
This seeme
I asked the same and Vietse Venema answer this:
Postfix 3.0 and later:
/etc/postfix/main.cf:
smtpd_sender_restrictions =
permit_mynetworks
permit_sasl_authenticated
check_sender_access inline:{
{ example.com = REJECT local sender from unauthorized
c
you can use this Google APP https://postmaster.google.com/managedomains
also you can use DKIM and or SPF verification
*
Este mensaje y todos los archivos adjuntos son confidenciales y de uso
exclusiv
exception to the rule reject_unknown_client_hostname since having it
active there are some ips that if they have inverse blocks me emails,
could you put some type of exception to certain ips that I really know
so that I do not block their mails?
--
*
El 29/11/2018 a las 9:34, Matus UHLAR - fantomas escribió:
On 29.11.18 09:09, Francesc Peñalvez wrote:
it may be a silly question but.Which option is appropriate to reject
emails from ip without ip resolved
you apparently mean "reject_unknown_client_hostname" in
smtpd_*_re
it may be a silly question but.Which option is appropriate to reject
emails from ip without ip resolved
--
*
Este mensaje y todos los archivos adjuntos son confidenciales y de uso
exclusivo por parte
El 16/11/2018 a las 15:41, Wietse Venema escribió:
Francesc Pe?alvez:
Lately we are receiving spam mails that apparently the mail from the and
the to is the same. How is it possible to avoid this?. I have configured
postfix to avoid the relay of emails and to be able to send mail through
my post
Lately we are receiving spam mails that apparently the mail from the and
the to is the same. How is it possible to avoid this?. I have configured
postfix to avoid the relay of emails and to be able to send mail through
my postfix is necessary the auth , these emails are sent externally from
sev
El 27/09/2018 a las 1:50, Francesc Peñalvez escribió:
El 27/09/2018 a las 1:19, Wietse Venema escribió:
Francesc Pe?alvez:
There are some ips that when wanting to connect with my postfix it is
impossible to do so when connecting in the same second they disconnect
without sending any data
for
El 27/09/2018 a las 1:19, Wietse Venema escribió:
Francesc Pe?alvez:
There are some ips that when wanting to connect with my postfix it is
impossible to do so when connecting in the same second they disconnect
without sending any data
for example:
Sep 26 21:20:47 ns postfix / smtpd [4679]: conn
There are some ips that when wanting to connect with my postfix it is
impossible to do so when connecting in the same second they disconnect
without sending any data
for example:
Sep 26 21:20:47 ns postfix / smtpd [4679]: connect from
mail2.segurcaixaadeslas.es [195.77.158.25]
Sep 26 21:20:47
I ve the last postfix server with tls and sasl.I find that from some ips
also with postfix servers do not get to connect properly.the syslog only i
see this:
Jun 14 12:02:10 ns postfix/smtpd[23322]: connect from x.x.x.x.x[x.x.x.x]
Jun 14 12:02:11 ns postfix/smtpd[23322]: disconnect from x.x.x.x.
59 matches
Mail list logo
