On 02/19/2016 08:05 PM, Sebastian Nielsen wrote:
>
> Yeah, I agree that actually, only 644 is required on that config
> file. But why get so angry when someone 666's a file to just get
> things working? Its not like a list of banned spam domains is
> something super-sensitive.
>
Maybe this makes
Everytime I need multiple processes to access the very same file and those
processes has interlocks that prevent them from running as the same user or
same group, I just "fix" the problem with 666.
That is a thing I ONLY do if I get a permission error when trying to do
something I want to do wi
> On 19 Feb 2016, at 23:52, Sebastian Nielsen wrote:
>
> but if you're hosting for example a mail server for a company, and only you
> as a sysadmin has shell access to the server, its no danger 666'ing files
> that throw permission errors. Then the file isn't really "world writable",
> since
On Sat, Feb 20, 2016 at 12:53:29AM +0200, Andreas Krischer - akbyte wrote:
So my question is: is their any possibility that postfix can detect
forwarding loops and just stop them? No matter on all the LDAP stuff,
shouldn't postfix be intelligent enough to detect if forwarding source
and destinati
On 02/19/2016 06:52 PM, Sebastian Nielsen wrote:
>
> 2: Its just a habit, everytime some process complains of not able to
> access a file, "666" is the universal solution. Of course, this isn't
> recommended in a web hosting setup, but if you're hosting for example
> a mail server for a company, a
Reid Sutherland:
[ Charset ISO-8859-1 converted... ]
> Wietse Venema wrote:
> >>> I don't think that it is a good idea to fill up your machine with
> >>> programs that keep timing out again and again and again. Postfix
> >>> is not only about performance and security, but also about safety
> >>> (m
Actually I have a xyz domain that mirrors my com domain. I use it for test
purposes.
Sent from my BlackBerry 10 smartphone.
Original Message
From: Sebastian Nielsen
Sent: Friday, February 19, 2016 3:53 PM
To: postfix-users@postfix.org
Subject: SV: SV: Blocking TLDs
1: REJECT tells the spamm
1: REJECT tells the spammer "Hey, your spam got stuck in the spam filter. Wanna
try again?".
Better to DISCARD it so the spammer think they got the spam through, then they
won't switch to a new domain.
I don't think anyone ever will receive legitimate mail from any of those spammy
TLDs listed i
Followed this additional annotation and looks like everything is working here
as it should. Thanks to all who gave me the information I needed.
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of A. Schulze
Sent: Friday, Februar
Noted. Thank you muchly for this information :) Filed away for future use :)
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of A. Schulze
Sent: Friday, February 19, 2016 4:52 PM
To: postfix-users@postfix.org
Subject: Re: SV: B
Hello dear postfix user!
I already asked on the German postfix-users-lists but nobody answered
there, so I hope, someone of you can help us :)
We have in a relatively large organization the following LDAP-Setup:
ou=users,dc=domain,dc=de contains all users with their attributes. We
use the `mail`
Sebastian Nielsen:
Then paste all the DISCARD lines into a new file called
/etc/postfix/banned_tlds (and also add some own TLDs there, its just to copy
paste one line and then change the TLD), and also remove lines for TLDs you
don’t want to block.
Chmod the banned_tlds file to 666 to ensure t
First add check_sender_access pcre:/etc/postfix/banned_tlds into
smtpd_sender_restrictions in main.cf
Then paste all the DISCARD lines into a new file called
/etc/postfix/banned_tlds (and also add some own TLDs there, its just to copy
paste one line and then change the TLD), and also remove lin
Just copy and passed the DISCARD contents into banned_tlds?
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Sebastian Nielsen
Sent: Friday, February 19, 2016 3:50 PM
To: postfix-users@postfix.org
Subject: SV: Blocking TLDs
smtpd_sender_restriction
Wietse Venema wrote:
I don't think that it is a good idea to fill up your machine with
programs that keep timing out again and again and again. Postfix
is not only about performance and security, but also about safety
(mail servers should be able to deal with problems and not require
a human baby
smtpd_sender_restrictions = check_sender_access
pcre:/etc/postfix/banned_tlds
banned_tlds:
/\.bid$/ DISCARD
/\.top$/ DISCARD
/\.xyz$/ DISCARD
/\.date$/ DISCARD
/\.faith$/ DISCARD
/\.download$/ DISCARD
Problem solved.
Från: owner-postfix-us...@postfix.org
[mailto:owner-postfi
Greetings all!
This is actually my first posting to the mailing list, but have actually
been following along on a regular basis and have learned quite a bit of good
things (and bad things *smiles*) about Postfix. Unfortunately, I have one
question that I am hoping someone here on the mailing l
Reid Sutherland:
> We also had to use the following hack to ensure module load failures do
> not result in bounces. I see that Unix::Syslog is absent from the this
> list or the above bounce may have been prevented.
Indeed, if your program had returned a temporary error status,
Postfix would ha
Wietse Venema wrote:
Reid Sutherland:
Hi,
Why does Postfix bounce on command execution failure,
The action depends on the command exit status. If you want Postfix
to retry, return the appropriate status.
Not fair, here was our problem:
Final-Recipient: rfc822; r...@vianet.ca
Original-Reci
Ray Dzek:
> We are load balancing our Postfix servers and as part of that there
> is a connection test to ensure the services are running. So the
> logs fill with connection checks. Is there a way to suppress those
> connections from the logs?
Even with one connect/disconnect event per second, the
On Fri, Feb 19, 2016 at 01:18:20PM -0600, Noel Jones wrote:
> On 2/19/2016 1:11 PM, Ruben Safir wrote:
> > Can aanyone clarify what this means? it is happing a lot on my mail server
> >
> > Feb 19 14:09:31 www postfix/smtpd[6978]: warning:
> > 70.14.214.162.list.dsbl.org: RBL lookup error: Host
Am 19. Februar 2016 20:32:20 MEZ, schrieb Ray Dzek :
>We are load balancing our Postfix servers and as part of that there is
>a connection test to ensure the services are running. So the logs fill
>with connection checks. Is there a way to suppress those connections
>from the logs?
Create a filte
Reid Sutherland:
> Hi,
>
> Why does Postfix bounce on command execution failure,
The action depends on the command exit status. If you want Postfix
to retry, return the appropriate status.
> or on command timeout?
I don't think that it is a good idea to fill up your machine with
programs that k
We are load balancing our Postfix servers and as part of that there is a
connection test to ensure the services are running. So the logs fill with
connection checks. Is there a way to suppress those connections from the logs?
Thanks in advance,
Ray
On 2/19/2016 1:11 PM, Ruben Safir wrote:
> Can aanyone clarify what this means? it is happing a lot on my mail server
>
> Feb 19 14:09:31 www postfix/smtpd[6978]: warning:
> 70.14.214.162.list.dsbl.org: RBL lookup error: Host or domain name not found.
> Name service error for name=70.14.214.162
Can aanyone clarify what this means? it is happing a lot on my mail server
Feb 19 14:09:31 www postfix/smtpd[6978]: warning: 70.14.214.162.list.dsbl.org:
RBL lookup error: Host or domain name not found. Name service error for
name=70.14.214.162.list.dsbl.org type=A: Host not found, try again
Hi,
Why does Postfix bounce on command execution failure, or on command
timeout? This isn't a situation for a hard failure, please clarify the
reasoning.
From postfix-2.11.7/src/global/pipe_command.c:672
} else if (write_status && write_errno != EPIPE) {
vstring_prepend
Udo Rader:
> Hi,
>
> is there a possibility to only allow PLAIN authentication when TLS or
> similar encryption has been negotiated?
>
> So far, I only found a way to either completely disable PLAIN
> authentication or allow it in general.
Postfix SMTP client:
smtp_sasl_security_options = noanon
Hi,
is there a possibility to only allow PLAIN authentication when TLS or
similar encryption has been negotiated?
So far, I only found a way to either completely disable PLAIN
authentication or allow it in general.
Udo
On Fri, Feb 19, 2016 at 02:55:45PM +0530, Jayesh Shinde wrote:
> I am doing this setting for sending email to "aexp.com" .
> w.r.t above info and docs i made below setting , but remote host saying
> "530 Must issue a STARTTLS command first."
The lookup key for the TLS policy table MUST match th
On 02/19/2016 05:01 AM, Viktor Dukhovni wrote:
On Thu, Feb 18, 2016 at 08:16:12PM +0530, Jayesh Shinde wrote:
How to relay only specific domain's email on over TLS and rest all other on
port 25 as normal i.e without TLS ?
Postfix 2.3 .. 2.10:
main.cf:
indexed = ${default_datab
31 matches
Mail list logo
