Wow, that was quick. Thanks Eero, really appreciate it.
Eoin
From: Eero Volotinen
Sent: Thursday, 28 June 2018 2:44 PM
To: Eoin Kim
Cc: postfix users
Subject: Re: [Question] disable_vrfy_command
you need to set that parameter to yes, to disable vrfy command.
Eero
to 28. kesäk. 2018 klo
you need to set that parameter to yes, to disable vrfy command.
Eero
to 28. kesäk. 2018 klo 7.13 Eoin Kim kirjoitti:
> Hi all,
>
>
>
> I was reading Postfix documentation and found this configuration parameter.
>
>
>
> *disable_vrfy_command** (default: no)*
>
> Disable the SMTP VRFY command.
Hi all,
I was reading Postfix documentation and found this configuration parameter.
disable_vrfy_command (default: no)
Disable the SMTP VRFY command. This stops some techniques used to harvest email
addresses.
I am not a native English speaker so a bit confused with the sentence above.
So, if
Disable greylist on port 587 submission, and port 465 if used, in rspamd do
not greylist msa senders
On 27. jun. 2018 23.33.55 David Mehler
Jun 27 16:45:15 hostname postfix/cleanup[55220]: 136C413982:
milter-reject: END-OF-MESSAGE from
cpe-xxx-xxx-xxx-xxx..xxx.xxx.xxx[xxx.xxx.xxx.xxx]:
Hello,
I'm running Postfix 3.3.1 with rspamd as an antti-spam solution. I
started getting this error when atempting to connect remotely via my
android phone with aquamail pro as client, and do not know what it
means, any help appreciated, my postconf -n is below.
Jun 27 16:45:15 hostname
On Wed, June 27, 2018 15:55, Viktor Dukhovni wrote:
Thank you for your assistance.
>
> And you should still try to find the real cause of the
> "queue file write error" issue. The DANE bounce backlog
> was a related symptom not a cause.
>
I believe that I have uncovered that as well.
No worries. Thanks again for your help. Found some details on google.
> On 27 Jun 2018, at 22:05, Noel Jones wrote:
>
> Sorry, I don't debian.
>
> IIRC, the Debian postfix package supplies a script that is supposed
> to populate the chroot on bootup. Track down the script and run it,
> or
On 6/27/2018 3:09 PM, dur...@mgtsciences.com wrote:
>
> Where does Postfix look for mail servers to REJECT connections out
> right?
> Like Sendmail's 'access'.
Postfix uses access control maps, specified in main.cf
http://www.postfix.org/SMTPD_ACCESS_README.html
owner-postfix-us...@postfix.org wrote on 06/27/2018 02:00:42 PM:
> From: Noel Jones
> To: postfix-users@postfix.org
> Date: 06/27/2018 02:01 PM
> Subject: Re: Need to understand mynetworks_style more
> Sent by: owner-postfix-us...@postfix.org
>
> On 6/27/2018 2:44 PM, dur...@mgtsciences.com
Thank you. That clarifies it for me. I will look at those links.
Durwin
From: Noel Jones
To: postfix-users@postfix.org
Date: 06/27/2018 02:01 PM
Subject:Re: Need to understand mynetworks_style more
Sent by:owner-postfix-us...@postfix.org
On 6/27/2018 2:44 PM,
Sorry, I don't debian.
IIRC, the Debian postfix package supplies a script that is supposed
to populate the chroot on bootup. Track down the script and run it,
or ask on a debian-specific forum.
-- Noel Jones
On 6/27/2018 2:57 PM, Sophie Loewenthal wrote:
> Thanks Noel.
>
> I restarted
On 6/27/2018 2:44 PM, dur...@mgtsciences.com wrote:
> In our live system, I have firewall forwarding port 25 to mail
> server. That mail server then delivers mail to Domino server.
>
> I am testing on a VM, and I have this much configured and working
> within our LAN.
>
> I am unclear as to
Thanks Noel.
I restarted with chroot disabled and problem went away.
Unsure what’s missing in chroot: I am using postfix 3.1.8-0+deb9u1 from Debian
repos. Is there a guide to putting the missing config in?
> On 27 Jun 2018, at 21:52, Noel Jones wrote:
>
> On 6/27/2018 2:45 PM, Sophie
> On Jun 27, 2018, at 11:47 AM, James B. Byrne wrote:
>
> Last week Viktor Dukhovni reported to me that our domain had a problem
> with our DNSSEC.
For what it is worth, your DNS looks 100% clean now, the previous
"denial of existence" issues are gone:
On 6/27/2018 2:45 PM, Sophie Loewenthal wrote:
> Hi,
>
> I don’t believe my Postfix install is doing the PTR lookups, or it broke in
> some way.
>
> I have this enabled:
> # postconf |grep smtpd_peername_lookup
> smtpd_peername_lookup = yes
>
> and my DNS can resolve the name:
> # host
Hi,
I don’t believe my Postfix install is doing the PTR lookups, or it broke in
some way.
I have this enabled:
# postconf |grep smtpd_peername_lookup
smtpd_peername_lookup = yes
and my DNS can resolve the name:
# host 168.100.1.3
3.1.100.168.in-addr.arpa domain name pointer
In our live system, I have firewall forwarding port 25 to mail server.
That mail server then delivers mail to Domino server.
I am testing on a VM, and I have this much configured and working within
our LAN.
I am unclear as to delivery restrictions. The default for
mynetworks_style is subnet,
On Wed, June 27, 2018 13:49, Wietse Venema wrote:
> James B. Byrne:
>> This still does not clarify for me why the double-bounce address was
>> being reported given that the postconf reported values for notify
>> did
>> not include bounces.
>
> Asl someone else on the list noted, this was
James B. Byrne:
> This still does not clarify for me why the double-bounce address was
> being reported given that the postconf reported values for notify did
> not include bounces.
Asl someone else on the list noted, this was triggered by the
'queue file write error' condition. Postfix is quote
On Tue, Jun 26, 2018 at 02:34:19PM -0400, James B. Byrne wrote:
> When we do we frequently (always?) get messages like this in
> the mail queue:
Well, I may not have solved the problem, but I have identified what it
is and provided a work-around for now.
The issue is this:
On 2018-06-26 03:37:03 (-0400), Viktor Dukhovni wrote:
Overall, I am somewhat skeptical that the STARTTLS everywhere
approach to improving SMTP security is a good idea
For MTA<->MTA communication, there really isn't another choice. While
accepting authenticated mail on port 465 is commonly
On Tue, Jun 26, 2018 at 02:34:19PM -0400, James B. Byrne wrote:
> When we do we frequently
> (always?) get messages like this in the mail queue:
Such important mails must not lay around in the queue, but needs to be
delivered.
> In: RCPT TO:
> Out: 250
On Tue, Jun 26, 2018 at 04:47:57PM -0400, Wietse Venema wrote:
> > Out: 451 4.3.0 Error: queue file write error
> You have "notify_classes = ... bounce ..." somewhere, otherwise
> you would not receive the above SMTP session recording.
>
> Try: postconf -P | grep notify_classes
Are you sure
23 matches
Mail list logo
