On 9/9/2011 5:52 μμ, jeffrey j donovan wrote:
use local recipient map for your local users and transport maps for the
delivery of others. You will have to tell amavisd how to relay local and remote.
do what Weiste said and allow programs to relay mail via localhost.
Thanks Jeffrey,
I guess w
On Sep 9, 2011, at 10:28 AM, Nikolaos Milas wrote:
> On 9/9/2011 3:14 μμ, Nikolaos Milas wrote:
>
>> Since this is just a relay, mail is not stored locally;
>> ...
>> So I was thinking I should configure postfix/spamassassin to keep local
>> copies of spam (to be also available for checking usi
On 9/9/2011 3:14 μμ, Nikolaos Milas wrote:
Since this is just a relay, mail is not stored locally;
...
So I was thinking I should configure postfix/spamassassin to keep
local copies of spam (to be also available for checking using IMAP)
and non-spam mail so as to make training feasible.
Can
Nikolaos Milas:
> On 9/9/2011 4:00 ??, Wietse Venema wrote:
>
> > If you don't use permit_mynetworks at all (check with: "postconf |
> > grep permit_mynetworks"), then mynetworks can be empty.
>
> Thanks Wietsie,
>
> mynetworks = 127.0.0.1/32 [::1]/128
>
> seems the right solution.
>
> In fac
On 9/9/2011 4:00 μμ, Wietse Venema wrote:
If you don't use permit_mynetworks at all (check with: "postconf |
grep permit_mynetworks"), then mynetworks can be empty.
Thanks Wietsie,
mynetworks = 127.0.0.1/32 [::1]/128
seems the right solution.
In fact I am using permit_mynetworks as the firs
Nikolaos Milas:
> Also, to disable sending outgoing mails from this server (which is only
> there to receive mail from the Internet as MX-designated mail server and
> work as a local relay to internal mail server) I am planning to use the
> setting:
>
> mynetworks =
>
> Would this have a
Thanks to Noel (and to the Postfix community in general) for the
guidance, my mail gateway is now running (still in test mode), together
with spamassassin, clamav and amavis-new.
Now, one more thing:
Since this is just a relay, mail is not stored locally; yet, I would
like to train spamassass
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/5/2011 7:26 AM, Nikolaos Milas wrote:
> On 3/9/2011 11:09 μμ, Noel Jones wrote: So, in order to
> implement such a solution, would it be sufficient to do
> something like the following, on the *gateway* mail server:
>
> smtpd_recipient_restrictio
On 5/9/2011 3:26 μμ, Nikolaos Milas wrote:
So, in order to implement such a solution, would it be sufficient to
do something like the following, on the *gateway* mail server:
smtpd_recipient_restrictions =
permit_mynetworks, reject_unverified_recipient,
reject_unauth_destina
On 3/9/2011 11:09 μμ, Noel Jones wrote:
If we use:
relay_recipient_maps =
(that is, empty) then *all* recipients for the hosted domains (those
listed in relay_domains) are accepted/forwarded?
Yes. That turns you into a backscatter source, clogging your queue
with undeliverable mail and ev
On 9/3/2011 2:52 PM, Nikolaos Milas wrote:
> On 3/9/2011 10:10 μμ, Noel Jones wrote:
>
>> Yes, although you may want to use relay: rather than smtp: as the
>> transport name. The different name allows postfix to more
>> efficiently schedule delivery for those domains, and allows you to
>> use diff
On 3/9/2011 10:10 μμ, Noel Jones wrote:
Yes, although you may want to use relay: rather than smtp: as the
transport name. The different name allows postfix to more efficiently
schedule delivery for those domains, and allows you to use different
relay delivery settings if needed. -- Noel Jones
On 9/3/2011 1:52 PM, Nikolaos Milas wrote:
> On 3/9/2011 9:41 μμ, Noel Jones wrote:
>
>> To accept mail for specified subdomains, add those domains to the
>> relay_domains parameter. This is the recommended solution.
>
> Thanks Noel,
>
> And to route incoming mails to different mail servers wou
On 3/9/2011 9:41 μμ, Noel Jones wrote:
To accept mail for specified subdomains, add those domains to the
relay_domains parameter. This is the recommended solution.
Thanks Noel,
And to route incoming mails to different mail servers would we use:
transport_maps = hash:/etc/postfix/transpor
On 9/3/2011 1:31 PM, Nikolaos Milas wrote:
> On 18/2/2011 6:48 μμ, Victor Duchovni wrote:
>
>> On Fri, Feb 18, 2011 at 06:43:28PM +0200, Nikolaos Milas wrote:
>>
>>> What is the suggested way to configure Postfix to play this role,
>>> i.e. to
>>> simply send all incoming (clean, after filtering)
On 18/2/2011 6:48 μμ, Victor Duchovni wrote:
On Fri, Feb 18, 2011 at 06:43:28PM +0200, Nikolaos Milas wrote:
What is the suggested way to configure Postfix to play this role, i.e. to
simply send all incoming (clean, after filtering) mail to another mail
server?
http://www.postfix.org/STA
Am 18.02.2011 18:55, schrieb Swapnil Bhaigude // Viva:
> how do I pass dkim-milter in postfix
can you please stop hijacking others threads with
your questions and without any usefull information?
signature.asc
Description: OpenPGP digital signature
how do I pass dkim-milter in postfix
On Fri, Feb 18, 2011 at 06:43:28PM +0200, Nikolaos Milas wrote:
> What is the suggested way to configure Postfix to play this role, i.e. to
> simply send all incoming (clean, after filtering) mail to another mail
> server?
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall
Hi,
Our mail server (vmail.example.com) uses Postfix (with ldap backend for
table lookups). However, in our domain (example.com) mail is always
reaching us through a gateway (which is defined as an MX for our
domain), say mailgw.example.com. This is a mail appliance (Cisco
Ironport) which fil
20 matches
Mail list logo
