Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
2826 connectés 

  FORUM HardWare.fr
  Linux et OS Alternatifs
  réseaux et sécurité

  [RESOLU] [POSTFIX] probleme de configuration

 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

[RESOLU] [POSTFIX] probleme de configuration

n°1040355
mozvillat
Posté le 07-05-2008 à 12:36:34  profilanswer
 

Bonjour à tous.
 
Nous venons d'installer un serveur web (pache, mysql,...) sur une fedora.
L'une de nos application web utilise la fonction mail de php afin d'envoyer des informations.
 
Pour ce faire, nous avons installé postfix sur le serveur, sachant que ce serveur doit juste relayer les messages vers notre serveur principal (sme-server).
 
Lors de l'utilisation de l'appli, aucune erreur n'est retournée, mais l'envoi ne se fait pas non plus !
 
De plus si je lance postfix (/etc/init.d/postfix start) le demarrage indique ok mais si je verifie son etat avec /etc/init.d/postfix status, il m'indique que master est arrete.
 
avant de poster la conf de postfix (main.cf), quelqu'un aurait il deja rencontré le probleme de lancement de postfix ?
 
merci d'avance pour vos reponses.


Message édité par mozvillat le 09-05-2008 à 08:32:24
mood
Publicité
Posté le 07-05-2008 à 12:36:34  profilanswer
 

n°1040363
toniotonio
Posté le 07-05-2008 à 12:44:51  profilanswer
 

postconf -n  
le master.cf
et les logs
 
merci


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°1040365
mozvillat
Posté le 07-05-2008 à 12:52:05  profilanswer
 

lorsque je saisi postconf -n il m'indique bash : command not found
 
j'ai du oublié de faire quelque chose (suis une buse sous linux)...
 
Sinon le main.cf
 

Code :
  1. # Global Postfix configuration file. This file lists only a subset
  2. # of all parameters. For the syntax, and for a complete parameter
  3. # list, see the postconf(5) manual page (command: "man 5 postconf" ).
  4. #
  5. # For common configuration examples, see BASIC_CONFIGURATION_README
  6. # and STANDARD_CONFIGURATION_README. To find these documents, use
  7. # the command "postconf html_directory readme_directory", or go to
  8. # http://www.postfix.org/.
  9. #
  10. # For best results, change no more than 2-3 parameters at a time,
  11. # and test if Postfix still works after every change.
  12. # SOFT BOUNCE
  13. #
  14. # The soft_bounce parameter provides a limited safety net for
  15. # testing.  When soft_bounce is enabled, mail will remain queued that
  16. # would otherwise bounce. This parameter disables locally-generated
  17. # bounces, and prevents the SMTP server from rejecting mail permanently
  18. # (by changing 5xx replies into 4xx replies). However, soft_bounce
  19. # is no cure for address rewriting mistakes or mail routing mistakes.
  20. #
  21. #soft_bounce = no
  22. # LOCAL PATHNAME INFORMATION
  23. #
  24. # The queue_directory specifies the location of the Postfix queue.
  25. # This is also the root directory of Postfix daemons that run chrooted.
  26. # See the files in examples/chroot-setup for setting up Postfix chroot
  27. # environments on different UNIX systems.
  28. #
  29. # The command_directory parameter specifies the location of all
  30. # postXXX commands.
  31. #
  32. command_directory = /usr/sbin
  33. # The daemon_directory parameter specifies the location of all Postfix
  34. # daemon programs (i.e. programs listed in the master.cf file). This
  35. # directory must be owned by root.
  36. #
  37. daemon_directory = /usr/libexec/postfix
  38. # QUEUE AND PROCESS OWNERSHIP
  39. #
  40. # The mail_owner parameter specifies the owner of the Postfix queue
  41. # and of most Postfix daemon processes.  Specify the name of a user
  42. # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
  43. # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
  44. # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
  45. # USER.
  46. #
  47. # The default_privs parameter specifies the default rights used by
  48. # the local delivery agent for delivery to external file or command.
  49. # These rights are used in the absence of a recipient user context.
  50. # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
  51. #
  52. #default_privs = nobody
  53. # INTERNET HOST AND DOMAIN NAMES
  54. #
  55. # The myhostname parameter specifies the internet hostname of this
  56. # mail system. The default is to use the fully-qualified domain name
  57. # from gethostname(). $myhostname is used as a default value for many
  58. # other configuration parameters.
  59. #
  60. myhostname = logement.ville-sallaumines.fr
  61. #myhostname = virtual.domain.tld
  62. # The mydomain parameter specifies the local internet domain name.
  63. # The default is to use $myhostname minus the first component.
  64. # $mydomain is used as a default value for many other configuration
  65. # parameters.
  66. #
  67. mydomain = ville-sallaumines.fr
  68. # SENDING MAIL
  69. #
  70. # The myorigin parameter specifies the domain that locally-posted
  71. # mail appears to come from. The default is to append $myhostname,
  72. # which is fine for small sites.  If you run a domain with multiple
  73. # machines, you should (1) change this to $mydomain and (2) set up
  74. # a domain-wide alias database that aliases each user to
  75. # user@that.users.mailhost.
  76. #
  77. # For the sake of consistency between sender and recipient addresses,
  78. # myorigin also specifies the default domain name that is appended
  79. # to recipient addresses that have no @domain part.
  80. #
  81. #myorigin = $myhostname
  82. #myorigin = $mydomain
  83. # RECEIVING MAIL
  84. # The inet_interfaces parameter specifies the network interface
  85. # addresses that this mail system receives mail on.  By default,
  86. # the software claims all active interfaces on the machine. The
  87. # parameter also controls delivery of mail to user@[ip.address].
  88. #
  89. # See also the proxy_interfaces parameter, for network addresses that
  90. # are forwarded to us via a proxy or network address translator.
  91. #
  92. # Note: you need to stop/start Postfix when this parameter changes.
  93. #
  94. #inet_interfaces = all
  95. #inet_interfaces = $myhostname
  96. #inet_interfaces = $myhostname, localhost
  97. inet_interfaces = localhost
  98. # The proxy_interfaces parameter specifies the network interface
  99. # addresses that this mail system receives mail on by way of a
  100. # proxy or network address translation unit. This setting extends
  101. # the address list specified with the inet_interfaces parameter.
  102. #
  103. # You must specify your proxy/NAT addresses when your system is a
  104. # backup MX host for other domains, otherwise mail delivery loops
  105. # will happen when the primary MX host is down.
  106. #
  107. #proxy_interfaces =
  108. #proxy_interfaces = 1.2.3.4
  109. # The mydestination parameter specifies the list of domains that this
  110. # machine considers itself the final destination for.
  111. #
  112. # These domains are routed to the delivery agent specified with the
  113. # local_transport parameter setting. By default, that is the UNIX
  114. # compatible delivery agent that lookups all recipients in /etc/passwd
  115. # and /etc/aliases or their equivalent.
  116. #
  117. # The default is $myhostname + localhost.$mydomain.  On a mail domain
  118. # gateway, you should also include $mydomain.
  119. #
  120. # Do not specify the names of virtual domains - those domains are
  121. # specified elsewhere (see VIRTUAL_README).
  122. #
  123. # Do not specify the names of domains that this machine is backup MX
  124. # host for. Specify those names via the relay_domains settings for
  125. # the SMTP server, or use permit_mx_backup if you are lazy (see
  126. # STANDARD_CONFIGURATION_README).
  127. #
  128. # The local machine is always the final destination for mail addressed
  129. # to user@[the.net.work.address] of an interface that the mail system
  130. # receives mail on (see the inet_interfaces parameter).
  131. #
  132. # Specify a list of host or domain names, /file/name or type:table
  133. # patterns, separated by commas and/or whitespace. A /file/name
  134. # pattern is replaced by its contents; a type:table is matched when
  135. # a name matches a lookup key (the right-hand side is ignored).
  136. # Continue long lines by starting the next line with whitespace.
  137. #
  138. # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
  139. #
  140. #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
  141. #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
  142. # mail.$mydomain, www.$mydomain, ftp.$mydomain
  143. # REJECTING MAIL FOR UNKNOWN LOCAL USERS
  144. #
  145. # The local_recipient_maps parameter specifies optional lookup tables
  146. # with all names or addresses of users that are local with respect
  147. # to $mydestination, $inet_interfaces or $proxy_interfaces.
  148. #
  149. # If this parameter is defined, then the SMTP server will reject
  150. # mail for unknown local users. This parameter is defined by default.
  151. #
  152. # To turn off local recipient checking in the SMTP server, specify
  153. # local_recipient_maps = (i.e. empty).
  154. #
  155. # The default setting assumes that you use the default Postfix local
  156. # delivery agent for local delivery. You need to update the
  157. # local_recipient_maps setting if:
  158. #
  159. # - You define $mydestination domain recipients in files other than
  160. #   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
  161. #   For example, you define $mydestination domain recipients in   
  162. #   the $virtual_mailbox_maps files.
  163. #
  164. # - You redefine the local delivery agent in master.cf.
  165. #
  166. # - You redefine the "local_transport" setting in main.cf.
  167. #
  168. # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
  169. #   feature of the Postfix local delivery agent (see local(8)).
  170. #
  171. # Details are described in the LOCAL_RECIPIENT_README file.
  172. #
  173. # Beware: if the Postfix SMTP server runs chrooted, you probably have
  174. # to access the passwd file via the proxymap service, in order to
  175. # overcome chroot restrictions. The alternative, having a copy of
  176. # the system passwd file in the chroot jail is just not practical.
  177. #
  178. # The right-hand side of the lookup tables is conveniently ignored.
  179. # In the left-hand side, specify a bare username, an @domain.tld
  180. # wild-card, or specify a user@domain.tld address.
  181. #
  182. #local_recipient_maps = unix:passwd.byname $alias_maps
  183. #local_recipient_maps = proxy:unix:passwd.byname $alias_maps
  184. #local_recipient_maps =
  185. # The unknown_local_recipient_reject_code specifies the SMTP server
  186. # response code when a recipient domain matches $mydestination or
  187. # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
  188. # and the recipient address or address local-part is not found.
  189. #
  190. # The default setting is 550 (reject mail) but it is safer to start
  191. # with 450 (try again later) until you are certain that your
  192. # local_recipient_maps settings are OK.
  193. #
  194. unknown_local_recipient_reject_code = 550
  195. # TRUST AND RELAY CONTROL
  196. # The mynetworks parameter specifies the list of "trusted" SMTP
  197. # clients that have more privileges than "strangers".
  198. #
  199. # In particular, "trusted" SMTP clients are allowed to relay mail
  200. # through Postfix.  See the smtpd_recipient_restrictions parameter
  201. # in postconf(5).
  202. #
  203. # You can specify the list of "trusted" network addresses by hand
  204. # or you can let Postfix do it for you (which is the default).
  205. #
  206. # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
  207. # clients in the same IP subnetworks as the local machine.
  208. # On Linux, this does works correctly only with interfaces specified
  209. # with the "ifconfig" command.
  210. #
  211. # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
  212. # clients in the same IP class A/B/C networks as the local machine.
  213. # Don't do this with a dialup site - it would cause Postfix to "trust"
  214. # your entire provider's network.  Instead, specify an explicit
  215. # mynetworks list by hand, as described below.
  216. # Specify "mynetworks_style = host" when Postfix should "trust"
  217. # only the local machine.
  218. #
  219. #mynetworks_style = class
  220. #mynetworks_style = subnet
  221. #mynetworks_style = host
  222. # Alternatively, you can specify the mynetworks list by hand, in
  223. # which case Postfix ignores the mynetworks_style setting.
  224. #
  225. # Specify an explicit list of network/netmask patterns, where the
  226. # mask specifies the number of bits in the network part of a host
  227. # address.
  228. #
  229. # You can also specify the absolute pathname of a pattern file instead
  230. # of listing the patterns here. Specify type:table for table-based lookups
  231. # (the value on the table right-hand side is not used).
  232. #
  233. #mynetworks = 168.100.189.0/28, 127.0.0.0/8
  234. #mynetworks = $config_directory/mynetworks
  235. #mynetworks = hash:/etc/postfix/network_table
  236. # The relay_domains parameter restricts what destinations this system will
  237. # relay mail to.  See the smtpd_recipient_restrictions description in
  238. # postconf(5) for detailed information.
  239. #
  240. # By default, Postfix relays mail
  241. # - from "trusted" clients (IP address matches $mynetworks) to any destination,
  242. # - from "untrusted" clients to destinations that match $relay_domains or
  243. #   subdomains thereof, except addresses with sender-specified routing.
  244. # The default relay_domains value is $mydestination.
  245. #
  246. # In addition to the above, the Postfix SMTP server by default accepts mail
  247. # that Postfix is final destination for:
  248. # - destinations that match $inet_interfaces or $proxy_interfaces,
  249. # - destinations that match $mydestination
  250. # - destinations that match $virtual_alias_domains,
  251. # - destinations that match $virtual_mailbox_domains.
  252. # These destinations do not need to be listed in $relay_domains.
  253. #
  254. # Specify a list of hosts or domains, /file/name patterns or type:name
  255. # lookup tables, separated by commas and/or whitespace.  Continue
  256. # long lines by starting the next line with whitespace. A file name
  257. # is replaced by its contents; a type:name table is matched when a
  258. # (parent) domain appears as lookup key.
  259. #
  260. # NOTE: Postfix will not automatically forward mail for domains that
  261. # list this system as their primary or backup MX host. See the
  262. # permit_mx_backup restriction description in postconf(5).
  263. #
  264. #relay_domains = $mydestination
  265. # INTERNET OR INTRANET
  266. # The relayhost parameter specifies the default host to send mail to
  267. # when no entry is matched in the optional transport(5) table. When
  268. # no relayhost is given, mail is routed directly to the destination.
  269. #
  270. # On an intranet, specify the organizational domain name. If your
  271. # internal DNS uses no MX records, specify the name of the intranet
  272. # gateway host instead.
  273. #
  274. # In the case of SMTP, specify a domain, host, host:port, [host]:port,
  275. # [address] or [address]:port; the form [host] turns off MX lookups.
  276. #
  277. # If you're connected via UUCP, see also the default_transport parameter.
  278. #
  279. #relayhost = $mydomain
  280. #relayhost = [gateway.my.domain]
  281. #relayhost = [mailserver.isp.tld]
  282. #relayhost = uucphost
  283. #relayhost = [an.ip.add.ress]
  284. # REJECTING UNKNOWN RELAY USERS
  285. #
  286. # The relay_recipient_maps parameter specifies optional lookup tables
  287. # with all addresses in the domains that match $relay_domains.
  288. #
  289. # If this parameter is defined, then the SMTP server will reject
  290. # mail for unknown relay users. This feature is off by default.
  291. #
  292. # The right-hand side of the lookup tables is conveniently ignored.
  293. # In the left-hand side, specify an @domain.tld wild-card, or specify
  294. # a user@domain.tld address.
  295. #
  296. #relay_recipient_maps = hash:/etc/postfix/relay_recipients
  297. # INPUT RATE CONTROL
  298. #
  299. # The in_flow_delay configuration parameter implements mail input
  300. # flow control. This feature is turned on by default, although it
  301. # still needs further development (it's disabled on SCO UNIX due
  302. # to an SCO bug).
  303. #
  304. # A Postfix process will pause for $in_flow_delay seconds before
  305. # accepting a new message, when the message arrival rate exceeds the
  306. # message delivery rate. With the default 100 SMTP server process
  307. # limit, this limits the mail inflow to 100 messages a second more
  308. # than the number of messages delivered per second.
  309. #
  310. # Specify 0 to disable the feature. Valid delays are 0..10.
  311. #
  312. #in_flow_delay = 1s
  313. # ADDRESS REWRITING
  314. #
  315. # The ADDRESS_REWRITING_README document gives information about
  316. # address masquerading or other forms of address rewriting including
  317. # username->Firstname.Lastname mapping.
  318. # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
  319. #
  320. # The VIRTUAL_README document gives information about the many forms
  321. # of domain hosting that Postfix supports.
  322. # "USER HAS MOVED" BOUNCE MESSAGES
  323. #
  324. # See the discussion in the ADDRESS_REWRITING_README document.
  325. # TRANSPORT MAP
  326. #
  327. # See the discussion in the ADDRESS_REWRITING_README document.
  328. # ALIAS DATABASE
  329. #
  330. # The alias_maps parameter specifies the list of alias databases used
  331. # by the local delivery agent. The default list is system dependent.
  332. #
  333. # On systems with NIS, the default is to search the local alias
  334. # database, then the NIS alias database. See aliases(5) for syntax
  335. # details.
  336. #
  337. # If you change the alias database, run "postalias /etc/aliases" (or
  338. # wherever your system stores the mail alias file), or simply run
  339. # "newaliases" to build the necessary DBM or DB file.
  340. #
  341. # It will take a minute or so before changes become visible.  Use
  342. # "postfix reload" to eliminate the delay.
  343. #
  344. #alias_maps = dbm:/etc/aliases
  345. alias_maps = hash:/etc/aliases
  346. #alias_maps = hash:/etc/aliases, nis:mail.aliases
  347. #alias_maps = netinfo:/aliases
  348. # The alias_database parameter specifies the alias database(s) that
  349. # are built with "newaliases" or "sendmail -bi".  This is a separate
  350. # configuration parameter, because alias_maps (see above) may specify
  351. # tables that are not necessarily all under control by Postfix.
  352. #
  353. #alias_database = dbm:/etc/aliases
  354. #alias_database = dbm:/etc/mail/aliases
  355. alias_database = hash:/etc/aliases
  356. #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
  357. # ADDRESS EXTENSIONS (e.g., user+foo)
  358. #
  359. # The recipient_delimiter parameter specifies the separator between
  360. # user names and address extensions (user+foo). See canonical(5),
  361. # local(8), relocated(5) and virtual(5) for the effects this has on
  362. # aliases, canonical, virtual, relocated and .forward file lookups.
  363. # Basically, the software tries user+foo and .forward+foo before
  364. # trying user and .forward.
  365. #
  366. #recipient_delimiter = +
  367. # DELIVERY TO MAILBOX
  368. #
  369. # The home_mailbox parameter specifies the optional pathname of a
  370. # mailbox file relative to a user's home directory. The default
  371. # mailbox file is /var/spool/mail/user or /var/mail/user.  Specify
  372. # "Maildir/" for qmail-style delivery (the / is required).
  373. #
  374. #home_mailbox = Mailbox
  375. #home_mailbox = Maildir/
  376. # The mail_spool_directory parameter specifies the directory where
  377. # UNIX-style mailboxes are kept. The default setting depends on the
  378. # system type.
  379. #
  380. #mail_spool_directory = /var/mail
  381. #mail_spool_directory = /var/spool/mail
  382. # The mailbox_command parameter specifies the optional external
  383. # command to use instead of mailbox delivery. The command is run as
  384. # the recipient with proper HOME, SHELL and LOGNAME environment settings.
  385. # Exception:  delivery for root is done as $default_user.
  386. #
  387. # Other environment variables of interest: USER (recipient username),
  388. # EXTENSION (address extension), DOMAIN (domain part of address),
  389. # and LOCAL (the address localpart).
  390. #
  391. # Unlike other Postfix configuration parameters, the mailbox_command
  392. # parameter is not subjected to $parameter substitutions. This is to
  393. # make it easier to specify shell syntax (see example below).
  394. #
  395. # Avoid shell meta characters because they will force Postfix to run
  396. # an expensive shell process. Procmail alone is expensive enough.
  397. #
  398. # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
  399. # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
  400. #
  401. #mailbox_command = /some/where/procmail
  402. #mailbox_command = /some/where/procmail -a "$EXTENSION"
  403. # The mailbox_transport specifies the optional transport in master.cf
  404. # to use after processing aliases and .forward files. This parameter
  405. # has precedence over the mailbox_command, fallback_transport and
  406. # luser_relay parameters.
  407. #
  408. # Specify a string of the form transport:nexthop, where transport is
  409. # the name of a mail delivery transport defined in master.cf.  The
  410. # :nexthop part is optional. For more details see the sample transport
  411. # configuration file.
  412. #
  413. # NOTE: if you use this feature for accounts not in the UNIX password
  414. # file, then you must update the "local_recipient_maps" setting in
  415. # the main.cf file, otherwise the SMTP server will reject mail for   
  416. # non-UNIX accounts with "User unknown in local recipient table".
  417. #
  418. #mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
  419. # If using the cyrus-imapd IMAP server deliver local mail to the IMAP
  420. # server using LMTP (Local Mail Transport Protocol), this is prefered
  421. # over the older cyrus deliver program by setting the
  422. # mailbox_transport as below:
  423. #
  424. # mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
  425. #
  426. # The efficiency of LMTP delivery for cyrus-imapd can be enhanced via
  427. # these settings.
  428. #
  429. # local_destination_recipient_limit = 300
  430. # local_destination_concurrency_limit = 5
  431. #
  432. # Of course you should adjust these settings as appropriate for the
  433. # capacity of the hardware you are using. The recipient limit setting
  434. # can be used to take advantage of the single instance message store
  435. # capability of Cyrus. The concurrency limit can be used to control
  436. # how many simultaneous LMTP sessions will be permitted to the Cyrus
  437. # message store.
  438. #
  439. # To use the old cyrus deliver program you have to set:
  440. #mailbox_transport = cyrus
  441. # The fallback_transport specifies the optional transport in master.cf
  442. # to use for recipients that are not found in the UNIX passwd database.
  443. # This parameter has precedence over the luser_relay parameter.
  444. #
  445. # Specify a string of the form transport:nexthop, where transport is
  446. # the name of a mail delivery transport defined in master.cf.  The
  447. # :nexthop part is optional. For more details see the sample transport
  448. # configuration file.
  449. #
  450. # NOTE: if you use this feature for accounts not in the UNIX password
  451. # file, then you must update the "local_recipient_maps" setting in
  452. # the main.cf file, otherwise the SMTP server will reject mail for   
  453. # non-UNIX accounts with "User unknown in local recipient table".
  454. #
  455. #fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp
  456. #fallback_transport =
  457. # The luser_relay parameter specifies an optional destination address
  458. # for unknown recipients.  By default, mail for unknown@$mydestination,
  459. # unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
  460. # as undeliverable.
  461. #
  462. # The following expansions are done on luser_relay: $user (recipient
  463. # username), $shell (recipient shell), $home (recipient home directory),
  464. # $recipient (full recipient address), $extension (recipient address
  465. # extension), $domain (recipient domain), $local (entire recipient
  466. # localpart), $recipient_delimiter. Specify ${name?value} or
  467. # ${name:value} to expand value only when $name does (does not) exist.
  468. #
  469. # luser_relay works only for the default Postfix local delivery agent.
  470. #
  471. # NOTE: if you use this feature for accounts not in the UNIX password
  472. # file, then you must specify "local_recipient_maps =" (i.e. empty) in
  473. # the main.cf file, otherwise the SMTP server will reject mail for   
  474. # non-UNIX accounts with "User unknown in local recipient table".
  475. #
  476. #luser_relay = $user@other.host
  477. #luser_relay = $local@other.host
  478. #luser_relay = admin+$local
  479.  
  480. # JUNK MAIL CONTROLS
  481. #
  482. # The controls listed here are only a very small subset. The file
  483. # SMTPD_ACCESS_README provides an overview.
  484. # The header_checks parameter specifies an optional table with patterns
  485. # that each logical message header is matched against, including
  486. # headers that span multiple physical lines.
  487. #
  488. # By default, these patterns also apply to MIME headers and to the
  489. # headers of attached messages. With older Postfix versions, MIME and
  490. # attached message headers were treated as body text.
  491. #
  492. # For details, see "man header_checks".
  493. #
  494. #header_checks = regexp:/etc/postfix/header_checks
  495. # FAST ETRN SERVICE
  496. #
  497. # Postfix maintains per-destination logfiles with information about
  498. # deferred mail, so that mail can be flushed quickly with the SMTP
  499. # "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
  500. # See the ETRN_README document for a detailed description.
  501. #
  502. # The fast_flush_domains parameter controls what destinations are
  503. # eligible for this service. By default, they are all domains that
  504. # this server is willing to relay mail to.
  505. #
  506. #fast_flush_domains = $relay_domains
  507. # SHOW SOFTWARE VERSION OR NOT
  508. #
  509. # The smtpd_banner parameter specifies the text that follows the 220
  510. # code in the SMTP server's greeting banner. Some people like to see
  511. # the mail version advertised. By default, Postfix shows no version.
  512. #
  513. # You MUST specify $myhostname at the start of the text. That is an
  514. # RFC requirement. Postfix itself does not care.
  515. #
  516. #smtpd_banner = $myhostname ESMTP $mail_name
  517. #smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
  518. # PARALLEL DELIVERY TO THE SAME DESTINATION
  519. #
  520. # How many parallel deliveries to the same user or domain? With local
  521. # delivery, it does not make sense to do massively parallel delivery
  522. # to the same user, because mailbox updates must happen sequentially,
  523. # and expensive pipelines in .forward files can cause disasters when
  524. # too many are run at the same time. With SMTP deliveries, 10
  525. # simultaneous connections to the same domain could be sufficient to
  526. # raise eyebrows.
  527. #
  528. # Each message delivery transport has its XXX_destination_concurrency_limit
  529. # parameter.  The default is $default_destination_concurrency_limit for
  530. # most delivery transports. For the local delivery agent the default is 2.
  531. #local_destination_concurrency_limit = 2
  532. #default_destination_concurrency_limit = 20
  533. # DEBUGGING CONTROL
  534. #
  535. # The debug_peer_level parameter specifies the increment in verbose
  536. # logging level when an SMTP client or server host name or address
  537. # matches a pattern in the debug_peer_list parameter.
  538. #
  539. debug_peer_level = 2
  540. # The debug_peer_list parameter specifies an optional list of domain
  541. # or network patterns, /file/name patterns or type:name tables. When
  542. # an SMTP client or server host name or address matches a pattern,
  543. # increase the verbose logging level by the amount specified in the
  544. # debug_peer_level parameter.
  545. #
  546. #debug_peer_list = 127.0.0.1
  547. #debug_peer_list = some.domain
  548. # The debugger_command specifies the external command that is executed
  549. # when a Postfix daemon program is run with the -D option.
  550. #
  551. # Use "command .. & sleep 5" so that the debugger can attach before
  552. # the process marches on. If you use an X-based debugger, be sure to
  553. # set up your XAUTHORITY environment variable before starting Postfix.
  554. #
  555. debugger_command =
  556.  PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
  557.  xxgdb $daemon_directory/$process_name $process_id & sleep 5
  558. # If you can't use X, use this to capture the call stack when a
  559. # daemon crashes. The result is in a file in the configuration
  560. # directory, and is named after the process name and the process ID.
  561. #
  562. # debugger_command =
  563. # PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
  564. # echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
  565. # >$config_directory/$process_name.$process_id.log & sleep 5
  566. #
  567. # Another possibility is to run gdb under a detached screen session.
  568. # To attach to the screen sesssion, su root and run "screen -r
  569. # <id_string>" where <id_string> uniquely matches one of the detached
  570. # sessions (from "screen -list" ).
  571. #
  572. # debugger_command =
  573. # PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
  574. # -dmS $process_name gdb $daemon_directory/$process_name
  575. # $process_id & sleep 1
  576. # INSTALL-TIME CONFIGURATION INFORMATION
  577. #
  578. # The following parameters are used when installing a new Postfix version.
  579. #
  580. # sendmail_path: The full pathname of the Postfix sendmail command.
  581. # This is the Sendmail-compatible mail posting interface.
  582. #
  583. sendmail_path = /usr/sbin/sendmail.postfix
  584. # newaliases_path: The full pathname of the Postfix newaliases command.
  585. # This is the Sendmail-compatible command to build alias databases.
  586. #
  587. newaliases_path = /usr/bin/newaliases.postfix
  588. # mailq_path: The full pathname of the Postfix mailq command.  This
  589. # is the Sendmail-compatible mail queue listing command.
  590. #
  591. mailq_path = /usr/bin/mailq.postfix
  592. # setgid_group: The group for mail submission and queue management
  593. # commands.  This must be a group name with a numerical group ID that
  594. # is not shared with other accounts, not even with the Postfix account.
  595. #
  596. setgid_group = postdrop
  597. # html_directory: The location of the Postfix HTML documentation.
  598. #
  599. html_directory = no
  600. # manpage_directory: The location of the Postfix on-line manual pages.
  601. #
  602. manpage_directory = /usr/share/man
  603. # sample_directory: The location of the Postfix sample configuration files.
  604. # This parameter is obsolete as of Postfix 2.1.
  605. #
  606. sample_directory = /usr/share/doc/postfix-2.4.5/samples
  607. # readme_directory: The location of the Postfix README files.
  608. #
  609. readme_directory = /usr/share/doc/postfix-2.4.5/README_FILES
  610. myorigin = ville-sallaumines.fr
  611. #mydestination = $myorigin
  612. relayhost = smtp.ville.sallaumines.fr


 
concernant les logs, il te faut lesquels (et comment les avoir) ?
 
merci de ton aide !

n°1040366
toniotonio
Posté le 07-05-2008 à 12:55:04  profilanswer
 

si postconf ne marche pas c'est que ton install est mauvaise.
 
tu compiles a partir des sources ou c'est du package ?
 


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°1040369
mozvillat
Posté le 07-05-2008 à 13:02:09  profilanswer
 

il a ete installé par un package pour fedora me semble t-il.
 
pour le postconf, dans un terminal tu saisi juste postconf -n (sans passer par /etc/xxx) ?

n°1040374
toniotonio
Posté le 07-05-2008 à 13:28:50  profilanswer
 

oui c'est ca
 
verifie ton install


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°1040454
mozvillat
Posté le 07-05-2008 à 15:04:36  profilanswer
 

je vais utiliser le lien dans ta signature pour effectuer une nouvelle install de postfix !! je te tiens au courant si je rencontre encore des probleme.
 
merci.

n°1040473
mozvillat
Posté le 07-05-2008 à 15:17:11  profilanswer
 

je viens de desinstaller postfix (yum remove postfix)
 
desinstallation ok.
 
puis reinstallation : yum install postfix.
 
yum installe le package.
 
sans rien modifier, postconf -n me redonne la meme erreur que tout à l'heure.
 
et /etc/init.d/postfix start m'indique bien ok
lors d'un status : master est arrete...
 
peut etre faut il d'autres packages en install, non ??
 
edit : je viens de trouver pourquoi postfix ne se lancait pas... sendmail tournait en tache de fond.
apres l'arret de sendmail, postfix accepte de se lancer et desormais master indique son pid.
 
on avance !!!
 
par contre, un postconf -n ne me donne toujours rien ???!!!!


Message édité par mozvillat le 07-05-2008 à 15:31:58
n°1040554
toniotonio
Posté le 07-05-2008 à 16:48:26  profilanswer
 

essaye  
 whereis postconf


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°1040558
mozvillat
Posté le 07-05-2008 à 16:55:31  profilanswer
 

whereis postconf me donne :

Code :
  1. [root@logement ~]# whereis postconf
  2. postconf: /usr/sbin/postconf /usr/share/man/man1/postconf.1.gz /usr/share/man/man5/postconf.5.gz


 
Je viens de reprendre à 0 le main.cf et supprimé les lignes de commentaires afin d'y voir plus clair.
 
Desormais mon appli envoi bien les mails (des comptes qui existent sur le serveur principal) mais ne relaye pas les messages en dehors de notre domaine.
 
Je te demande encore un peu d'aide, si tu vois ce qui cloche...a moins que ce soit le serveur principal qui refuse de relayer vers l'exterieur ??
 
Voici mon main.cf

Code :
  1. command_directory = /usr/sbin
  2. daemon_directory = /usr/libexec/postfix
  3. myhostname = logement.ville-sallaumines.fr
  4. mydomain = ville-sallaumines.fr
  5. inet_interfaces = localhost
  6. unknown_local_recipient_reject_code = 550
  7. alias_maps = hash:/etc/aliases
  8. alias_database = hash:/etc/aliases
  9. debug_peer_level = 2
  10. debugger_command =
  11.  PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
  12.  xxgdb $daemon_directory/$process_name $process_id & sleep 5
  13. sendmail_path = /usr/sbin/sendmail.postfix
  14. newaliases_path = /usr/bin/newaliases.postfix
  15. mailq_path = /usr/bin/mailq.postfix
  16. setgid_group = postdrop
  17. html_directory = no
  18. manpage_directory = /usr/share/man
  19. sample_directory = /usr/share/doc/postfix-2.4.5/samples
  20. readme_directory = /usr/share/doc/postfix-2.4.5/README_FILES
  21. myorigin = ville-sallaumines.fr
  22. relayhost = smtp.ville-sallaumines.fr


 
Peux tu m'indiquer si il y a des lignes inutiles ou manquantes ?
 
edit : je viens de regarder les logs du serveur de messagerie et c'est le smtp de mon fai qui rejette le message...le serveur web annonce un sous domaine... il faut que je regarde sur les noms de machines declarees.


Message édité par mozvillat le 07-05-2008 à 17:01:44
mood
Publicité
Posté le 07-05-2008 à 16:55:31  profilanswer
 

n°1040562
toniotonio
Posté le 07-05-2008 à 17:01:56  profilanswer
 

il y a bcp d'options inutiles (car identiques au defaut)
 
que donne  
 
/usr/sbin/postconf -n


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°1040563
mozvillat
Posté le 07-05-2008 à 17:14:03  profilanswer
 

aucun fichier ou repertoire de ce type
 
edit : j'avais oublié le s à sbin...
voici le retour de /usr/sbin/postconf -n

Code :
  1. [root@logement ~]# /usr/sbin/postconf -n
  2. alias_database = hash:/etc/aliases
  3. alias_maps = hash:/etc/aliases
  4. command_directory = /usr/sbin
  5. config_directory = /etc/postfix
  6. daemon_directory = /usr/libexec/postfix
  7. debug_peer_level = 2
  8. html_directory = no
  9. inet_interfaces = localhost
  10. mailq_path = /usr/bin/mailq.postfix
  11. manpage_directory = /usr/share/man
  12. myorigin = ville-sallaumines.fr
  13. newaliases_path = /usr/bin/newaliases.postfix
  14. readme_directory = /usr/share/doc/postfix-2.4.5/README_FILES
  15. relayhost = smtp.ville-sallaumines.fr
  16. sample_directory = /usr/share/doc/postfix-2.4.5/samples
  17. sendmail_path = /usr/sbin/sendmail.postfix
  18. setgid_group = postdrop
  19. unknown_local_recipient_reject_code = 550
  20. [root@logement ~]#


 
par contre, est ce que postfix envoie automatiquement son nom de machine+domaine ?  
 
le smtp de mon fai n'aime pas le sous domaine,voici l'erreur :
"delivery 1780: deferral: 82.216.111.2_does_not_like_recipient./Remote_host_said:_450_<nobody@logement.ville-sallaumines.fr>:_Sender_address_rejected:_Domain_not_found/Giving_up_on_82.216.111.2./"
en fait il faudrait que le mail soit envoyé par nobody@ville-sallaumines.fr
 
j'ai essayé de commenter myhostname et mydomain car le script php modifie le "from" et complete le "to"...


Message édité par mozvillat le 07-05-2008 à 17:15:41
n°1040568
toniotonio
Posté le 07-05-2008 à 17:35:51  profilanswer
 

fais voir les logs complet de l'erreur (/var/log/mail*)


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°1040615
mozvillat
Posté le 07-05-2008 à 19:37:57  profilanswer
 

je les post vendredi car la suis plus au boulot !!!
 
en tout cas merci beaucoup pour ton aide.

n°1040749
e_esprit
Posté le 08-05-2008 à 17:16:20  profilanswer
 

http://postfix.traduc.org/index.ph [...] masquerade
 
masquerade_domains = ville-sallaumines.fr


---------------
Ce n'est point ma façon de penser qui a fait mon malheur, c'est celle des autres.
n°1040837
mozvillat
Posté le 09-05-2008 à 08:31:41  profilanswer
 

merci e_esprit !!
 
avec l'ajout de masquerade_domains, plus de probleme, la sme accepte de relayer les messages vers l'exterieur.
 
Probleme resolu !


Message édité par mozvillat le 09-05-2008 à 08:31:56

Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Linux et OS Alternatifs
  réseaux et sécurité

  [RESOLU] [POSTFIX] probleme de configuration

 

Sujets relatifs
Problème Open office et codage des caractères : fichiers bloquésProblème de lecture sur SAMBA (read raw)
probleme automount/autofscomment compiler gcc en 64 bits :'( [Gentoo] [Résolu]
[ubuntu] problème grub error 18(RÉSOLU) Photoshop sur OSX, ne s'ouvre plus ?
probleme script client OCS INVENTORYProblème d'install debian
Problème d'export displayGentoo 2008_beta2 kde 4 only compilé via gcc-4.3 -march=core2[Résolu]
Plus de sujets relatifs à : [RESOLU] [POSTFIX] probleme de configuration


Copyright © 1997-2022 Hardware.fr SARL (Signaler un contenu illicite / Données personnelles) / Groupe LDLC / Shop HFR