2012/3/28 Daniele Nicolodi dani...@grinta.net
That's true, however, as far as I know, differently than most of other
open source software, there isn't a public source code repository for
the development of Postfix. Wieste, can you comment on this choice?
Did not come back for a while, hoping
The Postfix development model is not like that of other open source
projects with a steady stream of new commits, bugreports and bugfixes
for those new commits. One of the original Postfix goals, which
still stands today, is to provide software that isn't riddled with
security and other holes
On 4.4.2012, at 10.31, Γεώργιος Δεδούσης wrote:
Wietse, please comment, don't you think that a public repo, showing each
source code change would be useful for Postfix? An issue reporting system too?
Issue trackers seem to be kind of a waste of time for projects with few
developers:
a) You
Le lundi 02 avril 2012 à 11:36 +0200, Benny Pedersen a écrit :
Den 2012-04-01 21:18, ml skrev:
I just made the changes I think the problem is solved
thank you for the fruitful comments
nope !DSPAM sigs is still sent to me :)
that means i can now train my m...@junc.org on your server
Hello Wietse,
thank you for your straightforward response. I was absolutely not
advocating a change in the development model of Postfix, I have no
reason to think that the current one as any problem. I was merely
inquiring about the choice about the way the Postfix source code is
distributed.
Den 2012-04-04 17:28, ml skrev:
any idees
you currently using opt out in dspam.conf this include so mails sent to
postfix maillists
change dspam.conf to opt in, and set each local recipient to opt in,
this way you dont see !dspam in maillists, check maillist archives for
your own
We have an environment with two tiers of mail servers. The outer Postfix
servers receive mail for our entire domain and handle delivery for certain
addresses. Other specific regexp addresses at the same domain need to be
passed to different internal SMTP servers. Anything else must be bounced
Drew Mazurek:
We have an environment with two tiers of mail servers. The outer Postfix
servers receive mail for our entire domain and handle delivery for certain
addresses. Other specific regexp addresses at the same domain need to be
passed to different internal SMTP servers. Anything else
I'd like to set up a delivery rule / method which simply rejects
delivery for a specific domain (or set of domains).
The immediate need is testing based on a domain we control. We've
also got an issue of stale contacts for expired domains which pile up
in our queues but I haven't addressed them.
Wietse Venema:
Drew Mazurek:
We have an environment with two tiers of mail servers. The outer Postfix
servers receive mail for our entire domain and handle delivery for certain
addresses. Other specific regexp addresses at the same domain need to be
passed to different internal SMTP
* Daniele Nicolodi dani...@grinta.net:
Having to track the changes to Postix from version to version and to
snapshot to snapshot, what I would do is to import each revision into a
revision control system and compare them with the tools offered by it.
If a central repository would be publicly
On 4/4/2012 1:37 PM, Edward Morbius wrote:
I'd like to set up a delivery rule / method which simply rejects
delivery for a specific domain (or set of domains).
Add a transport_maps entry for the bad domain pointing to the error:
transport.
# main.cf
transport_maps = hash:/etc/postfix/transport
Further research. This looks promising.
http://kudithipudi.org/2009/05/15/how-to-block-outbound-e-mails-in-postfix/
On Wed, Apr 4, 2012 at 11:37 AM, Edward Morbius dredmorb...@gmail.com wrote:
I'd like to set up a delivery rule / method which simply rejects
delivery for a specific domain (or
My goal is to limit outbound email to only three domains. All other email
destined for any other domain should be redirected to a single, valid
internal mail box.
It isn't working. Email to addresses outside this domain are still being
delivered.
/etc/postfix/access:
domain1.com OK
domain2.com
On 4/4/2012 2:48 PM, Edward Morbius wrote:
Further research. This looks promising.
http://kudithipudi.org/2009/05/15/how-to-block-outbound-e-mails-in-postfix/
The above example uses the discard: transport to silently drop mail.
While this works, it is generally considered bad practice for
Eric Kimminau:
My goal is to limit outbound email to only three domains. All other email
destined for any other domain should be redirected to a single, valid
internal mail box.
It isn't working. Email to addresses outside this domain are still being
delivered.
/etc/postfix/access:
On 4/3/2012 8:32 PM, Noel Jones wrote:
On 4/3/2012 10:28 PM, Daniel L. Miller wrote:
I think a broader statement for what I'm looking for is to be able
to re-write the recipient based on the sender, and vice versa. If
Postfix does not support this, do you know of a tool that does that
I can
Thanks. I was going to look into alternate transports.
For the test, discard may be what we're looking for.
For the invalid domains, 'error' is much more appropriate.
On Wed, Apr 4, 2012 at 1:08 PM, Noel Jones njo...@megan.vbhcs.org wrote:
On 4/4/2012 2:48 PM, Edward Morbius wrote:
Further
2 issues:
1) I need to know when someone is attempting to use any domain but what we have
approved for testing. This is the reason for the redirect. I'm open to
alternatives but other than babysitting log files or every userid mailbox used
REJECT is tough to track.
2) I only have 3 domains
Wietse:
Instead of redirect, why not use reject:
/etc/postfix/transport:
example.com:
* reject:this destination is not allowed
Eric Kimminau:
1) I need to know when someone is attempting to use any domain but
what we have approved for testing.
Why do you care what domains users
FWIW I agree wholeheartedly with Wietse. We switched from sendmail to
Postfix 10 years ago. The code is very professional and very stable.
That is very unusual in today's open source world.
I really don't need to explain for any other reason than it is a requirement of
my customer. I appreciate the banter but the harder you fight me the more it
makes me believe the product cant meet our need.
Is it possible to limit all outbound email to 3 domains? If so, how?
Is it possible to
On 4/4/2012 9:55 PM, Eric Kimminau wrote:
I really don't need to explain for any other reason than it is a requirement
of my customer. I appreciate the banter but the harder you fight me the more
it makes me believe the product cant meet our need.
Is it possible to limit all outbound
On Wed, Apr 04, 2012 at 03:57:00PM -0400, Eric Kimminau wrote:
My goal is to limit outbound email to only three domains. All other email
destined for any other domain should be redirected to a single, valid
internal mail box.
I take it these are *destination* (recipient) domains, not *origin*
On Wed, Apr 04, 2012 at 04:11:34PM -0400, Wietse Venema wrote:
/etc/postfix/transport:
example.com :
* reject:this destination is not allowed
That should of course be
error:5.1.2 ...
not
reject: ...
since reject is not a transport, is is an
what i want to achieve is that for specific domains\servers\destinations
i will use auth user.
as i was just migrating mail system there was a hole that allowed remote
servers to send mail to local users behalf of a local users without
authentication as a local user and forging mails on this
26 matches
Mail list logo
