Dnia 26.09.2019 o godz. 14:48:56 Wietse Venema pisze:
>
> The simplest is to avoid "content filter -> /usr/sbin/sendmail" and
> instead use SMTP-based or Milter-based content inspection.
Yes, it looks that the easiest option was to move from running spamassassin
as after-queue content filter to r
> On Sep 26, 2019, at 3:29 PM, David Wells - Alfavinil S.A.
> wrote:
>
> The file vmailbox contains the following entries
>> testus...@example.comOK
>> testus...@example.comOK
>
> If I send an email to the address testus...@example.com it is
> successfully delivered to the mailbox as ex
I have to, i'm authenticating users against samba's ldap using gssapi.
Isn't postfix supposed to stop the mail before handing it to lmtp if
it's own map doesn't include the recipient?
Thanks!
Best regards,
David Wells.
El 26/09/2019 a las 17:08, @lbutlr escribió:
> On Sep 26, 2019, at 1:29 PM,
On Sep 26, 2019, at 1:29 PM, David Wells - Alfavinil S.A.
wrote:
> and as dovecot has the option "allow_all_users=yes”
Simple, don’t do that.
Somewhere in your chain something has to validate the users, otherwise yes,
everything will be accepted because that is what you told the system to do.
On Thu, 26 Sep 2019 10:46:27 +0200
Enrico Morelli wrote:
> On Thu, 26 Sep 2019 10:42:46 +0200
> Enrico Morelli wrote:
>
> > On Thu, 26 Sep 2019 16:37:14 +0800
> > Wesley Peng wrote:
> >
> > > on 2019/9/26 16:34, Enrico Morelli wrote:
> > > > I tried to put .monster or *.monster in sender
Good afternoon.
Dovecot is relaying mails to users that do not exist in the
virtual_mailbox_maps to the dovecot lmtp. I'm using dovecot's lmtp to
deliver mails for a virtual domain. The relevant postfix conf is as follows
> virtual_alias_maps = hash:/etc/postfix/virtual
> virtual_mailbox_domains =
Viktor Dukhovni:
> > Wouldn't it be possible to run a second pickup(8) instance with a different
> > configuration file, without milters and configured for a different queue
> > directory? And then run the after-filter sendmail(1) also configured for
> > that queue directory?
>
> This is likely "
> On Sep 26, 2019, at 1:43 PM, Jaroslaw Rafa wrote:
>
>> The most robust approach that comes to mind is a multi-instance
>> configuration:
>>
>> http://www.postfix.org/MULTI_INSTANCE_README.html#quick
>
> I think that running such a big and complicated setup is definitely a kind
> of over
Dnia 26.09.2019 o godz. 13:08:02 Viktor Dukhovni pisze:
> The most robust approach that comes to mind is a multi-instance configuration:
>
>http://www.postfix.org/MULTI_INSTANCE_README.html#quick
I think that running such a big and complicated setup is definitely a kind
of overkill for so sma
Wietse Venema:
> Would not "sendmail -G" suppress local modification?
>
>-G Gateway (relay) submission, as opposed to initial user submis-
> sion. Either do not rewrite addresses at all, or update incom-
> plete addresses with the domain information specified
Dnia 26.09.2019 o godz. 13:31:53 Wietse Venema pisze:
>
> Would not "sendmail -G" suppress local modification?
>
>-G Gateway (relay) submission, as opposed to initial user submis-
> sion. Either do not rewrite addresses at all, or update incom-
> plete addresses w
Jaroslaw Rafa:
> Hello All,
> I am using spamassassin with my postfix setup in form of "simple
> content filter", as described here:
> http://www.postfix.org/FILTER_README.html#simple_filter . That means, smtp
> server has the option "-o content_filter=spamassassin" defined in master.cf
> file, and
> On Sep 26, 2019, at 1:00 PM, Jaroslaw Rafa wrote:
>
> And here is where the trouble comes. When a mail arrives to my server with
> my own address as the sender (for example, my emails coming back from a
> mailing list), the content filter script also calls /usr/lib/sendmail to put
> the message
Hello All,
I am using spamassassin with my postfix setup in form of "simple
content filter", as described here:
http://www.postfix.org/FILTER_README.html#simple_filter . That means, smtp
server has the option "-o content_filter=spamassassin" defined in master.cf
file, and also a service named "spam
Davide Perini:
> Don't want to argue, but this is the kind of answers that shows that you
> never used docker,
> if so, why answer to the question?
I guess this demonstrates that some people have never used more
than one OS.
On a more sensible note, I'd be willing to collect build files that
cre
Ok davide,
does docker run on old cpu's, or how compatible is it with arm cpu's?
ever run an alpha dec?
postfix just provide the code, which compiles into binaries, postfix
don't get involved with packaging, thats the job of vendors.
thats why there are no official postfix docker images, ca
David-
Just FYI-
I created a Dockerfile by pulling in Ubuntu:latest and then ran apt
install postfix and set it from there.. The docker is ran by multiple
Mesos nodes without issue..
On Thu, Sep 26, 2019 at 12:34 PM Davide Perini
wrote:
> Don't want to argue, but this is the kind of answer
Don't want to argue, but this is the kind of answers that shows that you
never used docker,
if so, why answer to the question?
Il 2019-09-26 18:13 Wietse Venema ha scritto:
Davide Perini:
Thanks for the answer but what are the "official vendors" for this
purpose?
Docker hub does not work li
I have a dockerised set of images and kubernetes deployments for you to
look at if you're interested. They work well and serve my domains
without much problem
https://github.com/orgs/kubernetes-mail-server/dashboard
Take a look, maybe there is some contribution you want to make.
Chris
On 26.
Davide Perini:
> Thanks for the answer but what are the "official vendors" for this
> purpose?
> Docker hub does not work like this exactly. Most devs provides their own
> binaries in "official images".
>
> Why it's not the same for postfix?
Because not all the world is LINUX? Postfix is a cros
Thanks for the answer but what are the "official vendors" for this
purpose?
Docker hub does not work like this exactly. Most devs provides their own
binaries in "official images".
Why it's not the same for postfix?
In any case is there some good image I can trust or that you can
suggest?
T
Davide Perini:
> Hi all,
> is there an official image of postfix on docker hub?
>
> I can't find it, why?
Postfix developers provide Postfix source.
Vendors provide binaries (and redistribute source).
Wietse
Hi all,
is there an official image of postfix on docker hub?
I can't find it, why?
Thanks,
Davide
On Sep 26, 2019, at 4:01 AM, Dominic Raferd wrote:
> Of course this assumes pcre (or maybe regex) file. To ensure it picks
> up only email addresses in From header (and not text), then, using
> pcre file for header_checks:
No, you do the checks for the helo, not the From: header.
The idea is to
Date: Thu, 26 Sep 2019 12:22:33
From: Enrico Morelli
To: postfix-users@postfix.org
Subject: Re: How to block mail coming from a domain
I've search in my Debian 10 packages but there isn't postscreen.
Is it in bundle with new postfix version? In Debian 10 I've postfix
3.4.5
Hello, as written in
On Thu, 26 Sep 2019 at 11:24, Enrico Morelli
wrote:
> I've search in my Debian 10 packages but there isn't postscreen.
> Is it in bundle with new postfix version? In Debian 10 I've postfix
> 3.4.5
On Thu, 26 Sep 2019 11:29:38 +0100
Dominic Raferd wrote:
Yes it is a standard part of postfix -
On Thu, 26 Sep 2019 11:29:38 +0100
Dominic Raferd wrote:
> On Thu, 26 Sep 2019 at 11:24, Enrico Morelli
> wrote:
> > I've search in my Debian 10 packages but there isn't postscreen.
> > Is it in bundle with new postfix version? In Debian 10 I've postfix
> > 3.4.5
>
> Yes it is a standard part
On Thu, 26 Sep 2019 at 11:24, Enrico Morelli wrote:
> I've search in my Debian 10 packages but there isn't postscreen.
> Is it in bundle with new postfix version? In Debian 10 I've postfix
> 3.4.5
Yes it is a standard part of postfix - try 'man postscreen'
On Sep 26, 2019, at 03:51, Henrik K wrote:
> Obviously these will only work for envelope sender. Most likely needing
> header_checks /^From:.*\.monster/ here..
Yep. I use header checks to block most top level domains, letting only a dozen
or so through and rejecting all the rest since it is imp
On Thu, 26 Sep 2019 at 10:52, Henrik K wrote:
>
> On Thu, Sep 26, 2019 at 11:44:11AM +0200, Matus UHLAR - fantomas wrote:
> > On 26.09.19 10:34, Enrico Morelli wrote:
> > >in this days my mail server receiving a lot of mail coming from a
> > >domain ending with .monster...
>
> Obviously these will
On Sep 26, 2019, at 00:18, feier8097 wrote:
>
> The postfix system will return back an email with subject "Undelivered Mail
> Returned to Sender"
No, ALL mail servers will do this if they cannot deliver mail they accepted.
> But I don't want it send this message.
Then do not accept mail you
On 25.09.19 23:24, feier8097 wrote:
thanks for your help. But I want to change "bounce" to "discard". Beacause
When user sent mail to accunt without exist on the server.
put:
smtpd_reject_unlisted_recipient=yes
smtpd_reject_unlisted_sender=yes
into main.cf. This way your users will NOT send a
On Thu, 26 Sep 2019 10:42:46 +0200
Enrico Morelli wrote:
> On Thu, 26 Sep 2019 16:37:14 +0800
> Wesley Peng wrote:
>
> > on 2019/9/26 16:34, Enrico Morelli wrote:
> > > I tried to put .monster or *.monster in sender_access but doesn't
> > > work. Is there a way to block *.monster mails?
>
on 2019/9/26 16:42, Enrico Morelli wrote:
Can you setup spamassassin for domain blacklist?
regards.
How can do that?
The SpamAssassin whitelist and blacklist options can include globs, not
regular expressions. The valid metacharacters are ? and * to match 0-1
or 0-many characters respect
On Thu, 26 Sep 2019 16:37:14 +0800
Wesley Peng wrote:
> on 2019/9/26 16:34, Enrico Morelli wrote:
> > I tried to put .monster or *.monster in sender_access but doesn't
> > work. Is there a way to block *.monster mails?
>
> Can you setup spamassassin for domain blacklist?
>
> regards.
How can
on 2019/9/26 16:34, Enrico Morelli wrote:
I tried to put .monster or *.monster in sender_access but doesn't work.
Is there a way to block *.monster mails?
Can you setup spamassassin for domain blacklist?
regards.
36 matches
Mail list logo
