postfix-doc-3.7.3-150500.3.14.3<>,f44p9|+ U@9WtӈE|ΨF:P ST8~hM36lbt [TKz=?pm=a尯wuq!C3~$F.u mmAcC:BG/%^9`&K-瑐Ifn7k)jƯ?< وq) 3Rxk6aDSĘF(]x噸ͶP<`R}wkwOY}>;?d " I% ;ax~     A BFHJOO,RRRSK(So8Sx9U:aFz<GzPH}IPX0Y4\H]^ bcdGeLfOlQudv z<LPVCpostfix-doc3.7.3150500.3.14.3Documentations for the postfix packagePostfix aims to be an alternative to the widely-used sendmail program. This package contains the documentation for postfixf44h01-ch3aG -SUSE Linux Enterprise 15SUSE LLC IPL-1.0 OR EPL-2.0https://www.suse.com/Productivity/Networking/Email/Servershttp://www.postfix.orglinuxnoarch %N ]2,TAu O@( %D2HXO-ru+CT 1 hPW,6N)?RmT/74 jTRa(k^("Ju ~2 2-4slw$:r1Me7HQ!S7MT~k4_ ; a\k0 ؾ$Tq!UA=[A aIW wwu%iw#: QZ-*g&k)@ y})-C"1k#:wm@*:.0CIm@ `_,;h5|T -<Q :=fWE]3w*FQ.nw r&;O#S!#:m@g42[el2>K(r)>0N 3CKG} !AA큤AA큤A큤A큤A큤A큤AA큤A큤A큤f4,f4,f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4+f4,f4,f4,f4,f4f4W8^XDYn^f4HC^e<3y^eAf4a-a+=uPf4,_Ja`aaaa_Jaa_Ja`aast_Jaaaaaa`_Jasua_Jaaa\C"_J`s-y_Jbc`aaa_JaaR aaaaaaaaaaa_J_Jaasvasvaa_fc_J;a7aaïa7a7as{`,d6aszảaas|_J:aay\f4a'aïaa`_J:aaï_J;as{ama_xaaahqa -f4åJXza@e_J:_J;a_x3_x3aKbI%aaaBas|avGaaas{_J:_J:aå`Ra_fcaï_fba -_J:f4f4_J;aïa_J:åf4a7aa`,d6aaf4,f4,Ckf4@a+FE3f301cc5e38eaf40383b38612d5fb2db19901eed69ac06d33133a5feba3ae825365b6e95d9a8e814b914f0f4b2bc11e780578855582d63da51e1370d7096227f40611eda58725c683f118689e6ec63965f340c0b45b593db504c13cb3e6562ac82821a968e47926cac1c9d3e6b076f0db54cadd4479a7b33f48f3227ea20183dd42e6da7288a410a58734f2264ae7f8f42e35ed3714861c6bef825a3f82dafc2791d8133b61e72b8647edd0189c777fff208a717aac4ce3adb1cdef11bd8e2691c4dba67b1489a72b7b23ee0a8b10105d3bfd91b2c2ab2ebab0cdcf1ee3e75f00aca5fd2cc29fc7c69d4a1afda3d04b06df570a389913dcb0263e4fddfbc380e203e191d2cd2238a4de2ba2fdc7bc1154564f3796aa92152026b2cd0ffbf08d1382680727fcbfbd407ebdf46fa9c2641580ea51531705569594ed00fb29ef5c9dbc0183c1369d7c6753b17a679ea83dde52176a8202e53981e9ff387694459eba8c6a0c89d17c2194376d9296f67ee3d35e4d290d914611b1861c224844404a87da6bca30a0e0dd9ce2060d4907797fef0812bb86ae018548bcc2d4997c256699dfc306fe6a89c180659b82328c2894d068ba4dc6e646a82f8e7a93dacf1dbddd40b5e253362712b6349861c07873b343cea3ff66201edd311d7f05a9ce46603a5201533f3d4a43725c27d8cbd5b15fafdac8da1be6c97008a849b293da79d5ef382eeaa7fd5235462707f86cb6c0108c91486dcc72761e5511de33e81edf4a1244075ca444f12392c03cd8db2550fdf0a73c5baeeaf6ab467f1ee651d2d3774276a79c8bdaa03f587ceb55929647656b31a1d436ff89db5a48037b976c422c48877ad9a44bcb17b4e4691012ffe27116d309149e6224274b2e8211463d249732b5f8a61bbe7ad6828fb338e98776acfbf91a82bd613c5daa064e8c29dc47becdf00c3e57cf6d81f2e080c78175ea75e3776be09bdb1951d7940e2612822972f2cb2da2f921bea947b12bf62ff980809110e4d28223910ca8a3bca61ae2157040db403e38bb4c255f35369b3f056de7498177a1fc70063332bf310de80ea6169b9de0b037b53d7ce851613595bf697237a72ae055b4557cf4fe6e779bc977eae7ce06db1145ba8de03b792d626da4987b646d6494a9022f01197d7c05a73463003d800199aaa03d090bb2a337a3f0ab1afdffe897c7bd57d3b42f3019a0bb1aaac2b9a2ff7f99e95cc66925618a259c3dda5e5343adabf9cbf2d10b101b674f6e62ee934bd89cd6172f16217f17595ae08a251021802049477f0382e5c3f20c53db921ed26a06513b65c82f7fcb79e0541a7ee57786a04c34398fd71eac8705640569df15310507a6d9e311501414f9c00029aa68af7c39ffdfb6fa38e34852e9930a1267cedd1731b637271c3878f5ccb670ef060c318f1d71bb29f3922382f6dab3c90d71a6140913c61cfb3e3a895b17b0d5db25e1db51e48ff660477bba628411628afe510f66b6e1280b09e44f3e140afc69afbce7894d5b24a99aef70c6ac53be059389be40fb469db574887844f46083d51a292dc4b9214c11576858cf758bc8d0437be6a6e90479e756fa77f1a0b57f8adc83e6b00d8647e525e5e221b630938a45e84415cd8e70bdbc865931aabb2f7db47c5de61f1723a25bfae18951d87532c4879a4958467fb6fb28294bd06b982b4613f1c3e569f8943d9bd58dc52bd3ebc52fd8bce4f5bdbbd6a0dc40db295d8205194f536cab893caf1ff82c365808ed0efeefaa2f1665c1b65e03094d3a04b8a7ae774b6de8b16e6f309263bc8d5a69b32cd2598059ac88c84ae23eed99bd61babe308db8f5e30da671fdd93dfb8133e5b53b3cc0250861010467e5a2b6294a670cb3399cb05973ebb3cba2d8baeb2df14cb2e1b15f2ab6cd598efaf97df7485bc789f1ae2c9e400034788ba353c605baa83beaf90452f1a92302223f80feee517a645c4be2ebedb289925cfc68d6d29f47740c25f2a9715be49975f9b4c103c42056490947faa6d9296b5f291e160dbf67e5d6996f211359ccf58ffd4b7ec94f6ec35b383bd25d45dcd338f939960ec0b131d49b406fb6132b674e3c18291e0a045a2747257222b1fc7693892b786ac6c6503110daeb4271f77df953a803163f80709517a5eb600060669cbb26a97f2dbb48fa3c89a245e90650f5463ccb39529823509708b6b5ebc9f909f85a94f50531e2558748d00386084b8b317990fbb12e5e8e3d10d7a9f8d7681824f268db7bad81d7273fea6bf5e752eed21fd7807992fa9172785282f41268c6a9e4b204b4a48460441219c0995e6704eb16ffc70dbaa7269e8abb7948d29bbba160724f658ed482ab83d38bcff2b62788a54d6b3e4b172caa688c5a1df5b71a48b543bdf7b154eb1e65391bcf26cfd30b299c86e6449deccfe6cf6163c7551ff89de735b8c706d06722226cf0b1877d6158dd3fd9728b750458e0ba212e270cde79fae0b259fb1fc034cdfd4989fa5d34dd457fc9b72928d466447de56c9cb2835a77d8dba5cd03a863517feb85f8b61635107ca37f4a65335e9cf2216f18eec281d5621d29e637b486ba923162c8a8cb8f0fa18cbef5d1a3ca3f66a2332bcc2bdf81a70bfd6da31699ca6353069223489121c005d14b0e2d3212a9381bd42e1928c4c102160ca496dde1b0a0c5a88437140cf7f221cf8d511e66a19d2ae348556e8f637886c353f5f0382baabc364b557d1d76150b48b19e53aafb55e44f7d2b2af24cac44de2cd9a69324d1ba342a4cb41142e08280e159c5eb41e5290005508671aac3a89bfa8955bade19688282184a3a638d0444e320fb5e0a122b1e3e7140db05435820ad63bdee583480b8aa62115ef68ed858b3eaa2dce4945b82a270f41e9197ffe870035ef2a363932167f5ec81832314e871ea20107ee48768663dbdca2d3d6dd394246a378b43162d512d7a416e7c780be344badda882570b64fcbef283dac06b50c2e983ce9c3f0c1ee8da11d24227924139bfba7440bebf300911f16734e95afa8562e37bde0e30ab1c25379a05c692371cd143230e6625b1f44751e37ee7128b1a98cd9f23ec9455d3ecf20bc760c3fb25a5753b84337406f5c2d2fd7d4032918dff967a262954fb044aa5ea4ce9351e9d0f78e1eab8ecd1c8cc9523d766c04519a03dad7019389ee129aa4a434210de523182c3ad5f33021c22804ee93a6c156ffc577f67e162e3af6477f001da5de7b2d29fc7dabf8f491826322d93869b69f0779dc9fab7c1413749704efccf37b414f2d449495e36b9f1b63c95c1b260861f9ae74a08843d417e27fa09e3efed05e3e537af1c558e2e34734dcd8bcc79739bf48d9278786d0beacf83c9d4ff118175f28c4d1e937652cb2749c07d1ebe8fce5ccac56c1eed925acb92a56e71663ff72e35015e6b94a09c11520663d7b268de6f492eebee6462f3a6e6f6700034da6d1e9400ba29d59483adf46dd8bc9d2ca45d9f2867f2ea89fb2f9395b5283df27f93bc732e1af66332c06bfaa24f57d7e075f221b9d02d6b261cd5e563f1a6527afe48922a7438560abfe37f3476e7640deec33bcb3080e29992a12f7f548863192df2d7f8c1e295fefc599550ecf63bbd3e61de8ca8fbcdd1d9cb29d3c6e0ca061ef3604cf5030ceb2c2fde98b5e758f218227c11bf3c3ed48e7c1550feeebb242aea89f4129481e541ed4e77b1fbf351d4f40a819867ae2b57769705491ec418a1d528d2b4575178820fc84f2da1cac6b966906c6497027a6b53059d08fa4c16b7fbf3247d9bdbfcdc86fc703a031631b12b1871d08dfcfea6a3e0a462526c4f7e7ffd2a6e8aba72d1ba26ef0b0249c1057683381ccb923993d586d1272683c26a11a0c07efad9c22a309c2bcf180a76e4dd615f74ce8d278c1e2de0a1222bfc5eabc36cc857e8747d7b0da1d18f28dbeea063eef138b27ad418ff31915df4c1aaaed032f06618a8f76d9d1309fd06b93beba1798dbff1418953762a55ae08fb7896ee25b3aa19b1f2cae6be7db5f20900a641e4d75f50f07fa766c180fd375f78fcf7bbac6dd49106d7e34d05b552cc44520cbe4c43d93c0d0ac8aecff228be153567372c9d15fd9b109cf9e99ed7a36f64671ee34473052b87151de5ceaa71328c36f648fa0e28a2c12a3f7e9f45b0f5902e27e3047f8674a37787170c59c3781530f56a30ef9bd747ad6bcb54940e42d1292b110fcb563d8fe5bd526182005ff3eaa9fa9048cb8396cc26ae44a167698358e5a73b9aeb72e4579e9244e0f3549ca3e04d19dc9795fc4234049865d83266f767d903d17c33fd3d867a6d1c9f3033a70b5cdaf8142107b033f1ccbf5b43a99d3acb032ce9cc8dc572c07f4fcfaf560fe16f0ec2f9bb47a036ad01e376826d54f01993a8bab1367c76175b3a1c9ac44d232ba02c70969593514bc2abb6bff0fe4b114c80ed563a952b07d7b8e9746201449ceed5dc7c6d8e3b8a872f5d5241c226e45ab97fc1ceb14883cbe2deeb75060b2ec34406ba8cd81bb9ddad78379447989301b98842fd3de0e66469cdc4d2a11d35be686eaace911cc92779d9608fb429bb7abe18cb06b454bb0d260085ec5265dfcbd178a4b7a3ec97917c2fccfaa0d72c39a49ee8efcd561122907118f39d452f816c437039c1b9e51fb56df556846f98d51136516cf7df0ea0cab5213767cb63df30ce21237a6e900e6ec3c37e961a4b0664050888d5e57455e53ea41a154b3b1c34c5ffbf3d2fc08954df774614617cecb6bc1a290b0025a07663a767a10df291b815f321e3c3093f2008ba9537faa378b04834342327bddbb516d01794e7307c3b54d05d5aceca8b30ceee218c62b167804307102e95997ff4d01f8f6b45073811eef51d15370769bb77d47d9406cee4fb73d8ac243a1b68878294e6be489a0533263ca0896b77708e7f8247e30317f0bea3c24aab4039403003e8337f43b478defecd52f46edd5a83f7d4110e4374ad80cad112e61be65c553f6fd98d609f1d4f736530665ba4604ba136edfe11c0bc0808ebb798f37a70063a45169ccdb3f932d976a590e45283ae81515f67a8aa374bc69b489fd39e798c9646c5d1c258bf2b1e9e6777af505869dab4856f152d73aed71fdc50d519185d454f95a1d1a3fa584d9648cdfb3975fd090ad852ff0a2c99a77df63739a548494124ef6c8f2dd1b94ec0ab764184cc47a50a94a83d74db3527ef989776d6e4700f30f4ed5a8dfe86c656d60784a2010cad0b4cc96f9588e6aac258300bc6530db52abc0b717db2a306aeba094cbe76c241fe7f622d927b09e34cebf5a42a87d93bd7c7ae81387353978d160ec3ae3b3933774ec7d9b6a1e7a62d7e141d035cc059e7793755b8e3e462046f7ec4637746fe36c29ff5a0698da36aac6be118db5199aef6a65c99ba4f184d0aeb7c94aff715d5bcdc79cbe50c9c0660ffc240e5e8b929b9818d6318218a75c855abedb120e83c47d6e31895f65864dcadd734d63fa6139d25eabfd74fb5f4b019849b380bc29438874ad84c518f6da78c9f729dc41e1bfd405163f3b8c204d7974b0c74861362dc4edbce9e2a531f1da037cb6699caf20c9c5b3ba619f4f3730e9188f789604483b1c9fc0c81acbb867be5958690b81bde7e4e74fed815aee13ff1e4cb7c002888d8cf710f8b47a1dc457408162bbc8f22a9729173e4ffe539f2003be26d0119baf2241b564768e5bce4ad4117fd1255b454f2e76c417e0df9f771ed3e42733e7d02df4b9f93c1e9fd81d73fd36b71103391b980c0e88d4323d44a6029a8edbcfb288dad8b2ab432af29078eafb78350407d6e3e2a84b79446571317b15f8e442521b0c7c8ceab01a61574d1219efda20fa138213b94f0073ac9967be53be786ddffc4839addcaa482cf7b0e8efe042d126619463522cb2ced588e8b0078e0e3e21ec22c8fdddc7072e2b795f91070ddb507bcbfdea1d7492d8a4f7a00a34917321e8267b85db20311fc3e5b2f06326d592ad4b4a040583f445ecf2719a2a120c15e0da56e926c64bb9e11bdd9222e5cc661ca108b2db79b5a607b88a301337742ec1abfa41f271547fd8185eb218accd2fe17f8bfc2cb2ced588e8b0078e0e3e21ec22c8fdddc7072e2b795f91070ddb507bcbfdea2e07eb7f2c265b7a38c14e8305474f1b23502511718c0ec55a0d2c32d11be5298d841fff2f78978311417ea8dc6e66908959c9dbdef58ced22b7912c4294a4515eb808c02079cca5a9f74c742ff683e8fe8ffd899724317c6f284b043df23ae79068ac1a643e8a4304d57880ea4b2ebf996d9636ceb50e3563a29070a0b9b71171d701f90e80ca65818dc211e2034caffb2481dd36e1db6f4c588367dce96cd933de859c59274f626a3f7a1362ff57a7576e811d29a28f46e6958b1aa935b835919793a371dd2ed0b77ec54f38edddc0615ba49377c65cfe0c76f6984f9e935e5c5ab5bca7f34b543369bbdb1ba98e1f30052d15fddd6f6fa303dfb53109b706e3c17182c53b69c0ccf1a5d279d309d2379a8c55b967748eb4ea3b42bd783d3f302c538c8d9e6a34475424688432433f938840ad2d4ecdfa18d6a1b4255010d2081064bfdd9257e1f3ec6b32bda5c641b9b014ec5808d58f9f9810de94c14b81a47606d7e10b750934f45c4657c836ee8e31b358d24dc204d2ad590b6e0cefb5afd1440a9d7c74417d199511d68739b91294e704e2fdc2b17bd0048b48a9aea853d6378955aaf76feb5b86be8a4cf81a20c05134a7360ef1aa2d285b4915fa9e9c47cf6c52c9798205e9eb2dadf613bef10f27e3da732363f10be8c840c741bc634424a028911bbced384d183392ebabfa20027c178e91f50562a9594d893f864067917a33904f30a058a6a7fc2276fe568f498c585d23e21f1e162869df6c5fa47606d7e10b750934f45c4657c836ee8e31b358d24dc204d2ad590b6e0cefb54a0fe839e0b8d29d075517734942ca5ef1af0d2ddfd1f8efe6e3be7668b585abe37f037ad0705169b0cfc49f5d97f3952af13f0b0dab683e1205db73d5c0d9c9717eefa3fc49dc6df7651e2f8a1b849c3fe610f9d395cac2943d074c4838f592475b58e00ece65cf68ff2422fdebaafa0178333c707701b7d7921f927caa87382e9ac0e8b52d27d3f864d08ebca64f32b0c9b741730c5d3186c9e1183dc7aff5ee061ac83dcefecc8750e1a13d7797c93a70bdabf95d340f80eccaa32a4da8fb1e17489b8fa91e7e29a64062aac25cbf0e60c46f3bf8ecce17925389e70b96ecf25de97f69d9cf5ff496fe8867c30634d03ddc41e4c735812a25d858550fe149f5810ed8e1c5cc97d2af513793ac88838bd2bfbf5ccd359f02555f18e7b384d59a516e5c1a12749c065979afd8add435d43c6671ed0c7dec47fa8845fc2f878cd03dad8b0bd9cfb0fbe95b24b312e764a371e5a98a11461ea00346a4965c760f04ae0c6a31006faaf16fd4621ba540dcb28cd0dbffb350e12be43d489a1f0a7e2569e50abdc9ef5fd539ce24d8d899faf96b83301b9890fec2523619c0cc62ec08a6de75518a42940c05387813e4db9592c789e6394d3ba58ab201abaa6a213b1aca0c5e186d2565ad21f2ddce4fd0154f2d5ffaa6fd05d6890e3a916f99d3d060f9eab74cc8fb1ba2b96d29e735dec73bcf89712457eb20a3a6129f60f1587376c08bb74e9881a925ad316e24ab20de931216364c9aa35ba2869d48bf026ed3e4d25d3732cd5383b19373e8766ef2935cde43e9c4b04c840ae4480f3da6f5a8f4b4e53b0663d4b8222b0c9058cbb179945170923ff1a732079b9989bf6191f429dbd722162f19c468c140bd2dcd8738280d371ef35dcc07e2284ab068d84a35f5c0cc8b422837c49e1c7f09423237cdd769daae52b7d83e12ae2ce2777ac00ee045f956357916235641fe2bd991ea61ed66c822fec2da0dbb195090cd9a9bfe29914ae3b1bc925e4dc695ce84b248f714e73226899fb97750d4791ab1d5e2e729147688112a56b79123379702ddeec7bfa4dbd2cc98e4cbc288e7c680b646fcdd845b297831b53f14afb9347fa323588a24085cfccc0fb68b32a03f8e9247c4a60ff8929d4f45b2ddb8ff5ec139ff9e2811eb87c62bae1b11c3e628af9838fc364461ddf3a6bc196163833e026925c49e585696fbb7a6b3a59a13d4ea7ed5177da13a4609f78086c4e65eef274a97950ffb7c7c568f970496b8bd6f188aebc672a0a06259345323e8b9bc8c53bcb437bf78d7d3799e8bdd9db6899241f0f88ccb559ffb471ea2cb39333cc2546ec30d62bcce398d48653e3c5bd45457b0b242a42e46a701a726e0463baa1a122086c7b62ba467c4c456db305177d1feb6e4fe12be362835a9f2870ed114824998078993b3f930fdd1e0993a263a9e9ea995b4f93af823e46238247e1bbfd330314bf9ab2f71b219441b25de13d4383e5435794f5b8f343b9cf6cac45eeb513760b809af37793991e6cbc0630594296e1528becd89d265421dc96c3c0976aceefd24ef2190e4a268500de74d88df478644272ed4fc5520bdee4ca7f9abe45d20890a950d6b8a0b1a2b6c746c3c5d96ababd661a47606d7e10b750934f45c4657c836ee8e31b358d24dc204d2ad590b6e0cefb56b59971f74459a252bd1fcbd00b3107cb51f9f1a73130bcad807ba1e87318f9ebb53cabea699647ada9fb81c253e37f84b75f8dfd00a9307775f4bb2bb2aafe2551b4da3ced4159bbd66fc3da8eefc2f48e40c90612aa596c8bb12e8e663f433302c538c8d9e6a34475424688432433f938840ad2d4ecdfa18d6a1b4255010d23c47c06ddfb714246498966ae1e9eedbbda740ed5aab8044c237729235d25f30aacf8a0e81a041fd811a931be133dea88eb5e162e0169fe58b42c7e6a7cfc6160cbe6c62e74439b8d0c3eb35ccb92de677638399789355abca80ad1dccacefcd5d2390d6131e565ff11f9d1862a836420239418a19f1acd90c69491af5cf2cb559351279b3a623bd4f43db0564b7caa3cb5ac79eeea58adef67e10dcc9d06c48026be4d3bbb98fbae3da58deee1cac01593e406131e8ff88ee2a56cce76730c8911cff063b2af668f0a64f8e3b6df2cdc078ccf7849c77700786d346420fd7192cb2ced588e8b0078e0e3e21ec22c8fdddc7072e2b795f91070ddb507bcbfdea654c7ab38e8143b8ee0091a1779e1570e9cad2d4d81a7ec95e11385f352848ce668c942df2a63924442d4b0acd112a90031aa5b29c35a942111b9ee69cbd491e5fad01b075a540abc6f62d2b8437682f1a208fa843f6e839cba38ee8048c6b488981322f7675c5b79084321f1a8eb5758d4b9ac3ea315608a38ffcea733de3e26f101ddd6cfcf9c5305d48fbc61f552c050f822434d5fd7fc36ebc37bf8a850f929fd9b2ac5cfe2c19d980d5ec2f463b7631ed9661255f313d83a740b152b0ed176d7c83becdd7e0845cec45e44de62995ff23cfbaa960899351dab8ae71a6ae718fc1ff04495eb00d2ad288cf76eba90b5752935f62c989a4615cffa485d61173c8bb4a528df9d16439c169d1b50784e5c25f68fcf37d6545d97bdfdce46560rootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootpostfix-3.7.3-150500.3.14.3.src.rpmpostfix-doc     rpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PartialHardlinkSets)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)3.0.4-14.6.0-14.0.4-14.0-15.2-14.14.3f3@e(e;dܺ@d@bbbzSbq@bobf@b]RbJbBb4t@b/.@baa@araraqV@a^@a'@a$@a ``R@``E`"@`̊`D``r`!@`t6@`H`B@`3@`U`__@_@_@__j___L@_D@_?@_/@_p@_A@^^^b^'@^>@^=@^ku^=Q@^:@^8 @]e@]@]b@]m]M`@]:@]9]4S]]^@]@\@\\\@\~d\}@\zp@\y\\\LK\I[[=@[ͻ[[[[ZZUZZkZ@Z)-@Z@ZY@Y@YMY@Y@YY@YyYC@XQ@Xh@XX@XO@XO@X7@XM@Xv@Xk@X9y@X)@X lW1@W WPWJWDB@WDB@WVVVV@VhVU5@U@U@UUlI@UXU6;U3Tء@TOT@TTT@To)@TeTN3TD@varkoly@suse.comvarkoly@suse.comvarkoly@suse.comvarkoly@suse.comvarkoly@suse.comchris@computersalat.dechris@computersalat.dechris@computersalat.dechris@computersalat.dedimstar@opensuse.orgmrueckert@suse.demichael@stroeder.comvarkoly@suse.comilya@ilya.cfmichael@stroeder.comvarkoly@suse.comvarkoly@suse.commichael@stroeder.commichael@stroeder.comopensuse@dstoecker.dejsegitz@suse.comjsegitz@suse.comvarkoly@suse.comvarkoly@suse.comvarkoly@suse.comchris@computersalat.devarkoly@suse.commichael@stroeder.comvarkoly@suse.comchris@computersalat.dechris@computersalat.degmbr3@opensuse.orgmichael@stroeder.comchris@computersalat.demrueckert@suse.devarkoly@suse.commichael@stroeder.comvarkoly@suse.comvarkoly@suse.comvarkoly@suse.comvarkoly@suse.cominfo@paolostivanin.comsuse+build@de-korte.orgvarkoly@suse.comsuse+build@de-korte.orgsuse+build@de-korte.orgsuse+build@de-korte.orgvarkoly@suse.comvarkoly@suse.commichael@stroeder.commichael@stroeder.comkukuk@suse.comkukuk@suse.comsuse+build@de-korte.orgmichael@stroeder.comsuse+build@de-korte.orgkukuk@suse.commichael@stroeder.commichael@stroeder.commichael@stroeder.comsuse+build@de-korte.orgmichael@stroeder.commichael@stroeder.comvarkoly@suse.comvarkoly@suse.commichael@stroeder.commichael@stroeder.commliska@suse.czmichael@stroeder.comvarkoly@suse.comchris@computersalat.devarkoly@suse.commatthias.gerstner@suse.comchris@computersalat.demichael@stroeder.comvarkoly@suse.comdimstar@opensuse.orgtchvatal@suse.comvarkoly@suse.commichael@stroeder.comvarkoly@suse.comjslaby@suse.commrueckert@suse.demichael@stroeder.commax@suse.comchris@computersalat.dechris@computersalat.demalte.kraus@suse.commichael@stroeder.comchris@computersalat.dechris@computersalat.devarkoly@suse.comtchvatal@suse.comvarkoly@suse.commichael@stroeder.comlnussel@suse.deadam.majer@suse.devarkoly@suse.comilya@ilya.pp.uavarkoly@suse.comdimstar@opensuse.orgrbrown@suse.comkukuk@suse.demichael@stroeder.comvarkoly@suse.comchris@computersalat.devarkoly@suse.comvarkoly@suse.commichael@stroeder.comkukuk@suse.devarkoly@suse.commichael@stroeder.comchris@computersalat.dewerner@suse.dechris@computersalat.dekukuk@suse.demrueckert@suse.dewr@rosenauer.orgkukuk@suse.comchris@computersalat.devarkoly@suse.comvarkoly@suse.comchris@computersalat.dechris@computersalat.dechris@computersalat.demichael@stroeder.commichael@stroeder.comschwab@suse.dechris@computersalat.devarkoly@suse.comvarkoly@suse.comopensuse@dstoecker.demrueckert@suse.demrueckert@suse.demrueckert@suse.devarkoly@suse.comvarkoly@suse.commichael@stroeder.comjkeil@suse.demeissner@suse.commeissner@suse.commichael@stroeder.comcrrodriguez@opensuse.orgmpluskal@suse.commrueckert@suse.demrueckert@suse.demichael@stroeder.comvarkoly@suse.comvarkoly@suse.commpluskal@suse.comvarkoly@suse.comvarkoly@suse.comtchvatal@suse.comdimstar@opensuse.orgdmueller@suse.commichael@stroeder.com- Set inet_interfaces to loopback-only instead of localhost as proposed in man 5 postconf. (bsc#1223264)- (bsc#1218304) VUL-0: postfix: new SMTP smuggling attack (bsc#1218314) SMTP Smuggling - Spoofing E-Mails Worldwide Apply patch containing the feature smtpd_forbid_unauth_pipelining as default yes. add patch: postfix-3.7-patch06 - Security: the Postfix SMTP server optionally disconnects remote SMTP clients that violate RFC 2920 (or 5321) command pipelining constraints. The server replies with "554 5.5.0 Error: SMTP protocol synchronization" and logs the unexpected remote SMTP client input. Specify "smtpd_forbid_unauth_pipelining = yes" to enable. - Workaround to limit collateral damage from OS distributions that crank up security to 11, increasing the number of plaintext email deliveries. This introduces basic OpenSSL configuration file support, with two new parameters "tls_config_file" and "tls_config_name". Details are in the postconf(5) manpage under "tls_config_file" and "tls_config_name".- postfix: config.postfix causes too tight permission on main.cf (bsc#1215372)- CVE-2023-32182: postfix: config_postfix SUSE specific script potentially bad /tmp file usage (bsc#1211196) Use temp file created by mktemp- update to 3.7.3 postfix 3.7.2 - messages with many recipients are declared corrupt with warning: Unexpected record type 'X' at offset (bsc#1213515) This fixes a bug where some messages were not delivered after "warning: Unexpected record type 'X' The new version contains only the required patch- use correct source signature file (gpg2)- update to 3.7.2 https://de.postfix.org/ftpmirror/official/postfix-3.7.2.RELEASE_NOTES - rebase patches * pointer_to_literals.patch * postfix-linux45.patch * postfix-main.cf.patch * postfix-master.cf.patch * postfix-no-md5.patch * postfix-ssl-release-buffers.patch * postfix-vda-v14-3.0.3.patch * set-default-db-type.patch - build against libpcre2- remove *.swp from postfix-SUSE.tar.gz- fix config.postfix 'hash' leftover with relay_recipients - update postfix-main.cf.patch about * smtp_tls_security_level (obsoletes smtp_use_tls, smtp_enforce_tls) * smtpd_tls_security_level (obsoletes smtpd_use_tls, smtpd_enforce_tls) - rebase/refresh patches * harden_postfix.service.patch * postfix-avoid-infinit-loop-if-no-permission.patch * postfix-master.cf.patch * postfix-vda-v14-3.0.3.patch * set-default-db-type.patch- Change ed requires to /usr/bin/ed: allow busybox-ed to be used inside containers.- add missing requires for config.postfix and the postfix postinstall script: perl and ed- update to 3.6.6 * (problem introduced: Postfix 2.7) The milter_header_checks maps are now opened before the cleanup(8) server enters the chroot jail. * In an internal client module, "host or service not found" was a fatal error, causing the milter_default_action setting to be ignored. It is now a non-fatal error, just like a failure to connect. * The proxy_read_maps default value was missing up to 27 parameter names. The corresponding lookup tables were not automatically authorized for use with the proxymap(8) service. The parameter names were ending in _checks, _reply_footer, _reply_filter, _command_filter, and _delivery_status_filter. * (problem introduced: Postfix 3.0) With dynamic map loading enabled, an attempt to create a map with "postmap regexp:path" would result in a bogus error message "Is the postfix-regexp package installed?" instead of "unsupported map type for this operation". This happened with all non-dynamic map types (static, cidr, etc.) that have no 'bulk create' support.- config.postfix fails to set smtp_tls_security_level (bsc#1192314)- Refreshed spec-file via spec-cleaner and manual optimizated. * Added -p flag to all install commands. * Removed -f flag from all ln commands. - Changed file harden_postfix.service.patch (boo#1191988).- update to 3.6.5 * Glibc 2.34 implements closefrom(). This was causing a conflict with Postfix's implementation for systems that have no closefrom() implementation. * Support for Berkeley DB version 18. - removed obsolete postfix-3.6.2-glibc-234-build-fix.patch- Postfix on start don't run postalias /etc/postfix/aliases (error open database /etc/postfix/aliases.lmdb). (bsc#1197041) Apply proposed patch- config.postfix can't handle symlink'd /etc/resolv.cof (bsc#1195019) Adapt proposed change: using "cp -afL" by copying.- Update to 3.6.4 * Bug introduced in bugfix 20210708: duplicate bounce_notice_recipient entries in postconf output. This was caused by an incomplete fix to send SMTP session transcripts to $bounce_notice_recipient. * Bug introduced in Postfix 3.0: the proxymap daemon did not automatically authorize proxied maps inside pipemap (example: pipemap:{proxy:maptype:mapname, ...}) or inside unionmap. * Bug introduced in Postfix 2.5: off-by-one error while writing a string terminator. This code passed all memory corruption tests, presumably because it wrote over an alignment padding byte, or over an adjacent character byte that was never read. * The proxymap daemon did not automatically authorize map features added after Postfix 3.3, caused by missing *_maps parameter names in the proxy_read_maps default value. Found during code maintenance.- Update to 3.6.3 * (problem introduced in Postfix 2.4, released in 2007): queue file corruption after a Milter (for example, MIMEDefang) made a request to replace the message body with a copy of that message body plus additional text (for example, a SpamAssassin report). * (problem introduced in Postfix 2.10, released in 2012): The postconf "-x" option could produce incorrect output, because multiple functions were implicitly sharing a buffer for intermediate results. Problem report by raf, root cause analysis by Viktor Dukhovni. * (problem introduced in Postfix 2.11, released in 2013): The check_ccert_access feature worked as expected, but produced a spurious warning when Postfix was built without SASL support. Fix by Brad Barden. * Fix for a compiler warning due to a missing 'const' qualifier when compiling Postfix with OpenSSL 3. Depending on compiler settings this could cause the build to fail. * The known_tcp_ports settings had no effect. It also wasn't fully implemented. Problem report by Peter. * Fix for missing space between a hostname and warning text.- Ensure postfix can write to home directory or server side filtering wont work (sieve)- Ensure service can write to /etc/postfix- Added hardening to systemd service (bsc#1181400). Added harden_postfix.service.patch- config.postfix not updatet after lmdb switch (bsc#1190945) Adapt config.postfix- postfix master.cf: to include "submissions" service (bsc#1189684) Adapt master.cf patch- postfix fails with glibc 2.34 Define HAS_CLOSEFROM (bsc#1189101) add patch - postfix-3.6.2-glibc-234-build-fix.patch- fix config.postfix (follow up of bsc#1188477)- Syntax error in config.postfix (bsc#1188477)- Update to 3.6.2 * In Postfix 3.6, fixed a false "Result too large" (ERANGE) fatal error in the compatibility_level parser, because there was no 'errno = 0' statement before an strtol() call. * (problem introduced in Postfix 3.3) "Null pointer read" error in the cleanup daemon when "header_from_format = standard" (the default as of Postfix 3.3), and email was submitted with /usr/sbin/sendmail without From: header, and an all-space full name was specified in 1) the password file, 2) with "sendmail - F", or 3) with the NAME environment variable. Found by Renaud Metrich. * (problem introduced in Postfix 2.4) False "too many reverse jump" warnings in the showq daemon, because loop detection code was comparing memory addresses instead of queue file names. Reported by Mehmet Avcioglu. * (problem introduced in 1999) The Postfix SMTP server was sending all session transcripts to the error_notice_recipient (default: postmaster), instead of sending transcripts of bounced mail to the bounce_notice_recipient (default: postmaster). Reported by Hans van Zijst. * The texthash: map implementation broke tls_server_sni_maps, because it did not support multi-file inputs. Reported by Christopher Gurnee, who also found an instance of the missing code in the "postmap -F" source code. File: util/dict_thash.c.- spamd wants to start before mail-transfer-agent.target, but that target doesn't exist (bsc#1066854)- postfix-SUSE * rework sysconfig.postfix, add - POSTFIX_WITH_DKIM - POSTFIX_DKIM_CONN * rework config.postfix for main.cf - with_dkim - update postfix-main.cf.patch * add OpenDKIM settings- postfix-mysql * add mysql_relay_recipient_maps.cf - postfix-SUSE * rework sysconfig.postfix, add - POSTFIX_RELAY_RECIPIENTS - POSTFIX_BACKUPMX * add relay_recipients * rework config.postfix for main.cf - is_backupmx - relay_recipient_maps- Add now working CONFIG parameter to sysusers generator - Remove unnecessary group line from postfix-vmail-user.conf- Update to 3.6.1 * Bugfix (introduced: Postfix 2.11): the command "postmap lmdb:/file/name" (create LMDB database from textfile) handled duplicate input keys ungracefully, discarding entries stored up to and including the duplicate key, and causing a double free() call with lmdb versions 0.9.17 and later. Reported by Adi Prasaja; double free() root cause analysis by Howard Chu. * Typo (introduced: Postfix 3.4): silent_discard should be silent-discard in BDAT_README.- fix postfix-master.cf.patch * set correct indentation (again) for options of - submission (needs 3 spaces) - smtps (needs 4 spaces) to make config.postfix work nicely again- Update to 3.6.0 - Major changes - internal protocol identification Internal protocols have changed. You need to "postfix stop" before updating, or before backing out to an earlier release, otherwise long-running daemons (pickup, qmgr, verify, tlsproxy, postscreen) may fail to communicate with the rest of Postfix, causing mail delivery delays until Postfix is restarted. For more see /usr/share/doc/packages/postfix/RELEASE_NOTES - refreshed patches to apply cleanly again: fix-postfix-script.patch ipv6_disabled.patch pointer_to_literals.patch postfix-linux45.patch postfix-main.cf.patch postfix-master.cf.patch postfix-no-md5.patch postfix-ssl-release-buffers.patch postfix-vda-v14-3.0.3.patch set-default-db-type.patch- (bsc#1186669) - postfix.service has "Requires=var-run.mount" Remove bad requirements- Update to 3.5.10 with security fixes: * Missing null pointer checks (introduced in Postfix 3.4) after an internal I/O error during the smtp(8) to tlsproxy(8) handshake. Found by Coverity, reported by Jaroslav Skarvada. Based on a fix by Viktor Dukhovni. * Null pointer bug (introduced in Postfix 3.0) and memory leak (introduced in Postfix 3.4) after an inline: table syntax error in main.cf or master.cf. Found by Coverity, reported by Jaroslav Skarvada. Based on a fix by Viktor Dukhovni. * Incomplete null pointer check (introduced: Postfix 2.10) after truncated HaProxy version 1 handshake message. Found by Coverity, reported by Jaroslav Skarvada. Fix by Viktor Dukhovni. * Missing null pointer check (introduced: Postfix alpha) after null argv[0] value.- (bsc#1183305) - config.postfix uses db as suffix for postmaps Depending on DEF_DB_TYPE uses lmdb or db- (bsc#1182833) - /usr/share/fillup-templates/sysconfig.postfix still refers to /etc/services Use getent to detect if smtps is already defined.- (bsc#1180473) [Build 20201230] postfix has invalid default config (bsc#1181381) [Build 130.3] openQA test fails in mta, mutt - postfix broken: "queue file write error" and "error: unsupported dictionary type: hash" Export DEF_DB_TYPE before starting the perl script.- bsc#1180473 - [Build 20201230] postfix has invalid default config Fixing config.postfix and sysconfig.postfix- Update to 3.5.9 * improves the reporting of DNSSEC problems that may affect DANE security- Only do the conversion from the hash/btree databases to lmdb when the default database type changes from hash to lmdb and do not stop and start the service (the old compiled databases can live together with the new ones) - convert-bdb-to-lmdb.sh - Clean up the specfile * Remove < 1330 conditional builds * Use generated postfix-files instead of the obsolete one from postfix-SUSE.tar.gz * Use dynamicmaps.cf.d instead of modifying dynamicmaps.cf upon (de)installation of optional mysql, pgsql and ldap subpackages * Use default location for post-install, postfix-tls-script, postfix-wrapper and postmulti-script- Set lmdb to be the default db. - Convert btree tables to lmdb too. Stop postfix before converting from bdb to lmdb - This package is without bdb support. That's why convert must be done without any suse release condition. o remove patch postfix-no-btree.patch o add set-default-db-type.patch- Set database type for address_verify_map and postscreen_cache_map to lmdb (btree requires Berkeley DB) o add postfix-no-btree.patch- Set default database type to lmdb and fix update_postmaps script- Use variable substition instead of sed to remove .db suffix and substitute hash: for lmdb: in /etc/postfix/master.cf as well. Check before substitution if there is something to do (to keep rpmcheck happy).- bsc#1176650 L3: What is regularly triggering the "fillup" command and changing modify-time of /etc/sysconfig/postfix? o Remove miss placed fillup_only call from %verifyscript- Remove Berkeley DB dependency (JIRA#SLE-12191) The pacakges postfix is build without Berkely DB support. lmdb will be used instead of BDB. The pacakges postfix-bdb is build with Berkely DB support. o add patch for main.cf for postfix-bdb package postfix-bdb-main.cf.patch- Update to 3.5.8 * The Postfix SMTP client inserted into message headers longer than $line_length_limit (default: 2048), causing all subsequent header content to become message body content. * The postscreen daemon did not save a copy of the postscreen_dnsbl_reply_map lookup result. This has no effect when the recommended texthash: look table is used, but it could result in stale data with other lookup tables. * After deleting a recipient with a Milter, the Postfix recipient duplicate filter was not updated; the filter suppressed requests to add the recipient back. * Memory leak: the static: maps did not free their casefolding buffer. * With "smtpd_tls_wrappermode = yes", the smtps service was waiting for a TLS handshake, after processing an XCLIENT command. * The smtp_sasl_mechanism_filter implementation ignored table lookup errors, treating them as 'not found'. * The code that looks for Delivered-To: headers ignored headers longer than $line_length_limit (default: 2048).- Update to 3.5.7 * Fixed random certificate verification failures with "smtp_tls_connection_reuse = yes", because tlsproxy(8) was using the wrong global TLS context for connections that use DANE or non-DANE trust anchors.- Move ldap into an own sub-package like all other databases - Move manual pages to correct sub-package- Use sysusers.d to create system accounts - Remove wrong %config for systemd directory content- Use the correct signature file for source verification - Rename postfix-3.5.6.tar.gz.sig to postfix-3.5.6.tar.gz.asc (to prevent confusion, as the signature file from upstream with .sig extension is incompatible with the build service)- Update to 3.5.6 with following fixes: * Workaround for unexpected TLS interoperability problems when Postfix runs on OS distributions with system-wide OpenSSL configurations. * Memory leaks in the Postfix TLS library, the largest one involving multiple kBytes per peer certificate.- Add source verification (add postfix.keyring)- Use systemd_ordering instead of systemd_require. - Move /etc/postfix/system to /usr/lib/postfix/systemd [bsc#1173688] - Drop /var/adm/SuSEconfig from %post, it does nothing. - Rename postfix-SuSE to postfix-SUSE - Delete postfix-SUSE/README.SuSE, company name spelled wrong, completly outdated and not used. - Delete postfix-SUSE/SPAMASSASSIN+POSTFIX.SuSE, company name spelled wrong, outdated and not used. - sysconfig.mail-postfix: Fix description of MAIL_CREATE_CONFIG, SuSEconfig is gone since ages. - update_chroot.systemd: Remove advice to run SuSEconfig. - Remove rc.postfix, not used, outdated. - mkpostfixcert: Remove advice to run SuSEconfig.- Update to 3.5.4: * The connection_reuse attribute in smtp_tls_policy_maps always resulted in an "invalid attribute name" error. * SMTP over TLS connection reuse always failed for Postfix SMTP client configurations that specify explicit trust anchors (remote SMTP server certificates or public keys). * The Postfix SMTP client's DANE implementation would always send an SNI option with the name in a destination's MX record, even if the MX record pointed to a CNAME record. MX records that point to CNAME records are not conformant with RFC5321, and so are rare. Based on the DANE survey of ~2 million hosts it was found that with the corrected SMTP client behavior, sending SNI with the CNAME-expanded name, the SMTP server would not send a different certificate. This fix should therefore be safe.- Update to 3.5.3: * TLS handshake failure in the Postfix SMTP server during SNI processing, after the server-side TLS engine sent a TLSv1.3 HelloRetryRequest (HRR) to a remote SMTP client. * The command "postfix tls deploy-server-cert" did not handle a missing optional argument. This bug was introduced in Postfix 3.1.- Update to 3.5.2: * A TLS error for a database client caused a false 'lost connection' error for an SMTP over TLS session in the same Postfix process. This bug was introduced with Postfix 2.2. * The same bug existed in the tlsproxy(8) daemon, where a TLS error for one TLS session could cause a false 'lost connection' error for a concurrent TLS session in the same process. This bug was introduced with Postfix 2.8. * The Postfix build now disables DANE support on Linux systems with libc-musl such as Alpine, because libc-musl provides no indication whether DNS responses are authentic. This broke DANE support without a clear explanation. * Due to implementation changes in the ICU library, some Postfix daemons reported file access errrors (U_FILE_ACCESS_ERROR) after chroot(). This was fixed by initializing the ICU library before making the chroot() call. * Minor code changes to silence a compiler that special-cases string literals. * Segfault (null pointer) in the tlsproxy(8) client role when the server role was disabled. This typically happened on systems that do not receive mail, after configuring connection reuse for outbound SMTP over TLS. * The date portion of the maillog_file_rotate_suffix default value used the minute (%M) instead of the month (%m).- boo#1106004 fix incorrect locations for files in postfix-files- Dropped deprecated-RES_INSECURE1.patch to make DNSSEC-secured lookups and DANE mail transport work again - Update to 3.5.1: * Support for the haproxy v2 protocol. The Postfix implementation supports TCP over IPv4 and IPv6, as well as non-proxied connections; the latter are typically used for heartbeat tests. * Support to force-expire email messages. This introduces new postsuper(1) command-line options to request expiration, and additional information in mailq(1) or postqueue(1) output. * The Postfix SMTP and LMTP client support a list of nexthop destinations separated by comma or whitespace. These destinations will be tried in the specified order. * Incompatible changes: * Logging: Postfix daemon processes now log the from= and to= addresses in external (quoted) form in non-debug logging (info, warning, etc.). This means that when an address localpart contains spaces or other special characters, the localpart will be quoted, for example: from=<"name with spaces"@example.com> Specify "info_log_address_format = internal" for backwards compatibility. * Postfix now normalizes IP addresses received with XCLIENT, XFORWARD, or with the HaProxy protocol, for consistency with direct connections to Postfix. This may change the appearance of logging, and the way that check_client_access will match subnets of an IPv6 address.- Update to 3.4.10: * Bug (introduced: Postfix 2.3): Postfix Milter client state was not properly reset after one Milter in a multi-Milter configuration failed during MAIL FROM, resulting in a Postfix Milter client panic during the next MAIL FROM command in the same SMTP session.- bsc#1162891 server:mail/postfix: cond_slp bug on TW after moving /etc/services to /usr/etc/services- bsc#1160413 postfix fails with -fno-common- Update to 3.4.9: * Bug (introduced: Postfix 3.1): smtp_dns_resolver_options were broken while adding support for negative DNS response caching in postscreen. Postfix was inadvertently changed to call res_query() instead of res_search(). * Bug (introduced: Postfix 2.5): Postfix ignored the CONNECT macro overrides from a Milter application. Postfix now evaluates the Milter macros for an SMTP CONNECT event after the Postfix-to-Milter connection is negotiated. * Bug (introduced: Postfix 3.0): sanitize (remote) server responses before storing them in the verify database, to avoid Postfix warnings about malformed UTF8. Found during code maintenance.- Update to 3.4.8: * Fix for an Exim interoperability problem when postscreen after-220 checks are enabled. Bug introduced in Postfix 3.4: the code that detected "PIPELINING after BDAT" looked at the wrong variable. The warning now says "BDAT without valid RCPT", and the error is no longer treated as a command PIPELINING error, thus allowing mail to be delivered. Meanwhile, Exim has been fixed to stop sending BDAT commands when postscreen rejects all RCPT commands. * Usability bug, introduced in Postfix 3.4: the parser for key/certificate chain files rejected inputs that contain an EC PARAMETERS object. While this is technically correct (the documentation says what types are allowed) this is surprising behavior because the legacy cert/key parameters will accept such inputs. For now, the parser skips object types that it does not know about for usability, and logs a warning because ignoring inputs is not kosher. * Bug introduced in Postfix 2.8: don't gratuitously enable all after-220 tests when only one such test is enabled. This made selective tests impossible with 'good' clients. This will be fixed in older Postfix versions at some later time.- Backport deprecated-RES_INSECURE1.patch in order to fix boo#1149705.- Update to 3.4.7: * Robustness: the tlsproxy(8) daemon could go into a loop, logging a flood of error messages. Problem reported by Andreas Schulze after enabling SMTP/TLS connection reuse. * Workaround: OpenSSL changed an SSL_Shutdown() non-error result value into an error result value, causing logfile noise. * Configuration: the new 'TLS fast shutdown' parameter name was implemented incorrectly. The documentation said "tls_fast_shutdown_enable", but the code said "tls_fast_shutdown". This was fixed by changing the code, because no-one is expected to override the default. * Performance: workaround for poor TCP loopback performance on LINUX, where getsockopt(..., TCP_MAXSEG, ...) reports a bogus TCP maximal segment size that is 1/2 to 1/3 of the real MSS. To avoid client-side Nagle delays or server-side delayed ACKs caused by multiple smaller-than-MSS writes, Postfix chooses a VSTREAM buffer size that is a small multiple of the reported bogus MSS. This workaround increases the multiplier from 2x to 4x. * Robustness: the Postfix Dovecot client could segfault (null pointer read) or cause an SMTP server assertion to fail when talking to a fake Dovecot server. The Postfix Dovecot client now logs a proper error instead.- bsc#1120757 L3: File Permissions->Paranoid can cause a system hang Break loop if postfix has no permission in spool directory. - add postfix-avoid-infinit-loop-if-no-permission.patch- fix for boo#1144946 mydestination - missing default localhost * update config.postfix- bsc#1142881 - mkpostfixcert from Postfix still uses md- removal of SuSEfirewall2 service, since SuSEfirewall2 has been replaced by firewalld, see [1]. [1]: https://lists.opensuse.org/opensuse-factory/2019-01/msg00490.html- update example POSTFIX_BASIC_SPAM_PREVENTION: permit_mynetworks for * POSTFIX_SMTPD_HELO_RESTRICTIONS * POSTFIX_SMTPD_RECIPIENT_RESTRICTIONS - fix for: Can't connect to local MySQL server through socket '/run/mysql/mysql.sock' * update config.postfix * update update_chroot.systemd- Update to 3.4.6: * Workaround for implementations that hang Postfix while shutting down a TLS session, until Postfix times out. With "tls_fast_shutdown_enable = yes" (the default), Postfix no longer waits for the TLS peer to respond to a TLS 'close' request. This is recommended with TLSv1.0 and later. * Fixed a too-strict censoring filter that broke multiline Milter responses for header/body events. Problem report by Andreas Thienemann. * The code to reset Postfix SMTP server command counts was not called after a HaProxy handshake failure, causing stale numbers to be reported. Problem report by Joseph Ward. * postconf(5) documentation: tlsext_padding is not a tls_ssl_options feature. * smtp(8) documentation: updated the BUGS section text about Postfix support to reuse open TLS connections. * Portability: added "#undef sun" to util/unix_dgram_connect.c.- Ensure that postfix is member of all groups as before.- BuildRequire pkgconfig(systemd) instead of systemd: allow OBS to shortcut the build queues by allowing usage of systemd-mini- Drop the omc config fate#301838: * it is obsolete since SLE11- bsc#1104543 config.postfix does not start tlsmgr in master.cf when using POSTFIX_SMTP_TLS_CLIENT="must". Applyed the proposed patch.- Update to 3.4.5: Bugfix (introduced: Postfix 3.0): LMTP connections over UNIX-domain sockets were cached but not reused, due to a cache lookup key mismatch. Therefore, idle cached connections could exhaust LMTP server resources, resulting in two-second pauses between email deliveries. This problem was investigated by Juliana Rodrigueiro. File: smtp/smtp_connect.c.- Update to 3.4.4 o Incompatible changes - The Postfix SMTP server announces CHUNKING (BDAT command) by default. In the unlikely case that this breaks some important remote SMTP client, disable the feature as follows: /etc/postfix/main.cf: [#] The logging alternative: smtpd_discard_ehlo_keywords = chunking [#] The non-logging alternative: smtpd_discard_ehlo_keywords = chunking, silent_discard - This introduces a new master.cf service 'postlog' with type 'unix-dgram' that is used by the new postlogd(8) daemon. Before backing out to an older Postfix version, edit the master.cf file and remove the postlog entry. - Postfix 3.4 drops support for OpenSSL 1.0.1 - To avoid performance loss under load, the tlsproxy(8) daemon now requires a zero process limit in master.cf (this setting is provided with the default master.cf file). By default, a tlsproxy(8) process will retire after several hours. - To set the tlsproxy process limit to zero: postconf -F tlsproxy/unix/process_limit=0 postfix reload o Major changes - Postfix SMTP server support for RFC 3030 CHUNKING (the BDAT command) without BINARYMIME, in both smtpd(8) and postscreen(8). This has no effect on Milters, smtpd_mumble_restrictions, and smtpd_proxy_filter. See BDAT_README for more. - Support for logging to file or stdout, instead of using syslog. - Logging to file solves a usability problem for MacOS, and eliminates multiple problems with systemd-based systems. - Logging to stdout is useful when Postfix runs in a container, as it eliminates a syslogd dependency. - Better handling of undocumented(!) Linux behavior whether or not signals are delivered to a PID=1 process. - Support for (key, list of filenames) in map source text. Currently, this feature is used only by tls_server_sni_maps. - Automatic retirement: dnsblog(8) and tlsproxy(8) process will now voluntarily retire after after max_idle*max_use, or some sane limit if either limit is disabled. Without this, a process could stay busy for days or more. - Postfix SMTP client support for multiple deliveries per TLS-encrypted connection. This is primarily to improve mail delivery performance for destinations that throttle clients when they don't combine deliveries. This feature is enabled with "smtp_tls_connection_reuse=yes" in main.cf, or with "tls_connection_reuse=yes" in smtp_tls_policy_maps. It supports all Postfix TLS security levels including dane and dane-only. - SNI support in the Postfix SMTP server, the Postfix SMTP client, and in the tlsproxy(8) daemon (both server and client roles). See the postconf(5) documentation for the new tls_server_sni_maps and smtp_tls_servername parameters. - Support for files that contain multiple (key, certificate, trust chain) instances. This was required to implement server-side SNI table lookups, but it also eliminates the need for separate cert/key files for RSA, DSA, Elliptic Curve, and so on. - Support for smtpd_reject_footer_maps (as well as the postscreen variant postscreen_reject_footer_maps) for more informative reject messages. This is indexed with the Postfix SMTP server response text, and overrides the footer specified with smtpd_reject_footer. One will want to use a pcre: or regexp: map with this. o Bugfixes - Andreas Schulze discovered that reject_multi_recipient_bounce was producing false rejects with BDAT commands. This problem already existed with Postfix 2.2 smtpd_end_of_data_restrictons. Postfix 3.4.4 fixes both.- postfix-linux45.patch: support also newer kernels -- pretend we are still at kernel 3. Note that there are no conditionals for LINUX3 or LINUX4. And LINUX5 was generated, but not tested in the code which caused build failures.- skip set -x and fix version update changes entry- Update to 3.3.3 * When the master daemon runs with PID=1 (init mode), it will now reap child processes from non-Postfix code running in the same container, instead of terminating with a panic. * Bugfix (introduced: postfix-2.11): with posttls-finger, connections to unix-domain servers always resulted in "Failed to establish session" even after a connection was established. Jaroslav Skarva. File: posttls-finger/posttls-finger.c. * Bugfix (introduced: Postfix 3.0): with smtputf8_enable=yes, table lookups could casefold the search string when searching a lookup table that does not use fixed-string keys (regexp, pcre, tcp, etc.). Historically, Postfix would not case-fold the search string with such tables. File: util/dict_utf8.c.- PostrgeSQL's pg_config is meant for linking server extensions, use libpq's pkg-config instead, if available. This is needed to fix build with PostgreSQL 11.- rework config.postfix * disable commenting of smtpd_sasl_path/smtpd_sasl_type no need to comment, cause it is set to default anyway and 'uncommenting' would place it at end of file then which is not wanted- rework postfix-main.cf.patch * disable virtual_alias_domains cause (default: $virtual_alias_maps) - rework config.postfix * disable PCONF of virtual_alias_domains virtual_alias_maps will be set anyway to the correct value * extend virtual_alias_maps with - mysql_virtual_alias_domain_maps.cf - mysql_virtual_alias_domain_catchall_maps.cf - rework postfix-mysql, added * mysql_virtual_alias_domain_maps.cf * mysql_virtual_alias_domain_catchall_maps.cf needed for reject_unverified_recipient- binary hardening: link with full RELRO- Update to 3.3.2 * Support for OpenSSL 1.1.1 and TLSv1.3. * Bugfixes: - smtpd_discard_ehlo_keywords could not disable "SMTPUTF8", because some lookup table was using "EHLO_MASK_SMTPUTF8" instead. - minor memory leak in DANE support when minting issuer certs. - The Postfix build did not abort if the m4 command was not installed, resulting in a broken postconf command.- add POSTFIX_RELAY_DOMAINS * more flexibility to add to relay_domains without breaking config.postfix * rework restriction examples in sysconf.postfix based on postfix-buch.com (2. edtion by Hildebrandt, Koetter) - disable weak cipher: RC4 after check with https://ssl-tools.net/mailservers- update config.postfix * don't reject mail from authenticated users even if reject_unknown_client_hostname would match, add permit_sasl_authenticated to all restrictions requires smtpd_delay_reject = yes - update postfix-main.cf.patch * recover removed setting smtpd_sasl_path and smtpd_sasl_type, set to default value config.postfix will not 'enable' (remove #) var, but place modified (enabled) var at end of file, far away from place where it should be - rebase patches * fix-postfix-script.patch * postfix-vda-v14-3.0.3.patch * postfix-linux45.patch * postfix-master.cf.patch * pointer_to_literals.patch * postfix-no-md5.patch- bsc#1092939 - Postfixes postconf gives a lot of LDAP related warnings o add m4 as buildrequires, as proposed.- Add zlib-devel as buildrequires, previously included from openssl-devel- bsc#1087471 Unreleased Postfix update breaks SUSE Manager o Removing setting smtpd_sasl_path and smtpd_sasl_type to empty- Update to 3.3.1 * Postfix did not support running as a PID=1 process, which complicated Postfix deployment in containers. The "postfix start-fg" command will now run the Postfix master daemon as a PID=1 process if possible. Thanks for inputs from Andreas Schulze, Eray Aslan, and Viktor Dukhovni. * Segfault in the postconf(1) command after it could not open a Postfix database configuration file due to a file permission error (dereferencing a null pointer). Reported by Andreas Hasenack, fixed by Viktor Dukhovni. * The luser_relay feature became a black hole, when the luser_relay parameter was set to a non-existent local address (i.e. mail disappeared silently). Reported by J?rgen Thomsen. * Missing error propagation in the tlsproxy(8) daemon could result in a segfault after TLS handshake error (dereferencing a 0xffff...ffff pointer). This daemon handles the TLS protocol when a non-whitelisted client sends a STARTTLS command to postscreen(8).- remove pre-requirements on sysvinit(network) and sysvinit(syslog). There seems to be no good reason for that other than blowing up the dependencies (bsc#1092408).- bsc#1071807 postfix-SuSE/config.postfix: only reload postfix if the actual service is running. This prevents spurious and irrelevant error messages in system logs.- bsc#1082514 autoyast: postfix gets not set myhostname properly - set to localhost- Refresh spec-file via spec-cleaner and manual optinizations. * Add %license macro. * Set license to IPL-1.0 OR EPL-2.0. - Update to 3.3.0 * http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/postfix-3.3.0.RELEASE_NOTES * Dual license: in addition to the historical IBM Public License 1.0, Postfix is now also distributed with the more recent Eclipse Public License 2.0. Recipients can choose to take the software under the license of their choice. Those who are more comfortable with the IPL can continue with that license. * The postconf command now warns about unknown parameter names in a Postfix database configuration file. As with other unknown parameter names, these warnings can help to find typos early. * Container support: Postfix 3.3 will run in the foreground with "postfix start-fg". This requires that Postfix multi-instance support is disabled (the default). To collect Postfix syslog information on the container's host, mount the host's /dev/log socket into the container, for example with "docker run -v /dev/log:/dev/log ...other options...", and specify a distinct Postfix syslog_name setting in the container (for example with "postconf syslog_name=the-name-here"). * Milter support: applications can now send RET and ENVID parameters in SMFIR_CHGFROM (change envelope sender) requests. * Postfix-generated From: headers with 'full name' information are now formatted as "From: name
" by default. Specify "header_from_format = obsolete" to get the earlier form "From: address (name)". * Interoperability: when Postfix IPv6 and IPv4 support are both enabled, the Postfix SMTP client will now relax MX preferences and attempt to schedule similar numbers of IPv4 and IPv6 addresses. This works around mail delivery problems when a destination announces lots of primary MX addresses on IPv6, but is reachable only over IPv4 (or vice versa). The new behavior is controlled with the smtp_balance_mx_inet_protocols parameter. * Compatibility safety net: with compatibility_level < 1, the Postfix SMTP server now warns for mail that would be blocked by the Postfix 2.10 smtpd_relay_restrictions feature, without blocking that mail. There still is a steady trickle of sites that upgrade from an earlier Postfix version.- bsc#1065411 Package postfix should require package system-user-nobody - bsc#1080772 postfix smtpd throttle getting "hello" if no sasl auth was configured- Fix usage of fillup_only:-y is not a valid option to this macro.- Replace references to /var/adm/fillup-templates with new %_fillupdir macro (boo#1069468)- Don't mark postfix.service as config file, this is no config file. - Some of the Requires(pre) are needed for post-install and at runtime, fix the requires.- update to 3.2.4 * DANE interoperability. Postfix builds with OpenSSL 1.0.0 or 1.0.1 failed to send email to some sites with "TLSA 2 X X" DNS records associated with an intermediate CA certificate. Problem report and initial fix by Erwan Legrand. * Missing dynamicmaps support in the Postfix sendmail command. This broke authorized_submit_users settings that use a dynamically-loaded map type. Problem reported by Ulrich Zehl.- bnc#1059512 L3: Postfix Problem The applied changes breaks existing postfix configurations because daemon_directory was not adapted to the new value.- fix build for SLE * nothing provides libnsl-devel * add bcond_with libnsl- bnc#1059512 L3: Postfix Problem To manage multiple Postfix instances on a single host requires that daemon_directory and shlib_directory is different to avoid use of the shared directories also as per-instance directories. For this reason daemon_directory was set to /usr/lib/postfix/bin/. shlib_directory stands /usr/lib/postfix/.- bnc#1016491 postfix raported to log "warning: group or other writable:" on each symlink in config. * Add fix-postfix-script.patch- update to 3.2.3 * Extension propagation was broken with "recipient_delimiter = .". This change reverts a change that was trying to be too clever. * The postqueue command would abort with a panic message after it experienced an output write error while listing the mail queue. This change restores a write error check that was lost with the Postfix 3.2 rewrite of the vbuf_print formatter. * Restored sanity checks for dynamically-specified width and precision in format strings (%*, %.*, and %*.*). These checks were lost with the Postfix 3.2 rewrite of the vbuf_print formatter.- Add libnsl-devel build requires for glibc obsoleting libnsl- bnc#1045264 L3: postmap problem * Applying proposed patch of leen.meyer@ziggo.nl in bnc#771811- update to 3.2.2 * Security: Berkeley DB versions 2 and later try to read settings from a file DB_CONFIG in the current directory. This undocumented feature may introduce undisclosed vulnerabilities resulting in privilege escalation with Postfix set-gid programs (postdrop, postqueue) before they chdir to the Postfix queue directory, and with the postmap and postalias commands depending on whether the user's current directory is writable by other users. This fix does not change Postfix behavior for Berkeley DB versions < 3, but it does reduce postmap and postalias 'create' performance with Berkeley DB versions 3.0 .. 4.6. * The SMTP server receive_override_options were not restored at the end of an SMTP session, after the options were modified by an smtpd_milter_maps setting of "DISABLE". Milter support remained disabled for the life time of the smtpd process. * After the Postfix 3.2 address/domain table lookup overhaul, the check_sender_access and check_recipient_access features ignored a non-default parent_domain_matches_subdomains setting.- revert changes of postfix-main.cf.patch from rev=261 * config.postfix will not 'enable' (remove #) var, but place modified (enabled) var at end of file, far away from place where it should be * keep vars enabled but empty- Some cleanups * Fix SUSE postfix-files to avoid chown errors (anyway this file seems to be obsolete) * Avoid installing shared libraries twice * Refresh patch postfix-linux45.patch- update postfix-master.cf.patch * recover lost (with 3.2.0 update) submission, smtps sections * merge with upstream update - update config.postfix * update master.cf generation for submission - rebase patches against 3.2.0 * pointer_to_literals.patch * postfix-no-md5.patch * postfix-ssl-release-buffers.patch * postfix-vda-v14-3.0.3.patch- Require system group mail - Use mail group name instead of GID- update to 3.2.0 - [Feature 20170128] Postfix 3.2 fixes the handling of address extensions with email addresses that contain spaces. For example, the virtual_alias_maps, canonical_maps, and smtp_generic_maps features now correctly propagate an address extension from "aa bb+ext"@example.com to "cc dd+ext"@other.example, instead of producing broken output. - [Feature 20161008] "PASS" and "STRIP" actions in header/body_checks. "STRIP" is similar to "IGNORE" but also logs the action, and "PASS" disables header, body, and Milter inspection for the remainder of the message content. Contributed by Hobbit. - [Feature 20160330] The collate.pl script by Viktor Dukhovni for grouping Postfix logfile records into "sessions" based on queue ID and process ID information. It's in the auxiliary/collate directory of the Postfix source tree. - [Feature 20160527] Postfix 3.2 cidr tables support if/endif and negation (by prepending ! to a pattern), just like regexp and pcre tables. The primarily purpose is to improve readability of complex tables. See the cidr_table(5) manpage for syntax details. - [Incompat 20160925] In the Postfix MySQL database client, the default option_group value has changed to "client", to enable reading of "client" option group settings in the MySQL options file. This fixes a "not found" problem with Postfix queries that contain UTF8-encoded non-ASCII text. Specify an empty option_group value (option_group =) to get backwards-compatible behavior. - [Feature 20161217] Stored-procedure support for MySQL databases. Contributed by John Fawcett. See mysql_table(5) for instructions. - [Feature 20170128] The postmap command, and the inline: and texthash: maps now support spaces in left-hand field of the lookup table "source text". Use double quotes (") around a left-hand field that contains spaces, and use backslash (\) to protect embedded quotes in a left-hand field. There is no change in the processing of the right-hand field. - [Feature 20160611] The Postfix SMTP server local IP address and port are available in the policy delegation protocol (attribute names: server_address, server_port), in the Milter protocol (macro names: {daemon_addr}, {daemon_port}), and in the XCLIENT protocol (attribute names: DESTADDR, DESTPORT). - [Feature 20161024] smtpd_milter_maps support for per-client Milter configuration that overrides smtpd_milters, and that has the same syntax. A lookup result of "DISABLE" turns off Milter support. See MILTER_README.html for details. - [Feature 20160611] The Postfix SMTP server local IP address and port are available in the policy delegation protocol (attribute names: server_address, server_port), in the Milter protocol (macro names: {daemon_addr}, {daemon_port}), and in the XCLIENT protocol (attribute names: DESTADDR, DESTPORT). - [Incompat 20170129] The postqueue command no longer forces all message arrival times to be reported in UTC. To get the old behavior, set TZ=UTC in main.cf:import_environment (this override is not recommended, as it affects all Postfix utities and daemons). - [Incompat 20161227] For safety reasons, the sendmail -C option must specify an authorized directory: the default configuration directory, a directory that is listed in the default main.cf file with alternate_config_directories or multi_instance_directories, or the command must be invoked with root privileges (UID 0 and EUID 0). This mitigates a recurring problem with the PHP mail() function. - [Feature 20160625] The Postfix SMTP server now passes remote client and local server network address and port information to the Cyrus SASL library. Build with ``make makefiles "CCARGS=$CCARGS -DNO_IP_CYRUS_SASL_AUTH"'' for backwards compatibility. - [Feature 20161103] Postfix 3.2 disables the 'transitional' compatibility between the IDNA2003 and IDNA2008 standards for internationalized domain names (domain names beyond the limits of US-ASCII). This change makes Postfix behavior consistent with contemporary web browsers. It affects the handling of some corner cases such as German sz and Greek zeta. See http://unicode.org/cldr/utility/idna.jsp for more examples. Specify "enable_idna2003_compatibility = yes" to restore historical behavior (but keep in mind that the rest of the world may not make that same choice). - [Feature 20160828] Fixes for deprecated OpenSSL 1.1.0 API features, so that Postfix will build without depending on backwards-compatibility support. [Incompat 20161204] Postfix 3.2 removes tentative features that were implemented before the DANE spec was finalized: - Support for certificate usage PKIX-EE(1), - The ability to disable digest agility (Postfix now behaves as if "tls_dane_digest_agility = on"), and - The ability to disable support for "TLSA 2 [01] [12]" records that specify the digest of a trust anchor (Postfix now behaves as if "tls_dane_trust_anchor_digest_enable = yes). - [Feature 20161217] Postfix 3.2 enables elliptic curve negotiation with OpenSSL >= 1.0.2. This changes the default smtpd_tls_eecdh_grade setting to "auto", and introduces a new parameter tls_eecdh_auto_curves with the names of curves that may be negotiated. The default tls_eecdh_auto_curves setting is determined at compile time, and depends on the Postfix and OpenSSL versions. At runtime, Postfix will skip curve names that aren't supported by the OpenSSL library. - [Feature 20160611] The Postfix SMTP server local IP address and port are available in the policy delegation protocol (attribute names: server_address, server_port), in the Milter protocol (macro names: {daemon_addr}, {daemon_port}), and in the XCLIENT protocol (attribute names: DESTADDR, DESTPORT). - refresh postfix-master.cf.patch- make sure that system users can be created in %pre- Fix requires: - shadow is needed for postfix-mysql pre-install section - insserv is not needed if systemd is used- update postfix-mysql * update mysql_*.cf files * update postfix-mysql.sql (INNODB, utf8) - update postfix-main.cf.patch * uncomment smtpd_sasl_path, smtpd_sasl_type can be changed via POSTFIX_SMTP_AUTH_SERVICE=(cyrus,dovecot) * add option for smtp_tls_policy_maps (commented) - update postfix-master.cf.patch * fix indentation of submission, smtps options for correct enabling via config.postfix - update config.postfix * fix sync of CA certificates * fix master.cf generation for submission, smtps - rebase postfix-vda-v14-3.0.3.patch- FATE#322322 Update postfix to version 3.X Merging changes with SLES12-SP2 Removeved patches: add_missed_library.patch bnc#947707.diff dynamic_maps.patch postfix-db6.diff postfix-opensslconfig.patch bnc#947519.diff dynamic_maps_pie.patch postfix-post-install.patch These are included in the new version of postfix - Remove references to SuSEconfig.postfix from sysconfig docs. (bsc#871575) - bnc#947519 SuSEconfig.postfix should enforce umask 022 - bnc#947707 mail generated by Amavis being prevented from being re-adressed by /etc/postfix/virtual - bnc#972346 /usr/sbin/SuSEconfig.postfix is wrong - postfix-linux45.patch: handle Linux 4.x and Linux 5.x (used by aarch64) (bsc#940289)- update to 3.1.4 * The postscreen daemon did not merge the client test status information for concurrent sessions from the same IP address. * The Postfix SMTP server falsely rejected a sender address when validating a sender address with "smtpd_reject_unlisted_recipient = yes" or with "reject_unlisted_sender". Cause: the address validation code did not query sender_canonical_maps. * The virtual delivery agent did not detect failure to skip to the end of a mailbox file, so that mail would be delivered to the beginning of the file. This could happen when a mailbox file was already larger than the virtual mailbox size limit. * The postsuper logged an incorrect rename operation count after creating a missing directory. * The Postfix SMTP server falsely rejected mail when a sender-dependent "error" transport was configured. Cause: the SMTP server address validation code was not updated when the sender_dependent_default_transport_maps feature was introduced. * The Postfix SMTP server falsely rejected an SMTPUTF8 sender address, when "smtpd_delay_reject = no". * The "postfix tls deploy-server-cert" command used the wrong certificate and key file. This was caused by a cut-and-paste error in the postfix-tls-script file.- improve config.postfix * improve SASL stuff * add POSTFIX_SMTP_AUTH_SERVICE=(cyrus|dovecot)- improve config.postfix * improve with MySQL stuff- update vda patch to latest available * remove postfix-vda-v13-3.10.0.patch * add postfix-vda-v14-3.0.3.patch - rebase patches (and to be p0) * pointer_to_literals.patch * postfix-main.cf.patch * postfix-master.cf.patch * postfix-no-md5.patch * postfix-ssl-release-buffers.patch - add /etc/postfix/ssl as default DIR for SSL stuff * cacerts -> ../../ssl/certs/ * certs/ - revert POSTFIX_SSL_PATH from '/etc/ssl' to '/etc/postfix/ssl' - improve config.postfix * revert smtpd_tls_CApath to POSTFIX_SSL_PATH/cacerts which is a symlink to /etc/ssl/certs Without reverting, 'gen_CA' would create files which would then be on the previous defined 'sslpath(/etc/ssl)/certs' (smtpd_tls_CApath) Cert reqs would be placed in 'sslpath(/etc/ssl)/certs/postfixreq.pem' which is not a good idea. * mkchroot: sync '/etc/postfix/ssl' to chroot * improve PCONF for smtp{,d}_tls_{cert,key}_file, adding/removing from main.cf, show warning if enabled and file is missing- update to 3.1.3: * The Postfix SMTP server did not reset a previous session's failed/total command counts before rejecting a client that exceeds request or concurrency rates. This resulted in incorrect failed/total command counts being logged at the end of the rejected session. * The unionmap multi-table interface did not propagate table lookup errors, resulting in false "user unknown" responses. * The documentation was updated with a workaround for false "not found" errors with MySQL map queries that contain UTF8-encoded text. The workaround is to specify "option_group = client" in Postfix MySQL configuration files. This will be the default setting with Postfix 3.2 and later.- update to 3.1.2: * Changes to make Postfix build with OpenSSL 1.1.0. * The makedefs script ignored readme_directory=pathname overrides. Fix by Todd C. Olson. * The tls_session_ticket_cipher documentation says that the default cipher for TLS session tickets is aes-256-cbc, but the implemented default was aes-128-cbc. Note that TLS session ticket keys are rotated after 1/2 hour, to limit the impact of attacks on session ticket keys.- postfix-post-install.patch: remove empty patch- fix Changelog cause of Factory decline- Fix typo in config.postfix- bnc#981097 config.postfix creates broken main.cf for tls client configuration - bnc#981099 /etc/sysconfig/postfix: POSTFIX_SMTP_TLS_CLIENT incomplete - update to 3.1.1: - The new address_verify_pending_request_limit parameter introduces a safety limit for the number of address verification probes in the active queue. The default limit is 1/4 of the active queue maximum size. The queue manager enforces the limit by tempfailing probe messages that exceed the limit. This design avoids dependencies on global counters that get out of sync after a process or system crash. - Machine-readable, JSON-formatted queue listing with "postqueue -j" (no "mailq" equivalent). - The milter_macro_defaults feature provides an optional list of macro name=value pairs. These specify default values for Milter macros when no value is available from the SMTP session context. - Support to enforce a destination-independent delay between email deliveries. The following example inserts 20 seconds of delay between all deliveries with the SMTP transport, limiting the delivery rate to at most three messages per minute. smtp_transport_rate_delay = 20s - Historically, the default setting "postscreen_dnsbl_ttl = 1h" assumes that a "not found" result from a DNSBL server will be valid for one hour. This may have been adequate five years ago when postscreen was first implemented, but nowadays, that one hour can result in missed opportunities to block new spambots. To address this, postscreen now respects the TTL of DNSBL "not found" replies, as well as the TTL of DNSWL replies (both "found" and "not found"). The TTL for a "not found" reply is determined according to RFC 2308 (the TTL of an SOA record in the reply). Support for DNSBL or DNSWL reply TTL values is controlled by two configuration parameters: postscreen_dnsbl_min_ttl (default: 60 seconds). postscreen_dnsbl_max_ttl (default: $postscreen_dnsbl_ttl or 1 hour) The postscreen_dnsbl_ttl parameter is now obsolete, and has become the default value for the new postscreen_dnsbl_max_ttl parameter. - New "smtpd_client_auth_rate_limit" feature, to enforce an optional rate limit on AUTH commands per SMTP client IP address. Similar to other smtpd_client_*_rate_limit features, this enforces a limit on the number of requests per $anvil_rate_time_unit. - New SMTPD policy service attribute "policy_context", with a corresponding "smtpd_policy_service_policy_context" configuration parameter. Originally, this was implemented to share the same SMTPD policy service endpoint among multiple check_policy_service clients. - A new "postfix tls" command to quickly enable opportunistic TLS in the Postfix SMTP client or server, and to manage SMTP server keys and certificates, including certificate signing requests and TLSA DNS records for DANE.- build with working support for SMTPUTF8- fix build on sle11 by pointing _libexecdir to /usr/lib all the time.- some distros did not pull pkgconfig indirectly. pull it directly.- fix building the dynamic maps: the old build had postgresql e.g. with missing symbols. - convert to AUXLIBS_* instead of plain AUXLIBS which is needed for proper dynamic maps. - reordered the CCARGS and AUXLIBS* lines to group by feature - use pkgconfig or *_config tools where possible - picked up signed char from fedora spec file - enable lmdb support: new BR lmdb-devel, new subpackage postfix-lmdb. - don't delete vmail user/groups- update to 3.1.0 - Since version 3.0 postfix supports dynamic loading of cdb:, ldap:, lmdb:, mysql:, pcre:, pgsql:, sdbm:, and sqlite: database clients. Thats why the patches dynamic_maps.patch and dynamic_maps_pie.patch could be removed. - Adapting all the patches to postfix 3.1.0 - remove obsolete patches * add_missed_library.patch * postfix-opensslconfig.patch - update vda patch * remove postfix-vda-v13-2.10.0.patch * add postfix-vda-v13-3.10.0.patch - The patch postfix-db6.diff is not more neccessary - Backwards-compatibility safety net. With NEW Postfix installs, you MUST install a main.cf file with the setting "compatibility_level = 2". See conf/main.cf for an example. With UPGRADES of existing Postfix systems, you MUST NOT change the main.cf compatibility_level setting, nor add this setting if it does not exist. Several Postfix default settings have changed with Postfix 3.0. To avoid massive frustration with existing Postfix installations, Postfix 3.0 comes with a safety net that forces Postfix to keep running with backwards-compatible main.cf and master.cf default settings. This safety net depends on the main.cf compatibility_level setting (default: 0). Details are in COMPATIBILITY_README. - Major changes - tls * [Feature 20160207] A new "postfix tls" command to quickly enable opportunistic TLS in the Postfix SMTP client or server, and to manage SMTP server keys and certificates, including certificate signing requests and TLSA DNS records for DANE. * As of the middle of 2015, all supported Postfix releases no longer nable "export" grade ciphers for opportunistic TLS, and no longer use the deprecated SSLv2 and SSLv3 protocols for mandatory or opportunistic TLS. * [Incompat 20150719] The default Diffie-Hellman non-export prime was updated from 1024 to 2048 bits, because SMTP clients are starting to reject TLS handshakes with primes smaller than 2048 bits. * [Feature 20160103] The Postfix SMTP client by default enables DANE policies when an MX host has a (DNSSEC) secure TLSA DNS record, even if the MX DNS record was obtained with insecure lookups. The existence of a secure TLSA record implies that the host wants to talk TLS and not plaintext. For details see the smtp_tls_dane_insecure_mx_policy configuration parameter. - Major changes - default settings [Incompat 20141009] The default settings have changed for relay_domains (new: empty, old: $mydestination) and mynetworks_style (new: host, old: subnet). However the backwards-compatibility safety net will prevent these changes from taking effect, giving the system administrator the option to make an old default setting permanent in main.cf or to adopt the new default setting, before turning off backwards compatibility. See COMPATIBILITY_README for details. [Incompat 20141001] A new backwards-compatibility safety net forces Postfix to run with backwards-compatible main.cf and master.cf default settings after an upgrade to a newer but incompatible Postfix version. See COMPATIBILITY_README for details. While the backwards-compatible default settings are in effect, Postfix logs what services or what email would be affected by the incompatible change. Based on this the administrator can make some backwards-compatibility settings permanent in main.cf or master.cf, before turning off backwards compatibility. - Major changes - address verification safety [Feature 20151227] The new address_verify_pending_request_limit parameter introduces a safety limit for the number of address verification probes in the active queue. The default limit is 1/4 of the active queue maximum size. The queue manager enforces the limit by tempfailing probe messages that exceed the limit. This design avoids dependencies on global counters that get out of sync after a process or system crash. Tempfailing verify requests is not as bad as one might think. The Postfix verify cache proactively updates active addresses weeks before they expire. The address_verify_pending_request_limit affects only unknown addresses, and inactive addresses that have expired from the address verify cache (by default, after 31 days). - Major changes - json support [Feature 20151129] Machine-readable, JSON-formatted queue listing with "postqueue -j" (no "mailq" equivalent). The output is a stream of JSON objects, one per queue file. To simplify parsing, each JSON object is formatted as one text line followed by one newline character. See the postqueue(1) manpage for a detailed description of the output format. - Major changes - milter support [Feature 20150523] The milter_macro_defaults feature provides an optional list of macro name=value pairs. These specify default values for Milter macros when no value is available from the SMTP session context. For example, with "milter_macro_defaults = auth_type=TLS", the Postfix SMTP server will send an auth_type of "TLS" to a Milter, unless the remote client authenticates with SASL. This feature was originally implemented for a submission service that may authenticate clients with a TLS certificate, without having to make changes to the code that implements TLS support. - Major changes - output rate control [Feature 20150710] Destination-independent delivery rate delay Support to enforce a destination-independent delay between email deliveries. The following example inserts 20 seconds of delay between all deliveries with the SMTP transport, limiting the delivery rate to at most three messages per minute. /etc/postfix/main.cf: smtp_transport_rate_delay = 20s For details, see the description of default_transport_rate_delay and transport_transport_rate_delay in the postconf(5) manpage. - Major changes - postscreen dnsbl [Feature 20150710] postscreen support for the TTL of DNSBL and DNSWL lookup results Historically, the default setting "postscreen_dnsbl_ttl = 1h" assumes that a "not found" result from a DNSBL server will be valid for one hour. This may have been adequate five years ago when postscreen was first implemented, but nowadays, that one hour can result in missed opportunities to block new spambots. To address this, postscreen now respects the TTL of DNSBL "not found" replies, as well as the TTL of DNSWL replies (both "found" and "not found"). The TTL for a "not found" reply is determined according to RFC 2308 (the TTL of an SOA record in the reply). Support for DNSBL or DNSWL reply TTL values is controlled by two configuration parameters: postscreen_dnsbl_min_ttl (default: 60 seconds). This parameter specifies a minimum for the amount of time that a DNSBL or DNSWL result will be cached in the postscreen_cache_map. This prevents an excessive number of postscreen cache updates when a DNSBL or DNSWL server specifies a very small reply TTL. postscreen_dnsbl_max_ttl (default: $postscreen_dnsbl_ttl or 1 hour) This parameter specifies a maximum for the amount of time that a DNSBL or DNSWL result will be cached in the postscreen_cache_map. This prevents cache pollution when a DNSBL or DNSWL server specifies a very large reply TTL. The postscreen_dnsbl_ttl parameter is now obsolete, and has become the default value for the new postscreen_dnsbl_max_ttl parameter. - Major changes - sasl auth safety [Feature 20151031] New "smtpd_client_auth_rate_limit" feature, to enforce an optional rate limit on AUTH commands per SMTP client IP address. Similar to other smtpd_client_*_rate_limit features, this enforces a limit on the number of requests per $anvil_rate_time_unit. - Major changes - smtpd policy [Feature 20150913] New SMTPD policy service attribute "policy_context", with a corresponding "smtpd_policy_service_policy_context" configuration parameter. Originally, this was implemented to share the same SMTPD policy service endpoint among multiple check_policy_service clients.- bnc#958329 postfix fails to start when openslp is not installed- upstream update postfix 2.11.7: * The Postfix Milter client aborted with a panic while adding a message header, after adding a short message header with the header_checks PREPEND action. Fixed by invoking the header output function while PREPENDing a message header. * False alarms while scanning the Postfix queue. Fixed by resetting errno before calling readdir(). This defect was introduced 19970309. * The postmulti command produced an incorrect error message. * The postmulti command now refuses to create a new MTA instance when the template main.cf or master.cf file are missing. This is a common problem on Debian-like systems. * Turning on Postfix SMTP server HAProxy support broke TLS wrappermode. Fixed by temporarily using a 1-byte VSTREAM buffer to read the HAProxy connection hand-off information. * The xtext_unquote() function did not propagate error reports from xtext_unquote_append(), causing the decoder to return partial output, instead of rejecting malformed input. The Postfix SMTP server uses this function to parse input for the ENVID and ORCPT parameters, and for XFORWARD and XCLIENT command parameters.- boo#934060: Remove quirky hostname logic from config.postfix * /etc/hostname doesn't contain anything useful * linux.local is no good either * postfix will use `hostname`.localdomain as fallback- postfix-no-md5.patch: replace fingerprint defaults by sha1. bsc#928885- %verifyscript is a new section, move it out of the %ifdef so the fillups are run afterwards.- upstream update postfix 2.11.6: Default settings have been updated so that they no longer enable export-grade ciphers, and no longer enable the SSLv2 and SSLv3 protocols. - removed postfix-2.11.5_linux4.patch because it's obsolete - Bugfix (introduced: Postfix 2.11): with connection caching enabled (the default), recipients could be given to the wrong mail server. (bsc#944722)- postfix-SuSE.tar.gz/postfix.service: None of nss-lookup.target network.target local-fs.target time-sync.target should be Wanted or Required except by the services the implement the relevant functionality i.e network.target is wanted/required by networkmanager, wicked, systemd-network. other software must be ordered After them, see systemd.special(7)- Fix library symlink generation (boo#928662)- added postfix-2.11.5_linux4.patch: Allow building on kernel 4. Patch taken from: https://groups.google.com/forum/#!topic/mailing.postfix.users/fufS22sMGWY- update to postfix 2.11.5 - Bugfix (introduced: Postfix 2.6): sender_dependent_relayhost_maps ignored the relayhost setting in the case of a DUNNO lookup result. It would use the recipient domain instead. Viktor Dukhovni. Wietse took the pieces of code that enforce the precedence of a sender-dependent relayhost, the global relayhost, and the recipient domain, and put that code together in once place so that it is easier to maintain. File: trivial-rewrite/resolve.c. - Bitrot: prepare for future changes in OpenSSL API. Viktor Dukhovni. File: tls_dane.c. - Incompatibility: specifying "make makefiles" with "CC=command" will no longer override the default WARN setting.- upstream update postfix 2.11.4: Postfix 2.11.4 only: * Fix a core dump when smtp_policy_maps specifies an invalid TLS level. * Fix a missing " in \%s\", in postconf(1) fatal error messages, which violated the C language spec. Reported by Iain Hibbert. All supported releases: * Stop excessive recursion in the cleanup server while recovering from a virtual alias expansion loop. Problem found at Two Sigma. * Stop exponential memory allocation with virtual alias expansion loops. This came to light after fixing the previous problem.- correct pf_daemon_directory in spec. This must be /usr/lib/- bnc#914086 syntax error in config.postfix - Adapt config.postfix to be able to run on SLE11 too.- Don't install sysvinit script when systemd is used - Make explicit PreReq dependencies conditional only for older systems - Don't try to set explicit attributes to symlinks - Cleanup spec file vith spec-cleaner- bnc#912594 config.postfix creates config based on old options- bnc#911806 config.postfix does not set up correct saslauthd socket directory for chroot - bnc#910265 config.postfix does not upgrade the chroot - bnc#908003 wrong access rights on /usr/sbin/postdrop causes permission denied when trying to send a mail as non root user - bnc#729154 wrong permissions for some postfix components- Remove keyring and things as it is md5 based one no longer accepted by gpg 2.1- No longer perform gpg validation; osc source_validator does it implicit: + Drop gpg-offline BuildRequires. + No longer execute gpg_verify.- restore previously lost fix: Fri Oct 11 13:32:32 UTC 2013 - matz@suse.de - Ignore errors in %pre/%post.- postfix 2.11.3: * Fix for configurations that prepend message headers with Postfix access maps, policy servers or Milter applications. Postfix now hides its own Received: header from Milters and exposes prepended headers to Milters, regardless of the mechanism used to prepend a header. This fix reverts a partial solution that was released on October 13, 2014, and replaces it with a complete solution. * Portability fix for MacOS X 10.7.x (Darwin 11.x) build procedure. - postfix 2.11.2: * Fix for DMARC implementations based on SPF policy plus DKIM Milter. The PREPEND access/policy action added headers ABOVE Postfix's own Received: header, exposing Postfix's own Received: header to Milters (protocol violation) and hiding the PREPENDed header from Milters. PREPENDed headers are now added BELOW Postfix's own Received: header and remain visible to Milters. * The Postfix SMTP server logged an incorrect client name in reject messages for check_reverse_client_hostname_access and check_reverse_client_hostname_{mx,ns}_access. They replied with the verified client name, instead of the name that was rejected. * The qmqpd daemon crashed with null pointer bug when logging a lost connection while not in a mail transaction.h01-ch3a 1714723124  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~3.7.3-150500.3.14.3 postfix-docREADME_FILESAAAREADMEADDRESS_CLASS_READMEADDRESS_REWRITING_READMEADDRESS_VERIFICATION_READMEBACKSCATTER_READMEBASIC_CONFIGURATION_READMEBDAT_READMEBUILTIN_FILTER_READMECDB_READMECOMPATIBILITY_READMECONNECTION_CACHE_READMECONTENT_INSPECTION_READMEDATABASE_READMEDB_READMEDEBUG_READMEDSN_READMEETRN_READMEFILTER_READMEFORWARD_SECRECY_READMEIPV6_READMELDAP_READMELINUX_READMELMDB_READMELOCAL_RECIPIENT_READMEMAILDROP_READMEMAILLOG_READMEMEMCACHE_READMEMILTER_READMEMULTI_INSTANCE_READMEMYSQL_READMENFS_READMEOVERVIEWPACKAGE_READMEPCRE_READMEPGSQL_READMEPOSTSCREEN_3_5_READMEPOSTSCREEN_READMEQSHAPE_READMERELEASE_NOTESRESTRICTION_CLASS_READMESASL_READMESCHEDULER_READMESMTPD_ACCESS_READMESMTPD_POLICY_READMESMTPD_PROXY_READMESMTPUTF8_READMESOHO_READMESQLITE_READMESTANDARD_CONFIGURATION_READMESTRESS_READMETLS_LEGACY_READMETLS_READMETUNING_READMEULTRIX_READMEUUCP_READMEVERP_READMEVIRTUAL_READMEXCLIENT_READMEXFORWARD_READMEauxiliarycollateREADMEREADME.tlstypecollate.pltlstype.plname-addr-testgetaddrinfo.cgethostbyaddr.cgethostbyname.cgetnameinfo.cqshapeqshape.plrmailrmailhtmlADDRESS_CLASS_README.htmlADDRESS_REWRITING_README.htmlADDRESS_VERIFICATION_README.htmlBACKSCATTER_README.htmlBASIC_CONFIGURATION_README.htmlBDAT_README.htmlBUILTIN_FILTER_README.htmlCDB_README.htmlCOMPATIBILITY_README.htmlCONNECTION_CACHE_README.htmlCONTENT_INSPECTION_README.htmlDATABASE_README.htmlDB_README.htmlDEBUG_README.htmlDSN_README.htmlETRN_README.htmlFILTER_README.htmlFORWARD_SECRECY_README.htmlINSTALL.htmlIPV6_README.htmlLDAP_README.htmlLINUX_README.htmlLMDB_README.htmlLOCAL_RECIPIENT_README.htmlMAILDROP_README.htmlMAILLOG_README.htmlMEMCACHE_README.htmlMILTER_README.htmlMULTI_INSTANCE_README.htmlMYSQL_README.htmlMakefile.inNFS_README.htmlOVERVIEW.htmlPACKAGE_README.htmlPCRE_README.htmlPGSQL_README.htmlPOSTSCREEN_3_5_README.htmlPOSTSCREEN_README.htmlQSHAPE_README.htmlRESTRICTION_CLASS_README.htmlSASL_README.htmlSCHEDULER_README.htmlSMTPD_ACCESS_README.htmlSMTPD_POLICY_README.htmlSMTPD_PROXY_README.htmlSMTPUTF8_README.htmlSOHO_README.htmlSQLITE_README.htmlSTANDARD_CONFIGURATION_README.htmlSTRESS_README.htmlTLS_LEGACY_README.htmlTLS_README.htmlTUNING_README.htmlUUCP_README.htmlVERP_README.htmlVIRTUAL_README.htmlXCLIENT_README.htmlXFORWARD_README.htmlaccess.5.htmlaliases.5.htmlanvil.8.htmlbounce.5.htmlbounce.8.htmlcanonical.5.htmlcidr_table.5.htmlcleanup.8.htmldefer.8.htmldiscard.8.htmldnsblog.8.htmlerror.8.htmlflush.8.htmlgeneric.5.htmlheader_checks.5.htmlindex.htmlldap_table.5.htmllmdb_table.5.htmllmtp.8.htmllocal.8.htmlmailq.1.htmlmakedefs.1.htmlmaster.5.htmlmaster.8.htmlmemcache_table.5.htmlmysql_table.5.htmlnewaliases.1.htmlnisplus_table.5.htmloqmgr.8.htmlpcre_table.5.htmlpgsql_table.5.htmlpickup.8.htmlpipe.8.htmlpostalias.1.htmlpostcat.1.htmlpostconf.1.htmlpostconf.5.htmlpostdrop.1.htmlpostfix-logo.jpgpostfix-manuals.htmlpostfix-power.pngpostfix-tls.1.htmlpostfix-wrapper.5.htmlpostfix.1.htmlpostkick.1.htmlpostlock.1.htmlpostlog.1.htmlpostlogd.8.htmlpostmap.1.htmlpostmulti.1.htmlpostqueue.1.htmlpostscreen.8.htmlpostsuper.1.htmlposttls-finger.1.htmlproxymap.8.htmlqmgr.8.htmlqmqp-sink.1.htmlqmqp-source.1.htmlqmqpd.8.htmlqshape.1.htmlregexp_table.5.htmlrelocated.5.htmlscache.8.htmlsendmail.1.htmlshowq.8.htmlsmtp-sink.1.htmlsmtp-source.1.htmlsmtp.8.htmlsmtpd.8.htmlsocketmap_table.5.htmlspawn.8.htmlsqlite_table.5.htmltcp_table.5.htmltlsmgr.8.htmltlsproxy.8.htmltrace.8.htmltransport.5.htmltrivial-rewrite.8.htmlverify.8.htmlvirtual.5.htmlvirtual.8.htmlsampleschroot-setupLINUX2qmail-localqmail-local.txtsmtpd-policyREADME.SPFgreylist.pl/usr/share/doc/packages//usr/share/doc/packages/postfix-doc//usr/share/doc/packages/postfix-doc/README_FILES//usr/share/doc/packages/postfix-doc/auxiliary//usr/share/doc/packages/postfix-doc/auxiliary/collate//usr/share/doc/packages/postfix-doc/auxiliary/name-addr-test//usr/share/doc/packages/postfix-doc/auxiliary/qshape//usr/share/doc/packages/postfix-doc/auxiliary/rmail//usr/share/doc/packages/postfix-doc/html//usr/share/doc/packages/postfix-doc/samples//usr/share/doc/packages/postfix-doc/samples/chroot-setup//usr/share/doc/packages/postfix-doc/samples/qmail-local//usr/share/doc/packages/postfix-doc/samples/smtpd-policy/-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -gobs://build.suse.de/SUSE:Maintenance:33621/SUSE_SLE-15-SP5_Update/50414ae133915cedabe02c56174f052e-postfix.SUSE_SLE-15-SP5_Updatedrpmxz5x86_64-suse-linux     directoryASCII text, with overstrikingUTF-8 Unicode text, with overstrikingASCII textPerl script text executableC source, ASCII textPOSIX shell script, ASCII text executableHTML document, ASCII textHTML document, UTF-8 Unicode textHTML document, ASCII text, with very long linesJPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, comment: "CREATOR: XV Version 3.10a Rev: 12/29/94 (jp-extension 5.3.3 + PNG patch 1.2d) Quality = 75, S", baseline, precision 8, 204x98, frames 3PNG image data, 88 x 31, 8-bit/color RGB, non-interlacednews or mail, ASCII textDGv^ =utf-86c71eaff083ba3c6a720e60e7580de7d783b88f26243216b581f92dc98a1afc3?P7zXZ !t/ :]"k%IŇ/΄<:\co;"k7+VZ%'jMYL~%,+缈WzWڟ16B~ڳ8Ʊ%ř z/fxD7TIQ 3릏Xrtsذmc])- rds(dʎ0+0( 0}c##H2C1ak%Vz$O'C6)~ eSOH!{C?,|^phgr3yȐ%vj_ג76O؋ބ35Y+rLQ1ZQC`kYwE~04W@nM/z/#&Mfu.ݾ2!~(RQ1|s8 _߰c̋5ȦY9Pר^e5pY.-}EyzzT=4Z[%]ۮOؙ": YX4Cg8x66ȲsAxbs-i]Fh@^mћkBڇB fr]m$IeMu9 ͌ED)*FG]R~z4ZVlwa*t0_Q"#Ӱ)؊Ǧ7ؔ]O}aeĥ'6a[K_G/_`~jtL{X(gj4]2պ7Zl:Hѱ3q ̹C*swfN94X4GmcyBVP NNN̟ d 14NXPaq'xqفό- ;OWA9@ve:HzAwݳ9W|Qģ&Ş͝f6>lņX@%[T˔ó;|k=b2Č@o9KЙ>N_3"] 'uHv jHg %A4ʗ8ψ2.@:Ma̎}1Q?c+ҕͣPY6(",r,4I$B쮡gT#m/UP!|7|z6iD|SCDS?[s ?5ecwa_^|1mT0*UYM3 RϿN"%N @cJM'*'Qm{FXup|8q.ẎNcll{-e]y5@0UxD&7'( C~؝`щZn(#y{s3) cWn 7Qtȡ} m|g@@Lk㒣%o*]3`Dj̽ >G%M).=q<оmW9” $dƔ_e=,>[,JeJ"n{TcxbZo6lE×uh!8rn L&JEݲ7#HXqY~C{{NF~bªKZ 7h\AK~b!<*%nKLa`% QǭLSOMu2,W`^iHG`Ӝ5h؈\-u TIm[ -LkYJLZ0g?#T#!GƤƨn7 uX )zç딭 MᐱmKő̚7hRooֶmoʂqoz 92)Q㳕W{-=Jss}:_K;ҩƓout$ cTCհ'7.}QklYp=8>CôdowҨƭɕdݢTqg蹝pFI§mVX)\J<6^̡ JۥzZ}6h+G$E;Xth\N[72<;=9%B ᥾O0pyv!q/7A