Matus UHLAR - fantomas:
I was curious if I could do a script that would do the same, with the same
possible issues.
I can do perl, but it looks neither python nor perl have interface to postfix
what could e.g. expand maps without calling external commands.
On 01.07.21 22:49, Kevin N. wrote:
Am
On 2021-07-02 07:54, Maurizio Caloro wrote:
Searching any Service that offer free any possible MX Backup?
Found kisolabs "dot" com but it seems this service are down
perfekt for testing backup mx :=)
Thanks for possible update or help
you could do self service with another postfix server w
On http://www.postfix.org/SASL_README.html
it says:
To find out what SASL implementations are compiled into Postfix, use the
following commands:
% postconf -a (SASL support in the SMTP server)
% postconf -A (SASL support in the SMTP+LMTP client)
On our RHEL 8 server, postfix 3.5.8-1, dovecot 2
Matus UHLAR - fantomas:
> >>Matus UHLAR - fantomas:
> >>>I was curious if I could do a script that would do the same, with the same
> >>>possible issues.
> >>>
> >>>I can do perl, but it looks neither python nor perl have interface to
> >>>postfix
> >>>what could e.g. expand maps without calling e
>>Matus UHLAR - fantomas:
>>>I was curious if I could do a script that would do the same, with the same
>>>possible issues.
>>>
>>>I can do perl, but it looks neither python nor perl have interface to postfix
>>>what could e.g. expand maps without calling external commands.
On 01.07.21 22:49, Kev
:-)
Maybe seems strange but...
With those settings my postfix (3.5.9) no broken connections are reported:
smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1.1
smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1.1
But when I change to those:
smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1,
White, Daniel E. (GSFC-770.0)[NICS]:
> On http://www.postfix.org/SASL_README.html
> it says:
>
> To find out what SASL implementations are compiled into Postfix, use the
> following commands:
>
> % postconf -a (SASL support in the SMTP server)
> % postconf -A (SASL support in the SMTP+LMTP clie
On Fri, Jul 02, 2021 at 03:14:58PM +0200, Marek Kozlowski wrote:
> It looks like '!TLSv1' is seen as something like
> "!TLSv1.x" ("no TLS 1.x at all") rather than "!TLSv1.0". Yes it is a stupid
> supposition but I cannot think of any other explanation. Is it possible?
No, !TLSv
On Fri, Jul 02, 2021 at 03:14:58PM +0200, Marek Kozlowski wrote:
It looks like '!TLSv1' is seen as something like
"!TLSv1.x" ("no TLS 1.x at all") rather than "!TLSv1.0". Yes it is a stupid
supposition but I cannot think of any other explanation. Is it possible?
On 02.07.21
:-)
On 7/2/21 3:56 PM, Bastian Blank wrote:
On Fri, Jul 02, 2021 at 03:14:58PM +0200, Marek Kozlowski wrote:
It looks like '!TLSv1' is seen as something like
"!TLSv1.x" ("no TLS 1.x at all") rather than "!TLSv1.0". Yes it is a stupid
supposition but I cannot think of any ot
No. The smtpd_xxx parameters are for RECEIVING email.
The LMTP protocol is for DELIVERING email.
No. That text covers RECEIVING email. LMTP is for DELVERING email.
Maybe im over stating the obvious, but i can see how there could be some
ambiguity mentioned here.
In this context saying that
% postconf -A (SASL support in the SMTP+LMTP client)
I might be wrong, but I think that part of the document is actually
referring to the LMTP protocol in general and not necesarily to
Dovecot's LMTPD server.
https://en.wikipedia.org/wiki/Local_Mail_Transfer_Protocol
Cheers,
K.
On Fri, Jul 02, 2021 at 10:15:53AM -0400, post...@ptld.com wrote:
> > No. The smtpd_xxx parameters are for RECEIVING email.
> > The LMTP protocol is for DELIVERING email.
> >
> > No. That text covers RECEIVING email. LMTP is for DELVERING email.
>
> Maybe im over stating the obvious, but i can s
:-)
I'd like to disable any mail from 'my.domain' from external networks and
non authenticated users. For envelope addresses my solution works and is
as follows:
At first bind valid addresses with their owners:
smtpd_sender_restrictions =
...
reject_sender_login_mismatch,
:-)
I'd like to disable any mail from 'my.domain' from external networks and
non authenticated users. For envelope addresses my solution works and is
as follows:
At first bind valid addresses with their owners:
Precisely:
smtpd_sender_restrictions =
check_sender_acces ...
c
I'd like to disable any mail from 'my.domain' from external networks
Do you mean this literally? Stopping me from sending an email using my
mail server that claims to be from 'your.domain'?
You can't, you can only publish SPF records and hope the receiving mail
server of the spoofed email reje
:-)
On 7/2/21 5:02 PM, post...@ptld.com wrote:
Do you mean this literally? Stopping me from sending an email using my
mail server that claims to be from 'your.domain'?
You can't, you can only publish SPF records and hope the receiving mail
server of the spoofed email rejects it based on those
OK, small clarification:
I'd like to disable any mail from 'my.domain' from external networks
and non authenticated users...
...delivered to my users.
Making sure i understand, you are saying you want to stop me from using
my mail server from sending an email to one_of_your_users@your.domain
reject_sender_login_mismatch can be setup to only allow emails being
sent out where the from, not just the envelope-from, has to match the
users login credentials
Are you sure? The documentation only mentions the MAIL FROM address.
On 2021-07-02 17:05, Marek Kozlowski wrote:
I'd like to disable any mail from 'my.domain' from external networks
and non authenticated users...
...delivered to my users.
basicly all local senders in recipient maps is forged senders on port 25
?
easy to fix :=)
with postfixadmin:
check_se
:-)
On 7/2/21 5:10 PM, post...@ptld.com wrote:
OK, small clarification:
I'd like to disable any mail from 'my.domain' from external networks
and non authenticated users...
...delivered to my users.
Making sure i understand, you are saying you want to stop me from using
my mail server from s
On 2021-07-02 17:14, Marek Kozlowski wrote:
For some reasons I'd like not to apply restrictive SPF checking. For
envelopes my simple solution works perfectly without SPF. How about
internal "from:"
milters is needed for this one
reject if from is local not signed, but this is breaked by maill
On 07-02-2021 11:13 am, Damian wrote:
reject_sender_login_mismatch can be setup to only allow emails being
sent out where the from, not just the envelope-from, has to match the
users login credentials
Are you sure? The documentation only mentions the MAIL FROM address.
I think im sure. Here
Are you sure? The documentation only mentions the MAIL FROM address.
Oops, my last reply was on SPF receiving and now i see you were talking
about sending out login mismatched.
My understanding is that it verifies the from and not just the envelope
from, but if im wrong id like to know.
On 2021-07-02 17:22, post...@ptld.com wrote:
Am i wrong and the from= is actually the envelope
from or is it checking against the from address?
this is check_policy_service not reject_sender_login_mismatch
Hi,
Recently I was confronted with an error message like:
Can't write to /var/spool/mail/BLADDDIBLA
It took me another hour or so to find out why not.
It would be helpful if the error message would read something like:
Can't wite to /var/spool/mail/BLADIBLA, mailboxsize exceeded
This would make so
Adrian van Bloois:
> Hi,
> Recently I was confronted with an error message like:
> Can't write to /var/spool/mail/BLADDDIBLA
> It took me another hour or so to find out why not.
> It would be helpful if the error message would read something like:
> Can't wite to /var/spool/mail/BLADIBLA, mailboxsi
On 2021-07-02 at 10:04:29 UTC-0400 (Fri, 2 Jul 2021 16:04:29 +0200)
Marek Kozlowski
is rumored to have said:
But on the other hand it's hard to believe than some servers with a
good reputation (according to https://talosintelligence.com) of
reputable American universities still don't support T
On 7/2/21 11:05 AM, Marek Kozlowski wrote:
> :-)
>
> On 7/2/21 5:02 PM, post...@ptld.com wrote:
>>
>> Do you mean this literally? Stopping me from sending an email using my
>> mail server that claims to be from 'your.domain'?
>> You can't, you can only publish SPF records and hope the receiving m
On 2021-07-02 at 10:46:07 UTC-0400 (Fri, 2 Jul 2021 16:46:07 +0200)
Marek Kozlowski
is rumored to have said:
:-)
I'd like to disable any mail from 'my.domain' from external networks
and non authenticated users. For envelope addresses my solution works
and is as follows:
At first bind valid
On 2021-07-02 21:37, Phil Stracchino wrote:
main.cf:
smtpd_sender_restrictions = permit_mynetworks
...
check_sender_access lmdb:/etc/postfix/sasl_authenticated
whould be check_sasl_accesss imho
check_sender_access lmdb:/etc/postfix/block-l
On 01 Jul 2021, at 23:54, Maurizio Caloro wrote:
>
> Searching any Service that offer free any possible MX Backup?
MX backups are a legacy of 30-40 years ago when it was very common to have
machines that only periodically connected to the Internet. There are many
reasons they are a bad idea i
When going to https://www.postfix.org I get, after an invalid certificate error,
> Apache Software Foundation Distribution Directory
>
> The directories linked below contain current software releases from the
> Apache Software Foundation projects. Older non-recommended releases can be
> found o
On 03/07/2021 07:48, @lbutlr wrote:
When going to https://www.postfix.org I get, after an invalid certificate
error,...
The correct address is http://www.postfix.org (no https...)
34 matches
Mail list logo
