ail.com.
Well, this address is not matched in the table at all, so it just
falls through to "permit_mynetworks", which allows the delivery.
> From: Viktor Dukhovni via Postfix-users
> Sent: 07 May 2025 13:29
> To: postfix-users@postfix.org
> Subject: [pfx] Re: Configuration
,
virtual_alias_domains, virtual_mailbox_domains or relay_domains.
2. Restrict outgoing emails for all users so they can only send to a
list of allowed domains.
You can do this using restriction classes:
http://www.postfix.org/RESTRICTION_CLASS_README.html
or perhaps using external milter
---
This configuration is not working and the user "b...@sutisoft3.in" are
sending emails to @gmail.com.
Thanks,
Srinivasa Gowd.
-Original Message-
From: Viktor Dukhovni via Postfix-users
Sent: 07 May 2025 13:29
To: postfix-users@postfix.org
Subject: [pfx] Re: Configuration Requ
On Wed, May 07, 2025 at 12:57:29PM +0530, Srinivasa Gowd S via Postfix-users
wrote:
> 1.Allow incoming emails from all external domains to all internal
> users.
> 2. Restrict outgoing emails for all users so they can only send to
> a list of allowed domains.
&
Hello Postfix Support,
We would like to configure our Postfix server to meet the following
requirements:
1. Allow incoming emails from all external domains to all internal
users.
2. Restrict outgoing emails for all users so they can only send to a
list of allowed domains.
3
bout 25 IPs and CIDR blocks. The inline
> > tables would make this fairly manageable.
>
> That was the gambit.
>
> > It looks like if an IP isn't in check_client_access but is allowed to
> > relay then that IP could send as whoever they like. All IPs that
> > r
is allowed to
> relay then that IP could send as whoever they like. All IPs that
> relay would have to be in check_client_access.
So it it seems you rather want to restrict access to some domains for
to just the allowed IPs, rather than restrict some IPs to specific
domains.
> Coul
gt; > email. Some of those devices do not do authentication. I'd like to
> > restrict the sender domain based on the IP.
>
> How many distinct sender domains are in scope? If it is just a small
> handful, you can restriction classes:
>
> main.cf:
> smtpd_
On Fri, Sep 13, 2024 at 10:29:21AM -0500, Dan Lists via Postfix-users wrote:
> I have a small email relay server that is used to allow IOT devices to send
> email. Some of those devices do not do authentication. I'd like to
> restrict the sender domain based on the IP.
How
ntication. I'd like to
> > restrict the sender domain based on the IP.
> >
> > I'm looking for something like smtpd_sender_login_maps, but for client
> IPs.
>
> There is no IP-based analogon for smtpd_sender_login_mapss,
> due to lack of demand.
>
> If you
Dan Lists via Postfix-users:
> I have a small email relay server that is used to allow IOT devices to send
> email. Some of those devices do not do authentication. I'd like to
> restrict the sender domain based on the IP.
>
> I'm looking for something like smtpd_s
I have a small email relay server that is used to allow IOT devices to send
email. Some of those devices do not do authentication. I'd like to
restrict the sender domain based on the IP.
I'm looking for something like smtpd_sender_login_maps, but for client IPs.
Ex
On 2023/12/5 21:13, Jaroslaw Rafa via Postfix-users wrote:
Dnia 5.12.2023 o godz. 20:14:45 Cowbay via Postfix-users pisze:
I want this mail server to relay mails for specific domains only and
all the mails are relayed to another mail server ($relayhost
configured in main.cf).
I found that the
Dnia 5.12.2023 o godz. 20:14:45 Cowbay via Postfix-users pisze:
>
> I want this mail server to relay mails for specific domains only and
> all the mails are relayed to another mail server ($relayhost
> configured in main.cf).
>
> I found that there is no $sendmail_relay_restrictions configuratio
Hi,
I installed a Postfix mail server in a Linux LXC container.
I want this mail server to relay mails for specific domains only and all
the mails are relayed to another mail server ($relayhost configured in
main.cf).
I found that there is no $sendmail_relay_restrictions configuration like
On 12/23/22 19:06, raf wrote:
On Fri, Dec 23, 2022 at 01:14:26PM -0800, Jim Garrison wrote:
[snip]
Not relevant to your problem, but the above says that
only ipv4 is used but your config includes ipv6
addresses. You might want to delete it (and default to
"all"), or remove the ipv6 addresses f
t; Dec 23 12:24:18 janus postfix/qmgr[9910]: CC31BC0281: removed
>
>
> I've studied the excellent documentation thoroughly, and even found
> several how-to's on the web saying this is the way to restrict relaying
> to a specific client.
>
> What have I missed?
>
&
On 12/23/22 17:24, Wietse Venema wrote:
You should also include "postconf -P" for parameter settings in
master.cf.
Wietse
Not much there...
$ postconf -P
relay/unix/syslog_name = postfix/$service_name
--
Jim Garrison
j...@acm.org
You should also include "postconf -P" for parameter settings in
master.cf.
Wietse
oac.12 - gsmtp)
Dec 23 12:24:18 janus postfix/qmgr[9910]: CC31BC0281: removed
I've studied the excellent documentation thoroughly, and even found
several how-to's on the web saying this is the way to restrict relaying
to a specific client.
What have I missed?
postconf -n output (s
list,
what the title says actually, I have an alias for all current users
of an SMTP server but
I want to restrict sending to this alias address to some specific
senders only (the actual
users of the domain plus a small group of external senders ).
What I'm I looking for in the document
something like this?
http://www.postfix.org/RESTRICTION_CLASS_README.html#internal
On 4/26/21 10:11 AM, George Papas wrote:
> Hi list,
>
>
> what the title says actually, I have an alias for all current users
> of an SMTP server but
>
> I want to restrict sending to this
Hi list,
what the title says actually, I have an alias for all current users
of an SMTP server but
I want to restrict sending to this alias address to some specific
senders only (the actual
users of the domain plus a small group of external senders ).
What I'm I looking for i
Hi Ansgar,
Thank you. It worked like a charm.
On Wed, 6 Jan 2021 at 16:16, Ansgar Wiechers wrote:
> On 2021-01-06 Burn Zero wrote:
> > I need to restrict outbound email to the internet by client IP. i.e.
> > if an IP is in a blocked list, it should only be allowed to be se
On 2021-01-06 Burn Zero wrote:
> I need to restrict outbound email to the internet by client IP. i.e.
> if an IP is in a blocked list, it should only be allowed to be sent to
> local domains. Is this possible? Please advise.
>
> I read http://www.postfix.org/RESTRICTION_CLASS_REA
Hi,
I need to restrict outbound email to the internet by client IP. i.e. if an
IP is in a blocked list, it should only be allowed to be sent to local
domains. Is this possible? Please advise.
I read http://www.postfix.org/RESTRICTION_CLASS_README.html but it is only
using the usernames and not
> @lbutlr wrote:
>> > a wrote:
>> > > However, an outside network can still identify as a local email
>> > > account to send into my network, making imposters possible.
>> >
>> > Do not allow connections on port 25 that claim to be from your domains.
>> >
>> > (I think this works still):
>>
>> Yes.
> @lbutlr wrote:
> > a wrote:
> > > However, an outside network can still identify as a local email
> > > account to send into my network, making imposters possible.
> >
> > Do not allow connections on port 25 that claim to be from your domains.
> >
> > (I think this works still):
>
> Yes. It work
On 20/02/2020 03:39, Bob Proulx wrote:
> I do a slight variation on this that I think is slightly better.
> Instead of pcre tables I use hash tables. Which should be slightly more
> efficient. And won't suffer from common substring matches such as
> hitting by accident on goodkreme.com or othe
@lbutlr wrote:
> a wrote:
> > However, an outside network can still identify as a local email
> > account to send into my network, making imposters possible.
>
> Do not allow connections on port 25 that claim to be from your domains.
>
> (I think this works still):
Yes. It works.
> smtpd_helo_
xes on my server which is what I want. And it does
> restrict relaying from outside networks to other email addresses and that's
> how I need it to work. It's great postfix is set to do this by default.
> However, an outside network can still identify as a local email account
I looked around online to try to see examples to stop this but haven't
found any yet. Maybe I'm missing something simple.
My postfix server does allow incoming connections from the outside world to
deliver mail to mailboxes on my server which is what I want. And it does
restrict rel
On 8/21/2018 11:24 PM, mli...@x76.eu wrote:
> Hello,
> I have a number of authenticated senders I would like to restrict to
> certain recipient domains.
>
> I.e. user "apachel...@example.org" should only be able to send emails to
> domains "example.org" and &
Actually I'm using cbpolicy with postfix to restric recipients and incoming
mail to prevent spam attacks
El mar., 21 de ago. de 2018 a la(s) 23:25, mli...@x76.eu
escribió:
> Hello,
> I have a number of authenticated senders I would like to restrict to
> certain recipient domains.
Hello,
I have a number of authenticated senders I would like to restrict to
certain recipient domains.
I.e. user "apachel...@example.org" should only be able to send emails to
domains "example.org" and "foobarbaz.com".
Recipient/s with any other domain (e.g.
,
defer_unauth_destination
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
192.168.10.0/24
192.168.20.0/24
hash:/etc/postfix/SMTP_allow.txt
In the txt file are the specific mail addresses.
Now i have to restrict some subnets to send mails only to domains like
acme.com or jdoe.com.
I
Justin Peavey:
> Hi Wietse,
>
> The noted difference is for b...@trashcan.org,
> smtpd_recipient_restrictions is never evaluated at all. For
Show the smtpd logging.
Wietse
Hi Wietse,
The noted difference is for b...@trashcan.org, smtpd_recipient_restrictions is
never evaluated at all. For b...@trashcan.org there is no ‘START Recipient
address RESTRICTIONS’ or any of the related logs for
smtpd_recipient_restrictions.For arling...@trashcan.org,
smtp_recipien
Here is the start of evaluating smtpd_recipient_restrictions:
> Dec 23 16:06:34 ip-172-31-54-95 postfix/smtpd[13472]: extract_addr: in:
> , result: arling...@trashcan.org
> Dec 23 16:06:34 ip-172-31-54-95 postfix/smtpd[13472]: >>> START Recipient
> address RESTRICTIONS <<<
> Dec 23 16:06:34 ip-
I’ve spent more time reviewing and while my observations may be flawed, they do
seem to be consistent. What I continue to observe is that when an address is
matched in /etc/alias, that the smtp_recipient_restrictions are not processed
and therefore the suggested restrictions are not having any
Justin Peavey:
> I appreciate that the filter does not distinguish between domains.
> Nonetheless, I see different filtering behavior for email destined for the
> domain listed in mydomain which also have entries in /etc/aliases vs. the
> domains listed as virtual domains.
>
> Sent from my TI
Haven't you tried postfix spf verification for your mail server with proper
-all dns configuration for your domain?
Anvar Kuchkartaev
an...@anvartay.com
Original Message
From: Omniver
Sent: domingo, 10 de diciembre de 2017 21:07
To: postfix-users@postfix.org
Subject: How to restrict se
I appreciate that the filter does not distinguish between domains. Nonetheless,
I see different filtering behavior for email destined for the domain listed in
mydomain which also have entries in /etc/aliases vs. the domains listed as
virtual domains.
Sent from my TI-99/4A
> On Dec 14, 2017,
Justin Peavey:
>
> Thanks for the reply, unfortunately the approach doesn?t seem to work for me.
> It appears that that the regardless of the smtp_recipient_restrictions
> setting, that any addresses listed in /etc/aliases addressed to $mydomain is
> bypassing any blocking/filtering. Is this
Thanks for the reply, unfortunately the approach doesn’t seem to work for me.
It appears that that the regardless of the smtp_recipient_restrictions setting,
that any addresses listed in /etc/aliases addressed to $mydomain is bypassing
any blocking/filtering. Is this expected behavior?
>
>
Omniver:
> I have a mail server receiving internet mail for my primary domain and for a
> few virtual domains. I'm having some spam issues with internet mail coming
> in for address@mydomain for addresses intended for use by local
> tools/scripts which are listed in /etc/aliases. Any ideas on how
I have a mail server receiving internet mail for my primary domain and for a
few virtual domains. I'm having some spam issues with internet mail coming
in for address@mydomain for addresses intended for use by local
tools/scripts which are listed in /etc/aliases. Any ideas on how can I make
it th
Matus:
why just outgoing? Are you willing to accept spam with fake from in your
domain?
On 07.09.17 15:13, Scott Techlist wrote:
I am not willing. Inbound is already restricted and functioning properly.
That said, I migrated my configs from an older version of PF so now you made me
worry a
Matus:
>why just outgoing? Are you willing to accept spam with fake from in your
>domain?
I am not willing. Inbound is already restricted and functioning properly.
That said, I migrated my configs from an older version of PF so now you made me
worry about *how* it is restricted.
I have se
On 9/5/2017 2:48 PM, techlist06 wrote:
Is it possible to restrict outgoing mail to be from one of my "valid"
local or virtual aliases? And I want to restrict outbound from one
address in particular.
On 05.09.17 15:25, Noel Jones wrote:
The easiest way would be
First time I've tried the inline map type. And, I think the spaces may have
been what was hosing my earlier attempts. Appreciate the pointer very much.
Will give this a go.
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
On 9/5/2017 3:39 PM, techlist06 wrote:
> Just what I was hoping for, the easy button. Thank you.
>
> What about the one (valid) sender I want to prevent? I've got a IMAP
> account setup for spam reporting, I want to be sure no one who has access to
> it sends anything from that account.
>
>
>
Just what I was hoping for, the easy button. Thank you.
What about the one (valid) sender I want to prevent? I've got a IMAP
account setup for spam reporting, I want to be sure no one who has access to
it sends anything from that account.
--
Sent from: http://postfix.1071664.n5.nabble.com/
ts send via TLS authentication on 587. Currently I don't
> think I have any restrictions on what an outbound address can be. I do have
> some aliases so I do not want to restrict to logon names only.
>
> Is it possible to restrict outgoing mail to be from one of my "val
think
I have any restrictions on what an outbound address can be. I do have some
aliases so I do not want to restrict to logon names only.
Is it possible to restrict outgoing mail to be from one of my "valid" local or
virtual aliases? And I want to restrict outbound from one address
> My understanding is that packet radio has been allowed in part of the
> HAM band and in part of the Marine SSB band for quite a long time.
>
> Curtis
That's correct Curtis. In fact, worldwide electronic mail was possible with
packet and the worldwide BBS network long before commercial Interne
In message <20160716192156.09767350@kendramatic>
jdebert writes:
>
> On Sat, 16 Jul 2016 11:42:44 -0400
> Yuval Levy wrote:
>
> > It is indeed a matter of interpretation, and I would like to see the
> > FCC rules text. Questions:
> > (1) how do they define "encrypted"?
>
> The rules and regu
Am 16.07.16 21:30 schrieb(en) Sebastian Nielsen:
You could use iptables to look for:
"--BEGIN"
"--END"
"/signed"
"/encrypted"
"/pkcs7"
"/pgp"
Anywhere in the packet. In that case, you drop the connection, send a RST
IMO this is too restrictive as it would produce false positives, e.g. for you
On Sat, 16 Jul 2016 11:42:44 -0400
Yuval Levy wrote:
> It is indeed a matter of interpretation, and I would like to see the
> FCC rules text. Questions:
> (1) how do they define "encrypted"?
The rules and regulations are very clear on what is permitted. They do
not need to define anything else.
> You could use iptables to look for:
> "--BEGIN"
> "--END"
> "/signed"
> "/encrypted"
> "/pkcs7"
> "/pgp"
Thanks to all. I've got enough to get me started with my homework. Lots to
learn.
Regards,
Michael
The problem you got, is that the encrypted content has already travelled the
amateur frequencies even if you block/reject the mail.
Thus the rules are already broken, thus you should deal with those users in
a "AUP" way even if the mail gets blocked. Better might be to block this in
firewall then.
> On Jul 16, 2016, at 11:11, Erwan David wrote:
>
>> Le 16/07/2016 à 19:04, Jan Ceuleers a écrit :
>>> On 16/07/16 17:42, Yuval Levy wrote:
>>> Imposing the onus on the SMTP server operator is like imposing the onus
>>> on gas stations for fueling vehicles used in criminal endeavors. It
>>> doe
Michael Fox:
> > So, are there other obvious ways to recognize encrypted contents, other
> than
> > "Content-Type: multipart/encrypted"?
Albrecht:
> Basically, you need to check for
> - OpenPGP/Inline (inspect every body, see rfc 2440, sect. 6.2)
> - OpenPGP/Mime (multipart/encrypted, see rfc 3156
Le 16/07/2016 à 19:04, Jan Ceuleers a écrit :
> On 16/07/16 17:42, Yuval Levy wrote:
>> Imposing the onus on the SMTP server operator is like imposing the onus
>> on gas stations for fueling vehicles used in criminal endeavors. It
>> does not fly because the gas station can't possibly know what th
On 16/07/16 17:42, Yuval Levy wrote:
> Imposing the onus on the SMTP server operator is like imposing the onus
> on gas stations for fueling vehicles used in criminal endeavors. It
> does not fly because the gas station can't possibly know what the user
> will use the vehicle for, other than (prob
(Non-US) lawyer here, chiming in after the itch became to strong.
Initially I wanted to stay out of this debate, the solution of which is
obviously non-technical and probably OT.
DISCLAIMER: THE FOLLOWING IS NOT LEGAL ADVICE.
On 16-07-16 11:04 AM, /dev/rob0 wrote:
> You have already discarded STA
Le 16/07/2016 à 16:49, Jan Ceuleers a écrit :
> On 16/07/16 15:59, Michael Fox wrote:
>> So, are there other obvious ways to recognize encrypted contents, other than
>> "Content-Type: multipart/encrypted"?
> Theoretical (and therefore possibly entirely impractical) answer:
>
> Encrypted data contai
say in email, "... is not the arrow beyond thee?" (KJV, 1 Samuel
20:37.) That could contain a hidden message.
Don't let them push you down this slippery slope. If you are really
worried about it, call the FCC or a private attorney and get a solid
interpretation.
> I'd l
On 16/07/16 15:59, Michael Fox wrote:
> So, are there other obvious ways to recognize encrypted contents, other than
> "Content-Type: multipart/encrypted"?
Theoretical (and therefore possibly entirely impractical) answer:
Encrypted data contains a high amount of entropy, meaning that it does
not
Le 16/07/2016 à 16:39, Phil Stracchino a écrit :
> On 07/16/16 10:32, Albrecht Dreß wrote:
>> Am 16.07.16 15:59 schrieb(en) Michael Fox:
>>> So, are there other obvious ways to recognize encrypted contents, other than
>>> "Content-Type: multipart/encrypted"?
>> Basically, you need to check for
>> -
On 07/16/16 10:32, Albrecht Dreß wrote:
> Am 16.07.16 15:59 schrieb(en) Michael Fox:
>> So, are there other obvious ways to recognize encrypted contents, other than
>> "Content-Type: multipart/encrypted"?
>
> Basically, you need to check for
> - OpenPGP/Inline (inspect every body, see rfc 2440, se
Am 16.07.16 15:59 schrieb(en) Michael Fox:
So, are there other obvious ways to recognize encrypted contents, other than
"Content-Type: multipart/encrypted"?
Basically, you need to check for
- OpenPGP/Inline (inspect every body, see rfc 2440, sect. 6.2)
- OpenPGP/Mime (multipart/encrypted, see r
> minimize it with some filtering for the obvious cases
> as you propose.
Thanks Marco. I hadn't thought of some of those cases.
But I would still like to block the obvious cases, as you say.
So, are there other obvious ways to recognize encrypted contents, other than
"Content-Type: multipart/
cies. Some of our clients may connect via amateur radio.
>
> I'd like to be able to restrict it only for certain clients. But, as I
> understand it, header checks can only be applied globally, to all mail.
>
> Sorry if this is a dumb question. But, unfortunately, I don't ha
I'd like to be able to reject mail that contains encrypted content. This is
to satisfy US FCC rules against encrypted content on amateur radio
frequencies. Some of our clients may connect via amateur radio.
I'd like to be able to restrict it only for certain clients. But, as I
und
I run some front end servers, transporting a bunch of domains, but I'd
like to restrict the access to users existing on the server itself
(u...@mailserver.domain.tld). E.g. only accessible from localhost.
There are no IMAP or POP servers present, just Postfix.
1) which consequences has s
On 7/23/2015 6:38 AM, Istvan Prosinger wrote:
> Wietse,
>
> thanks, but let me make it more clear - I'm not trying to limit the
> number of emails towards the destination domains (like yahoo.com),
> but from the domains the server is sending from (sender domains).
>
> The idea behind this is not
Wietse,
thanks, but let me make it more clear - I'm not trying to limit the
number of emails towards the destination domains (like yahoo.com), but
from the domains the server is sending from (sender domains).
The idea behind this is not a "polite delivery policy" towards the other
servers, b
Istvan Prosinger:
> Hi everyone,
>
> Can anyone pinpoint me to a simple way to limit the outgoing number of
> emails in a time frame per domain, without involving policyd and mysql,
> or any other 3rd party script?
http://www.postfix.org/postconf.5.html#transport_destination_rate_delay
http://w
On Thu, 23 Jul 2015 10:47:25 +0200
Istvan Prosinger wrote:
> Can anyone pinpoint me to a simple way to limit the outgoing number
> of emails in a time frame per domain, without involving policyd and
> mysql, or any other 3rd party script?
>
> I'm looking for a simple restriction with a hash tabl
Hi everyone,
Can anyone pinpoint me to a simple way to limit the outgoing number of
emails in a time frame per domain, without involving policyd and mysql,
or any other 3rd party script?
I'm looking for a simple restriction with a hash table or so.
Best Regards,
Istvan
On Sun, Jun 21, 2015, at 08:19 PM, Noel Jones wrote:
> For local addresses, use an alias maps entry to pipe the mail to a
> program during local delivery.
>
> main.cf
> alias_maps = hash:/path/aliases
>
> # aliases
> spam: | /path/spam
> ham: | /path/ham
It's made no difference here; still
On 6/21/2015 6:55 PM, PGNd wrote:
> On Sun, Jun 21, 2015, at 03:15 PM, PGNd wrote:
>> The link references will surely provide the solution; just not obvious quite
>> yet.
>
> Attempting to design a config for mail sent from backend valid user
> (us...@1.com) to 'spam@' address on frontend, s
On Sun, Jun 21, 2015, at 03:15 PM, PGNd wrote:
> The link references will surely provide the solution; just not obvious quite
> yet.
Attempting to design a config for mail sent from backend valid user
(us...@1.com) to 'spam@' address on frontend, specifically to
"spam.1...@mail..com" to
On Sat, Jun 20, 2015, at 04:15 PM, Noel Jones wrote:
> > should do the trick. (?)
> Yes, that should work as expected.
> > Still ok here?
> That's fine. This doesn't have any direct effect on rejecting unknown users.
Appreciate the confirmations.
> > Suggest that I need the spam.1234@ and ha
On 6/19/2015 11:05 PM, PGNd wrote:
>
>
> On Fri, Jun 19, 2015, at 06:44 PM, Noel Jones wrote:
>> You can control it with a check_recipient_access map in place of
>> your blanket reject_unverified_recipient.
>
> Ah.
>
> My goal is:
>
> -- for {spam,ham}.1...@mail..com accept & pipe to
On Fri, Jun 19, 2015, at 06:44 PM, Noel Jones wrote:
> You can control it with a check_recipient_access map in place of
> your blanket reject_unverified_recipient.
Ah.
My goal is:
-- for {spam,ham}.1...@mail..com accept & pipe to FILTER
'sa-spam'/'sa-ham', respectively
--
...
>
> Message relay is correctly restricted to the 'relay_domains' list.
>
> OTOH, remote recipient verification probes are allowed/executed for both mail
> sent to user@
>
> -- the 'relay' domains list
> -- the canonical domain,
bes are allowed/executed for both mail
sent to user@
-- the 'relay' domains list
-- the canonical domain, .com
.com is local-only; it's NOT hosted at the remote backend.
How do I correctly restrict/prevent remote address verification probes being
executed for the canonical domain?
: Tuesday, February 17, 2015 1:09 PM
To: postfix-users@postfix.org
Subject: Re: smtpd_recipient_restrictions to restrict outbound email to
selected domains
On Tue, Feb 17, 2015 at 07:03:39PM +, Steve Zeng wrote:
> Thanks for the hint. The transport map seems do the trick...
>
> /et
On Tue, Feb 17, 2015 at 07:03:39PM +, Steve Zeng wrote:
> Thanks for the hint. The transport map seems do the trick...
>
> /etc/postfix/main.cf
> transport_maps = hash:/etc/postfix/transport
>
> /etc/postfix/transport
> mypartnerorg.com :
> mycompany.com :
> *
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Viktor Dukhovni
Sent: Tuesday, February 17, 2015 10:48 AM
To: postfix-users@postfix.org
Subject: Re: smtpd_recipient_restrictions to restrict outbound email to
selected domains
On Tue
On Tue, Feb 17, 2015 at 06:35:11PM +, Steve Zeng wrote:
> > Via SMTP from outside, or via sendmail(1) locally?
>
> I run mail locally as below:
> mail -s "hotmail" myusern...@hotmail.com < /etc/hosts
Well, smtpd(8) restrictions don't apply to locally submitted email.
I generally configure t
strictions to restrict outbound email to
selected domains
Thanks, Viktor.
> Via SMTP from outside, or via sendmail(1) locally?
I run mail locally as below:
mail -s "hotmail" myusern...@hotmail.com<mailto:myusern...@hotmail.com> <
/etc/hosts
>You'll need to
...@postfix.org]
On Behalf Of Viktor Dukhovni
Sent: Monday, February 16, 2015 5:16 PM
To: postfix-users@postfix.org
Subject: Re: smtpd_recipient_restrictions to restrict outbound email to
selected domains
On Tue, Feb 17, 2015 at 12:48:45AM +, Steve Zeng wrote:
> I am running postfix 2.3
On Tue, Feb 17, 2015 at 12:48:45AM +, Steve Zeng wrote:
> I am running postfix 2.3.3 on Redhat RHEL 5 for a local SMTP MTA. For
> security purpose, we need to restrict its outbound emails to selected
> destination domains only.
>
> http://www.postfix.org/
Greetings!
I am running postfix 2.3.3 on Redhat RHEL 5 for a local SMTP MTA. For security
purpose, we need to restrict its outbound emails to selected destination
domains only.
http://www.postfix.org/postconf.5.html#smtpd_recipient_restrictions
The default is:
smtpd_recipient_restrictions
+1 for imapsync, as we use it extensively when migrating a new customer
onto our servers and they have a slew of email stored with their old
provider that can't be left behind.
On Nov 19, 2014 7:49 AM, "Mikael Bak" wrote:
> Hi,
>
> On 11/19/2014 03:27 AM, Joe Acquisto-j4 wrote:
> [snip]
>
>> I wa
Hi,
On 11/19/2014 03:27 AM, Joe Acquisto-j4 wrote:
[snip]
I was daydreaming about ways to get messages from the old system to the
new one, as might be required. For a bit it seemed feasible to cobble up
something to allow messages to be sent via SMTP from the old system
to the new, in a contro
>>> On 11/18/2014 at 4:02 PM, Wietse Venema wrote:
I mis-stated the situation. Allow me to attempt to restate.
There will be no address translation involved at all. The email address both
user and domain will remain the same. The current system will be "retired"
to an "off line" status yet t
1 - 100 of 332 matches
Mail list logo
