If RoundRobin is best practise/preferred solution, should I then do:
; zone file fragment
IN MX 10 mail.example.com.
mailIN A 192.168.0.4
IN A 192.168.0.5
IN A 192.168.0.6
or
; zone file fragment
IN MX 10 mail.example.com.
I
I have an odd requirement of redirecting info@ for a reasonable
large number of domains to i...@example.com. Figured
this could be done with 2.7.1 using:
virtual_alias_domains = pcre:${config_directory}/virtual_alias_domains
/.*/ anything
virtual_alias_maps = pcre:${config_directory}/virtual_al
On 2012-03-09 8:04 PM, Romans Malinovskis wrote:
I must have mentioned that the demo is running here:
http://postfixadmin.agiletoolkit.org
Have a nice weekend everyone.
Ummm... postfixadmin already exists, is very mature, and works well for
many. Why reinvent the wheel? Regardless, you need
Le 2012-03-10 05:46, The_Ace a écrit :
2012/3/10 ml
Le samedi 10 mars 2012 à 09:28 +0530, The_Ace a écrit :
On Thu, Mar 8, 2012 at 12:32 PM, Nikolaos Milas
wrote:
> On 8/3/2012 6:40 πμ, Eero Volotinen wrote:
>
> What is the best / reliable site to find newer
postfi
On 3/10/12, Noel Butler wrote:
> On Sat, 2012-03-10 at 11:08 +1000, Nick Edwards wrote:
>
>> On 3/10/12, Reindl Harald wrote:
>
>> > what type of entries are you using in your SPF record?
>> > i found out that a/mx entries sometimes making troubles and since
>> > we changed our backend to use onl
Allan Wind:
> I have an odd requirement of redirecting info@ for a reasonable
> large number of domains to i...@example.com. Figured
> this could be done with 2.7.1 using:
>
> virtual_alias_domains = pcre:${config_directory}/virtual_alias_domains
>
> /.*/ anything
This makes all domain names a
>> I must have mentioned that the demo is running here:
>>
>> http://postfixadmin.agiletoolkit.org
>>
>> Have a nice weekend everyone.
>
> Ummm... postfixadmin already exists, is very mature, and works well for many.
> Why reinvent the wheel? Regardless, you need to use a different name…
I nee
On 2012-03-10 7:46 AM, Romans Malinovskis wrote:
Ummm... postfixadmin already exists, is very mature, and works
wellfor many. Why reinvent the wheel? Regardless, you need to use a
different name…
I needed to customize and it’s very difficult to do so with
postfixadmin.
>
It worked well out
> There is already a plan to allow for very easy customization by allowing you
> to add custom fields that will not be zapped by upgrades:
>
> https://sourceforge.net/tracker/?func=detail&aid=2686461&group_id=191583&atid=937967
>
> Maybe you could consider working on that instead?
I am not very
Michael Maymann:
> If RoundRobin is best practise/preferred solution, should I then do:
>
> ; zone file fragment
> IN MX 10 mail.example.com.
>
> mailIN A 192.168.0.4
> IN A 192.168.0.5
> IN A 192.168.0.6
>
> or
>
> ; zone file fragment
>
On Sat, Mar 10, 2012 at 01:05:48PM +,
Romans Malinovskis wrote:
> > regardless, you still need to use something other than
> > postfixadmin.agiletoolkit.org for the name.
>
> Im open for suggestions. It’s juts an experiment for now.
Consider that postfixadmin is itself a misnomer: it is a
Hi,
Wietse: thanks for your quick reply :) !
We have the following internal clients:
- R&D Linux sendmail clients
- some special_home_brew websolutions that endusers maintain
- NetApp storage systems
- etc.
Mail path:
Internal_clients->my_postfix_mailrelay(s)->external_receiving_mailserver
We're
Michael Maymann:
> How do I best setup a loadshared failover postfix mailrelay solution for
> this on RHEL6 ?
To repeat my previous response:
- MX records are useful only for MTAs.
- If you have end-user clients, use A records.
Perhaps surprisingly, that response still stands. The mail protocol
On Sat, Mar 10, 2012 at 05:25:05AM -0500, Allan Wind wrote:
> I have an odd requirement of redirecting info@ for a reasonable
> large number of domains to i...@example.com.
Wietse has already answered about the problem you made, but I have
some things to add. First, WHY are you doing this? Why al
Den 2012-03-10 13:46, Romans Malinovskis skrev:
Without reinventing the wheel, you don’t get to fly.
+1
wishes from me:
roundcube plugin, not a new login page pr user
dspam support
amavisd support
where is the paypal account ?
Den 2012-03-10 09:47, Michael Maymann skrev:
; zone file fragment
IN MX 10 mail.example.com.
mail IN A 192.168.0.4
IN A 192.168.0.5
IN A 192.168.0.6
dont list rfc1918 ip in mx, but if its just a question on model, go for
this solution
Hi all,
I am currently running into some issues with Postfix on my Amazon EC2
instance, not talking to OpenDKIM milter (also running on the same box).
I believe Postfix isn't following smtpd_milters/non_smtpd_milters
parameters. The reason is that no matter what port number I use (even
non-wo
On 2012-03-10 07:25:42, Wietse Venema wrote:
> No surprise, that mail delivery fails: all your domains are hijacked
> by the virtual_alias_domains address class, and you define only one
> user name there.
>
> See: http://www.postfix.org/ADDRESS_CLASS_README.html
I read over this a few times befor
On 3/10/2012 9:57 AM, Antony wrote:
> Hi all,
>
> I am currently running into some issues with Postfix on my Amazon
> EC2 instance, not talking to OpenDKIM milter (also running on the
> same box). I believe Postfix isn't following
> smtpd_milters/non_smtpd_milters parameters. The reason is that no
On 3/10/2012 10:29 AM, Allan Wind wrote:
> On 2012-03-10 07:25:42, Wietse Venema wrote:
>> No surprise, that mail delivery fails: all your domains are hijacked
>> by the virtual_alias_domains address class, and you define only one
>> user name there.
>>
>> See: http://www.postfix.org/ADDRESS_CLASS_
Noel,
Thank you. It confirms the theory that postfix is not aware of the
settings for smtpd_milters
~$ sudo postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
default_transport = aws-email
inet_protoco
On 3/10/2012 11:20 AM, Antony wrote:
> Noel,
>
> Thank you. It confirms the theory that postfix is not aware of the
> settings for smtpd_milters
> ~$ sudo postconf -n
> relayhost = email-smtp.us-east-1.amazonaws.com
Typically (but not always) the relayhost should be enclosed in
brackets "[...]"
Noel,
Yes, thank you! I shouldn't have used vim to edit the file directly. Had
I used postconf -e, it would have save me the pain.
Mar 10 18:15:29 ip-x postfix/master[2468]: terminating on signal 15
Mar 10 18:15:29 ip-x postfix/master[3086]: daemon started -- version
2.7.0, configurat
Greetings and thanks for reading,
My question pertains to re-writing headers for addressed that are
aliased to other addresses in /etc/aliases. Background information:
* Company with a global IT staff. We install several servers a week.
They are Debian or CentOS. On these systems, in /etc/
Hi,
Wietse: always nice with a bit of humor... :) !
I guess I then only need A records, as this will be our only mailserver
inhouse for R&D.
Benny: I guess this is not needed then, but just out of curiosity: for a
internal sending-only mailrelay why can't I use RFC1918 IPs ?
1. Is best practice t
Andy Wolfenstein:
> Greetings and thanks for reading,
>
> My question pertains to re-writing headers for addressed that are
> aliased to other addresses in /etc/aliases. Background information:
Postfix is an MTA, not a content-management system, therefore it
does not directly support header rewr
On 2012-03-10 09:17:25, /dev/rob0 wrote:
> Wietse has already answered about the problem you made, but I have
> some things to add. First, WHY are you doing this? Why all domains
> and why only info@? This does not make much sense.
I was seeing if there was a way to avoid having to maintain a
l
Am 10.03.2012 02:08, schrieb Nick Edwards:
>> thelounge.net. 86400 IN SPF "v=spf1 ip4:91.118.73.15
>> ip4:91.118.73.20 ip4:91.118.73.17
>> ip4:91.118.73.6 ip4:91.118.73.32 ip4:91.118.73.38 ip4:91.118.73.30
>> ip4:91.118.73.1 ip4:89.207.144.27 -all"
>>
>> thelounge.net.
Reindl Harald wrote:
>
>
>Am 10.03.2012 02:08, schrieb Nick Edwards:
>>> thelounge.net. 86400 IN SPF "v=spf1
>ip4:91.118.73.15
>>> ip4:91.118.73.20 ip4:91.118.73.17
>>> ip4:91.118.73.6 ip4:91.118.73.32 ip4:91.118.73.38 ip4:91.118.73.30
>>> ip4:91.118.73.1 ip4:89.207.144.27 -
29 matches
Mail list logo
