September 2011 - infrastructure - Fedora mailing-lists

ssh private keys on our systems
by Seth Vidal 20 Oct '11

20 Oct '11

Hi, I'd like to put a new policy in place which goes something like this: If you upload your private keys (encrypted or not) we will remove them, then we will remove your public keys from FAS and force you to login and give a new one in FAS. We do the last step on the basis that your private key, being on a networked, multi-user machine is now exposed to the world and potentially compromised. So we can no longer trust it. thoughts? Thanks, -sv

13 20

REMINDER: Beta Prerelease Change Freeze
by Kevin Fenzi 05 Oct '11

05 Oct '11

Just a reminder we have now entered into Beta pre-release freeze. Per: http://infrastructure.fedoraproject.org/infra/docs/release-infra.txt All machines/instances in the 'pre release' freeze: https://fedorahosted.org/fedora-infrastructure/browser/architecture/Environ… All changes to these machines require 2 +1's from rel-eng or sysadmin-main after being reviewed on this list. This freeze is over 2011-09-27 (unless Beta slips, then it's over when Beta is released). kevin

1 1

Email sending delays and archiving delays for aeolus-devel@lists.fedorahosted.org
by Chris Alfonso 29 Sep '11

29 Sep '11

Hello, The aeolus project development team is consistently seeing long delays (hours) when sending email to aeolus-devel(a)lists.fedorahosted.org. We are also seeing the archives lag by a couple days. Do any of you know of relay or archiving issues? If not, is there anyone that can look into the issue? Let me know if you need more information. Thanks, Chris

2 1

Meeting Agenda Item: Introduction Ramon Almeida
by Ramon Almeida 29 Sep '11

29 Sep '11

Hello, I am Ramon Almeida of Brazil / Bahia and want to help with system administration on servers fedora. Follows standard answers to the questionnaire. * IRC Channels -> #fedora-br , #fedora-ambassadors, #fedora-admin Ircname -> Mufiu or Mufius * Skills -Programming shellscript,perl,c++ -Services postfix,exim,qmail,zimbra,cpanel,mediawiki,apache,php... iptables,openvpn,ldap,mysql,postgresql... * Want learn more about services and programming languages. * Want to help in service and script's that i know Think this is it.

3 2

Plan for tomorrow's Fedora Infrastructure meeting (2011-09-29)
by Kevin Fenzi 29 Sep '11

29 Sep '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-09-29 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * Password/Ssh-key/Cert reset flag day discussion. * Upcoming Tasks/Items (nirik) 2011-09-13 - 2011-10-04: Beta change freeze 2011-10-01 mail fi-apprentice folks. 2011-10-04: Fedora 16 Beta 2011-10-09 Remove inactive fi-apprentice people. 2011-10-25 - 2011-11-08: Final change freeze 2011-11-01 mail fi-apprentice folks. 2011-11-08: Fedora 16 release. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/report/10 * Request for Resources progress report - askfedora - paste Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

[PATCH] disable procmail as the mailbox command all over the place since we do not do any local delivery at all.
by Seth Vidal 27 Sep '11

27 Sep '11

From: Seth Vidal <skvidal(a)fedoraproject.org> --- modules/postfix/files/main.cf/main.cf | 2 +- .../main.cf/main.cf.collab1.fedoraproject.org | 2 +- .../main.cf.compose-x86-01.phx2.fedoraproject.org | 2 +- .../main.cf/main.cf.hosted1.fedoraproject.org | 2 +- .../main.cf.insight01.stg.phx2.fedoraproject.org | 2 +- modules/postfix/files/main.cf/main.cf.phx | 2 +- modules/postfix/files/main.cf/main.cf.stg | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/modules/postfix/files/main.cf/main.cf b/modules/postfix/files/main.cf/main.cf index 0e502d2..c0b9306 100644 --- a/modules/postfix/files/main.cf/main.cf +++ b/modules/postfix/files/main.cf/main.cf @@ -447,7 +447,7 @@ recipient_delimiter = + # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. # -mailbox_command = /usr/bin/procmail +#mailbox_command = /usr/bin/procmail #mailbox_command = /some/where/procmail -a "$EXTENSION" # The mailbox_transport specifies the optional transport in master.cf diff --git a/modules/postfix/files/main.cf/main.cf.collab1.fedoraproject.org b/modules/postfix/files/main.cf/main.cf.collab1.fedoraproject.org index 0d0c15d..a13b490 100644 --- a/modules/postfix/files/main.cf/main.cf.collab1.fedoraproject.org +++ b/modules/postfix/files/main.cf/main.cf.collab1.fedoraproject.org @@ -448,7 +448,7 @@ recipient_delimiter = + # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. # -mailbox_command = /usr/bin/procmail +#mailbox_command = /usr/bin/procmail #mailbox_command = /some/where/procmail -a "$EXTENSION" # The mailbox_transport specifies the optional transport in master.cf diff --git a/modules/postfix/files/main.cf/main.cf.compose-x86-01.phx2.fedoraproject.o… b/modules/postfix/files/main.cf/main.cf.compose-x86-01.phx2.fedoraproject.o… index 405b067..d334bfd 100644 --- a/modules/postfix/files/main.cf/main.cf.compose-x86-01.phx2.fedoraproject.o… +++ b/modules/postfix/files/main.cf/main.cf.compose-x86-01.phx2.fedoraproject.o… @@ -447,7 +447,7 @@ recipient_delimiter = + # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. # -mailbox_command = /usr/bin/procmail +#mailbox_command = /usr/bin/procmail #mailbox_command = /some/where/procmail -a "$EXTENSION" # The mailbox_transport specifies the optional transport in master.cf diff --git a/modules/postfix/files/main.cf/main.cf.hosted1.fedoraproject.org b/modules/postfix/files/main.cf/main.cf.hosted1.fedoraproject.org index 3f1d481..2c8edf0 100644 --- a/modules/postfix/files/main.cf/main.cf.hosted1.fedoraproject.org +++ b/modules/postfix/files/main.cf/main.cf.hosted1.fedoraproject.org @@ -448,7 +448,7 @@ recipient_delimiter = + # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. # -mailbox_command = /usr/bin/procmail +#mailbox_command = /usr/bin/procmail #mailbox_command = /some/where/procmail -a "$EXTENSION" # The mailbox_transport specifies the optional transport in master.cf diff --git a/modules/postfix/files/main.cf/main.cf.insight01.stg.phx2.fedoraproject.org b/modules/postfix/files/main.cf/main.cf.insight01.stg.phx2.fedoraproject.org index 1f2c730..0d97a5d 100644 --- a/modules/postfix/files/main.cf/main.cf.insight01.stg.phx2.fedoraproject.org +++ b/modules/postfix/files/main.cf/main.cf.insight01.stg.phx2.fedoraproject.org @@ -447,7 +447,7 @@ recipient_delimiter = + # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. # -mailbox_command = /usr/bin/procmail +#mailbox_command = /usr/bin/procmail #mailbox_command = /some/where/procmail -a "$EXTENSION" # The mailbox_transport specifies the optional transport in master.cf diff --git a/modules/postfix/files/main.cf/main.cf.phx b/modules/postfix/files/main.cf/main.cf.phx index 1707639..5e73448 100644 --- a/modules/postfix/files/main.cf/main.cf.phx +++ b/modules/postfix/files/main.cf/main.cf.phx @@ -447,7 +447,7 @@ recipient_delimiter = + # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. # -mailbox_command = /usr/bin/procmail +#mailbox_command = /usr/bin/procmail #mailbox_command = /some/where/procmail -a "$EXTENSION" # The mailbox_transport specifies the optional transport in master.cf diff --git a/modules/postfix/files/main.cf/main.cf.stg b/modules/postfix/files/main.cf/main.cf.stg index d250cdb..f364dc3 100644 --- a/modules/postfix/files/main.cf/main.cf.stg +++ b/modules/postfix/files/main.cf/main.cf.stg @@ -447,7 +447,7 @@ recipient_delimiter = + # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. # -mailbox_command = /usr/bin/procmail +#mailbox_command = /usr/bin/procmail #mailbox_command = /some/where/procmail -a "$EXTENSION" # The mailbox_transport specifies the optional transport in master.cf -- 1.7.2.1

3 2

My Introduction
by Abdel Gadiel Martínez Lassonde 26 Sep '11

26 Sep '11

Hello to all! My name is *Abdel Martínez* and I'm from *Panama*. I'm really interested in *participate* in *Infraestructure* *Team*. I love to *program* in *Java*and *Python*. I will *share* all my knowledge with you and learn (a lot) with this experience. I hope to be accepted. In advance, *thank you* a lot. -- *Abdel G. Martínez L. **Oracle Certified Associate, Java SE 5 and 6* ***Fedora Ambassador & Campus Ambassador* *Fedora Developer & Packager* *Celular: **6125-1563 **Correo Electrónico: * *abdel.g.martinez.l(a)gmail.com* <abdel.g.martinez.l(a)gmail.com>

1 0

freeze break request: ask01
by Kevin Fenzi 26 Sep '11

26 Sep '11

I'd like to setup a ask01 production instance this week. This entails adding it to dns, etc. Almost all of the changes don't affect our freeze, except one: I have to add the host to the phx service file, which affects frozen hosts. Here's the commit (along with new files under modules/askbot/ and a new node under manifests/nodes/ask01.phx2.fedoraproject.org.pp). comments welcome. kevin -- diff --git a/manifests/services/phx.pp b/manifests/services/phx.pp index 73aeb11..1fd24cd 100644 --- a/manifests/services/phx.pp +++ b/manifests/services/phx.pp @@ -154,6 +154,12 @@ class phx { host_aliases => ['git', 'svn.fedoraproject.org', 'svn', 'hg.fedoraproject.org', 'hg'], ensure => absent, } + host { 'ask01.fedoraproject.org': + ip => '10.5.126.79', + host_aliases => [ + 'ask01', + ] + } # we have gateway.phx2.fedoraproject.org now. #host { 'gateway.fedoraproject.org': # ip => '10.8.34.50', diff --git a/manifests/services/proxy.pp b/manifests/services/proxy.pp index b397bf5..bc8a591 100644 --- a/manifests/services/proxy.pp +++ b/manifests/services/proxy.pp @@ -345,6 +345,11 @@ class proxy { cert_name => "wildcard.fedoraproject.org", sSLCertificateChainFile => "wildcard.fedoraproject.org.intermediate.cert", } + httpd::website { "ask.fedoraproject.org": + ips => $wildcard_fpo_ips, + server_aliases => [ "ask.stg.fedoraproject.org" ], + ssl => false, + } httpd::mime-type { "site icon": website => "fedoraproject.org", @@ -352,6 +357,12 @@ class proxy { extensions => [ ".ico" ], } + askbot::proxy { "ask.fedoraproject.org": + website => "ask.fedoraproject.org", + path => "/", + proxyurl => "http://ask01", + } + fedora-web::proxy { "fedoraproject.org": website => "fedoraproject.org", } diff --git a/modules/bind/files/master/126.5.10.in-addr.arpa b/modules/bind/files/master/126.5.10.in-addr.arpa index a7c1bb2..12dc200 100644 --- a/modules/bind/files/master/126.5.10.in-addr.arpa +++ b/modules/bind/files/master/126.5.10.in-addr.arpa @@ -2,7 +2,7 @@ $TTL 86400 @ IN SOA 126.5.10.in-addr.arpa. hostmaster.fedoraproject.org. ( ; Make SURE to update the serial # when changes are made. Format is YYYYMMDDNN ; (NN is just a counter to handle multiple changes in one day). - 2011092202 ; Serial + 2011092301 ; Serial 28800 ; Refresh 14400 ; Retry 1000000 ; Expire @@ -82,7 +82,7 @@ $TTL 86400 76 IN PTR db05.phx2.fedoraproject.org. 77 IN PTR unused. 78 IN PTR unused. -79 IN PTR unused. +79 IN PTR ask01.phx2.fedoraproject.org. 80 IN PTR ask01.stg.phx2.fedoraproject.org. 81 IN PTR app01.stg.phx2.fedoraproject.org. 82 IN PTR app02.stg.phx2.fedoraproject.org. diff --git a/modules/bind/files/master/168.192.in-addr.arpa b/modules/bind/files/master/168.192.in-addr.arpa index 436bb70..adacffa 100644 --- a/modules/bind/files/master/168.192.in-addr.arpa +++ b/modules/bind/files/master/168.192.in-addr.arpa @@ -2,7 +2,7 @@ $TTL 86400 @ IN SOA 168.192.in-addr.arpa. hostmaster.fedoraproject.org. ( ; Make SURE to update the serial # when changes are made. Format is YYYYMMDDNN ; (NN is just a counter to handle multiple changes in one day). - 2011092201 ; Serial + 2011092301 ; Serial 3600 ; Refresh 600 ; Retry 1000000 ; Expire @@ -62,9 +62,9 @@ $TTL 86400 48.1 IN PTR bodhost01.vpn.fedoraproject.org. 49.1 IN PTR fas03.vpn.fedoraproject.org. 50.1 IN PTR unused. -51.1 IN PTR unused. +51.1 IN PTR ask01.vpn.fedoraproject.org. 52.1 IN PTR proxy07.vpn.fedoraproject.org. -53.1 IN PTR unused. +53.1 IN PTR db04.vpn.fedoraproject.org. 54.1 IN PTR memcached03.vpn.fedoraproject.org. 55.1 IN PTR db05.vpn.fedoraproject.org. 56.1 IN PTR log02.vpn.fedoraproject.org. diff --git a/modules/bind/files/master/fedoraproject.org b/modules/bind/files/master/fedoraproject.org index 5602c6c..f4c1b95 100644 --- a/modules/bind/files/master/fedoraproject.org +++ b/modules/bind/files/master/fedoraproject.org @@ -1,6 +1,6 @@ $TTL 3600 @ IN SOA ns01.fedoraproject.org. hostmaster.fedoraproject.org. ( - 2011092202 ; Serial + 2011092301 ; Serial 1H ; refresh 10M ; retry 4W ; expire @@ -78,6 +78,7 @@ app6 IN CNAME app06 archive IN CNAME secondary01 archives IN CNAME secondary01 astronomy IN CNAME wildcard +ask IN CNAME wildcard ask.stg IN A 209.132.181.14 autoqa IN A 209.132.181.29 autoqa-stg IN A 209.132.181.9 diff --git a/modules/bind/files/master/phx2.fedoraproject.org b/modules/bind/files/master/phx2.fedoraproject.org index 07f35f0..03ed2d5 100644 --- a/modules/bind/files/master/phx2.fedoraproject.org +++ b/modules/bind/files/master/phx2.fedoraproject.org @@ -11,6 +11,7 @@ $TTL 3600 @ IN NS ns03.phx2.fedoraproject.org. @ IN NS ns04.phx2.fedoraproject.org. +ask01 IN A 10.5.126.79 ask01.stg IN A 10.5.126.80 app01 IN A 10.5.126.31 app1 IN CNAME app01 diff --git a/modules/bind/files/master/vpn.fedoraproject.org b/modules/bind/files/master/vpn.fedoraproject.org index ca11118..202e36e 100644 --- a/modules/bind/files/master/vpn.fedoraproject.org +++ b/modules/bind/files/master/vpn.fedoraproject.org @@ -27,6 +27,7 @@ app06 IN A 192.168.1.24 app6 IN CNAME app06 app07 IN A 192.168.1.23 app7 IN CNAME app07 +ask01 IN A 192.168.1.51 asterisk01 IN A 192.168.1.34 asterisk1 IN CNAME asterisk01 asterisk02 IN A 192.168.1.36 @@ -47,10 +48,10 @@ collab01 IN A 192.168.1.21 collab1 IN CNAME collab01 collab02 IN A 192.168.1.37 collab2 IN CNAME collab02 -cstore01 IN A 192.168.1.50 -cstore1 IN CNAME cstore01 -cstore02 IN A 192.168.1.51 -cstore2 IN CNAME cstore02 +;cstore01 IN A 192.168.1.50 +;cstore1 IN CNAME cstore01 +;cstore02 IN A 192.168.1.51 +;cstore2 IN CNAME cstore02 db01 IN A 192.168.1.18 ;db02 IN A 192.168.1.19 ;db2 IN CNAME db02

3 2

Zarafa
by Kevin Fenzi 26 Sep '11

26 Sep '11

Greetings. I finally sat down and poked around with the current version of zarafa we have setup (7.0.0). Some observations: * It seems more responsive and nicer than the 6.x versions were. * There doesn't seem to be a way to disable features and just show the calendar that I can figure out. The email part is always there. ;( However, unless we have it set to send incoming emails there, it works fine for just sending calendar invites and the like. * The ical / caldav feeds seem to be there and working. Took a bit to find them, but they do work. * We can't enable z-push as it's non free, so thats no push for a bunch of mobile devices. * Calendars are per user. There is a group calendar feature, but it seems to not be available in the free version. So, I am thinking that if we don't want to offer mail hosting, zarafa isn't going to be something we want to support/deploy. The only one still getting email into it is Mike. I don't know if other folks are using the calendar or not, but we should check that. Any further thoughts or conclusions? Or should we set a sunset date? kevin

6 11

Meeting Agenda Item: Introduction Kishore Kumar
by Arichella, Kishore Kumar 22 Sep '11

22 Sep '11

Hello all, My name is Kishore Kumar. My IRC handle is KKA. I am currently working as a System administrator at a Social networking company. I have a 3+ years of experience and I hold 'Red Hat Enterprise Security: Network Services' as well as 'Red Hat Enterprise Virtualization' certifications. I am interested in helping out fedora infrastructure team. I have started learning Python but I have good knowledge in Shell and Perl scripting. I want to improve my skill set which I think I can gain them here. I am at GMT+5.30. Thanks, Kishore A

2 1

Production instance of Ask Fedora
by Rahul Sundaram 22 Sep '11

22 Sep '11

Hi I would like to do the soft launch of Ask Fedora before the end of this month and announce it widely in sync with Fedora 16 release. I will coordinate with Fedora marketing for this. The reason for doing a soft launch earlier is to be able to seed the forum with some good questions and answers and fix any last minute issues that might show up in a bit more larger use. upfiles alias in the httpd configuration for Askbot has been added via puppet for now. If the patch for fixing the duplicate subject in the email alerts is included as a hotfix, we can enable that. Currently I have disabled subject in the staging instance. The patch is here https://github.com/ASKBOT/askbot-devel/commit/dca33d4bdb002a1c882ba0b1f7952… Upstream is hoping to do a new release soon and these fixes will be rolled into the update then. I would like to try out varnish but that can wait for a while. I am still waiting on a logo from the Fedora design team but meanwhile have disabled the default logo in the settings as well. We have modified the CSS only lightly because upstream has contracted a professional designer to do a new theme and the format is expected to change quite a bit. Once that is done in say 2 to 3 weeks, I intend to get a Fedora theme done as well shortly after. Let me know your thoughts. Rahul

2 1

karichel@corp.untd.com
by Arichella, Kishore Kumar 22 Sep '11

22 Sep '11

-KKA

1 0

Plan for tomorrow's Fedora Infrastructure Meeting (2011-09-22)
by Kevin Fenzi 22 Sep '11

22 Sep '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-09-22 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * Beta freeze extending a week. * Password/Ssh-key/Cert reset flag day discussion. * Bastion outages/openvpn discussion. * Upcoming Tasks/Items (nirik) 2011-09-13 - 27: Beta change freeze 2011-09-27: Fedora 16 Beta 2011-10-01 mail fi-apprentice folks. 2011-10-09 Remove inactive fi-apprentice people. 2011-10-18 - 2011-11-01: Final change freeze 2011-11-01: Fedora 16 release. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/report/10 NOTE: I have cleaned out the ones that have been sitting around with this tag. Anytime anyone would like to discuss a ticket, just add the meeting keyword and we will get to it in this section. * Request for Resources progress report - askfedora - paste Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

Karem left a message for you...
by Sammy 21 Sep '11

21 Sep '11

Karem left a message for you... Its sender and content will be shown only to you and you can delete it at any time. You can instantly reply to it, using the message exchange system. To find out what's in the message, just follow this link: http://eu1.badoo.com/0247022633/in/MyFtVR-KoE8/?lang_id=3&m=21&mid=4e794e50… Some more patiently waiting folks: Tito (Cairo, Egypt) Tota (Cairo, Egypt) Shaimaa fekry (Cairo, Egypt) http://eu1.badoo.com/0247022633/in/MyFtVR-KoE8/?lang_id=3&m=21&mid=4e794e50… If the link in this message does not work, try copying and pasting it into your browser. This email is part of our delivery procedure for the message sent by Karem. If you have received this email by mistake, please ignore it. The message will be deleted soon. Have fun! The Badoo Team You have received this email, because a Badoo member has left a message for you on Badoo. This is a post-only mailing. Replies to this message are not monitored or answered. If you don't want to receive any more messages from Badoo, please notify us: http://eu1.badoo.com/impersonation.phtml?lang_id=3&mail_code=21&email=infra…

1 0

Freeze break request: bastion03 -> bastion01
by Stephen John Smoogen 20 Sep '11

20 Sep '11

We are having issues with the email gateway bastion03. In trying to resolve the issue we have built a bastion01 with RHEL-6 i686 versus RHEL-6 x86_64 and would like to switch over to it Steps: 1) Copy SSH keys from bastion03 to bastion01 2) Shutdown bastion03 3) Bring up bastion01 with required IP. 4) Test to see if the system core dumps. If the problem is resolved we are done. If the problem is not, we will move to RHEL-5 to replicate earlier bastion systems. -- Stephen J Smoogen. "The core skill of innovators is error recovery, not failure avoidance." Randy Nelson, President of Pixar University. "Let us be kind, one to another, for most of us are fighting a hard battle." -- Ian MacLaren

3 2

Meeting Agenda Item: Introduction Jonathan Nalley
by Jonathan Nalley 20 Sep '11

20 Sep '11

Hello all, my IRC handle is ke4zvu3, i'm in the Eastern time zone, and I also have a wiki page[1] setup. My skill set, most of which I have or still get to work with at $dayjob, would include but not be limited to (in no particular order) VMware (i.e. vSphere, Lab Manager, vCloud Director), PHP, NetApp SANs, various Apache implementations, Ci$co load balancers, various LDAP implementations, various radius servers, tacacs, RHEL, satellite & kickstart, mediawiki, JBoss, squid, a modicum of perl and bash scripting, BIND, mysql (booo), PostgreSQL, Nagios, SVN, postfix, sendmail, and mailman. I currently serve as a Systems Engineer role where I end up doing alot of R&D, PoC, and some documentation work. At various times in my $dayjob and overall career I've also toggled between serving in a sysadmin role of production and non-production systems. Infra seems to make prolific use of Puppet which is very exciting to see personally. I've helped implement/use Puppet on a contract job and in the end learned enough to know that there's so much more I have to learn. I'll actually be working more with KVM at $dayjob in the upcoming days and weeks which I'm pretty stoked about. Among other things, I look forward to learning more about the distributed nature of the infrastructure used at Fedora and to hear, see, and learn how awesomely you guys are using Puppet. For now I've currently blocked off about 5 - 7.5 hours per workweek to dedicate to Infra work. I've been hanging out in #fedora-admin and #fedora-noc off and on for several months now and plan to keep doing so on a more steady basis. I've also been in the marketing group for I think a couple releases or more now. I'm not 100% sure if I'm limited to choosing just one FIG to start off with[2], but based on the limited amount of info I know about each FIG, their relationships, lines of separation, division of labor, and what’s required to work on the tickets I referenced below, I would say maybe some or all of these: sysadmin-web sysadmin-hosted sysadmin-tools If I do need to narrow down my FIG selection, I may need to seek out info from the FIG leaders or others in Infra that can give guidance beyond what's described about them on the wiki[3]. >From looking at the trac list of active tickets[4], the following ones seemed like easy low hanging fruit that I would be interested in and capable of diving into and hopefully taking care of, pending conversations with the respective current ticket assignees: https://fedorahosted.org/fedora-infrastructure/ticket/1968 https://fedorahosted.org/fedora-infrastructure/ticket/504 https://fedorahosted.org/fedora-infrastructure/ticket/2816 https://fedorahosted.org/fedora-infrastructure/ticket/1658 --- [1]: https://fedoraproject.org/wiki/User:Jnalley [2]: https://fedoraproject.org/wiki/Infrastructure/GettingStarted#What_do_I_do_n… [3]: https://fedoraproject.org/wiki/Infrastructure/FIGs [4]: https://fedorahosted.org/fedora-infrastructure/report/1

3 4

Re: infrastructure Digest, Vol 64, Issue 18
by Karm Al-Postany 20 Sep '11

20 Sep '11

I Can Test On My Own servers ! On 9/20/11, infrastructure-request(a)lists.fedoraproject.org <infrastructure-request(a)lists.fedoraproject.org> wrote: > Send infrastructure mailing list submissions to > infrastructure(a)lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.fedoraproject.org/mailman/listinfo/infrastructure > or, via email, send a message with subject or body 'help' to > infrastructure-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > infrastructure-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of infrastructure digest..." > > > Today's Topics: > > 1. Re: Meeting Agenda Item: Introduction Jonathan Nalley > (Kevin Fenzi) > 2. Re: Meeting Agenda Item: Introduction Jonathan Nalley > (Pierre-Yves Chibon) > 3. Avast! A todo thread for ye! (Kevin Fenzi) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 19 Sep 2011 10:43:37 -0600 > From: Kevin Fenzi <kevin(a)scrye.com> > Subject: Re: Meeting Agenda Item: Introduction Jonathan Nalley > To: infrastructure(a)lists.fedoraproject.org > Message-ID: <20110919104337.7e93a950(a)jelerak.scrye.com> > Content-Type: text/plain; charset="us-ascii" > > On Fri, 16 Sep 2011 16:57:05 -0400 > Jonathan Nalley <jnalley(a)jnalley.com> wrote: > >> Hello all, my IRC handle is ke4zvu3, i'm in the Eastern time zone, and >> I also have a wiki page[1] setup. > > Welcome! > > ...snip... > >> sysadmin-web >> sysadmin-hosted >> sysadmin-tools >> >> If I do need to narrow down my FIG selection, I may need to seek out >> info from the FIG leaders or others in Infra that can give guidance >> beyond what's described about them on the wiki[3]. > > sure, ask away on IRC is probibly the best bet. > >> From looking at the trac list of active tickets[4], the following ones >> seemed like easy low hanging fruit that I would be interested in and >> capable of diving into and hopefully taking care of, pending >> conversations with the respective current ticket assignees: >> >> https://fedorahosted.org/fedora-infrastructure/ticket/1968 > > Likely a fas coding issue. ;) > >> https://fedorahosted.org/fedora-infrastructure/ticket/504 > > This likely might be best to wait until we upgrade to new trac (our > current version is very old) > >> https://fedorahosted.org/fedora-infrastructure/ticket/2816 > > Check with pingou the status on this one... > >> https://fedorahosted.org/fedora-infrastructure/ticket/1658 > > Would require sysadmin-hosted I think... but if you are willing to > document the process better and then run thru it, I can get you setup. > > Welcome again. > > kevin >

1 0

Avast! A todo thread for ye!
by Kevin Fenzi 19 Sep '11

19 Sep '11

For folks working in infrastructure, what are you working on this week? Note that I am not looking for some detailed todo list, just after having fought your monday and read your emails and looked at tickets and bugs and requests, what kind of things are you going to try and work on this week? On friday, if you looked and finished X, you would feel happy about the week. whats X? Last week I said: (X indicates I managed to finish that item): X Document bastion machines and their oddities in infa-docs. - Going to try and fix syslog from non vpn machines. (Decided here to wait and just add other machines to vpn in the 192.168.100 range and make sure thats firewalled off from anything except logging and such. X Get our Beta tickets filed and the freeze setup tomorrow (announce it, etc) - Look at updating CSI (Got things checked out, but not too far on updating it yet) X Work on askbot in stg some more. X Continue new machine (rhel6) plans. X Typical putting out fires, fixing things as they break, fixing things that send me email. This week: - Plan for password/sshkey reset flag day. - Look at updating CSI - make a proxy08 and prep it to replace proxy01 - Look into yubikey/googleauthenticator and come up with a plan. - more ask.stg work. - Finally look at zarafa and decide fate. anyone else? How did you do last week? Anything big this week? :) kevin

1 0

Re: [PATCH] finish the postfix migration to sanity away from the templates. This should allow us to have main.cf and master.cf files in the postfix/files/dirs with extensions corresponding to the fqdn/hostname/group/datacenter that they are and a sen
by Ricky Elrod 17 Sep '11

17 Sep '11

Looks fine from a quick read-through here as well. As long as someone is around to babysit this in case it goes to heck, (Kevin said he should be around this weekend), +1. On Fri, Sep 16, 2011 at 5:34 PM, Kevin Fenzi <kevin(a)scrye.com> wrote: > This looks ok to me from a quick glance. I'll note that this should fix > a log spam we have been getting for a while and also fix it so that new > hosts can run puppet ok (currently there's a template issue in postfix > stopping that from happening). > > If we want to make the changes today we need to make sure some of us > are around to debug any issues tonight. (I should be). > > There's a number of 'relayHost=' directives. They should also be > removed? > > +1. > > kevin > > _______________________________________________ > infrastructure mailing list > infrastructure(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/infrastructure >

1 0

[PATCH] finish the postfix migration to sanity away from the templates. This should allow us to have main.cf and master.cf files in the postfix/files/dirs with extensions corresponding to the fqdn/hostname/group/datacenter that they are and a sensible default.
by Seth Vidal 16 Sep '11

16 Sep '11

From: Seth Vidal <skvidal(a)fedoraproject.org> all without lots of random definitions --- .../nodes/compose-x86-01.phx2.fedoraproject.org.pp | 2 - manifests/services/gateway.pp | 17 +- manifests/services/smtp-mm.pp | 16 +- manifests/services/valueadd.pp | 22 +- modules/postfix/files/main.cf/main.cf | 2 +- modules/postfix/files/main.cf/main.cf.bastion | 704 -------------------- modules/postfix/files/main.cf/main.cf.external | 685 ------------------- modules/postfix/files/main.cf/main.cf.gateway | 704 ++++++++++++++++++++ modules/postfix/files/main.cf/main.cf.phx | 685 +++++++++++++++++++ modules/postfix/files/master.cf/master.cf | 96 +++ modules/postfix/files/master.cf/master.cf.hosted01 | 98 +++ modules/postfix/files/master.cf/master.cf.value | 100 +++ modules/postfix/manifests/init.pp | 108 +--- 13 files changed, 1722 insertions(+), 1517 deletions(-) delete mode 100644 modules/postfix/files/main.cf/main.cf.bastion delete mode 100644 modules/postfix/files/main.cf/main.cf.external create mode 100644 modules/postfix/files/main.cf/main.cf.gateway create mode 100644 modules/postfix/files/main.cf/main.cf.phx create mode 100644 modules/postfix/files/master.cf/master.cf create mode 100644 modules/postfix/files/master.cf/master.cf.hosted01 create mode 100644 modules/postfix/files/master.cf/master.cf.value diff --git a/manifests/nodes/compose-x86-01.phx2.fedoraproject.org.pp b/manifests/nodes/compose-x86-01.phx2.fedoraproject.org.pp index bd5f051..2e82631 100644 --- a/manifests/nodes/compose-x86-01.phx2.fedoraproject.org.pp +++ b/manifests/nodes/compose-x86-01.phx2.fedoraproject.org.pp @@ -1,6 +1,4 @@ node compose-x86-01 { - # For some reason rawhide postfix wants FQDN - $relayHost='bastion.phx2.fedoraproject.org' include phx include composer } diff --git a/manifests/services/gateway.pp b/manifests/services/gateway.pp index 58c0c3c..79ca3a7 100644 --- a/manifests/services/gateway.pp +++ b/manifests/services/gateway.pp @@ -1,25 +1,14 @@ class gateway{ $fas_groups = [ 'sysadmin-ask', 'sysadmin-web', 'sysadmin-main', 'sysadmin-cvs', 'sysadmin-build', 'sysadmin-noc', 'sysadmin-releng', 'sysadmin-dba', 'sysadmin-hosted', 'sysadmin-tools', 'qa-admin', 'sysadmin-spin' , 'sysadmin-cloud', 'fi-apprentice' ] $syncFasOften = true - $relayhost=1 $isRelayGateway=true $sshd_config_PasswordAuthentication = 'no' $sshd_config_PermitRootLogin = 'yes' $sshd_config_PermitTunnel = 'yes' $transport_maps='hash:/etc/postfix/transport' - postfix::postfix { 'server': - mydomain => 'fedoraproject.org', - myorigin => 'fedoraproject.org', - inet_interfaces => 'all', - mydestination => '$myhostname, localhost.$mydomain, fedora.redhat.com, localhost , $mydomain', # escaped on purpose - mynetworks => 'localhost.localdomain, localhost, 127.0.0.1, 10.5.125.0/24, 10.5.126.0/24, 10.5.127.0/24, 192.168.0.0/16', - relay_domains => '$mydestination fedora.phx.redhat.com', - alias_maps => 'hash:/etc/aliases, hash:/etc/postfix/package-owner', - transport_maps => 'hash:/etc/postfix/transport', - smtp_helo_name => 'bastion.fedoraproject.org', - mailbox_transport => 'lmtp:10.5.126.73:2003', - local_recipient_maps => 'hash:/etc/postfix/relay_recipient_maps' - } + $postfix_group = 'gateway' + postfix::postfix { 'server':} + postfix::transport{'transports.gateway': } include global include snmp-utils diff --git a/manifests/services/smtp-mm.pp b/manifests/services/smtp-mm.pp index 3178f94..2bdb1e1 100644 --- a/manifests/services/smtp-mm.pp +++ b/manifests/services/smtp-mm.pp @@ -1,16 +1,8 @@ class smtp-mm { $fas_groups = [ 'sysadmin-main', 'sysadmin-noc', 'sysadmin-tools' , 'fi-apprentice' ] - $isMailmanSMTP=1 - postfix::postfix { 'server': - mydomain => 'fedoraproject.org', - myorigin => 'fedoraproject.org', - inet_interfaces => 'all', - relayhost => ' ', - mydestination => '$myhostname, localhost.$mydomain', - relay_domains => '$mydestination lists.fedoraproject.org lists.fedorahosted.org', - transport_maps => 'hash:/etc/postfix/transport' - } - + $postfix_group = 'smtp-mm' + postfix::postfix { 'server':} + postfix::transport { 'transports.mm-smtp': } include global include fas::client include selinux-enforcing @@ -19,7 +11,7 @@ class smtp-mm { collectd::collectd { 'log02': } - postfix::transport { 'transports.mm-smtp': } + # Firewall Rules, allow SMTP traffic through iptables::firewall { 'ipv4': diff --git a/manifests/services/valueadd.pp b/manifests/services/valueadd.pp index 1917643..1a6c41f 100644 --- a/manifests/services/valueadd.pp +++ b/manifests/services/valueadd.pp @@ -3,26 +3,8 @@ class valueadd { $fas_ssh_groups = [ '@all'] $fas_restricted_app = '/dev/null' - postfix::postfix { 'server': - mydomain => 'fedoraproject.org', - myorigin => 'fedoraproject.org', - inet_interfaces => 'all', - relayhost => 'bastion', - mydestination => '$myhostname, localhost.$mydomain, localhost', - relay_domains => ' ', - custom => ['#TLS - SMTP AUTH', - 'disable_vrfy_command = yes', - 'smtpd_use_tls = yes', - 'smtpd_tls_auth_only = yes', - 'tls_random_source = dev:/dev/urandom', - 'smtpd_tls_cert_file = /etc/postfix/cert.pem', - 'smtpd_tls_key_file = /etc/postfix/key.pem', - 'smtpd_sasl_auth_enable = yes', - 'smtpd_sasl_security_options = noanonymous', - 'broken_sasl_auth_clients = yes', - 'smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination'], - smtps => true, - } + $postfix_group = 'value' + postfix::postfix { 'server':} include cyrus-sasl::cyrus-sasl diff --git a/modules/postfix/files/main.cf/main.cf b/modules/postfix/files/main.cf/main.cf index 1707639..0e502d2 100644 --- a/modules/postfix/files/main.cf/main.cf +++ b/modules/postfix/files/main.cf/main.cf @@ -313,7 +313,7 @@ unknown_local_recipient_reject_code = 550 #relayhost = [mailserver.isp.tld] #relayhost = uucphost #relayhost = [an.ip.add.ress] -relayhost = bastion +relayhost = # REJECTING UNKNOWN RELAY USERS diff --git a/modules/postfix/files/main.cf/main.cf.bastion b/modules/postfix/files/main.cf/main.cf.bastion deleted file mode 100644 index f0b52de..0000000 --- a/modules/postfix/files/main.cf/main.cf.bastion +++ /dev/null @@ -1,704 +0,0 @@ -# Global Postfix configuration file. This file lists only a subset -# of all parameters. For the syntax, and for a complete parameter -# list, see the postconf(5) manual page (command: "man 5 postconf"). -# -# For common configuration examples, see BASIC_CONFIGURATION_README -# and STANDARD_CONFIGURATION_README. To find these documents, use -# the command "postconf html_directory readme_directory", or go to -# http://www.postfix.org/. -# -# For best results, change no more than 2-3 parameters at a time, -# and test if Postfix still works after every change. - -# Custom rules - -# SOFT BOUNCE -# -# The soft_bounce parameter provides a limited safety net for -# testing. When soft_bounce is enabled, mail will remain queued that -# would otherwise bounce. This parameter disables locally-generated -# bounces, and prevents the SMTP server from rejecting mail permanently -# (by changing 5xx replies into 4xx replies). However, soft_bounce -# is no cure for address rewriting mistakes or mail routing mistakes. -# -#soft_bounce = no - -# LOCAL PATHNAME INFORMATION -# -# The queue_directory specifies the location of the Postfix queue. -# This is also the root directory of Postfix daemons that run chrooted. -# See the files in examples/chroot-setup for setting up Postfix chroot -# environments on different UNIX systems. -# -queue_directory = /var/spool/postfix - -# The command_directory parameter specifies the location of all -# postXXX commands. -# -command_directory = /usr/sbin - -# The daemon_directory parameter specifies the location of all Postfix -# daemon programs (i.e. programs listed in the master.cf file). This -# directory must be owned by root. -# -daemon_directory = /usr/libexec/postfix - -# The data_directory parameter specifies the location of Postfix-writable -# data files (caches, random numbers). This directory must be owned -# by the mail_owner account (see below). -# -data_directory = /var/lib/postfix - -# QUEUE AND PROCESS OWNERSHIP -# -# The mail_owner parameter specifies the owner of the Postfix queue -# and of most Postfix daemon processes. Specify the name of a user -# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS -# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In -# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED -# USER. -# -mail_owner = postfix - -# The default_privs parameter specifies the default rights used by -# the local delivery agent for delivery to external file or command. -# These rights are used in the absence of a recipient user context. -# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER. -# -#default_privs = nobody - -# INTERNET HOST AND DOMAIN NAMES -# -# The myhostname parameter specifies the internet hostname of this -# mail system. The default is to use the fully-qualified domain name -# from gethostname(). $myhostname is used as a default value for many -# other configuration parameters. -# -#myhostname = host.domain.tld -#myhostname = virtual.domain.tld - - -smtp_helo_name = bastion.fedoraproject.org - -# The mydomain parameter specifies the local internet domain name. -# The default is to use $myhostname minus the first component. -# $mydomain is used as a default value for many other configuration -# parameters. -# -#mydomain = domain.tld - -mydomain = fedoraproject.org - -# SENDING MAIL -# -# The myorigin parameter specifies the domain that locally-posted -# mail appears to come from. The default is to append $myhostname, -# which is fine for small sites. If you run a domain with multiple -# machines, you should (1) change this to $mydomain and (2) set up -# a domain-wide alias database that aliases each user to -# user(a)that.users.mailhost. -# -# For the sake of consistency between sender and recipient addresses, -# myorigin also specifies the default domain name that is appended -# to recipient addresses that have no @domain part. -# -#myorigin = $myhostname -#myorigin = $mydomain - -myorigin = fedoraproject.org - -# RECEIVING MAIL - -# The inet_interfaces parameter specifies the network interface -# addresses that this mail system receives mail on. By default, -# the software claims all active interfaces on the machine. The -# parameter also controls delivery of mail to user(a)[ip.address]. -# -# See also the proxy_interfaces parameter, for network addresses that -# are forwarded to us via a proxy or network address translator. -# -# Note: you need to stop/start Postfix when this parameter changes. -# -#inet_interfaces = all -#inet_interfaces = $myhostname -#inet_interfaces = $myhostname, localhost - -inet_interfaces = all - -# The proxy_interfaces parameter specifies the network interface -# addresses that this mail system receives mail on by way of a -# proxy or network address translation unit. This setting extends -# the address list specified with the inet_interfaces parameter. -# -# You must specify your proxy/NAT addresses when your system is a -# backup MX host for other domains, otherwise mail delivery loops -# will happen when the primary MX host is down. -# -#proxy_interfaces = -#proxy_interfaces = 1.2.3.4 - -# The mydestination parameter specifies the list of domains that this -# machine considers itself the final destination for. -# -# These domains are routed to the delivery agent specified with the -# local_transport parameter setting. By default, that is the UNIX -# compatible delivery agent that lookups all recipients in /etc/passwd -# and /etc/aliases or their equivalent. -# -# The default is $myhostname + localhost.$mydomain. On a mail domain -# gateway, you should also include $mydomain. -# -# Do not specify the names of virtual domains - those domains are -# specified elsewhere (see VIRTUAL_README). -# -# Do not specify the names of domains that this machine is backup MX -# host for. Specify those names via the relay_domains settings for -# the SMTP server, or use permit_mx_backup if you are lazy (see -# STANDARD_CONFIGURATION_README). -# -# The local machine is always the final destination for mail addressed -# to user(a)[the.net.work.address] of an interface that the mail system -# receives mail on (see the inet_interfaces parameter). -# -# Specify a list of host or domain names, /file/name or type:table -# patterns, separated by commas and/or whitespace. A /file/name -# pattern is replaced by its contents; a type:table is matched when -# a name matches a lookup key (the right-hand side is ignored). -# Continue long lines by starting the next line with whitespace. -# -# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS". -# - -mydestination = $myhostname, localhost.$mydomain, fedora.redhat.com, localhost , $mydomain -#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain -#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, -# mail.$mydomain, www.$mydomain, ftp.$mydomain - -# REJECTING MAIL FOR UNKNOWN LOCAL USERS -# -# The local_recipient_maps parameter specifies optional lookup tables -# with all names or addresses of users that are local with respect -# to $mydestination, $inet_interfaces or $proxy_interfaces. -# -# If this parameter is defined, then the SMTP server will reject -# mail for unknown local users. This parameter is defined by default. -# -# To turn off local recipient checking in the SMTP server, specify -# local_recipient_maps = (i.e. empty). -# -# The default setting assumes that you use the default Postfix local -# delivery agent for local delivery. You need to update the -# local_recipient_maps setting if: -# -# - You define $mydestination domain recipients in files other than -# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files. -# For example, you define $mydestination domain recipients in -# the $virtual_mailbox_maps files. -# -# - You redefine the local delivery agent in master.cf. -# -# - You redefine the "local_transport" setting in main.cf. -# -# - You use the "luser_relay", "mailbox_transport", or "fallback_transport" -# feature of the Postfix local delivery agent (see local(8)). -# -# Details are described in the LOCAL_RECIPIENT_README file. -# -# Beware: if the Postfix SMTP server runs chrooted, you probably have -# to access the passwd file via the proxymap service, in order to -# overcome chroot restrictions. The alternative, having a copy of -# the system passwd file in the chroot jail is just not practical. -# -# The right-hand side of the lookup tables is conveniently ignored. -# In the left-hand side, specify a bare username, an @domain.tld -# wild-card, or specify a user(a)domain.tld address. -# -#local_recipient_maps = unix:passwd.byname $alias_maps -#local_recipient_maps = proxy:unix:passwd.byname $alias_maps -#local_recipient_maps = -local_recipient_maps = $alias_maps hash:/etc/postfix/relay_recipient_maps - -# The unknown_local_recipient_reject_code specifies the SMTP server -# response code when a recipient domain matches $mydestination or -# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty -# and the recipient address or address local-part is not found. -# -# The default setting is 550 (reject mail) but it is safer to start -# with 450 (try again later) until you are certain that your -# local_recipient_maps settings are OK. -# -unknown_local_recipient_reject_code = 550 - -# TRUST AND RELAY CONTROL - -# The mynetworks parameter specifies the list of "trusted" SMTP -# clients that have more privileges than "strangers". -# -# In particular, "trusted" SMTP clients are allowed to relay mail -# through Postfix. See the smtpd_recipient_restrictions parameter -# in postconf(5). -# -# You can specify the list of "trusted" network addresses by hand -# or you can let Postfix do it for you (which is the default). -# -# By default (mynetworks_style = subnet), Postfix "trusts" SMTP -# clients in the same IP subnetworks as the local machine. -# On Linux, this does works correctly only with interfaces specified -# with the "ifconfig" command. -# -# Specify "mynetworks_style = class" when Postfix should "trust" SMTP -# clients in the same IP class A/B/C networks as the local machine. -# Don't do this with a dialup site - it would cause Postfix to "trust" -# your entire provider's network. Instead, specify an explicit -# mynetworks list by hand, as described below. -# -# Specify "mynetworks_style = host" when Postfix should "trust" -# only the local machine. -# -#mynetworks_style = class -#mynetworks_style = subnet -#mynetworks_style = host - - -# Alternatively, you can specify the mynetworks list by hand, in -# which case Postfix ignores the mynetworks_style setting. -# -# Specify an explicit list of network/netmask patterns, where the -# mask specifies the number of bits in the network part of a host -# address. -# -# You can also specify the absolute pathname of a pattern file instead -# of listing the patterns here. Specify type:table for table-based lookups -# (the value on the table right-hand side is not used). -# -#mynetworks = 168.100.189.0/28, 127.0.0.0/8 -#mynetworks = $config_directory/mynetworks -#mynetworks = hash:/etc/postfix/network_table - -mynetworks = localhost.localdomain, localhost, 127.0.0.1, 10.5.125.0/24, 10.5.126.0/24, 10.5.127.0/24, 192.168.0.0/16 - -# The relay_domains parameter restricts what destinations this system will -# relay mail to. See the smtpd_recipient_restrictions description in -# postconf(5) for detailed information. -# -# By default, Postfix relays mail -# - from "trusted" clients (IP address matches $mynetworks) to any destination, -# - from "untrusted" clients to destinations that match $relay_domains or -# subdomains thereof, except addresses with sender-specified routing. -# The default relay_domains value is $mydestination. -# -# In addition to the above, the Postfix SMTP server by default accepts mail -# that Postfix is final destination for: -# - destinations that match $inet_interfaces or $proxy_interfaces, -# - destinations that match $mydestination -# - destinations that match $virtual_alias_domains, -# - destinations that match $virtual_mailbox_domains. -# These destinations do not need to be listed in $relay_domains. -# -# Specify a list of hosts or domains, /file/name patterns or type:name -# lookup tables, separated by commas and/or whitespace. Continue -# long lines by starting the next line with whitespace. A file name -# is replaced by its contents; a type:name table is matched when a -# (parent) domain appears as lookup key. -# -# NOTE: Postfix will not automatically forward mail for domains that -# list this system as their primary or backup MX host. See the -# permit_mx_backup restriction description in postconf(5). -# -#relay_domains = $mydestination - -relay_domains = $mydestination fedora.phx.redhat.com - -# INTERNET OR INTRANET - -# The relayhost parameter specifies the default host to send mail to -# when no entry is matched in the optional transport(5) table. When -# no relayhost is given, mail is routed directly to the destination. -# -# On an intranet, specify the organizational domain name. If your -# internal DNS uses no MX records, specify the name of the intranet -# gateway host instead. -# -# In the case of SMTP, specify a domain, host, host:port, [host]:port, -# [address] or [address]:port; the form [host] turns off MX lookups. -# -# If you're connected via UUCP, see also the default_transport parameter. -# -#relayhost = $mydomain -#relayhost = [gateway.my.domain] -#relayhost = [mailserver.isp.tld] -#relayhost = uucphost -#relayhost = [an.ip.add.ress] - - -# REJECTING UNKNOWN RELAY USERS -# -# The relay_recipient_maps parameter specifies optional lookup tables -# with all addresses in the domains that match $relay_domains. -# -# If this parameter is defined, then the SMTP server will reject -# mail for unknown relay users. This feature is off by default. -# -# The right-hand side of the lookup tables is conveniently ignored. -# In the left-hand side, specify an @domain.tld wild-card, or specify -# a user(a)domain.tld address. -# -#relay_recipient_maps = hash:/etc/postfix/relay_recipients - -# INPUT RATE CONTROL -# -# The in_flow_delay configuration parameter implements mail input -# flow control. This feature is turned on by default, although it -# still needs further development (it's disabled on SCO UNIX due -# to an SCO bug). -# -# A Postfix process will pause for $in_flow_delay seconds before -# accepting a new message, when the message arrival rate exceeds the -# message delivery rate. With the default 100 SMTP server process -# limit, this limits the mail inflow to 100 messages a second more -# than the number of messages delivered per second. -# -# Specify 0 to disable the feature. Valid delays are 0..10. -# -#in_flow_delay = 1s - -# ADDRESS REWRITING -# -# The ADDRESS_REWRITING_README document gives information about -# address masquerading or other forms of address rewriting including -# username->Firstname.Lastname mapping. - -# ADDRESS REDIRECTION (VIRTUAL DOMAIN) -# -# The VIRTUAL_README document gives information about the many forms -# of domain hosting that Postfix supports. - -# "USER HAS MOVED" BOUNCE MESSAGES -# -# See the discussion in the ADDRESS_REWRITING_README document. - -# TRANSPORT MAP -# -# See the discussion in the ADDRESS_REWRITING_README document. - -# ALIAS DATABASE -# -# The alias_maps parameter specifies the list of alias databases used -# by the local delivery agent. The default list is system dependent. -# -# On systems with NIS, the default is to search the local alias -# database, then the NIS alias database. See aliases(5) for syntax -# details. -# -# If you change the alias database, run "postalias /etc/aliases" (or -# wherever your system stores the mail alias file), or simply run -# "newaliases" to build the necessary DBM or DB file. -# -# It will take a minute or so before changes become visible. Use -# "postfix reload" to eliminate the delay. -# -#alias_maps = dbm:/etc/aliases -alias_maps = hash:/etc/aliases -alias_maps = hash:/etc/aliases, hash:/etc/postfix/package-owner -#alias_maps = hash:/etc/aliases, nis:mail.aliases -#alias_maps = netinfo:/aliases - -# The alias_database parameter specifies the alias database(s) that -# are built with "newaliases" or "sendmail -bi". This is a separate -# configuration parameter, because alias_maps (see above) may specify -# tables that are not necessarily all under control by Postfix. -# -#alias_database = dbm:/etc/aliases -#alias_database = dbm:/etc/mail/aliases -alias_database = hash:/etc/aliases -#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases - -# ADDRESS EXTENSIONS (e.g., user+foo) -# -# The recipient_delimiter parameter specifies the separator between -# user names and address extensions (user+foo). See canonical(5), -# local(8), relocated(5) and virtual(5) for the effects this has on -# aliases, canonical, virtual, relocated and .forward file lookups. -# Basically, the software tries user+foo and .forward+foo before -# trying user and .forward. -# -recipient_delimiter = + - -# DELIVERY TO MAILBOX -# -# The home_mailbox parameter specifies the optional pathname of a -# mailbox file relative to a user's home directory. The default -# mailbox file is /var/spool/mail/user or /var/mail/user. Specify -# "Maildir/" for qmail-style delivery (the / is required). -# -#home_mailbox = Mailbox -#home_mailbox = Maildir/ - -# The mail_spool_directory parameter specifies the directory where -# UNIX-style mailboxes are kept. The default setting depends on the -# system type. -# -#mail_spool_directory = /var/mail -#mail_spool_directory = /var/spool/mail - -# The mailbox_command parameter specifies the optional external -# command to use instead of mailbox delivery. The command is run as -# the recipient with proper HOME, SHELL and LOGNAME environment settings. -# Exception: delivery for root is done as $default_user. -# -# Other environment variables of interest: USER (recipient username), -# EXTENSION (address extension), DOMAIN (domain part of address), -# and LOCAL (the address localpart). -# -# Unlike other Postfix configuration parameters, the mailbox_command -# parameter is not subjected to $parameter substitutions. This is to -# make it easier to specify shell syntax (see example below). -# -# Avoid shell meta characters because they will force Postfix to run -# an expensive shell process. Procmail alone is expensive enough. -# -# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN -# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. -# -#mailbox_command = /some/where/procmail -#mailbox_command = /some/where/procmail -a "$EXTENSION" - -# The mailbox_transport specifies the optional transport in master.cf -# to use after processing aliases and .forward files. This parameter -# has precedence over the mailbox_command, fallback_transport and -# luser_relay parameters. -# -# Specify a string of the form transport:nexthop, where transport is -# the name of a mail delivery transport defined in master.cf. The -# :nexthop part is optional. For more details see the sample transport -# configuration file. -# -# NOTE: if you use this feature for accounts not in the UNIX password -# file, then you must update the "local_recipient_maps" setting in -# the main.cf file, otherwise the SMTP server will reject mail for -# non-UNIX accounts with "User unknown in local recipient table". -# -#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp - -# If using the cyrus-imapd IMAP server deliver local mail to the IMAP -# server using LMTP (Local Mail Transport Protocol), this is prefered -# over the older cyrus deliver program by setting the -# mailbox_transport as below: -# -# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp -# -# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via -# these settings. -# -# local_destination_recipient_limit = 300 -# local_destination_concurrency_limit = 5 -# -# Of course you should adjust these settings as appropriate for the -# capacity of the hardware you are using. The recipient limit setting -# can be used to take advantage of the single instance message store -# capability of Cyrus. The concurrency limit can be used to control -# how many simultaneous LMTP sessions will be permitted to the Cyrus -# message store. -# -# To use the old cyrus deliver program you have to set: -#mailbox_transport = cyrus - - -mailbox_transport = lmtp:10.5.126.73:2003 - -# The fallback_transport specifies the optional transport in master.cf -# to use for recipients that are not found in the UNIX passwd database. -# This parameter has precedence over the luser_relay parameter. -# -# Specify a string of the form transport:nexthop, where transport is -# the name of a mail delivery transport defined in master.cf. The -# :nexthop part is optional. For more details see the sample transport -# configuration file. -# -# NOTE: if you use this feature for accounts not in the UNIX password -# file, then you must update the "local_recipient_maps" setting in -# the main.cf file, otherwise the SMTP server will reject mail for -# non-UNIX accounts with "User unknown in local recipient table". -# -#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp -#fallback_transport = - -# The luser_relay parameter specifies an optional destination address -# for unknown recipients. By default, mail for unknown@$mydestination, -# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned -# as undeliverable. -# -# The following expansions are done on luser_relay: $user (recipient -# username), $shell (recipient shell), $home (recipient home directory), -# $recipient (full recipient address), $extension (recipient address -# extension), $domain (recipient domain), $local (entire recipient -# localpart), $recipient_delimiter. Specify ${name?value} or -# ${name:value} to expand value only when $name does (does not) exist. -# -# luser_relay works only for the default Postfix local delivery agent. -# -# NOTE: if you use this feature for accounts not in the UNIX password -# file, then you must specify "local_recipient_maps =" (i.e. empty) in -# the main.cf file, otherwise the SMTP server will reject mail for -# non-UNIX accounts with "User unknown in local recipient table". -# -#luser_relay = $user(a)other.host -#luser_relay = $local(a)other.host -#luser_relay = admin+$local - -# JUNK MAIL CONTROLS -# -# The controls listed here are only a very small subset. The file -# SMTPD_ACCESS_README provides an overview. - -# The header_checks parameter specifies an optional table with patterns -# that each logical message header is matched against, including -# headers that span multiple physical lines. -# -# By default, these patterns also apply to MIME headers and to the -# headers of attached messages. With older Postfix versions, MIME and -# attached message headers were treated as body text. -# -# For details, see "man header_checks". -# -#header_checks = regexp:/etc/postfix/header_checks - -# FAST ETRN SERVICE -# -# Postfix maintains per-destination logfiles with information about -# deferred mail, so that mail can be flushed quickly with the SMTP -# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld". -# See the ETRN_README document for a detailed description. -# -# The fast_flush_domains parameter controls what destinations are -# eligible for this service. By default, they are all domains that -# this server is willing to relay mail to. -# -#fast_flush_domains = $relay_domains - -# SHOW SOFTWARE VERSION OR NOT -# -# The smtpd_banner parameter specifies the text that follows the 220 -# code in the SMTP server's greeting banner. Some people like to see -# the mail version advertised. By default, Postfix shows no version. -# -# You MUST specify $myhostname at the start of the text. That is an -# RFC requirement. Postfix itself does not care. -# -#smtpd_banner = $myhostname ESMTP $mail_name -#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version) - -# PARALLEL DELIVERY TO THE SAME DESTINATION -# -# How many parallel deliveries to the same user or domain? With local -# delivery, it does not make sense to do massively parallel delivery -# to the same user, because mailbox updates must happen sequentially, -# and expensive pipelines in .forward files can cause disasters when -# too many are run at the same time. With SMTP deliveries, 10 -# simultaneous connections to the same domain could be sufficient to -# raise eyebrows. -# -# Each message delivery transport has its XXX_destination_concurrency_limit -# parameter. The default is $default_destination_concurrency_limit for -# most delivery transports. For the local delivery agent the default is 2. - -#local_destination_concurrency_limit = 2 -#default_destination_concurrency_limit = 20 - -# DEBUGGING CONTROL -# -# The debug_peer_level parameter specifies the increment in verbose -# logging level when an SMTP client or server host name or address -# matches a pattern in the debug_peer_list parameter. -# -debug_peer_level = 2 - -# The debug_peer_list parameter specifies an optional list of domain -# or network patterns, /file/name patterns or type:name tables. When -# an SMTP client or server host name or address matches a pattern, -# increase the verbose logging level by the amount specified in the -# debug_peer_level parameter. -# -#debug_peer_list = 127.0.0.1 -#debug_peer_list = some.domain - -# The debugger_command specifies the external command that is executed -# when a Postfix daemon program is run with the -D option. -# -# Use "command .. & sleep 5" so that the debugger can attach before -# the process marches on. If you use an X-based debugger, be sure to -# set up your XAUTHORITY environment variable before starting Postfix. -# -debugger_command = - PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin - ddd $daemon_directory/$process_name $process_id & sleep 5 - -# If you can't use X, use this to capture the call stack when a -# daemon crashes. The result is in a file in the configuration -# directory, and is named after the process name and the process ID. -# -# debugger_command = -# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; -# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 -# >$config_directory/$process_name.$process_id.log & sleep 5 -# -# Another possibility is to run gdb under a detached screen session. -# To attach to the screen sesssion, su root and run "screen -r -# <id_string>" where <id_string> uniquely matches one of the detached -# sessions (from "screen -list"). -# -# debugger_command = -# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen -# -dmS $process_name gdb $daemon_directory/$process_name -# $process_id & sleep 1 - -# INSTALL-TIME CONFIGURATION INFORMATION -# -# The following parameters are used when installing a new Postfix version. -# -# sendmail_path: The full pathname of the Postfix sendmail command. -# This is the Sendmail-compatible mail posting interface. -# -sendmail_path = /usr/sbin/sendmail.postfix - -# newaliases_path: The full pathname of the Postfix newaliases command. -# This is the Sendmail-compatible command to build alias databases. -# -newaliases_path = /usr/bin/newaliases.postfix - -# mailq_path: The full pathname of the Postfix mailq command. This -# is the Sendmail-compatible mail queue listing command. -# -mailq_path = /usr/bin/mailq.postfix - -# setgid_group: The group for mail submission and queue management -# commands. This must be a group name with a numerical group ID that -# is not shared with other accounts, not even with the Postfix account. -# -setgid_group = postdrop - -# html_directory: The location of the Postfix HTML documentation. -# -html_directory = no - -# manpage_directory: The location of the Postfix on-line manual pages. -# -manpage_directory = /usr/share/man - -# sample_directory: The location of the Postfix sample configuration files. -# This parameter is obsolete as of Postfix 2.1. -# -sample_directory = /usr/share/doc/postfix-2.5.6/samples - -# readme_directory: The location of the Postfix README files. -# -readme_directory = /usr/share/doc/postfix-2.5.6/README_FILES -# Enable IPv4, and IPv6 if supported -inet_protocols = all - -# mapping so we know where to go for .redhat.com mail - -transport_maps = hash:/etc/postfix/transport -local_header_rewrite_clients = static:all - - diff --git a/modules/postfix/files/main.cf/main.cf.external b/modules/postfix/files/main.cf/main.cf.external deleted file mode 100644 index 0e502d2..0000000 --- a/modules/postfix/files/main.cf/main.cf.external +++ /dev/null @@ -1,685 +0,0 @@ -# "false" -# Global Postfix configuration file. This file lists only a subset -# of all parameters. For the syntax, and for a complete parameter -# list, see the postconf(5) manual page (command: "man 5 postconf"). -# -# For common configuration examples, see BASIC_CONFIGURATION_README -# and STANDARD_CONFIGURATION_README. To find these documents, use -# the command "postconf html_directory readme_directory", or go to -# http://www.postfix.org/. -# -# For best results, change no more than 2-3 parameters at a time, -# and test if Postfix still works after every change. - -# SOFT BOUNCE -# -# The soft_bounce parameter provides a limited safety net for -# testing. When soft_bounce is enabled, mail will remain queued that -# would otherwise bounce. This parameter disables locally-generated -# bounces, and prevents the SMTP server from rejecting mail permanently -# (by changing 5xx replies into 4xx replies). However, soft_bounce -# is no cure for address rewriting mistakes or mail routing mistakes. -# -#soft_bounce = no - -# LOCAL PATHNAME INFORMATION -# -# The queue_directory specifies the location of the Postfix queue. -# This is also the root directory of Postfix daemons that run chrooted. -# See the files in examples/chroot-setup for setting up Postfix chroot -# environments on different UNIX systems. -# -queue_directory = /var/spool/postfix - -# The command_directory parameter specifies the location of all -# postXXX commands. -# -command_directory = /usr/sbin - -# The daemon_directory parameter specifies the location of all Postfix -# daemon programs (i.e. programs listed in the master.cf file). This -# directory must be owned by root. -# -daemon_directory = /usr/libexec/postfix - -# QUEUE AND PROCESS OWNERSHIP -# -# The mail_owner parameter specifies the owner of the Postfix queue -# and of most Postfix daemon processes. Specify the name of a user -# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS -# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In -# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED -# USER. -# -mail_owner = postfix - -# The default_privs parameter specifies the default rights used by -# the local delivery agent for delivery to external file or command. -# These rights are used in the absence of a recipient user context. -# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER. -# -#default_privs = nobody - -# INTERNET HOST AND DOMAIN NAMES -# -# The myhostname parameter specifies the internet hostname of this -# mail system. The default is to use the fully-qualified domain name -# from gethostname(). $myhostname is used as a default value for many -# other configuration parameters. -# -#myhostname = host.domain.tld -#myhostname = virtual.domain.tld - -# The mydomain parameter specifies the local internet domain name. -# The default is to use $myhostname minus the first component. -# $mydomain is used as a default value for many other configuration -# parameters. -# -#mydomain = domain.tld - -# SENDING MAIL -# -# The myorigin parameter specifies the domain that locally-posted -# mail appears to come from. The default is to append $myhostname, -# which is fine for small sites. If you run a domain with multiple -# machines, you should (1) change this to $mydomain and (2) set up -# a domain-wide alias database that aliases each user to -# user(a)that.users.mailhost. -# -# For the sake of consistency between sender and recipient addresses, -# myorigin also specifies the default domain name that is appended -# to recipient addresses that have no @domain part. -# -#myorigin = $myhostname -#myorigin = $mydomain - -mydomain = fedoraproject.org -myorigin = fedoraproject.org - -# RECEIVING MAIL - -# The inet_interfaces parameter specifies the network interface -# addresses that this mail system receives mail on. By default, -# the software claims all active interfaces on the machine. The -# parameter also controls delivery of mail to user(a)[ip.address]. -# -# See also the proxy_interfaces parameter, for network addresses that -# are forwarded to us via a proxy or network address translator. -# -# Note: you need to stop/start Postfix when this parameter changes. -# -#inet_interfaces = all -#inet_interfaces = $myhostname -#inet_interfaces = $myhostname, localhost -inet_interfaces = all - -# The proxy_interfaces parameter specifies the network interface -# addresses that this mail system receives mail on by way of a -# proxy or network address translation unit. This setting extends -# the address list specified with the inet_interfaces parameter. -# -# You must specify your proxy/NAT addresses when your system is a -# backup MX host for other domains, otherwise mail delivery loops -# will happen when the primary MX host is down. -# -#proxy_interfaces = -#proxy_interfaces = 1.2.3.4 - -# The mydestination parameter specifies the list of domains that this -# machine considers itself the final destination for. -# -# These domains are routed to the delivery agent specified with the -# local_transport parameter setting. By default, that is the UNIX -# compatible delivery agent that lookups all recipients in /etc/passwd -# and /etc/aliases or their equivalent. -# -# The default is $myhostname + localhost.$mydomain. On a mail domain -# gateway, you should also include $mydomain. -# -# Do not specify the names of virtual domains - those domains are -# specified elsewhere (see VIRTUAL_README). -# -# Do not specify the names of domains that this machine is backup MX -# host for. Specify those names via the relay_domains settings for -# the SMTP server, or use permit_mx_backup if you are lazy (see -# STANDARD_CONFIGURATION_README). -# -# The local machine is always the final destination for mail addressed -# to user(a)[the.net.work.address] of an interface that the mail system -# receives mail on (see the inet_interfaces parameter). -# -# Specify a list of host or domain names, /file/name or type:table -# patterns, separated by commas and/or whitespace. A /file/name -# pattern is replaced by its contents; a type:table is matched when -# a name matches a lookup key (the right-hand side is ignored). -# Continue long lines by starting the next line with whitespace. -# -# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS". -# -mydestination = $myhostname, localhost.$mydomain, fedora.redhat.com, localhost -#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain -#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, -# mail.$mydomain, www.$mydomain, ftp.$mydomain - -# REJECTING MAIL FOR UNKNOWN LOCAL USERS -# -# The local_recipient_maps parameter specifies optional lookup tables -# with all names or addresses of users that are local with respect -# to $mydestination, $inet_interfaces or $proxy_interfaces. -# -# If this parameter is defined, then the SMTP server will reject -# mail for unknown local users. This parameter is defined by default. -# -# To turn off local recipient checking in the SMTP server, specify -# local_recipient_maps = (i.e. empty). -# -# The default setting assumes that you use the default Postfix local -# delivery agent for local delivery. You need to update the -# local_recipient_maps setting if: -# -# - You define $mydestination domain recipients in files other than -# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files. -# For example, you define $mydestination domain recipients in -# the $virtual_mailbox_maps files. -# -# - You redefine the local delivery agent in master.cf. -# -# - You redefine the "local_transport" setting in main.cf. -# -# - You use the "luser_relay", "mailbox_transport", or "fallback_transport" -# feature of the Postfix local delivery agent (see local(8)). -# -# Details are described in the LOCAL_RECIPIENT_README file. -# -# Beware: if the Postfix SMTP server runs chrooted, you probably have -# to access the passwd file via the proxymap service, in order to -# overcome chroot restrictions. The alternative, having a copy of -# the system passwd file in the chroot jail is just not practical. -# -# The right-hand side of the lookup tables is conveniently ignored. -# In the left-hand side, specify a bare username, an @domain.tld -# wild-card, or specify a user(a)domain.tld address. -# -#local_recipient_maps = unix:passwd.byname $alias_maps -#local_recipient_maps = proxy:unix:passwd.byname $alias_maps -#local_recipient_maps = - -# The unknown_local_recipient_reject_code specifies the SMTP server -# response code when a recipient domain matches $mydestination or -# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty -# and the recipient address or address local-part is not found. -# -# The default setting is 550 (reject mail) but it is safer to start -# with 450 (try again later) until you are certain that your -# local_recipient_maps settings are OK. -# -unknown_local_recipient_reject_code = 550 - -# TRUST AND RELAY CONTROL - -# The mynetworks parameter specifies the list of "trusted" SMTP -# clients that have more privileges than "strangers". -# -# In particular, "trusted" SMTP clients are allowed to relay mail -# through Postfix. See the smtpd_recipient_restrictions parameter -# in postconf(5). -# -# You can specify the list of "trusted" network addresses by hand -# or you can let Postfix do it for you (which is the default). -# -# By default (mynetworks_style = subnet), Postfix "trusts" SMTP -# clients in the same IP subnetworks as the local machine. -# On Linux, this does works correctly only with interfaces specified -# with the "ifconfig" command. -# -# Specify "mynetworks_style = class" when Postfix should "trust" SMTP -# clients in the same IP class A/B/C networks as the local machine. -# Don't do this with a dialup site - it would cause Postfix to "trust" -# your entire provider's network. Instead, specify an explicit -# mynetworks list by hand, as described below. -# -# Specify "mynetworks_style = host" when Postfix should "trust" -# only the local machine. -# -#mynetworks_style = class -#mynetworks_style = subnet -#mynetworks_style = host - -# Alternatively, you can specify the mynetworks list by hand, in -# which case Postfix ignores the mynetworks_style setting. -# -# Specify an explicit list of network/netmask patterns, where the -# mask specifies the number of bits in the network part of a host -# address. -# -# You can also specify the absolute pathname of a pattern file instead -# of listing the patterns here. Specify type:table for table-based lookups -# (the value on the table right-hand side is not used). -# -#mynetworks = 168.100.189.0/28, 127.0.0.0/8 -#mynetworks = $config_directory/mynetworks -#mynetworks = hash:/etc/postfix/network_table - - -# The relay_domains parameter restricts what destinations this system will -# relay mail to. See the smtpd_recipient_restrictions description in -# postconf(5) for detailed information. -# -# By default, Postfix relays mail -# - from "trusted" clients (IP address matches $mynetworks) to any destination, -# - from "untrusted" clients to destinations that match $relay_domains or -# subdomains thereof, except addresses with sender-specified routing. -# The default relay_domains value is $mydestination. -# -# In addition to the above, the Postfix SMTP server by default accepts mail -# that Postfix is final destination for: -# - destinations that match $inet_interfaces or $proxy_interfaces, -# - destinations that match $mydestination -# - destinations that match $virtual_alias_domains, -# - destinations that match $virtual_mailbox_domains. -# These destinations do not need to be listed in $relay_domains. -# -# Specify a list of hosts or domains, /file/name patterns or type:name -# lookup tables, separated by commas and/or whitespace. Continue -# long lines by starting the next line with whitespace. A file name -# is replaced by its contents; a type:name table is matched when a -# (parent) domain appears as lookup key. -# -# NOTE: Postfix will not automatically forward mail for domains that -# list this system as their primary or backup MX host. See the -# permit_mx_backup restriction description in postconf(5). -# -#relay_domains = $mydestination - - - -# INTERNET OR INTRANET - -# The relayhost parameter specifies the default host to send mail to -# when no entry is matched in the optional transport(5) table. When -# no relayhost is given, mail is routed directly to the destination. -# -# On an intranet, specify the organizational domain name. If your -# internal DNS uses no MX records, specify the name of the intranet -# gateway host instead. -# -# In the case of SMTP, specify a domain, host, host:port, [host]:port, -# [address] or [address]:port; the form [host] turns off MX lookups. -# -# If you're connected via UUCP, see also the default_transport parameter. -# -#relayhost = $mydomain -#relayhost = [gateway.my.domain] -#relayhost = [mailserver.isp.tld] -#relayhost = uucphost -#relayhost = [an.ip.add.ress] -relayhost = - - -# REJECTING UNKNOWN RELAY USERS -# -# The relay_recipient_maps parameter specifies optional lookup tables -# with all addresses in the domains that match $relay_domains. -# -# If this parameter is defined, then the SMTP server will reject -# mail for unknown relay users. This feature is off by default. -# -# The right-hand side of the lookup tables is conveniently ignored. -# In the left-hand side, specify an @domain.tld wild-card, or specify -# a user(a)domain.tld address. -# -#relay_recipient_maps = hash:/etc/postfix/relay_recipients - -# INPUT RATE CONTROL -# -# The in_flow_delay configuration parameter implements mail input -# flow control. This feature is turned on by default, although it -# still needs further development (it's disabled on SCO UNIX due -# to an SCO bug). -# -# A Postfix process will pause for $in_flow_delay seconds before -# accepting a new message, when the message arrival rate exceeds the -# message delivery rate. With the default 100 SMTP server process -# limit, this limits the mail inflow to 100 messages a second more -# than the number of messages delivered per second. -# -# Specify 0 to disable the feature. Valid delays are 0..10. -# -#in_flow_delay = 1s - -# ADDRESS REWRITING -# -# The ADDRESS_REWRITING_README document gives information about -# address masquerading or other forms of address rewriting including -# username->Firstname.Lastname mapping. - -masquerade_domains = redhat.com -masquerade_exceptions = root apache - -# ADDRESS REDIRECTION (VIRTUAL DOMAIN) -# -# The VIRTUAL_README document gives information about the many forms -# of domain hosting that Postfix supports. - -# "USER HAS MOVED" BOUNCE MESSAGES -# -# See the discussion in the ADDRESS_REWRITING_README document. - -# TRANSPORT MAP -# -# See the discussion in the ADDRESS_REWRITING_README document. - -# ALIAS DATABASE -# -# The alias_maps parameter specifies the list of alias databases used -# by the local delivery agent. The default list is system dependent. -# -# On systems with NIS, the default is to search the local alias -# database, then the NIS alias database. See aliases(5) for syntax -# details. -# -# If you change the alias database, run "postalias /etc/aliases" (or -# wherever your system stores the mail alias file), or simply run -# "newaliases" to build the necessary DBM or DB file. -# -# It will take a minute or so before changes become visible. Use -# "postfix reload" to eliminate the delay. -# -#alias_maps = dbm:/etc/aliases -alias_maps = hash:/etc/aliases -#alias_maps = hash:/etc/aliases, nis:mail.aliases -#alias_maps = netinfo:/aliases - -# The alias_database parameter specifies the alias database(s) that -# are built with "newaliases" or "sendmail -bi". This is a separate -# configuration parameter, because alias_maps (see above) may specify -# tables that are not necessarily all under control by Postfix. -# -#alias_database = dbm:/etc/aliases -#alias_database = dbm:/etc/mail/aliases -alias_database = hash:/etc/aliases -#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases - -# ADDRESS EXTENSIONS (e.g., user+foo) -# -# The recipient_delimiter parameter specifies the separator between -# user names and address extensions (user+foo). See canonical(5), -# local(8), relocated(5) and virtual(5) for the effects this has on -# aliases, canonical, virtual, relocated and .forward file lookups. -# Basically, the software tries user+foo and .forward+foo before -# trying user and .forward. -# -recipient_delimiter = + - -# DELIVERY TO MAILBOX -# -# The home_mailbox parameter specifies the optional pathname of a -# mailbox file relative to a user's home directory. The default -# mailbox file is /var/spool/mail/user or /var/mail/user. Specify -# "Maildir/" for qmail-style delivery (the / is required). -# -#home_mailbox = Mailbox -#home_mailbox = Maildir/ - -# The mail_spool_directory parameter specifies the directory where -# UNIX-style mailboxes are kept. The default setting depends on the -# system type. -# -#mail_spool_directory = /var/mail -#mail_spool_directory = /var/spool/mail - -# The mailbox_command parameter specifies the optional external -# command to use instead of mailbox delivery. The command is run as -# the recipient with proper HOME, SHELL and LOGNAME environment settings. -# Exception: delivery for root is done as $default_user. -# -# Other environment variables of interest: USER (recipient username), -# EXTENSION (address extension), DOMAIN (domain part of address), -# and LOCAL (the address localpart). -# -# Unlike other Postfix configuration parameters, the mailbox_command -# parameter is not subjected to $parameter substitutions. This is to -# make it easier to specify shell syntax (see example below). -# -# Avoid shell meta characters because they will force Postfix to run -# an expensive shell process. Procmail alone is expensive enough. -# -# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN -# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. -# -mailbox_command = /usr/bin/procmail -#mailbox_command = /some/where/procmail -a "$EXTENSION" - -# The mailbox_transport specifies the optional transport in master.cf -# to use after processing aliases and .forward files. This parameter -# has precedence over the mailbox_command, fallback_transport and -# luser_relay parameters. -# -# Specify a string of the form transport:nexthop, where transport is -# the name of a mail delivery transport defined in master.cf. The -# :nexthop part is optional. For more details see the sample transport -# configuration file. -# -# NOTE: if you use this feature for accounts not in the UNIX password -# file, then you must update the "local_recipient_maps" setting in -# the main.cf file, otherwise the SMTP server will reject mail for -# non-UNIX accounts with "User unknown in local recipient table". -# -#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp - -# If using the cyrus-imapd IMAP server deliver local mail to the IMAP -# server using LMTP (Local Mail Transport Protocol), this is prefered -# over the older cyrus deliver program by setting the -# mailbox_transport as below: -# -# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp -# -# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via -# these settings. -# -# local_destination_recipient_limit = 300 -# local_destination_concurrency_limit = 5 -# -# Of course you should adjust these settings as appropriate for the -# capacity of the hardware you are using. The recipient limit setting -# can be used to take advantage of the single instance message store -# capability of Cyrus. The concurrency limit can be used to control -# how many simultaneous LMTP sessions will be permitted to the Cyrus -# message store. -# -# To use the old cyrus deliver program you have to set: -#mailbox_transport = cyrus - -# The fallback_transport specifies the optional transport in master.cf -# to use for recipients that are not found in the UNIX passwd database. -# This parameter has precedence over the luser_relay parameter. -# -# Specify a string of the form transport:nexthop, where transport is -# the name of a mail delivery transport defined in master.cf. The -# :nexthop part is optional. For more details see the sample transport -# configuration file. -# -# NOTE: if you use this feature for accounts not in the UNIX password -# file, then you must update the "local_recipient_maps" setting in -# the main.cf file, otherwise the SMTP server will reject mail for -# non-UNIX accounts with "User unknown in local recipient table". -# -#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp -#fallback_transport = - -#transport_maps = hash:/etc/postfix/transport -# The luser_relay parameter specifies an optional destination address -# for unknown recipients. By default, mail for unknown@$mydestination, -# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned -# as undeliverable. -# -# The following expansions are done on luser_relay: $user (recipient -# username), $shell (recipient shell), $home (recipient home directory), -# $recipient (full recipient address), $extension (recipient address -# extension), $domain (recipient domain), $local (entire recipient -# localpart), $recipient_delimiter. Specify ${name?value} or -# ${name:value} to expand value only when $name does (does not) exist. -# -# luser_relay works only for the default Postfix local delivery agent. -# -# NOTE: if you use this feature for accounts not in the UNIX password -# file, then you must specify "local_recipient_maps =" (i.e. empty) in -# the main.cf file, otherwise the SMTP server will reject mail for -# non-UNIX accounts with "User unknown in local recipient table". -# -#luser_relay = $user(a)other.host -#luser_relay = $local(a)other.host -#luser_relay = admin+$local - -# JUNK MAIL CONTROLS -# -# The controls listed here are only a very small subset. The file -# SMTPD_ACCESS_README provides an overview. - -# The header_checks parameter specifies an optional table with patterns -# that each logical message header is matched against, including -# headers that span multiple physical lines. -# -# By default, these patterns also apply to MIME headers and to the -# headers of attached messages. With older Postfix versions, MIME and -# attached message headers were treated as body text. -# -# For details, see "man header_checks". -# -header_checks = regexp:/etc/postfix/header_checks - -# FAST ETRN SERVICE -# -# Postfix maintains per-destination logfiles with information about -# deferred mail, so that mail can be flushed quickly with the SMTP -# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld". -# See the ETRN_README document for a detailed description. -# -# The fast_flush_domains parameter controls what destinations are -# eligible for this service. By default, they are all domains that -# this server is willing to relay mail to. -# -#fast_flush_domains = $relay_domains - -# SHOW SOFTWARE VERSION OR NOT -# -# The smtpd_banner parameter specifies the text that follows the 220 -# code in the SMTP server's greeting banner. Some people like to see -# the mail version advertised. By default, Postfix shows no version. -# -# You MUST specify $myhostname at the start of the text. That is an -# RFC requirement. Postfix itself does not care. -# -#smtpd_banner = $myhostname ESMTP $mail_name -#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version) - -# PARALLEL DELIVERY TO THE SAME DESTINATION -# -# How many parallel deliveries to the same user or domain? With local -# delivery, it does not make sense to do massively parallel delivery -# to the same user, because mailbox updates must happen sequentially, -# and expensive pipelines in .forward files can cause disasters when -# too many are run at the same time. With SMTP deliveries, 10 -# simultaneous connections to the same domain could be sufficient to -# raise eyebrows. -# -# Each message delivery transport has its XXX_destination_concurrency_limit -# parameter. The default is $default_destination_concurrency_limit for -# most delivery transports. For the local delivery agent the default is 2. - -#local_destination_concurrency_limit = 2 -#default_destination_concurrency_limit = 20 - -# DEBUGGING CONTROL -# -# The debug_peer_level parameter specifies the increment in verbose -# logging level when an SMTP client or server host name or address -# matches a pattern in the debug_peer_list parameter. -# -debug_peer_level = 2 - -# The debug_peer_list parameter specifies an optional list of domain -# or network patterns, /file/name patterns or type:name tables. When -# an SMTP client or server host name or address matches a pattern, -# increase the verbose logging level by the amount specified in the -# debug_peer_level parameter. -# -#debug_peer_list = 127.0.0.1 -#debug_peer_list = some.domain - -# The debugger_command specifies the external command that is executed -# when a Postfix daemon program is run with the -D option. -# -# Use "command .. & sleep 5" so that the debugger can attach before -# the process marches on. If you use an X-based debugger, be sure to -# set up your XAUTHORITY environment variable before starting Postfix. -# -debugger_command = - PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin - xxgdb $daemon_directory/$process_name $process_id & sleep 5 - -# If you can't use X, use this to capture the call stack when a -# daemon crashes. The result is in a file in the configuration -# directory, and is named after the process name and the process ID. -# -# debugger_command = -# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; -# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 -# >$config_directory/$process_name.$process_id.log & sleep 5 -# -# Another possibility is to run gdb under a detached screen session. -# To attach to the screen sesssion, su root and run "screen -r -# <id_string>" where <id_string> uniquely matches one of the detached -# sessions (from "screen -list"). -# -# debugger_command = -# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen -# -dmS $process_name gdb $daemon_directory/$process_name -# $process_id & sleep 1 - -# INSTALL-TIME CONFIGURATION INFORMATION -# -# The following parameters are used when installing a new Postfix version. -# -# sendmail_path: The full pathname of the Postfix sendmail command. -# This is the Sendmail-compatible mail posting interface. -# -sendmail_path = /usr/sbin/sendmail.postfix - -# newaliases_path: The full pathname of the Postfix newaliases command. -# This is the Sendmail-compatible command to build alias databases. -# -newaliases_path = /usr/bin/newaliases.postfix - -# mailq_path: The full pathname of the Postfix mailq command. This -# is the Sendmail-compatible mail queue listing command. -# -mailq_path = /usr/bin/mailq.postfix - -# setgid_group: The group for mail submission and queue management -# commands. This must be a group name with a numerical group ID that -# is not shared with other accounts, not even with the Postfix account. -# -setgid_group = postdrop - -# html_directory: The location of the Postfix HTML documentation. -# -html_directory = no - -# manpage_directory: The location of the Postfix on-line manual pages. -# -manpage_directory = /usr/share/man - -# sample_directory: The location of the Postfix sample configuration files. -# This parameter is obsolete as of Postfix 2.1. -# -sample_directory = /usr/share/doc/postfix-2.4.5/samples - -# readme_directory: The location of the Postfix README files. -# -readme_directory = /usr/share/doc/postfix-2.4.5/README_FILES - -# add this to new postfix to get it to add proper message-id and other -# headers to outgoing emails via the gateway. - - diff --git a/modules/postfix/files/main.cf/main.cf.gateway b/modules/postfix/files/main.cf/main.cf.gateway new file mode 100644 index 0000000..f0b52de --- /dev/null +++ b/modules/postfix/files/main.cf/main.cf.gateway @@ -0,0 +1,704 @@ +# Global Postfix configuration file. This file lists only a subset +# of all parameters. For the syntax, and for a complete parameter +# list, see the postconf(5) manual page (command: "man 5 postconf"). +# +# For common configuration examples, see BASIC_CONFIGURATION_README +# and STANDARD_CONFIGURATION_README. To find these documents, use +# the command "postconf html_directory readme_directory", or go to +# http://www.postfix.org/. +# +# For best results, change no more than 2-3 parameters at a time, +# and test if Postfix still works after every change. + +# Custom rules + +# SOFT BOUNCE +# +# The soft_bounce parameter provides a limited safety net for +# testing. When soft_bounce is enabled, mail will remain queued that +# would otherwise bounce. This parameter disables locally-generated +# bounces, and prevents the SMTP server from rejecting mail permanently +# (by changing 5xx replies into 4xx replies). However, soft_bounce +# is no cure for address rewriting mistakes or mail routing mistakes. +# +#soft_bounce = no + +# LOCAL PATHNAME INFORMATION +# +# The queue_directory specifies the location of the Postfix queue. +# This is also the root directory of Postfix daemons that run chrooted. +# See the files in examples/chroot-setup for setting up Postfix chroot +# environments on different UNIX systems. +# +queue_directory = /var/spool/postfix + +# The command_directory parameter specifies the location of all +# postXXX commands. +# +command_directory = /usr/sbin + +# The daemon_directory parameter specifies the location of all Postfix +# daemon programs (i.e. programs listed in the master.cf file). This +# directory must be owned by root. +# +daemon_directory = /usr/libexec/postfix + +# The data_directory parameter specifies the location of Postfix-writable +# data files (caches, random numbers). This directory must be owned +# by the mail_owner account (see below). +# +data_directory = /var/lib/postfix + +# QUEUE AND PROCESS OWNERSHIP +# +# The mail_owner parameter specifies the owner of the Postfix queue +# and of most Postfix daemon processes. Specify the name of a user +# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS +# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In +# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED +# USER. +# +mail_owner = postfix + +# The default_privs parameter specifies the default rights used by +# the local delivery agent for delivery to external file or command. +# These rights are used in the absence of a recipient user context. +# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER. +# +#default_privs = nobody + +# INTERNET HOST AND DOMAIN NAMES +# +# The myhostname parameter specifies the internet hostname of this +# mail system. The default is to use the fully-qualified domain name +# from gethostname(). $myhostname is used as a default value for many +# other configuration parameters. +# +#myhostname = host.domain.tld +#myhostname = virtual.domain.tld + + +smtp_helo_name = bastion.fedoraproject.org + +# The mydomain parameter specifies the local internet domain name. +# The default is to use $myhostname minus the first component. +# $mydomain is used as a default value for many other configuration +# parameters. +# +#mydomain = domain.tld + +mydomain = fedoraproject.org + +# SENDING MAIL +# +# The myorigin parameter specifies the domain that locally-posted +# mail appears to come from. The default is to append $myhostname, +# which is fine for small sites. If you run a domain with multiple +# machines, you should (1) change this to $mydomain and (2) set up +# a domain-wide alias database that aliases each user to +# user(a)that.users.mailhost. +# +# For the sake of consistency between sender and recipient addresses, +# myorigin also specifies the default domain name that is appended +# to recipient addresses that have no @domain part. +# +#myorigin = $myhostname +#myorigin = $mydomain + +myorigin = fedoraproject.org + +# RECEIVING MAIL + +# The inet_interfaces parameter specifies the network interface +# addresses that this mail system receives mail on. By default, +# the software claims all active interfaces on the machine. The +# parameter also controls delivery of mail to user(a)[ip.address]. +# +# See also the proxy_interfaces parameter, for network addresses that +# are forwarded to us via a proxy or network address translator. +# +# Note: you need to stop/start Postfix when this parameter changes. +# +#inet_interfaces = all +#inet_interfaces = $myhostname +#inet_interfaces = $myhostname, localhost + +inet_interfaces = all + +# The proxy_interfaces parameter specifies the network interface +# addresses that this mail system receives mail on by way of a +# proxy or network address translation unit. This setting extends +# the address list specified with the inet_interfaces parameter. +# +# You must specify your proxy/NAT addresses when your system is a +# backup MX host for other domains, otherwise mail delivery loops +# will happen when the primary MX host is down. +# +#proxy_interfaces = +#proxy_interfaces = 1.2.3.4 + +# The mydestination parameter specifies the list of domains that this +# machine considers itself the final destination for. +# +# These domains are routed to the delivery agent specified with the +# local_transport parameter setting. By default, that is the UNIX +# compatible delivery agent that lookups all recipients in /etc/passwd +# and /etc/aliases or their equivalent. +# +# The default is $myhostname + localhost.$mydomain. On a mail domain +# gateway, you should also include $mydomain. +# +# Do not specify the names of virtual domains - those domains are +# specified elsewhere (see VIRTUAL_README). +# +# Do not specify the names of domains that this machine is backup MX +# host for. Specify those names via the relay_domains settings for +# the SMTP server, or use permit_mx_backup if you are lazy (see +# STANDARD_CONFIGURATION_README). +# +# The local machine is always the final destination for mail addressed +# to user(a)[the.net.work.address] of an interface that the mail system +# receives mail on (see the inet_interfaces parameter). +# +# Specify a list of host or domain names, /file/name or type:table +# patterns, separated by commas and/or whitespace. A /file/name +# pattern is replaced by its contents; a type:table is matched when +# a name matches a lookup key (the right-hand side is ignored). +# Continue long lines by starting the next line with whitespace. +# +# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS". +# + +mydestination = $myhostname, localhost.$mydomain, fedora.redhat.com, localhost , $mydomain +#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain +#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, +# mail.$mydomain, www.$mydomain, ftp.$mydomain + +# REJECTING MAIL FOR UNKNOWN LOCAL USERS +# +# The local_recipient_maps parameter specifies optional lookup tables +# with all names or addresses of users that are local with respect +# to $mydestination, $inet_interfaces or $proxy_interfaces. +# +# If this parameter is defined, then the SMTP server will reject +# mail for unknown local users. This parameter is defined by default. +# +# To turn off local recipient checking in the SMTP server, specify +# local_recipient_maps = (i.e. empty). +# +# The default setting assumes that you use the default Postfix local +# delivery agent for local delivery. You need to update the +# local_recipient_maps setting if: +# +# - You define $mydestination domain recipients in files other than +# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files. +# For example, you define $mydestination domain recipients in +# the $virtual_mailbox_maps files. +# +# - You redefine the local delivery agent in master.cf. +# +# - You redefine the "local_transport" setting in main.cf. +# +# - You use the "luser_relay", "mailbox_transport", or "fallback_transport" +# feature of the Postfix local delivery agent (see local(8)). +# +# Details are described in the LOCAL_RECIPIENT_README file. +# +# Beware: if the Postfix SMTP server runs chrooted, you probably have +# to access the passwd file via the proxymap service, in order to +# overcome chroot restrictions. The alternative, having a copy of +# the system passwd file in the chroot jail is just not practical. +# +# The right-hand side of the lookup tables is conveniently ignored. +# In the left-hand side, specify a bare username, an @domain.tld +# wild-card, or specify a user(a)domain.tld address. +# +#local_recipient_maps = unix:passwd.byname $alias_maps +#local_recipient_maps = proxy:unix:passwd.byname $alias_maps +#local_recipient_maps = +local_recipient_maps = $alias_maps hash:/etc/postfix/relay_recipient_maps + +# The unknown_local_recipient_reject_code specifies the SMTP server +# response code when a recipient domain matches $mydestination or +# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty +# and the recipient address or address local-part is not found. +# +# The default setting is 550 (reject mail) but it is safer to start +# with 450 (try again later) until you are certain that your +# local_recipient_maps settings are OK. +# +unknown_local_recipient_reject_code = 550 + +# TRUST AND RELAY CONTROL + +# The mynetworks parameter specifies the list of "trusted" SMTP +# clients that have more privileges than "strangers". +# +# In particular, "trusted" SMTP clients are allowed to relay mail +# through Postfix. See the smtpd_recipient_restrictions parameter +# in postconf(5). +# +# You can specify the list of "trusted" network addresses by hand +# or you can let Postfix do it for you (which is the default). +# +# By default (mynetworks_style = subnet), Postfix "trusts" SMTP +# clients in the same IP subnetworks as the local machine. +# On Linux, this does works correctly only with interfaces specified +# with the "ifconfig" command. +# +# Specify "mynetworks_style = class" when Postfix should "trust" SMTP +# clients in the same IP class A/B/C networks as the local machine. +# Don't do this with a dialup site - it would cause Postfix to "trust" +# your entire provider's network. Instead, specify an explicit +# mynetworks list by hand, as described below. +# +# Specify "mynetworks_style = host" when Postfix should "trust" +# only the local machine. +# +#mynetworks_style = class +#mynetworks_style = subnet +#mynetworks_style = host + + +# Alternatively, you can specify the mynetworks list by hand, in +# which case Postfix ignores the mynetworks_style setting. +# +# Specify an explicit list of network/netmask patterns, where the +# mask specifies the number of bits in the network part of a host +# address. +# +# You can also specify the absolute pathname of a pattern file instead +# of listing the patterns here. Specify type:table for table-based lookups +# (the value on the table right-hand side is not used). +# +#mynetworks = 168.100.189.0/28, 127.0.0.0/8 +#mynetworks = $config_directory/mynetworks +#mynetworks = hash:/etc/postfix/network_table + +mynetworks = localhost.localdomain, localhost, 127.0.0.1, 10.5.125.0/24, 10.5.126.0/24, 10.5.127.0/24, 192.168.0.0/16 + +# The relay_domains parameter restricts what destinations this system will +# relay mail to. See the smtpd_recipient_restrictions description in +# postconf(5) for detailed information. +# +# By default, Postfix relays mail +# - from "trusted" clients (IP address matches $mynetworks) to any destination, +# - from "untrusted" clients to destinations that match $relay_domains or +# subdomains thereof, except addresses with sender-specified routing. +# The default relay_domains value is $mydestination. +# +# In addition to the above, the Postfix SMTP server by default accepts mail +# that Postfix is final destination for: +# - destinations that match $inet_interfaces or $proxy_interfaces, +# - destinations that match $mydestination +# - destinations that match $virtual_alias_domains, +# - destinations that match $virtual_mailbox_domains. +# These destinations do not need to be listed in $relay_domains. +# +# Specify a list of hosts or domains, /file/name patterns or type:name +# lookup tables, separated by commas and/or whitespace. Continue +# long lines by starting the next line with whitespace. A file name +# is replaced by its contents; a type:name table is matched when a +# (parent) domain appears as lookup key. +# +# NOTE: Postfix will not automatically forward mail for domains that +# list this system as their primary or backup MX host. See the +# permit_mx_backup restriction description in postconf(5). +# +#relay_domains = $mydestination + +relay_domains = $mydestination fedora.phx.redhat.com + +# INTERNET OR INTRANET + +# The relayhost parameter specifies the default host to send mail to +# when no entry is matched in the optional transport(5) table. When +# no relayhost is given, mail is routed directly to the destination. +# +# On an intranet, specify the organizational domain name. If your +# internal DNS uses no MX records, specify the name of the intranet +# gateway host instead. +# +# In the case of SMTP, specify a domain, host, host:port, [host]:port, +# [address] or [address]:port; the form [host] turns off MX lookups. +# +# If you're connected via UUCP, see also the default_transport parameter. +# +#relayhost = $mydomain +#relayhost = [gateway.my.domain] +#relayhost = [mailserver.isp.tld] +#relayhost = uucphost +#relayhost = [an.ip.add.ress] + + +# REJECTING UNKNOWN RELAY USERS +# +# The relay_recipient_maps parameter specifies optional lookup tables +# with all addresses in the domains that match $relay_domains. +# +# If this parameter is defined, then the SMTP server will reject +# mail for unknown relay users. This feature is off by default. +# +# The right-hand side of the lookup tables is conveniently ignored. +# In the left-hand side, specify an @domain.tld wild-card, or specify +# a user(a)domain.tld address. +# +#relay_recipient_maps = hash:/etc/postfix/relay_recipients + +# INPUT RATE CONTROL +# +# The in_flow_delay configuration parameter implements mail input +# flow control. This feature is turned on by default, although it +# still needs further development (it's disabled on SCO UNIX due +# to an SCO bug). +# +# A Postfix process will pause for $in_flow_delay seconds before +# accepting a new message, when the message arrival rate exceeds the +# message delivery rate. With the default 100 SMTP server process +# limit, this limits the mail inflow to 100 messages a second more +# than the number of messages delivered per second. +# +# Specify 0 to disable the feature. Valid delays are 0..10. +# +#in_flow_delay = 1s + +# ADDRESS REWRITING +# +# The ADDRESS_REWRITING_README document gives information about +# address masquerading or other forms of address rewriting including +# username->Firstname.Lastname mapping. + +# ADDRESS REDIRECTION (VIRTUAL DOMAIN) +# +# The VIRTUAL_README document gives information about the many forms +# of domain hosting that Postfix supports. + +# "USER HAS MOVED" BOUNCE MESSAGES +# +# See the discussion in the ADDRESS_REWRITING_README document. + +# TRANSPORT MAP +# +# See the discussion in the ADDRESS_REWRITING_README document. + +# ALIAS DATABASE +# +# The alias_maps parameter specifies the list of alias databases used +# by the local delivery agent. The default list is system dependent. +# +# On systems with NIS, the default is to search the local alias +# database, then the NIS alias database. See aliases(5) for syntax +# details. +# +# If you change the alias database, run "postalias /etc/aliases" (or +# wherever your system stores the mail alias file), or simply run +# "newaliases" to build the necessary DBM or DB file. +# +# It will take a minute or so before changes become visible. Use +# "postfix reload" to eliminate the delay. +# +#alias_maps = dbm:/etc/aliases +alias_maps = hash:/etc/aliases +alias_maps = hash:/etc/aliases, hash:/etc/postfix/package-owner +#alias_maps = hash:/etc/aliases, nis:mail.aliases +#alias_maps = netinfo:/aliases + +# The alias_database parameter specifies the alias database(s) that +# are built with "newaliases" or "sendmail -bi". This is a separate +# configuration parameter, because alias_maps (see above) may specify +# tables that are not necessarily all under control by Postfix. +# +#alias_database = dbm:/etc/aliases +#alias_database = dbm:/etc/mail/aliases +alias_database = hash:/etc/aliases +#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases + +# ADDRESS EXTENSIONS (e.g., user+foo) +# +# The recipient_delimiter parameter specifies the separator between +# user names and address extensions (user+foo). See canonical(5), +# local(8), relocated(5) and virtual(5) for the effects this has on +# aliases, canonical, virtual, relocated and .forward file lookups. +# Basically, the software tries user+foo and .forward+foo before +# trying user and .forward. +# +recipient_delimiter = + + +# DELIVERY TO MAILBOX +# +# The home_mailbox parameter specifies the optional pathname of a +# mailbox file relative to a user's home directory. The default +# mailbox file is /var/spool/mail/user or /var/mail/user. Specify +# "Maildir/" for qmail-style delivery (the / is required). +# +#home_mailbox = Mailbox +#home_mailbox = Maildir/ + +# The mail_spool_directory parameter specifies the directory where +# UNIX-style mailboxes are kept. The default setting depends on the +# system type. +# +#mail_spool_directory = /var/mail +#mail_spool_directory = /var/spool/mail + +# The mailbox_command parameter specifies the optional external +# command to use instead of mailbox delivery. The command is run as +# the recipient with proper HOME, SHELL and LOGNAME environment settings. +# Exception: delivery for root is done as $default_user. +# +# Other environment variables of interest: USER (recipient username), +# EXTENSION (address extension), DOMAIN (domain part of address), +# and LOCAL (the address localpart). +# +# Unlike other Postfix configuration parameters, the mailbox_command +# parameter is not subjected to $parameter substitutions. This is to +# make it easier to specify shell syntax (see example below). +# +# Avoid shell meta characters because they will force Postfix to run +# an expensive shell process. Procmail alone is expensive enough. +# +# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN +# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. +# +#mailbox_command = /some/where/procmail +#mailbox_command = /some/where/procmail -a "$EXTENSION" + +# The mailbox_transport specifies the optional transport in master.cf +# to use after processing aliases and .forward files. This parameter +# has precedence over the mailbox_command, fallback_transport and +# luser_relay parameters. +# +# Specify a string of the form transport:nexthop, where transport is +# the name of a mail delivery transport defined in master.cf. The +# :nexthop part is optional. For more details see the sample transport +# configuration file. +# +# NOTE: if you use this feature for accounts not in the UNIX password +# file, then you must update the "local_recipient_maps" setting in +# the main.cf file, otherwise the SMTP server will reject mail for +# non-UNIX accounts with "User unknown in local recipient table". +# +#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp + +# If using the cyrus-imapd IMAP server deliver local mail to the IMAP +# server using LMTP (Local Mail Transport Protocol), this is prefered +# over the older cyrus deliver program by setting the +# mailbox_transport as below: +# +# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp +# +# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via +# these settings. +# +# local_destination_recipient_limit = 300 +# local_destination_concurrency_limit = 5 +# +# Of course you should adjust these settings as appropriate for the +# capacity of the hardware you are using. The recipient limit setting +# can be used to take advantage of the single instance message store +# capability of Cyrus. The concurrency limit can be used to control +# how many simultaneous LMTP sessions will be permitted to the Cyrus +# message store. +# +# To use the old cyrus deliver program you have to set: +#mailbox_transport = cyrus + + +mailbox_transport = lmtp:10.5.126.73:2003 + +# The fallback_transport specifies the optional transport in master.cf +# to use for recipients that are not found in the UNIX passwd database. +# This parameter has precedence over the luser_relay parameter. +# +# Specify a string of the form transport:nexthop, where transport is +# the name of a mail delivery transport defined in master.cf. The +# :nexthop part is optional. For more details see the sample transport +# configuration file. +# +# NOTE: if you use this feature for accounts not in the UNIX password +# file, then you must update the "local_recipient_maps" setting in +# the main.cf file, otherwise the SMTP server will reject mail for +# non-UNIX accounts with "User unknown in local recipient table". +# +#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp +#fallback_transport = + +# The luser_relay parameter specifies an optional destination address +# for unknown recipients. By default, mail for unknown@$mydestination, +# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned +# as undeliverable. +# +# The following expansions are done on luser_relay: $user (recipient +# username), $shell (recipient shell), $home (recipient home directory), +# $recipient (full recipient address), $extension (recipient address +# extension), $domain (recipient domain), $local (entire recipient +# localpart), $recipient_delimiter. Specify ${name?value} or +# ${name:value} to expand value only when $name does (does not) exist. +# +# luser_relay works only for the default Postfix local delivery agent. +# +# NOTE: if you use this feature for accounts not in the UNIX password +# file, then you must specify "local_recipient_maps =" (i.e. empty) in +# the main.cf file, otherwise the SMTP server will reject mail for +# non-UNIX accounts with "User unknown in local recipient table". +# +#luser_relay = $user(a)other.host +#luser_relay = $local(a)other.host +#luser_relay = admin+$local + +# JUNK MAIL CONTROLS +# +# The controls listed here are only a very small subset. The file +# SMTPD_ACCESS_README provides an overview. + +# The header_checks parameter specifies an optional table with patterns +# that each logical message header is matched against, including +# headers that span multiple physical lines. +# +# By default, these patterns also apply to MIME headers and to the +# headers of attached messages. With older Postfix versions, MIME and +# attached message headers were treated as body text. +# +# For details, see "man header_checks". +# +#header_checks = regexp:/etc/postfix/header_checks + +# FAST ETRN SERVICE +# +# Postfix maintains per-destination logfiles with information about +# deferred mail, so that mail can be flushed quickly with the SMTP +# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld". +# See the ETRN_README document for a detailed description. +# +# The fast_flush_domains parameter controls what destinations are +# eligible for this service. By default, they are all domains that +# this server is willing to relay mail to. +# +#fast_flush_domains = $relay_domains + +# SHOW SOFTWARE VERSION OR NOT +# +# The smtpd_banner parameter specifies the text that follows the 220 +# code in the SMTP server's greeting banner. Some people like to see +# the mail version advertised. By default, Postfix shows no version. +# +# You MUST specify $myhostname at the start of the text. That is an +# RFC requirement. Postfix itself does not care. +# +#smtpd_banner = $myhostname ESMTP $mail_name +#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version) + +# PARALLEL DELIVERY TO THE SAME DESTINATION +# +# How many parallel deliveries to the same user or domain? With local +# delivery, it does not make sense to do massively parallel delivery +# to the same user, because mailbox updates must happen sequentially, +# and expensive pipelines in .forward files can cause disasters when +# too many are run at the same time. With SMTP deliveries, 10 +# simultaneous connections to the same domain could be sufficient to +# raise eyebrows. +# +# Each message delivery transport has its XXX_destination_concurrency_limit +# parameter. The default is $default_destination_concurrency_limit for +# most delivery transports. For the local delivery agent the default is 2. + +#local_destination_concurrency_limit = 2 +#default_destination_concurrency_limit = 20 + +# DEBUGGING CONTROL +# +# The debug_peer_level parameter specifies the increment in verbose +# logging level when an SMTP client or server host name or address +# matches a pattern in the debug_peer_list parameter. +# +debug_peer_level = 2 + +# The debug_peer_list parameter specifies an optional list of domain +# or network patterns, /file/name patterns or type:name tables. When +# an SMTP client or server host name or address matches a pattern, +# increase the verbose logging level by the amount specified in the +# debug_peer_level parameter. +# +#debug_peer_list = 127.0.0.1 +#debug_peer_list = some.domain + +# The debugger_command specifies the external command that is executed +# when a Postfix daemon program is run with the -D option. +# +# Use "command .. & sleep 5" so that the debugger can attach before +# the process marches on. If you use an X-based debugger, be sure to +# set up your XAUTHORITY environment variable before starting Postfix. +# +debugger_command = + PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin + ddd $daemon_directory/$process_name $process_id & sleep 5 + +# If you can't use X, use this to capture the call stack when a +# daemon crashes. The result is in a file in the configuration +# directory, and is named after the process name and the process ID. +# +# debugger_command = +# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; +# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 +# >$config_directory/$process_name.$process_id.log & sleep 5 +# +# Another possibility is to run gdb under a detached screen session. +# To attach to the screen sesssion, su root and run "screen -r +# <id_string>" where <id_string> uniquely matches one of the detached +# sessions (from "screen -list"). +# +# debugger_command = +# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen +# -dmS $process_name gdb $daemon_directory/$process_name +# $process_id & sleep 1 + +# INSTALL-TIME CONFIGURATION INFORMATION +# +# The following parameters are used when installing a new Postfix version. +# +# sendmail_path: The full pathname of the Postfix sendmail command. +# This is the Sendmail-compatible mail posting interface. +# +sendmail_path = /usr/sbin/sendmail.postfix + +# newaliases_path: The full pathname of the Postfix newaliases command. +# This is the Sendmail-compatible command to build alias databases. +# +newaliases_path = /usr/bin/newaliases.postfix + +# mailq_path: The full pathname of the Postfix mailq command. This +# is the Sendmail-compatible mail queue listing command. +# +mailq_path = /usr/bin/mailq.postfix + +# setgid_group: The group for mail submission and queue management +# commands. This must be a group name with a numerical group ID that +# is not shared with other accounts, not even with the Postfix account. +# +setgid_group = postdrop + +# html_directory: The location of the Postfix HTML documentation. +# +html_directory = no + +# manpage_directory: The location of the Postfix on-line manual pages. +# +manpage_directory = /usr/share/man + +# sample_directory: The location of the Postfix sample configuration files. +# This parameter is obsolete as of Postfix 2.1. +# +sample_directory = /usr/share/doc/postfix-2.5.6/samples + +# readme_directory: The location of the Postfix README files. +# +readme_directory = /usr/share/doc/postfix-2.5.6/README_FILES +# Enable IPv4, and IPv6 if supported +inet_protocols = all + +# mapping so we know where to go for .redhat.com mail + +transport_maps = hash:/etc/postfix/transport +local_header_rewrite_clients = static:all + + diff --git a/modules/postfix/files/main.cf/main.cf.phx b/modules/postfix/files/main.cf/main.cf.phx new file mode 100644 index 0000000..1707639 --- /dev/null +++ b/modules/postfix/files/main.cf/main.cf.phx @@ -0,0 +1,685 @@ +# "false" +# Global Postfix configuration file. This file lists only a subset +# of all parameters. For the syntax, and for a complete parameter +# list, see the postconf(5) manual page (command: "man 5 postconf"). +# +# For common configuration examples, see BASIC_CONFIGURATION_README +# and STANDARD_CONFIGURATION_README. To find these documents, use +# the command "postconf html_directory readme_directory", or go to +# http://www.postfix.org/. +# +# For best results, change no more than 2-3 parameters at a time, +# and test if Postfix still works after every change. + +# SOFT BOUNCE +# +# The soft_bounce parameter provides a limited safety net for +# testing. When soft_bounce is enabled, mail will remain queued that +# would otherwise bounce. This parameter disables locally-generated +# bounces, and prevents the SMTP server from rejecting mail permanently +# (by changing 5xx replies into 4xx replies). However, soft_bounce +# is no cure for address rewriting mistakes or mail routing mistakes. +# +#soft_bounce = no + +# LOCAL PATHNAME INFORMATION +# +# The queue_directory specifies the location of the Postfix queue. +# This is also the root directory of Postfix daemons that run chrooted. +# See the files in examples/chroot-setup for setting up Postfix chroot +# environments on different UNIX systems. +# +queue_directory = /var/spool/postfix + +# The command_directory parameter specifies the location of all +# postXXX commands. +# +command_directory = /usr/sbin + +# The daemon_directory parameter specifies the location of all Postfix +# daemon programs (i.e. programs listed in the master.cf file). This +# directory must be owned by root. +# +daemon_directory = /usr/libexec/postfix + +# QUEUE AND PROCESS OWNERSHIP +# +# The mail_owner parameter specifies the owner of the Postfix queue +# and of most Postfix daemon processes. Specify the name of a user +# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS +# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In +# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED +# USER. +# +mail_owner = postfix + +# The default_privs parameter specifies the default rights used by +# the local delivery agent for delivery to external file or command. +# These rights are used in the absence of a recipient user context. +# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER. +# +#default_privs = nobody + +# INTERNET HOST AND DOMAIN NAMES +# +# The myhostname parameter specifies the internet hostname of this +# mail system. The default is to use the fully-qualified domain name +# from gethostname(). $myhostname is used as a default value for many +# other configuration parameters. +# +#myhostname = host.domain.tld +#myhostname = virtual.domain.tld + +# The mydomain parameter specifies the local internet domain name. +# The default is to use $myhostname minus the first component. +# $mydomain is used as a default value for many other configuration +# parameters. +# +#mydomain = domain.tld + +# SENDING MAIL +# +# The myorigin parameter specifies the domain that locally-posted +# mail appears to come from. The default is to append $myhostname, +# which is fine for small sites. If you run a domain with multiple +# machines, you should (1) change this to $mydomain and (2) set up +# a domain-wide alias database that aliases each user to +# user(a)that.users.mailhost. +# +# For the sake of consistency between sender and recipient addresses, +# myorigin also specifies the default domain name that is appended +# to recipient addresses that have no @domain part. +# +#myorigin = $myhostname +#myorigin = $mydomain + +mydomain = fedoraproject.org +myorigin = fedoraproject.org + +# RECEIVING MAIL + +# The inet_interfaces parameter specifies the network interface +# addresses that this mail system receives mail on. By default, +# the software claims all active interfaces on the machine. The +# parameter also controls delivery of mail to user(a)[ip.address]. +# +# See also the proxy_interfaces parameter, for network addresses that +# are forwarded to us via a proxy or network address translator. +# +# Note: you need to stop/start Postfix when this parameter changes. +# +#inet_interfaces = all +#inet_interfaces = $myhostname +#inet_interfaces = $myhostname, localhost +inet_interfaces = all + +# The proxy_interfaces parameter specifies the network interface +# addresses that this mail system receives mail on by way of a +# proxy or network address translation unit. This setting extends +# the address list specified with the inet_interfaces parameter. +# +# You must specify your proxy/NAT addresses when your system is a +# backup MX host for other domains, otherwise mail delivery loops +# will happen when the primary MX host is down. +# +#proxy_interfaces = +#proxy_interfaces = 1.2.3.4 + +# The mydestination parameter specifies the list of domains that this +# machine considers itself the final destination for. +# +# These domains are routed to the delivery agent specified with the +# local_transport parameter setting. By default, that is the UNIX +# compatible delivery agent that lookups all recipients in /etc/passwd +# and /etc/aliases or their equivalent. +# +# The default is $myhostname + localhost.$mydomain. On a mail domain +# gateway, you should also include $mydomain. +# +# Do not specify the names of virtual domains - those domains are +# specified elsewhere (see VIRTUAL_README). +# +# Do not specify the names of domains that this machine is backup MX +# host for. Specify those names via the relay_domains settings for +# the SMTP server, or use permit_mx_backup if you are lazy (see +# STANDARD_CONFIGURATION_README). +# +# The local machine is always the final destination for mail addressed +# to user(a)[the.net.work.address] of an interface that the mail system +# receives mail on (see the inet_interfaces parameter). +# +# Specify a list of host or domain names, /file/name or type:table +# patterns, separated by commas and/or whitespace. A /file/name +# pattern is replaced by its contents; a type:table is matched when +# a name matches a lookup key (the right-hand side is ignored). +# Continue long lines by starting the next line with whitespace. +# +# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS". +# +mydestination = $myhostname, localhost.$mydomain, fedora.redhat.com, localhost +#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain +#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, +# mail.$mydomain, www.$mydomain, ftp.$mydomain + +# REJECTING MAIL FOR UNKNOWN LOCAL USERS +# +# The local_recipient_maps parameter specifies optional lookup tables +# with all names or addresses of users that are local with respect +# to $mydestination, $inet_interfaces or $proxy_interfaces. +# +# If this parameter is defined, then the SMTP server will reject +# mail for unknown local users. This parameter is defined by default. +# +# To turn off local recipient checking in the SMTP server, specify +# local_recipient_maps = (i.e. empty). +# +# The default setting assumes that you use the default Postfix local +# delivery agent for local delivery. You need to update the +# local_recipient_maps setting if: +# +# - You define $mydestination domain recipients in files other than +# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files. +# For example, you define $mydestination domain recipients in +# the $virtual_mailbox_maps files. +# +# - You redefine the local delivery agent in master.cf. +# +# - You redefine the "local_transport" setting in main.cf. +# +# - You use the "luser_relay", "mailbox_transport", or "fallback_transport" +# feature of the Postfix local delivery agent (see local(8)). +# +# Details are described in the LOCAL_RECIPIENT_README file. +# +# Beware: if the Postfix SMTP server runs chrooted, you probably have +# to access the passwd file via the proxymap service, in order to +# overcome chroot restrictions. The alternative, having a copy of +# the system passwd file in the chroot jail is just not practical. +# +# The right-hand side of the lookup tables is conveniently ignored. +# In the left-hand side, specify a bare username, an @domain.tld +# wild-card, or specify a user(a)domain.tld address. +# +#local_recipient_maps = unix:passwd.byname $alias_maps +#local_recipient_maps = proxy:unix:passwd.byname $alias_maps +#local_recipient_maps = + +# The unknown_local_recipient_reject_code specifies the SMTP server +# response code when a recipient domain matches $mydestination or +# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty +# and the recipient address or address local-part is not found. +# +# The default setting is 550 (reject mail) but it is safer to start +# with 450 (try again later) until you are certain that your +# local_recipient_maps settings are OK. +# +unknown_local_recipient_reject_code = 550 + +# TRUST AND RELAY CONTROL + +# The mynetworks parameter specifies the list of "trusted" SMTP +# clients that have more privileges than "strangers". +# +# In particular, "trusted" SMTP clients are allowed to relay mail +# through Postfix. See the smtpd_recipient_restrictions parameter +# in postconf(5). +# +# You can specify the list of "trusted" network addresses by hand +# or you can let Postfix do it for you (which is the default). +# +# By default (mynetworks_style = subnet), Postfix "trusts" SMTP +# clients in the same IP subnetworks as the local machine. +# On Linux, this does works correctly only with interfaces specified +# with the "ifconfig" command. +# +# Specify "mynetworks_style = class" when Postfix should "trust" SMTP +# clients in the same IP class A/B/C networks as the local machine. +# Don't do this with a dialup site - it would cause Postfix to "trust" +# your entire provider's network. Instead, specify an explicit +# mynetworks list by hand, as described below. +# +# Specify "mynetworks_style = host" when Postfix should "trust" +# only the local machine. +# +#mynetworks_style = class +#mynetworks_style = subnet +#mynetworks_style = host + +# Alternatively, you can specify the mynetworks list by hand, in +# which case Postfix ignores the mynetworks_style setting. +# +# Specify an explicit list of network/netmask patterns, where the +# mask specifies the number of bits in the network part of a host +# address. +# +# You can also specify the absolute pathname of a pattern file instead +# of listing the patterns here. Specify type:table for table-based lookups +# (the value on the table right-hand side is not used). +# +#mynetworks = 168.100.189.0/28, 127.0.0.0/8 +#mynetworks = $config_directory/mynetworks +#mynetworks = hash:/etc/postfix/network_table + + +# The relay_domains parameter restricts what destinations this system will +# relay mail to. See the smtpd_recipient_restrictions description in +# postconf(5) for detailed information. +# +# By default, Postfix relays mail +# - from "trusted" clients (IP address matches $mynetworks) to any destination, +# - from "untrusted" clients to destinations that match $relay_domains or +# subdomains thereof, except addresses with sender-specified routing. +# The default relay_domains value is $mydestination. +# +# In addition to the above, the Postfix SMTP server by default accepts mail +# that Postfix is final destination for: +# - destinations that match $inet_interfaces or $proxy_interfaces, +# - destinations that match $mydestination +# - destinations that match $virtual_alias_domains, +# - destinations that match $virtual_mailbox_domains. +# These destinations do not need to be listed in $relay_domains. +# +# Specify a list of hosts or domains, /file/name patterns or type:name +# lookup tables, separated by commas and/or whitespace. Continue +# long lines by starting the next line with whitespace. A file name +# is replaced by its contents; a type:name table is matched when a +# (parent) domain appears as lookup key. +# +# NOTE: Postfix will not automatically forward mail for domains that +# list this system as their primary or backup MX host. See the +# permit_mx_backup restriction description in postconf(5). +# +#relay_domains = $mydestination + + + +# INTERNET OR INTRANET + +# The relayhost parameter specifies the default host to send mail to +# when no entry is matched in the optional transport(5) table. When +# no relayhost is given, mail is routed directly to the destination. +# +# On an intranet, specify the organizational domain name. If your +# internal DNS uses no MX records, specify the name of the intranet +# gateway host instead. +# +# In the case of SMTP, specify a domain, host, host:port, [host]:port, +# [address] or [address]:port; the form [host] turns off MX lookups. +# +# If you're connected via UUCP, see also the default_transport parameter. +# +#relayhost = $mydomain +#relayhost = [gateway.my.domain] +#relayhost = [mailserver.isp.tld] +#relayhost = uucphost +#relayhost = [an.ip.add.ress] +relayhost = bastion + + +# REJECTING UNKNOWN RELAY USERS +# +# The relay_recipient_maps parameter specifies optional lookup tables +# with all addresses in the domains that match $relay_domains. +# +# If this parameter is defined, then the SMTP server will reject +# mail for unknown relay users. This feature is off by default. +# +# The right-hand side of the lookup tables is conveniently ignored. +# In the left-hand side, specify an @domain.tld wild-card, or specify +# a user(a)domain.tld address. +# +#relay_recipient_maps = hash:/etc/postfix/relay_recipients + +# INPUT RATE CONTROL +# +# The in_flow_delay configuration parameter implements mail input +# flow control. This feature is turned on by default, although it +# still needs further development (it's disabled on SCO UNIX due +# to an SCO bug). +# +# A Postfix process will pause for $in_flow_delay seconds before +# accepting a new message, when the message arrival rate exceeds the +# message delivery rate. With the default 100 SMTP server process +# limit, this limits the mail inflow to 100 messages a second more +# than the number of messages delivered per second. +# +# Specify 0 to disable the feature. Valid delays are 0..10. +# +#in_flow_delay = 1s + +# ADDRESS REWRITING +# +# The ADDRESS_REWRITING_README document gives information about +# address masquerading or other forms of address rewriting including +# username->Firstname.Lastname mapping. + +masquerade_domains = redhat.com +masquerade_exceptions = root apache + +# ADDRESS REDIRECTION (VIRTUAL DOMAIN) +# +# The VIRTUAL_README document gives information about the many forms +# of domain hosting that Postfix supports. + +# "USER HAS MOVED" BOUNCE MESSAGES +# +# See the discussion in the ADDRESS_REWRITING_README document. + +# TRANSPORT MAP +# +# See the discussion in the ADDRESS_REWRITING_README document. + +# ALIAS DATABASE +# +# The alias_maps parameter specifies the list of alias databases used +# by the local delivery agent. The default list is system dependent. +# +# On systems with NIS, the default is to search the local alias +# database, then the NIS alias database. See aliases(5) for syntax +# details. +# +# If you change the alias database, run "postalias /etc/aliases" (or +# wherever your system stores the mail alias file), or simply run +# "newaliases" to build the necessary DBM or DB file. +# +# It will take a minute or so before changes become visible. Use +# "postfix reload" to eliminate the delay. +# +#alias_maps = dbm:/etc/aliases +alias_maps = hash:/etc/aliases +#alias_maps = hash:/etc/aliases, nis:mail.aliases +#alias_maps = netinfo:/aliases + +# The alias_database parameter specifies the alias database(s) that +# are built with "newaliases" or "sendmail -bi". This is a separate +# configuration parameter, because alias_maps (see above) may specify +# tables that are not necessarily all under control by Postfix. +# +#alias_database = dbm:/etc/aliases +#alias_database = dbm:/etc/mail/aliases +alias_database = hash:/etc/aliases +#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases + +# ADDRESS EXTENSIONS (e.g., user+foo) +# +# The recipient_delimiter parameter specifies the separator between +# user names and address extensions (user+foo). See canonical(5), +# local(8), relocated(5) and virtual(5) for the effects this has on +# aliases, canonical, virtual, relocated and .forward file lookups. +# Basically, the software tries user+foo and .forward+foo before +# trying user and .forward. +# +recipient_delimiter = + + +# DELIVERY TO MAILBOX +# +# The home_mailbox parameter specifies the optional pathname of a +# mailbox file relative to a user's home directory. The default +# mailbox file is /var/spool/mail/user or /var/mail/user. Specify +# "Maildir/" for qmail-style delivery (the / is required). +# +#home_mailbox = Mailbox +#home_mailbox = Maildir/ + +# The mail_spool_directory parameter specifies the directory where +# UNIX-style mailboxes are kept. The default setting depends on the +# system type. +# +#mail_spool_directory = /var/mail +#mail_spool_directory = /var/spool/mail + +# The mailbox_command parameter specifies the optional external +# command to use instead of mailbox delivery. The command is run as +# the recipient with proper HOME, SHELL and LOGNAME environment settings. +# Exception: delivery for root is done as $default_user. +# +# Other environment variables of interest: USER (recipient username), +# EXTENSION (address extension), DOMAIN (domain part of address), +# and LOCAL (the address localpart). +# +# Unlike other Postfix configuration parameters, the mailbox_command +# parameter is not subjected to $parameter substitutions. This is to +# make it easier to specify shell syntax (see example below). +# +# Avoid shell meta characters because they will force Postfix to run +# an expensive shell process. Procmail alone is expensive enough. +# +# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN +# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER. +# +mailbox_command = /usr/bin/procmail +#mailbox_command = /some/where/procmail -a "$EXTENSION" + +# The mailbox_transport specifies the optional transport in master.cf +# to use after processing aliases and .forward files. This parameter +# has precedence over the mailbox_command, fallback_transport and +# luser_relay parameters. +# +# Specify a string of the form transport:nexthop, where transport is +# the name of a mail delivery transport defined in master.cf. The +# :nexthop part is optional. For more details see the sample transport +# configuration file. +# +# NOTE: if you use this feature for accounts not in the UNIX password +# file, then you must update the "local_recipient_maps" setting in +# the main.cf file, otherwise the SMTP server will reject mail for +# non-UNIX accounts with "User unknown in local recipient table". +# +#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp + +# If using the cyrus-imapd IMAP server deliver local mail to the IMAP +# server using LMTP (Local Mail Transport Protocol), this is prefered +# over the older cyrus deliver program by setting the +# mailbox_transport as below: +# +# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp +# +# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via +# these settings. +# +# local_destination_recipient_limit = 300 +# local_destination_concurrency_limit = 5 +# +# Of course you should adjust these settings as appropriate for the +# capacity of the hardware you are using. The recipient limit setting +# can be used to take advantage of the single instance message store +# capability of Cyrus. The concurrency limit can be used to control +# how many simultaneous LMTP sessions will be permitted to the Cyrus +# message store. +# +# To use the old cyrus deliver program you have to set: +#mailbox_transport = cyrus + +# The fallback_transport specifies the optional transport in master.cf +# to use for recipients that are not found in the UNIX passwd database. +# This parameter has precedence over the luser_relay parameter. +# +# Specify a string of the form transport:nexthop, where transport is +# the name of a mail delivery transport defined in master.cf. The +# :nexthop part is optional. For more details see the sample transport +# configuration file. +# +# NOTE: if you use this feature for accounts not in the UNIX password +# file, then you must update the "local_recipient_maps" setting in +# the main.cf file, otherwise the SMTP server will reject mail for +# non-UNIX accounts with "User unknown in local recipient table". +# +#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp +#fallback_transport = + +#transport_maps = hash:/etc/postfix/transport +# The luser_relay parameter specifies an optional destination address +# for unknown recipients. By default, mail for unknown@$mydestination, +# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned +# as undeliverable. +# +# The following expansions are done on luser_relay: $user (recipient +# username), $shell (recipient shell), $home (recipient home directory), +# $recipient (full recipient address), $extension (recipient address +# extension), $domain (recipient domain), $local (entire recipient +# localpart), $recipient_delimiter. Specify ${name?value} or +# ${name:value} to expand value only when $name does (does not) exist. +# +# luser_relay works only for the default Postfix local delivery agent. +# +# NOTE: if you use this feature for accounts not in the UNIX password +# file, then you must specify "local_recipient_maps =" (i.e. empty) in +# the main.cf file, otherwise the SMTP server will reject mail for +# non-UNIX accounts with "User unknown in local recipient table". +# +#luser_relay = $user(a)other.host +#luser_relay = $local(a)other.host +#luser_relay = admin+$local + +# JUNK MAIL CONTROLS +# +# The controls listed here are only a very small subset. The file +# SMTPD_ACCESS_README provides an overview. + +# The header_checks parameter specifies an optional table with patterns +# that each logical message header is matched against, including +# headers that span multiple physical lines. +# +# By default, these patterns also apply to MIME headers and to the +# headers of attached messages. With older Postfix versions, MIME and +# attached message headers were treated as body text. +# +# For details, see "man header_checks". +# +header_checks = regexp:/etc/postfix/header_checks + +# FAST ETRN SERVICE +# +# Postfix maintains per-destination logfiles with information about +# deferred mail, so that mail can be flushed quickly with the SMTP +# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld". +# See the ETRN_README document for a detailed description. +# +# The fast_flush_domains parameter controls what destinations are +# eligible for this service. By default, they are all domains that +# this server is willing to relay mail to. +# +#fast_flush_domains = $relay_domains + +# SHOW SOFTWARE VERSION OR NOT +# +# The smtpd_banner parameter specifies the text that follows the 220 +# code in the SMTP server's greeting banner. Some people like to see +# the mail version advertised. By default, Postfix shows no version. +# +# You MUST specify $myhostname at the start of the text. That is an +# RFC requirement. Postfix itself does not care. +# +#smtpd_banner = $myhostname ESMTP $mail_name +#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version) + +# PARALLEL DELIVERY TO THE SAME DESTINATION +# +# How many parallel deliveries to the same user or domain? With local +# delivery, it does not make sense to do massively parallel delivery +# to the same user, because mailbox updates must happen sequentially, +# and expensive pipelines in .forward files can cause disasters when +# too many are run at the same time. With SMTP deliveries, 10 +# simultaneous connections to the same domain could be sufficient to +# raise eyebrows. +# +# Each message delivery transport has its XXX_destination_concurrency_limit +# parameter. The default is $default_destination_concurrency_limit for +# most delivery transports. For the local delivery agent the default is 2. + +#local_destination_concurrency_limit = 2 +#default_destination_concurrency_limit = 20 + +# DEBUGGING CONTROL +# +# The debug_peer_level parameter specifies the increment in verbose +# logging level when an SMTP client or server host name or address +# matches a pattern in the debug_peer_list parameter. +# +debug_peer_level = 2 + +# The debug_peer_list parameter specifies an optional list of domain +# or network patterns, /file/name patterns or type:name tables. When +# an SMTP client or server host name or address matches a pattern, +# increase the verbose logging level by the amount specified in the +# debug_peer_level parameter. +# +#debug_peer_list = 127.0.0.1 +#debug_peer_list = some.domain + +# The debugger_command specifies the external command that is executed +# when a Postfix daemon program is run with the -D option. +# +# Use "command .. & sleep 5" so that the debugger can attach before +# the process marches on. If you use an X-based debugger, be sure to +# set up your XAUTHORITY environment variable before starting Postfix. +# +debugger_command = + PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin + xxgdb $daemon_directory/$process_name $process_id & sleep 5 + +# If you can't use X, use this to capture the call stack when a +# daemon crashes. The result is in a file in the configuration +# directory, and is named after the process name and the process ID. +# +# debugger_command = +# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; +# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 +# >$config_directory/$process_name.$process_id.log & sleep 5 +# +# Another possibility is to run gdb under a detached screen session. +# To attach to the screen sesssion, su root and run "screen -r +# <id_string>" where <id_string> uniquely matches one of the detached +# sessions (from "screen -list"). +# +# debugger_command = +# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen +# -dmS $process_name gdb $daemon_directory/$process_name +# $process_id & sleep 1 + +# INSTALL-TIME CONFIGURATION INFORMATION +# +# The following parameters are used when installing a new Postfix version. +# +# sendmail_path: The full pathname of the Postfix sendmail command. +# This is the Sendmail-compatible mail posting interface. +# +sendmail_path = /usr/sbin/sendmail.postfix + +# newaliases_path: The full pathname of the Postfix newaliases command. +# This is the Sendmail-compatible command to build alias databases. +# +newaliases_path = /usr/bin/newaliases.postfix + +# mailq_path: The full pathname of the Postfix mailq command. This +# is the Sendmail-compatible mail queue listing command. +# +mailq_path = /usr/bin/mailq.postfix + +# setgid_group: The group for mail submission and queue management +# commands. This must be a group name with a numerical group ID that +# is not shared with other accounts, not even with the Postfix account. +# +setgid_group = postdrop + +# html_directory: The location of the Postfix HTML documentation. +# +html_directory = no + +# manpage_directory: The location of the Postfix on-line manual pages. +# +manpage_directory = /usr/share/man + +# sample_directory: The location of the Postfix sample configuration files. +# This parameter is obsolete as of Postfix 2.1. +# +sample_directory = /usr/share/doc/postfix-2.4.5/samples + +# readme_directory: The location of the Postfix README files. +# +readme_directory = /usr/share/doc/postfix-2.4.5/README_FILES + +# add this to new postfix to get it to add proper message-id and other +# headers to outgoing emails via the gateway. + + diff --git a/modules/postfix/files/master.cf/master.cf b/modules/postfix/files/master.cf/master.cf new file mode 100644 index 0000000..d6aec25 --- /dev/null +++ b/modules/postfix/files/master.cf/master.cf @@ -0,0 +1,96 @@ +# +# Postfix master process configuration file. For details on the format +# of the file, see the master(5) manual page (command: "man 5 master"). +# +# ========================================================================== +# service type private unpriv chroot wakeup maxproc command + args +# (yes) (yes) (yes) (never) (100) +# ========================================================================== +smtp inet n - n - - smtpd +#submission inet n - n - - smtpd +# -o smtpd_enforce_tls=yes +# -o smtpd_sasl_auth_enable=yes +# -o smtpd_client_restrictions=permit_sasl_authenticated,reject +#628 inet n - n - - qmqpd +pickup fifo n - n 60 1 pickup +cleanup unix n - n - 0 cleanup +qmgr fifo n - n 300 1 qmgr +#qmgr fifo n - n 300 1 oqmgr +tlsmgr unix - - n 1000? 1 tlsmgr +rewrite unix - - n - - trivial-rewrite +bounce unix - - n - 0 bounce +defer unix - - n - 0 bounce +trace unix - - n - 0 bounce +verify unix - - n - 1 verify +flush unix n - n 1000? 0 flush +proxymap unix - - n - - proxymap +smtp unix - - n - - smtp +# When relaying mail as backup MX, disable fallback_relay to avoid MX loops +relay unix - - n - - smtp + -o fallback_relay= +# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 +showq unix n - n - - showq +error unix - - n - - error +retry unix - - n - - error +discard unix - - n - - discard +local unix - n n - - local +virtual unix - n n - - virtual +lmtp unix - - n - - lmtp +anvil unix - - n - 1 anvil +scache unix - - n - 1 scache +# +# ==================================================================== +# Interfaces to non-Postfix software. Be sure to examine the manual +# pages of the non-Postfix software to find out what options it wants. +# +# Many of the following services use the Postfix pipe(8) delivery +# agent. See the pipe(8) man page for information about ${recipient} +# and other message envelope options. +# ==================================================================== +# +# maildrop. See the Postfix MAILDROP_README file for details. +# Also specify in main.cf: maildrop_destination_recipient_limit=1 +# +#maildrop unix - n n - - pipe +# flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient} +# +# ==================================================================== +# +# The Cyrus deliver program has changed incompatibly, multiple times. +# +#old-cyrus unix - n n - - pipe +# flags=R user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -m ${extension} ${user} +# +# ==================================================================== +# +# Cyrus 2.1.5 (Amos Gouaux) +# Also specify in main.cf: cyrus_destination_recipient_limit=1 +# +#cyrus unix - n n - - pipe +# user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m ${extension} ${user} +# +# ==================================================================== +# +# See the Postfix UUCP_README file for configuration details. +# +#uucp unix - n n - - pipe +# flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) +# +# ==================================================================== +# +# Other external delivery methods. +# +#ifmail unix - n n - - pipe +# flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) +# +#bsmtp unix - n n - - pipe +# flags=Fq. user=bsmtp argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient +# +#scalemail-backend unix - n n - 2 pipe +# flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store +# ${nexthop} ${user} ${extension} +# +#mailman unix - n n - - pipe +# flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py +# ${nexthop} ${user} + diff --git a/modules/postfix/files/master.cf/master.cf.hosted01 b/modules/postfix/files/master.cf/master.cf.hosted01 new file mode 100644 index 0000000..10d6c23 --- /dev/null +++ b/modules/postfix/files/master.cf/master.cf.hosted01 @@ -0,0 +1,98 @@ +# +# Postfix master process configuration file. For details on the format +# of the file, see the master(5) manual page (command: "man 5 master"). +# +# ========================================================================== +# service type private unpriv chroot wakeup maxproc command + args +# (yes) (yes) (yes) (never) (100) +# ========================================================================== +smtp inet n - n - - smtpd -o content_filter=spamassassin +#submission inet n - n - - smtpd +# -o smtpd_enforce_tls=yes +# -o smtpd_sasl_auth_enable=yes +# -o smtpd_client_restrictions=permit_sasl_authenticated,reject +#628 inet n - n - - qmqpd +pickup fifo n - n 60 1 pickup +cleanup unix n - n - 0 cleanup +qmgr fifo n - n 300 1 qmgr +#qmgr fifo n - n 300 1 oqmgr +tlsmgr unix - - n 1000? 1 tlsmgr +rewrite unix - - n - - trivial-rewrite +bounce unix - - n - 0 bounce +defer unix - - n - 0 bounce +trace unix - - n - 0 bounce +verify unix - - n - 1 verify +flush unix n - n 1000? 0 flush +proxymap unix - - n - - proxymap +smtp unix - - n - - smtp +# When relaying mail as backup MX, disable fallback_relay to avoid MX loops +relay unix - - n - - smtp + -o fallback_relay= +# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 +showq unix n - n - - showq +error unix - - n - - error +retry unix - - n - - error +discard unix - - n - - discard +local unix - n n - - local +virtual unix - n n - - virtual +lmtp unix - - n - - lmtp +anvil unix - - n - 1 anvil +scache unix - - n - 1 scache +# +# ==================================================================== +# Interfaces to non-Postfix software. Be sure to examine the manual +# pages of the non-Postfix software to find out what options it wants. +# +# Many of the following services use the Postfix pipe(8) delivery +# agent. See the pipe(8) man page for information about ${recipient} +# and other message envelope options. +# ==================================================================== +# +# maildrop. See the Postfix MAILDROP_README file for details. +# Also specify in main.cf: maildrop_destination_recipient_limit=1 +# +#maildrop unix - n n - - pipe +# flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient} +# +# ==================================================================== +# +# The Cyrus deliver program has changed incompatibly, multiple times. +# +#old-cyrus unix - n n - - pipe +# flags=R user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -m ${extension} ${user} +# +# ==================================================================== +# +# Cyrus 2.1.5 (Amos Gouaux) +# Also specify in main.cf: cyrus_destination_recipient_limit=1 +# +#cyrus unix - n n - - pipe +# user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m ${extension} ${user} +# +# ==================================================================== +# +# See the Postfix UUCP_README file for configuration details. +# +#uucp unix - n n - - pipe +# flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) +# +# ==================================================================== +# +# Other external delivery methods. +# +#ifmail unix - n n - - pipe +# flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) +# +#bsmtp unix - n n - - pipe +# flags=Fq. user=bsmtp argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient +# +#scalemail-backend unix - n n - 2 pipe +# flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store +# ${nexthop} ${user} ${extension} +# +#mailman unix - n n - - pipe +# flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py +# ${nexthop} ${user} + +spamassassin unix - n n - - pipe user=spammy argv=/usr/bin/spamc -e /usr/sbin/sendmail.postfix -oi -f ${sender} ${recipient} + diff --git a/modules/postfix/files/master.cf/master.cf.value b/modules/postfix/files/master.cf/master.cf.value new file mode 100644 index 0000000..3800ecc --- /dev/null +++ b/modules/postfix/files/master.cf/master.cf.value @@ -0,0 +1,100 @@ +# +# Postfix master process configuration file. For details on the format +# of the file, see the master(5) manual page (command: "man 5 master"). +# +# ========================================================================== +# service type private unpriv chroot wakeup maxproc command + args +# (yes) (yes) (yes) (never) (100) +# ========================================================================== +smtp inet n - n - - smtpd +#submission inet n - n - - smtpd +# -o smtpd_enforce_tls=yes +# -o smtpd_sasl_auth_enable=yes +# -o smtpd_client_restrictions=permit_sasl_authenticated,reject +smtps inet n - n - - smtpd + -o smtpd_tls_wrappermode=yes + -o smtpd_sasl_auth_enable=yes + -o smtpd_client_restrictions=permit_sasl_authenticated,reject +#628 inet n - n - - qmqpd +pickup fifo n - n 60 1 pickup +cleanup unix n - n - 0 cleanup +qmgr fifo n - n 300 1 qmgr +#qmgr fifo n - n 300 1 oqmgr +tlsmgr unix - - n 1000? 1 tlsmgr +rewrite unix - - n - - trivial-rewrite +bounce unix - - n - 0 bounce +defer unix - - n - 0 bounce +trace unix - - n - 0 bounce +verify unix - - n - 1 verify +flush unix n - n 1000? 0 flush +proxymap unix - - n - - proxymap +smtp unix - - n - - smtp +# When relaying mail as backup MX, disable fallback_relay to avoid MX loops +relay unix - - n - - smtp + -o fallback_relay= +# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 +showq unix n - n - - showq +error unix - - n - - error +retry unix - - n - - error +discard unix - - n - - discard +local unix - n n - - local +virtual unix - n n - - virtual +lmtp unix - - n - - lmtp +anvil unix - - n - 1 anvil +scache unix - - n - 1 scache +# +# ==================================================================== +# Interfaces to non-Postfix software. Be sure to examine the manual +# pages of the non-Postfix software to find out what options it wants. +# +# Many of the following services use the Postfix pipe(8) delivery +# agent. See the pipe(8) man page for information about ${recipient} +# and other message envelope options. +# ==================================================================== +# +# maildrop. See the Postfix MAILDROP_README file for details. +# Also specify in main.cf: maildrop_destination_recipient_limit=1 +# +#maildrop unix - n n - - pipe +# flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient} +# +# ==================================================================== +# +# The Cyrus deliver program has changed incompatibly, multiple times. +# +#old-cyrus unix - n n - - pipe +# flags=R user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -m ${extension} ${user} +# +# ==================================================================== +# +# Cyrus 2.1.5 (Amos Gouaux) +# Also specify in main.cf: cyrus_destination_recipient_limit=1 +# +#cyrus unix - n n - - pipe +# user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m ${extension} ${user} +# +# ==================================================================== +# +# See the Postfix UUCP_README file for configuration details. +# +#uucp unix - n n - - pipe +# flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) +# +# ==================================================================== +# +# Other external delivery methods. +# +#ifmail unix - n n - - pipe +# flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) +# +#bsmtp unix - n n - - pipe +# flags=Fq. user=bsmtp argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient +# +#scalemail-backend unix - n n - 2 pipe +# flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store +# ${nexthop} ${user} ${extension} +# +#mailman unix - n n - - pipe +# flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py +# ${nexthop} ${user} + diff --git a/modules/postfix/manifests/init.pp b/modules/postfix/manifests/init.pp index 0014122..72513e1 100644 --- a/modules/postfix/manifests/init.pp +++ b/modules/postfix/manifests/init.pp @@ -2,41 +2,11 @@ class postfix::server { # back port to work with new master.cf file - - $smtps=false + # AFAICT THIS IS NOT USED AT ALL package { postfix: ensure => present } - if $isRelayGateway { - $notRelayGateway = '' - } else { - $isRelayGateway = false - } - - if $relayHost { - $notRelayHost = '' - } else { - $relayHost = 'bastion' - } - - if $spamEnabled { - $notSpamEnabled = '' - } else { - $spamEnabled = false - } - - if $isMailmanSMTP { - $notisMailmanSMTP = '' - } else { - $isMailmanSMTP = false - } - if $transport_maps { - $transport_maps = '' - } else { - $transport_maps = 'hash:/etc/postfix/transport' - } - service { postfix: ensure => running, enable => true, @@ -44,13 +14,25 @@ class postfix::server { } file { '/etc/postfix/main.cf': - content => template("postfix/main.cf.erb"), + source => [ + "puppet:///postfix/main.cf/main.cf.$fqdn", + "puppet:///postfix/main.cf/main.cf.$hostname", + "puppet:///postfix/main.cf/main.cf.$postfix_group", + "puppet:///postfix/main.cf/main.cf.$datacenter", + "puppet:///postfix/main.cf/main.cf", + ], mode => 0644, notify => Service['postfix'], require => Package['postfix'] } file { '/etc/postfix/master.cf': - content => template("postfix/master.cf.erb"), + source => [ + "puppet:///postfix/master.cf/master.cf.$fqdn", + "puppet:///postfix/master.cf/master.cf.$hostname", + "puppet:///postfix/master.cf/master.cf.$postfix_group", + "puppet:///postfix/master.cf/master.cf.$datacenter", + "puppet:///postfix/master.cf/master.cf", + ], mode => 0644, notify => Service['postfix'], require => Package['postfix'] @@ -58,26 +40,6 @@ class postfix::server { } -class postfix::relay_server inherits postfix::server { - $isRelayGateway=1 -} - -class postfix::mailman_smtp inherits postfix::relay_server { - - file { '/etc/postfix/transports': - source => 'puppet:///postfix/transports', - owner => root, - group => root, - mode => 0644, - notify => [ Service['postfix'], Exec['rebuild_transports']], - require => Package['postfix'], - } - exec { rebuild_transports: - command => '/usr/sbin/postmap /etc/postfix/transport', - refreshonly => true - } -} - define postfix::transport () { file { "/etc/postfix/transport": source => "puppet:///postfix/$name", @@ -91,29 +53,6 @@ define postfix::transport () { } define postfix::postfix ( - $myhostname='', - $mydomain='', - $myorigin='', - $inet_interfaces='', - $mydestination='', - $mynetworks_style='', - $mynetworks='', - $relay_domains='', - $relayhost='', - $transport_maps='', - $alias_maps='hash:/etc/aliases', - $smtp_helo_name='$myhostname', - $mailbox_transport='', - $custom='', - $smtps=false, - $local_recipient_maps='' - ) { - - if $spamEnabled { - $notSpamEnabled = '' - } else { - $spamEnabled = false - } package { postfix: ensure => present @@ -126,14 +65,25 @@ define postfix::postfix ( } file { '/etc/postfix/main.cf': - content => template("postfix/main.cf.default.erb"), + source => [ + "puppet:///postfix/main.cf/main.cf.$fqdn", + "puppet:///postfix/main.cf/main.cf.$hostname", + "puppet:///postfix/main.cf/main.cf.$postfix_group", + "puppet:///postfix/main.cf/main.cf.$datacenter", + "puppet:///postfix/main.cf/main.cf", + ], mode => 0644, notify => Service['postfix'], require => Package['postfix'] } - file { '/etc/postfix/master.cf': - content => template("postfix/master.cf.erb"), + source => [ + "puppet:///postfix/master.cf/master.cf.$fqdn", + "puppet:///postfix/master.cf/master.cf.$hostname", + "puppet:///postfix/master.cf/master.cf.$postfix_group", + "puppet:///postfix/master.cf/master.cf.$datacenter", + "puppet:///postfix/master.cf/master.cf", + ], mode => 0644, notify => Service['postfix'], require => Package['postfix'] -- 1.7.2.1

2 2

Freeze break request: Switch back to bastion02 for now
by Kevin Fenzi 16 Sep '11

16 Sep '11

We've continued to have issues with bastion03 and this bug: https://bugzilla.redhat.com/show_bug.cgi?id=725332 It's been requiring a reboot every day or two, resulting in 5-10min of downtime and about 90 pages. ;( I hate changes on fridays and more so during a freeze, but I think we need to switch back to bastion02 for now to avoid this issue until we can get a fix. So, I would like to: - commit the following patch. - puppet update nameservers to get the new info. - puppet update bastion02/03 to get openvpn running on 02 and stopped on 03 - Make sure everything reconnects. Unfortunately this will result in a small outage, but no worse than the bastion03 ones have been. If we don't want to do it now, I can wait until the next time bastion03 freaks out and just change it then, since it should be all prepped below: diff --git a/manifests/nodes/bastion02.phx2.fedoraproject.org.pp b/manifests/nodes/bastion02.phx2.fe index 4018ec9..1a0ee7c 100644 --- a/manifests/nodes/bastion02.phx2.fedoraproject.org.pp +++ b/manifests/nodes/bastion02.phx2.fedoraproject.org.pp @@ -1,6 +1,5 @@ node bastion02{ - # Moving openvpn over to bastion03 - $enable_openvpn = false + $enable_openvpn = true include phx $syncFasAliases = true include gateway diff --git a/manifests/nodes/bastion03.phx2.fedoraproject.org.pp b/manifests/nodes/bastion03.phx2.fe index 8c5fca9..b7b0f32 100644 --- a/manifests/nodes/bastion03.phx2.fedoraproject.org.pp +++ b/manifests/nodes/bastion03.phx2.fedoraproject.org.pp @@ -3,7 +3,7 @@ node bastion03{ # comment out the line below when bastion02 is down or going to be down. # Under normal situations, only one bastion host should be running openvpn # or we'll end up with a split-brain problem in the network - #$enable_openvpn = false + $enable_openvpn = false include phx $syncFasAliases = true include gateway diff --git a/modules/bind/files/master/fedoraproject.org b/modules/bind/files/master/fedoraproject.o index 5b72f2d..f3dc836 100644 --- a/modules/bind/files/master/fedoraproject.org +++ b/modules/bind/files/master/fedoraproject.org @@ -1,6 +1,6 @@ $TTL 3600 @ IN SOA ns01.fedoraproject.org. hostmaster.fedoraproject.org. ( - 2011091301 ; Serial + 2011091601 ; Serial 1H ; refresh 10M ; retry 4W ; expire @@ -85,7 +85,7 @@ autoqa-stg IN A 209.132.181.9 ; need rhit to fix. bastion01 IN A 209.132.181.2 bastion02 IN A 209.132.181.3 -bastion IN A 209.132.181.2 +bastion IN A 209.132.181.3 bastion-comm01 IN A 209.132.181.13 backup02 IN A 152.19.134.140 blogs IN CNAME wildcard diff --git a/modules/bind/files/master/phx2.fedoraproject.org b/modules/bind/files/master/phx2.fedor index b8caea3..7c9eed7 100644 --- a/modules/bind/files/master/phx2.fedoraproject.org +++ b/modules/bind/files/master/phx2.fedoraproject.org @@ -28,7 +28,7 @@ bapp01 IN A 10.5.126.38 bapp1 IN CNAME bapp01 bapp02 IN A 10.5.126.39 bapp2 IN CNAME bapp02 -bastion IN CNAME bastion03 +bastion IN CNAME bastion02 ;bastion01 IN A 10.5.126.13 ;bastion1 IN CNAME bastion01 bastion02 IN A 10.5.126.11

4 4

Plan for tomorrow's Fedora Infrastructure meeting (2011-09-15)
by Kevin Fenzi 15 Sep '11

15 Sep '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-09-15 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * Password/Ssh-key/Cert reset flag day discussion. * Bastion outages/openvpn discussion. * Upcoming Tasks/Items (nirik) 2011-09-13 - 27: Beta change freeze 2011-09-27: Fedora 16 Beta 2011-10-01 mail fi-apprentice folks. 2011-10-09 Remove inactive fi-apprentice people. 2011-10-18 - 2011-11-01: Final change freeze 2011-11-01: Fedora 16 release. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/report/10 NOTE: I have cleaned out the ones that have been sitting around with this tag. Anytime anyone would like to discuss a ticket, just add the meeting keyword and we will get to it in this section. * Request for Resources progress report - askfedora - paste Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

RHEL 6 packages information
by Roberto Sassu 14 Sep '11

14 Sep '11

Hi all i'm trying to obtain the update type information about released RHEL 6 packages. Unfortunately, this information is not available in the Fedora database. There is a place where i can get it? Thanks in advance for replies Regards Roberto Sassu

2 3

bastion03 outage this afternoon
by Kevin Fenzi 14 Sep '11

14 Sep '11

We had an outage of bastion03 this afternoon. Because it's the vpn hub, lots of services were affected. It looks like it's running into https://bugzilla.redhat.com/show_bug.cgi?id=725332 So, if this re-occurs, we should either: a) switch it to use e1000 instead of virtio network devices. or b) switch back to bastion02 (which is still there and rhel5). So, keep an eye out for outages of services where you see a lot of ping loss or not answer at all from bastion.fedoraproject.org. For the record, the outage started at 22:45 and ran until 22:55 or so. kevin

3 3

[Change Request] Fix checkout and pull ordering.
by Ricky Zhou 13 Sep '11

13 Sep '11

This change is needed for the beta website and releases.txt changes. --- modules/fedora-web/files/syncStatic.sh | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/modules/fedora-web/files/syncStatic.sh b/modules/fedora-web/files/syncStatic.sh index ffbf781..5cf0644 100644 --- a/modules/fedora-web/files/syncStatic.sh +++ b/modules/fedora-web/files/syncStatic.sh @@ -51,8 +51,8 @@ cd /srv/web/fedora-web /usr/bin/git reset -q --hard || exit 1 #/usr/bin/git checkout -q master || exit 1 -/usr/bin/git pull -q --ff-only || exit 1 /usr/bin/git checkout -q f16-alpha || exit 1 +/usr/bin/git pull -q --ff-only || exit 1 build fedoraproject.org build spins.fedoraproject.org -- 1.7.2.1

2 1

todo: ask everyone what their todo is for the week
by Kevin Fenzi 13 Sep '11

13 Sep '11

Greetings. I thought I would try a little something out this week. For folks working in infrastructure, what are you working on this week? Note that I am not looking for some detailed todo list, just after having fought your monday and read your emails and looked at tickets and bugs and requests, what kind of things are you going to try and work on this week? On friday, if you looked and finished X, you would feel happy about the week. whats X? Here's mine: - Document bastion machines and their oddities in infa-docs. - Going to try and fix syslog from non vpn machines. - Get our Beta tickets filed and the freeze setup tomorrow (announce it, etc) - Look at updating CSI - Work on askbot in stg some more. - Continue new machine (rhel6) plans. - Typical putting out fires, fixing things as they break, fixing things that send me email. anyone else have any goals for the week? kevin

5 4

Proposal for action: SSH Key, User Cert and Password Flag Day
by Seth Vidal 12 Sep '11

12 Sep '11

Given recent events in the linux-y world I think it might do us a service to impose an ssh-key, user cert and password enforced change flag day. The idea would be everyone would be required to change their passwords, ssh keys and any user certs they have before being allowed to do anything else on our systems. Anyone failing to change them would be locked out after a specific date. In particular I would like to make sure that ssh keys get changed - so much so that I would want to keep a copy of the existing ssh keys and verify that the new one does not match the old one before allowing it to be used. I'd like to discuss the efficacy and timing of this. If anyone has perspective that is helpful, please share it. I think this should be done soon, personally. -sv

5 6

Introduction
by Magyar Zoltán 12 Sep '11

12 Sep '11

Hi All! My name is Zoltán Magyar. Basically I live in Hungary (but for now I'm in Ireland until 1st of March, 2012). I'm using fedora since 4 or 5 years now, and I pretty like it so far. I guess it's time for me to take part in helping this OS to get even better. I have some knowledge in software development in general, I'm currently learning Java, Python, have used SQL a bit. I'm mostly looking for some programming tasks, but I'm also interested in networking and cluster and HA stuff. I work as a full-time software developer at Ericsson, mainly doing function test related stuff. Hard to tell the time I could contribute, but I hope I can free up at least 3-4 hours a week! I'm happy to listen to any pointers about where/how to start contributing! :-) Cheers, Zoli

2 2

new hosts plans and thoughts
by Kevin Fenzi 12 Sep '11

12 Sep '11

As some of you may have noted, I've been building up some new hosts of late. I thought I would give an overview here and plans moving forward and provide a list left to do for those folks in sysadmin-main who wish to help out. :) We have 4 old xen boxes that are going out of service at the end of next month, so we need to get all guests off them before then. Those are: xen03, xen05, xen09, xen15. We have new machines: virthost05-10 and bvirthost04 On the rel-eng side: * I have setup a releng03 to replace releng01 on bvirthost04 * I have setup a releng04 to replace releng02 on bvirthost01 * I have setup a kojipkgs02 to replace kojipkgs02 on bvirthost04 I need to get them finished up and access to the netapp mounts, then we can look at migrating over to them. Once we migrate, bxen03 will be empty and can be re-installed as bvirthost05. We might look then at moving things around a bit to take advantage of bvirthost05. The only outage here would be kojipkgs, and we could make that pretty short/fast. On the staging front: * We need to make a db02.stg thats rhel6. Soon all our db's will be rhel6, and we want staging to match up. I think we should use virthost10 for this. * We need to migrate fas01.stg and pkgs01.stg to virthost10. These are already rhel6. I suppose we could re-install them, but migrating seems reasonable to me. * We may want to migrate some or all the stg on virthost13. virthost13 is now out of warentee. We might not care too much since it's only stg there. Thoughts? On the production front: * I have made a db01 on virthost04. This will replace db02. I'd like to look at doing this wed next week. (2011-09-07). This WILL require an outage, since db02 has fas on it along with many other things. Should we do this outage in the evening? Other thoughts on time? * I have made a bastion03 on virthost04. This will replace bastion02. We will need to swap IP's for it to work with the external IP in phx2. I figure we can do this at the same time as the db outage above. * Machines that still need building/setting up for you sysadmin-main folks who want to help out: - bastion04 to replace bastion01. Should be on a different virthost from bastion03. - proxy08 to replace proxy1 (rhel5). - value03 and value04 (on different virthosts) to replace value01/02. - app02 and app04 are on those xen boxes, so we need to move them. We can't do RHEL6 yet however. So, we could wait a bit more in hopes of being able to rebuild them as RHEL6, or just migrate them, or rebuild them as RHEL5. Once this is all done that leaves us with just xen04 as a xen box in phx2. We can then look at moving stuff off it and repaving it as virthost11. kevin

2 2

infrastructure
by rexchou 11 Sep '11

11 Sep '11

Hello Does fedora on the C language project?

4 3

Help get fpaste.org (fpaste-server) into Fedora Infrastructure
by Clint Savage 10 Sep '11

10 Sep '11

Today, I deployed the latest fpaste-server[1] package on a development box[2] within Fedora Infrastructure. I’d like to get some folks to hit it and do some testing. If you have time, I would love it if you could take a moment, read below and help. To help, just point your browser to http://paste01.dev.fedoraproject.org/ and add some pastes. In fact, it should be pretty sturdy. If you do happen to find a bug, please file it on our fedorahosted.org[3] trac instance. Or you can roll your own. Install your own instance of fpaste-server. I’ve posted some simple installation instructions[4] for anyone who is interested. We are always looking for helpers to make fpaste-server better. Please contact me if you are interested in helping improve or maintain this simple and fun project. Thanks a ton! herlo 1 - http://koji.fedoraproject.org/koji/packageinfo?packageID=11844 2 - http://paste01.dev.fedoraproject.org/ 3 - https://fedorahosted.org/fpaste-server/ 4 - https://fedorahosted.org/fpaste-server/browser/INSTALL.rst

3 3

bastion03 outage/issue tonight
by Kevin Fenzi 09 Sep '11

09 Sep '11

At around 05:20 UTC there were vpn issues. bastion03 (the current vpn hub) was only sporadically reachable. It wasn't clear if this was a network issue, or something with the instance. I was able to login, but then it would just not respond for minutes at a time, then recover. I got in and upped it's cpus (it had only 1, I changed to 4) and rebooted it and everything came back up and was working again at around 5:40 UTC. I couldn't find much in the logs, but more eyes on it welcome. Hopefully it was just a network issue (although I could get to bastion02 fine), or a lack of cpu power. kevin

1 0

Plan for tomorrow's Fedora Infrastructure meeting (2011-09-08)
by Kevin Fenzi 08 Sep '11

08 Sep '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-09-08 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * Upcoming new machine plans. * Upcoming Tasks/Items (nirik) 2011-09-13 - 27: Beta change freeze 2011-09-09 Remove inactive fi-apprentice people. 2011-09-27: Fedora 16 Beta 2011-10-01 mail fi-apprentice folks. 2011-10-09 Remove inactive fi-apprentice people. 2011-10-18 - 2011-11-01: Final change freeze 2011-11-01: Fedora 16 release. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/report/10 NOTE: I have cleaned out the ones that have been sitting around with this tag. Anytime anyone would like to discuss a ticket, just add the meeting keyword and we will get to it in this section. Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

bastion changes
by Kevin Fenzi 08 Sep '11

08 Sep '11

Just a heads up about bastion changes with today's outage: bastion03 is currently the primary vpn hub as well as the default when you go to 'bastion.fedoraproject.org'. This used to be bastion02 before today, so you will note that ssh host key fingerprints have changed since this cutover. bastion01 has been retired. bastion02 will be retired in favor of bastion04 sometime in the next few days. kevin

1 0

AUTO: Shannon Mcleod is out of the office (returning 09/08/2011)
by Shannon Mcleod 07 Sep '11

07 Sep '11

I am out of the office until 09/08/2011. I am attending to personal business today and will be back in the office on Thursday. Tim Blow is my backup. Thanks, Shannon McLeod Unix System Administrator Dubuque GDF Note: This is an automated response to your message "infrastructure Digest, Vol 64, Issue 5" sent on 9/7/11 6:00:23. This is the only notification you will receive while this person is away.

1 0

New python-fedora and you
by Toshio Kuratomi 07 Sep '11

07 Sep '11

I've just updated python-fedora on the app servers to 0.3.25. This update has quite a few changes to the server helpers. For people watching for end user issues, if someone reports problems with logging in and out of the turbogears web apps on admin.fedoraproject.org or having their csrf token cause problems it is possible that the python-fedora update is to blame. Please let me know if you spot something like that and I'll try to troubleshoot. (abadger1999 on irc). For web application developers there have been a few deprecations and additions. * The fedora.tg.tg1utils and fedora.tg.tg2utils modules have been deprecated. tg1 and tg2 have their own hierarchy now: fedora.tg.utils (for TG1) and fedora.tg2.utils (for tg2). * The TG2 auth middleware has been reworked a bit. It should no longer log you out if you don't have a CSRF token. You should be able to regain your logged in status simply by clicking on a link. Links should have the CSRF token embedded in them in these instances. * Additionally, the TG2 fas auth middleware has had its metadata updated so that it is compatible with the default TG2 auth provider. This should make it possible to write code that is compatible with both out-of-the-box TG2 auth and the faswho auth middleware. * Provisions for testing web applications with the faswho auth provider have been made and documented. You should now be able to set faswho to use tes fas servers for authentication. Details of setting this up are in the updated documentation. https://fedorahosted.org/releases/p/y/python-fedora/doc/faswho.html#authent… * One last, untested feature is that the CSRF middleware that faswho uses to protect against CSRF attacks has been made independent of faswho. You should be able to combine it with other repoze.who auth providers (like the TG2 default auth provider) to have CSRF protection in your application. If you are working on an app that should be able to auth against both fas and some other repoze.who auth source, please feel free to test this and report any bugs to me. This is a desirable feature and I want to make it work. https://fedorahosted.org/releases/p/y/python-fedora/doc/faswho.html#using-c… * Last but not least, just as we have genshi templates for TG1 for CSRF enabled login forms and buttons we now have mako templates for TG2 that do the same. With all the other changes in this release, it shouldn't be hard to make a TG2 version of the genshi templates if those are needed. https://fedorahosted.org/releases/p/y/python-fedora/doc/faswho.html#templat… -Toshio

1 0

Meeting Agenda Item: Introduction batnomuun
by Nomuun.B 06 Sep '11

06 Sep '11

Hi all, My IRC handle: batnomuun I new user fedora. I study IT university in Mongolia. I know python, sql little lol. Hopeful, I will learn lot of things this project. It's very important to my future job career.

2 1

Ask Fedora SOP complete
by Rahul Sundaram 02 Sep '11

02 Sep '11

Hi All settings, customizations are now fully documented at https://fedoraproject.org/wiki/Ask_Fedora_SOP Next step would be to use Puppet to automate all of this and we are good to go although I am going to continue to update to the latest versions from upstream for a while since I have a bunch of feature requests that upstream has committed to implementing or already been implemented in the git head. I haven't yet tested with memcached but I expect the production launch would need this. When I did test it earlier, it seemed buggy although it might have been just my misconfiguration. I will test again soon. I hope to do the initial production launch before Fedora 16 release. http://fedoraproject.org/wiki/Releases/16/Schedule Rahul

2 2

serverbeach maint window: 2011-09-12/13
by Kevin Fenzi 01 Sep '11

01 Sep '11

From an email from serverbeach: > 70103::serverbeach4, 70104::serverbeach5 > > Please be advised that on September 12th starting at 22:00CT > and ending on September 13 at 05:00CT, we will be continuing our > planned ServerBeach Network Upgrades in the SAT Data Center that will > provide you with a more robust and scalable network and enable us to > better server your needs using our new Juniper Routing equipment. > > This maintenance will last approximately 7 hours, during > which your server will experience up to 5 minutes of network downtime > as your gateway is moved to the new Juniper routing equipment. Once > this is done, we will be configuring the newer routers and you will > see 6 brief periods of latency/packet loss as we redirect traffic to > the newer systems. This maintenance will ensure that the networking > systems are standardized and will allow us to use more supported > commands for configuring and investigating issues at the networking > level. Serverbeach04 and 05 are hosted01 and 02. So, just a head up that we may see some short network outages in that window. kevin

1 0

Plan for tomorrow's Fedora Infrastructure meeting (2011-09-01)
by Kevin Fenzi 01 Sep '11

01 Sep '11

The infrastructure team will be having it's weekly meeting tomorrow 2011-09-01 at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * New folks introductions and Apprentice tasks. * Upcoming new machine plans. * Upcoming Tasks/Items (nirik) 2011-08-31: send out outage announcement for next week 2011-09-01 infra meeting 2011-09-01 mail fi-apprentice folks. 2011-09-06: Outage to migrate from db02 to db01 and bastion02 -> bastion03 2011-08-31 send infra meeting agenda 2011-09-13 - 27: Beta change freeze 2011-09-09 Remove inactive fi-apprentice people. 2011-09-27: Fedora 16 Beta 2011-10-01 mail fi-apprentice folks. 2011-10-09 Remove inactive fi-apprentice people. 2011-10-18 - 2011-11-01: Final change freeze 2011-11-01: Fedora 16 release. * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/report/10 NOTE: I have cleaned out the ones that have been sitting around with this tag. Anytime anyone would like to discuss a ticket, just add the meeting keyword and we will get to it in this section. Submit your agenda items, as tickets in the trac instance and send a note replying to this thread. More info here: https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings Thanks kevin

1 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure September 2011