On Fri, 21 Oct 2016 22:15:32 +0200, Paul van der Vlis
wrote:
> Hello,
> Some settings and logs:
>
> smtpd_relay_restrictions =
> permit_mynetworks,
> permit_sasl_authenticated,
> check_sender_access hash:/etc/postfix/whitelist,
> reject_invalid_hostname,
> reject_non_fqdn_sender,
>
On Fri, 14 Jun 2013 17:10:16 +0200, Bernhard Schmidt
wrote:
> This gets even worse when the mail has two recipients
> ... doesnotexist@ does not exist, t1@ does...
>
> mail from:
> 250 2.1.0 Sender OK
> rcpt to:
> 250 2.1.5 Recipient OK
> rcpt to:
> 250 2.1.5 Recipient OK
> data
> 354 Start
On Wed, 7 Mar 2012 15:46:25 -0800 (PST), Scott Brown
wrote:
> I am trying to install Postfix with mysql on CentOS 6.0.
> I am trying to follow the instructions
> at http://www.postfix.org/MYSQL_README.html
> I downloaded the mysql libraries and source code.
> The libmysql was extracted
> to /
On Mon, 14 Feb 2011 14:28:22 -0600, /dev/rob0 wrote:
> On Mon, Feb 14, 2011 at 03:55:25PM +0200, JC Putter wrote:
>> Can postscreen be compared to SNARE?
> http://en.wikipedia.org/wiki/Snare gives me no clue as to what you
> might be asking. However, postscreen has documentation:
> http://ww
On Fri, 14 Jan 2011 12:59:38 +0100, John Fawcett wrote:
> I get the following warnings with postfix-2.8-20110112 even though I
> don't use any more postscreen_whitelist_networks and
> postscreen_blacklist_networks in my configuration having replaced them
> by the new postscreen_access_list.
At l
(just a faint impact, ...)
since postfix-2.8-20110102, postscreen_cache_map file has been
named "psc_cache" by default.
postfix-2.8-20110112:
./global/mail_params.h:#define DEF_PSC_CACHE_MAP
"btree:$data_directory/psc_cache"
though man postscreen said,
...
postscreen_cache_map (btree:$
On Wed, 29 Dec 2010 10:14:49 -0500, Joan Moreau wrote:
> Can you just tell me how to put
> the mailing queue in a DB (mysql database in my case) ?
you may simply deploy MySQLfs (FUSE+MySQL) if you do not mind
speeds, loads,...etc.
http://sourceforge.net/projects/mysqlfs/
pgp7HNgIbhXrK.pgp
Des
Wietse:
> Again. if something can already be done with smtpd plus milter or
> policy plugin or content filter then I urge you to keep using that
> already existing functionality.
and also said,
> Postscreen's purpose is to keep zombies away so that you can keep
> using the existing smtpd feature
> Cassidy Larson:
>> We had an incident today where we had a user with a compromised
>> machine. Their email/pass made it back to some botnet which proceeded
>> to SASL auth to our mail servers and send numerous spam messages from
>> many different hosts. The spamming hosts didnt trigger our
>> sm
From: Wietse Venema
Subject: Re: SRS implementation
Date: Sat, 22 May 2010 09:35:29 -0400 (EDT)
> Tomoyuki Murakami:
>> > First, this would accept mail for forwarder+anyuser=anydom...@my.dom,
>> > meaning that it would be an open relay. A more secure implementation
>>
Hi, Wieste,
Thanks for reply.
From: Wietse Venema
Subject: Re: SRS implementation
Date: Fri, 21 May 2010 16:13:45 -0400 (EDT)
> First, this would accept mail for forwarder+anyuser=anydom...@my.dom,
> meaning that it would be an open relay. A more secure implementation
> would compute a hash of (
Hi, all
I'm just playing with implement SRS(Sender Rewriting Scheme)-like
function into Postfix.
*SRS - http://www.openspf.org/SRS
A trivial patch, attached this message would do the following.
* rewrite sender when the message will forward to other site/domain.
* Nope when the VERP setting is
From: Birta Levente
Subject: DKIM-milter only for outgoing
Date: Thu, 15 Apr 2010 17:23:12 +0300
> My postfix server is set up with amavisd-new and dkim-milter.
>
> In the main.cf:
>
> content_filter = smtp-amavis:[127.0.0.1]:10024
>
> smtpd_milters = inet:localhost:20209
> non_smtpd_milters =
13 matches
Mail list logo
