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

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

  Messagerie : mail disparaissent, se décallent, vont dans spam....

 



 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

Messagerie : mail disparaissent, se décallent, vont dans spam....

n°949926
headquaker
steam : headquaker
Posté le 05-09-2007 à 09:42:09  profilanswer
 

Bonjour à toutes et à tous,
 
Je suis en stage dans une entreprise et j'entends depuis quelques temps qu'il y a un problème de mail que personne n'arrive à résoudre.
Voilà la description :
 
Serveur : Postfix + DSPAM
Client : Outlook express
 
Le problème : attention ce problème n'arrive pas à tous les clients mais totalement au hasard, de même que les conséquences
 
- les mails de clients vont dans le dossier spam même lorsque on dit au filtre que tel ou tel mail n'est pas un spam
- les mails sont simplement supprimer des clients mais sont toujours présents sur le serveur
- il y a un décallage dans les mails : je m'explique, quand on clique sur un mail dans le client, le contenu de ce mail de correspond pas à l'objet. Il y a comme un décallage entre les objets et le contenu des mails
 
PS : je précise que cela vaut aussi bien pour les mails internes qu'externes
 
Je ne suis pas en charge de ce dossier, mais ca pourrait bien m'aider si je pouvais leur apporter une solution....la société qui s'occupe du serveur de mail est apparement incapable... -_-.
 
voilà merci à vous


Message édité par headquaker le 05-09-2007 à 09:43:04
mood
Publicité
Posté le 05-09-2007 à 09:42:09  profilanswer
 

n°949927
Fork Bomb
Obsédé textuel
Posté le 05-09-2007 à 09:44:32  profilanswer
 

Ton client vient d'envoyer ce message dans la mauvaise catégorie du forum.


---------------
Décentralisons Internet-Bépo-Troll Bingo - "Pour adoucir le mélange, pressez trois quartiers d’orange !"
n°949928
toniotonio
Posté le 05-09-2007 à 09:44:51  profilanswer
 

pour t'aider il faudrait la conf complete et des logs.
 
postconf -n
master.cf
la conf de dspam


Message édité par toniotonio le 05-09-2007 à 09:45:05

---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°949934
headquaker
steam : headquaker
Posté le 05-09-2007 à 09:54:25  profilanswer
 

je vais voir si je peux fournir les infos. merci

n°949938
headquaker
steam : headquaker
Posté le 05-09-2007 à 10:05:40  profilanswer
 

Code :
  1. postconf -n
  2. alias_database = hash:/etc/aliases
  3. alias_maps = hash:/etc/aliases
  4. append_dot_mydomain = no
  5. biff = no
  6. config_directory = /etc/postfix
  7. inet_interfaces = all
  8. inet_protocols = all
  9. mailbox_size_limit = 0
  10. mydestination = localhost, localhost.localdomain, localhost
  11. myhostname = srv-xmail
  12. mynetworks = 127.0.0.0/8 x.x.x.x/8 y.y.y.y/24
  13. recipient_delimiter = +
  14. relayhost = [x.x.x.x]
  15. smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)


Master.cf
 

Code :
  1. 127.0.0.1:smtp      inet  n       -       -       -       -       smtpd
  2. x.x.x.x:smtp      inet  n       -       -       -       -       smtpd -o conten                                                                             t_filter
  3. x.x.x.x2:smtp      inet  n       -       -       -       -       smtpd
  4. #
  5. # SMTP Utilisant le filtre d'ajout des pieds-de-page
  6. #smtp      inet  n       -       -       -       -       smtpd #-o content_filte                                                                             r=dfilt:
  7. #submission inet n      -       -       -       -       smtpd
  8. #       -o smtpd_etrn_restrictions=reject
  9. #628      inet  n       -       -       -       -       qmqpd
  10. pickup    fifo  n       -       -       60      1       pickup
  11. cleanup   unix  n       -       -       -       0       cleanup
  12. qmgr      fifo  n       -       -       300     1       qmgr
  13. #qmgr     fifo  n       -       -       300     1       oqmgr
  14. rewrite   unix  -       -       -       -       -       trivial-rewrite
  15. bounce    unix  -       -       -       -       0       bounce
  16. defer     unix  -       -       -       -       0       bounce
  17. trace     unix  -       -       -       -       0       bounce
  18. verify    unix  -       -       -       -       1       verify
  19. flush     unix  n       -       -       1000?   0       flush
  20. proxymap  unix  -       -       n       -       -       proxymap
  21. smtp      unix  -       -       -       -       -       smtp
  22. relay     unix  -       -       -       -       -       smtp
  23. #       -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
  24. showq     unix  n       -       -       -       -       showq
  25. error     unix  -       -       -       -       -       error
  26. local     unix  -       n       n       -       -       local
  27. virtual   unix  -       n       n       -       -       virtual
  28. lmtp      unix  -       -       n       -       -       lmtp
  29. anvil     unix  -       -       n       -       1       anvil
  30. #
  31. # Interfaces to non-Postfix software. Be sure to examine the manual
  32. # pages of the non-Postfix software to find out what options it wants.
  33. #
  34. # maildrop. See the Postfix MAILDROP_README file for details.
  35. #
  36. maildrop  unix  -       n       n       -       -       pipe
  37.   flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
  38. uucp      unix  -       n       n       -       -       pipe
  39.   flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
  40. ifmail    unix  -       n       n       -       -       pipe
  41.   flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
  42. bsmtp     unix  -       n       n       -       -       pipe
  43.   flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -d -t$nexthop -f$sender $recipi                                                                             ent
  44. scalemail-backend unix  -       n       n       -       2       pipe
  45.   flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop}                                                                              ${user} ${extension}
  46. # only used by postfix-tls
  47. #tlsmgr   fifo  -       -       n       300     1       tlsmgr
  48. #smtps    inet  n       -       n       -       -       smtpd -o smtpd_tls_wrapp                                                                             ermode=yes -o smtpd_sasl_auth_enable=yes
  49. #587      inet  n       -       n       -       -       smtpd -o smtpd_enforce_t                                                                             ls=yes -o smtpd_sasl_auth_enable=yes
  50. tlsmgr    unix  -       -       -       1000?   1       tlsmgr
  51. scache    unix  -       -       -       -       1       scache
  52. discard   unix  -       -       -       -       -       discard
  53. # Ma défintion de mon filter d'ajout de pied-de-page
  54. #
  55. dfilt   unix    -       n       n       -       -       pipe flags=Rq user=filte                                                                             r argv=/etc/postfix/disclaimer -f ${sender} -- ${recipient}


 
dspam.conf
 

Code :
  1. ## $Id: dspam.conf.in,v 1.72 2006/05/14 15:40:42 jonz Exp $
  2. ## dspam.conf -- DSPAM configuration file
  3. ##
  4. #
  5. # DSPAM Home: Specifies the base directory to be used for DSPAM storage
  6. #
  7. Home /var/spool/dspam
  8. #
  9. # StorageDriver: Specifies the storage driver backend (library) to use.
  10. # You'll only need to set this if you are using dynamic storage driver plugins.
  11. # The default when one storage driver is specified is to statically link. Be
  12. # sure to include the path to the library if necessary, and some systems may
  13. # use an extension other than .so.
  14. #
  15. # Options include:
  16. #
  17. #   libmysql_drv.so     libpgsql_drv.so   libsqlite_drv.so
  18. #   libsqlite3_drv.so   libora_drv.so     libhash_drv.so
  19. #
  20. # IMPORTANT: Switching storage drivers requires more than merely changing
  21. # this option. If you do not wish to lose all of your data, you will need to
  22. # migrate it to the new backend before making this change.
  23. #
  24. #StorageDriver /usr/lib/dspam/libhash_drv.so
  25. StorageDriver /usr/lib/dspam/libmysql_drv.so
  26. #
  27. # Trusted Delivery Agent: Specifies the local delivery agent DSPAM should call
  28. # when delivering mail as a trusted user. Use %u to specify the user DSPAM is
  29. # processing mail for. It is generally a good idea to allow the MTA to specify
  30. # the pass-through arguments at run-time, but they may also be specified here.
  31. #
  32. # Most operating system defaults:
  33. #TrustedDeliveryAgent "/usr/bin/procmail"       # Linux
  34. #TrustedDeliveryAgent "/usr/bin/mail"           # Solaris
  35. #TrustedDeliveryAgent "/usr/libexec/mail.local" # FreeBSD
  36. #TrustedDeliveryAgent "/usr/bin/procmail"       # Cygwin
  37. #
  38. # Other popular configurations:
  39. #TrustedDeliveryAgent "/usr/cyrus/bin/deliver" # Cyrus
  40. #TrustedDeliveryAgent "/bin/maildrop"  # Maildrop
  41. #TrustedDeliveryAgent "/usr/local/sbin/exim -oMr spam-scanned" # Exim
  42. #
  43. #TrustedDeliveryAgent "/usr/bin/procmail -m %u"
  44. #TrustedDeliveryAgent "/usr/bin/maildrop -d %u"
  45. #TrustedDeliveryAgent "/usr/sbin/deliverquota -c -w 90 /home/%u/Maildir/ 10000"
  46. #
  47. # Untrusted Delivery Agent: Specifies the local delivery agent and arguments
  48. # DSPAM should use when delivering mail and running in untrusted user mode.
  49. # Because DSPAM will not allow pass-through arguments to be specified to
  50. # untrusted users, all arguments should be specified here. Use %u to specify
  51. # the user DSPAM is processing mail for. This configuration parameter is only
  52. # necessary if you plan on allowing untrusted processing.
  53. #
  54. TrustedDeliveryAgent "/usr/sbin/sendmail"
  55. # AU début, Untrusted...
  56. #UntrustedDeliveryAgent "/usr/bin/maildrop -d %u"
  57. #UntrustedDeliveryAgent "/usr/sbin/deliverquota -c -w 90 /home/%u/Maildir/ 10000"
  58. #
  59. # SMTP or LMTP Delivery: Alternatively, you may wish to use SMTP or LMTP
  60. # delivery to deliver your message to the mail server. You will need to
  61. # configure with --enable-daemon to use host delivery, however you do not need
  62. # to operate in daemon mode. Specify an IP address or UNIX path to a domain
  63. # socket below as a host.
  64. #
  65. # If you would like to set up DeliveryHost's on a per-domain basis, use
  66. # the syntax: DeliveryHost.domain.com 1.2.3.4
  67. #
  68. #DeliveryHost        127.0.0.1
  69. #DeliveryPort        24
  70. #DeliveryIdent       localhost
  71. #DeliveryProto       LMTP
  72. #
  73. # FallbackDomains: If you want to specify certain domains as fallback domains,
  74. # enable this option. For example, you could create a user @domain.com, and
  75. # if bob@domain.com does not resolve to a known user on the system, the user
  76. # could default to your @domain.com user. NOTE: This also requires designating
  77. # fallbackDomain for the domain name;
  78. # e.g. dspam_admin ch pref domain.com fallbackDomain on
  79. #
  80. #FallbackDomains on
  81. #
  82. # Quarantine Agent: DSPAM's default behavior is to quarantine all mail it
  83. # thinks is spam. If you wish to override this behavior, you may specify
  84. # a quarantine agent which will be called with all messages DSPAM thinks is
  85. # spam. Use %u to specify the user DSPAM is processing mail for.
  86. #
  87. QuarantineAgent "/usr/bin/procmail -p -m /etc/dspam/rc-quarantine %u"
  88. #
  89. # DSPAM can optionally process "plused users" (addresses in the user+detail
  90. # form) by truncating the username just before the "+", so all internal
  91. # processing occurs for "user", but delivery will be performed for
  92. # "user+detail". This is only useful if the LDA can handle "plused users"
  93. # (for example Cyrus IMAP) and when configured for LMTP delivery above
  94. #
  95. #EnablePlusedDetail on
  96. #
  97. # Quarantine Mailbox: DSPAM's LMTP code can send spam mail using LMTP to a
  98. # "plused" mailbox (such as user+quarantine) leaving quarantine processing
  99. # for retraining or deletion to be performed by the LDA and the mail client.
  100. # "plused" mailboxes are supported by Cyrus IMAP and possibly other LDAs.
  101. # The mailbox name must have the +
  102. #
  103. #QuarantineMailbox +quarantine
  104. #
  105. # OnFail: What to do if local delivery or quarantine should fail. If set
  106. # to "unlearn", DSPAM will unlearn the message prior to exiting with an
  107. # un successful return code. The default option, "error" will not unlearn
  108. # the message but return the appropriate error code. The unlearn option
  109. # is use-ful on some systems where local delivery failures will cause the
  110. # message to be requeued for delivery, and could result in the message
  111. # being processed multiple times. During a very large failure, however,
  112. # this could cause a significant load increase.
  113. #
  114. OnFail error
  115. # Trusted Users: Only the users specified below will be allowed to perform
  116. # administrative functions in DSPAM such as setting the active user and
  117. # accessing tools. All other users attempting to run DSPAM will be restricted;
  118. # their uids will be forced to match the active username and they will not be
  119. # able to specify delivery agent privileges or use tools.
  120. #
  121. Trust root
  122. Trust dspam
  123. Trust mail
  124. Trust mailnull
  125. Trust smmsp
  126. Trust daemon
  127. #Trust nobody
  128. #Trust majordomo
  129. #
  130. # Debugging: Enables debugging for some or all users. IMPORTANT: DSPAM must
  131. # be compiled with debug support in order to use this option. DSPAM should
  132. # never be running in production with debug active unless you are
  133. # troubleshooting problems.
  134. #
  135. # DebugOpt: One or more of: process, classify, spam, fp, inoculation, corpus
  136. #   process     standard message processing
  137. #   classify    message classification using --classify
  138. #   spam        error correction of missed spam
  139. #   fp          error correction of false positives
  140. #   inoculation message inoculations (source=inoculation)
  141. #   corpus      corpusfed messages (source=corpus)
  142. #
  143. #Debug *
  144. #Debug bob bill
  145. #
  146. #DebugOpt process spam fp
  147. #Debug *
  148. #DebugOpt process spam fp classify
  149. #
  150. # ClassAlias: Alias a particular class to spam/nonspam. This is useful if
  151. # classifying things other than spam.
  152. #ClassAliasSpam badstuff
  153. #ClassAliasNonspam goodstuff
  154. #
  155. # Training Mode: The default training mode to use for all operations, when
  156. # one has not been specified on the commandline or in the user's preferences.
  157. # Acceptable values are: toe, tum, teft, notrain
  158. #
  159. TrainingMode teft
  160. #
  161. # TestConditionalTraining: By default, dspam will retrain certain errors
  162. # until the condition is no longer met. This usually accelerates learning.
  163. # Some people argue that this can increase the risk of errors, however.
  164. #
  165. TestConditionalTraining on
  166. #
  167. # Features: Specify features to activate by default; can also be specified
  168. # on the commandline. See the documentation for a list of available features.
  169. # If _any_ features are specified on the commandline, these are ignored.
  170. #
  171. # NOTE: For standard "CRM114" Markovian weighting, use sbph
  172. #
  173. #Feature sbph
  174. #Feature noise
  175. Feature chained
  176. Feature whitelist
  177. # Training Buffer: The training buffer waters down statistics during training.
  178. # It is designed to prevent false positives, but can also dramatically reduce
  179. # dspam's catch rate during initial training. This can be a number from 0
  180. # (no buffering) to 10 (maximum buffering). If you are paranoid about false
  181. # positives, you should probably enable this option.
  182. #Feature tb=5
  183. Feature tb=5
  184. #
  185. # Algorithms: Specify the statistical algorithms to use, overriding any
  186. # defaults configured in the build. The options are:
  187. #    naive       Naive-Bayesian (All Tokens)
  188. #    graham      Graham-Bayesian ("A Plan for Spam" )
  189. #    burton      Burton-Bayesian (SpamProbe)
  190. #    robinson    Robinson's Geometric Mean Test (Obsolete)
  191. #    chi-square  Fisher-Robinson's Chi-Square Algorithm
  192. #
  193. # You may have multiple algorithms active simultaneously, but it is strongly
  194. # recommended that you group Bayesian algorithms with other Bayesian
  195. # algorithms, and any use of Chi-Square remain exclusive.
  196. #
  197. # NOTE: For standard "CRM114" Markovian weighting, use 'naive', or consider
  198. #       using 'burton' for slightly better accuracy
  199. #
  200. # Don't mess with this unless you know what you're doing
  201. #
  202. #Algorithm chi-square
  203. #Algorithm naive
  204. Algorithm graham burton
  205. #
  206. # PValue: Specify the technique used for calculating PValues, overriding any
  207. # defaults configured in the build. These options are:
  208. #    graham      Graham's Technique ("A Plan for Spam" )
  209. #    robinson    Robinson's Technique
  210. #    markov      Markovian Weighted Technique
  211. #
  212. # Unlike algorithms, you may only have one of these defined. Use of the
  213. # chi-square algorithm automatically changes this to robinson.
  214. #
  215. # Don't mess with this unless you know what you're doing.
  216. #
  217. #PValue robinson
  218. #PValue markov
  219. PValue graham
  220. #
  221. # SupressWebStats: Enable this if you are not using the CGI, and don't want
  222. # .stats files written.
  223. #SupressWebStats on
  224. #
  225. # ImprobabilityDrive: Calculate odds-ratios for ham/spam, and add to
  226. # X-DSPAM-Improbability headers
  227. ImprobabilityDrive on
  228. statisticalSedation off
  229. #
  230. # Preferences: Specify any preferences to set by default, unless otherwise
  231. # overridden by the user (see next section) or a default.prefs file.
  232. # If user or default.prefs are found, the user's preferences will override any
  233. # defaults.
  234. #
  235. Preference "spamAction=tag"
  236. #Preference "signatureLocation=message" # 'message' or 'headers'
  237. Preference "signatureLocation=message" # 'message' or 'headers'
  238. #Preference "showFactors=on"
  239. #Preference "spamAction=tag"
  240. Preference "spamSubject=[SPAM]"
  241. #
  242. # Overrides: Specifies the user preferences which may override configuration
  243. # and commandline defaults. Any other preferences supplied by an untrusted user
  244. # will be ignored.
  245. #
  246. AllowOverride trainingMode
  247. AllowOverride spamAction spamSubject
  248. AllowOverride statisticalSedation
  249. AllowOverride enableBNR
  250. AllowOverride enableWhitelist
  251. AllowOverride signatureLocation
  252. AllowOverride showFactors
  253. AllowOverride optIn optOut
  254. AllowOverride whitelistThreshold
  255. # --- Oracle ---
  256. #OraServer       "(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521))(CONNECT_DATA=(SID=PROD)))"
  257. #OraUser         dspam
  258. #OraPass         changeme
  259. #OraSchema       dspam
  260. # --- SQLite ---
  261. #SQLitePragma   "synchronous = OFF"
  262. # --- Hash ---
  263. # HashRecMax: Default number of records to create in the initial segment when
  264. # building hash files. 100,000 yields files 1.6MB in size, but can fill up
  265. # fast, so be sure to increase this (to a million or more) if you're not using
  266. # autoextend.
  267. #
  268. # Primes List:
  269. #  53, 97, 193, 389, 769, 1543, 3079, 6151, 12289, 24593, 49157, 98317, 196613,
  270. #  393241, 786433, 1572869, 3145739, 6291469, 12582917, 25165843, 50331653,
  271. #  100663319, 201326611, 402653189, 805306457, 1610612741, 3221225473,
  272. #  4294967291
  273. #
  274. HashRecMax  98317
  275. # HashAutoExtend: Autoextend hash databases when they fill up. This allows
  276. # them to continue to train by adding extents (extensions) to the file. There
  277. # will be a small delay during the growth process, as everything needs to be
  278. # closed and remapped.
  279. #
  280. HashAutoExtend  on 
  281. # HashMaxExtents: The maximum number of extents that may be created in a single
  282. # hash file. Set this to zero for unlimited
  283. #
  284. HashMaxExtents  0
  285. # HashExtentSize: The record size for newly created extents. Creating this too
  286. # small could result in many extents being created. Creating this too large
  287. # could result in excessive disk space usage.
  288. #
  289. HashExtentSize  49157
  290. # HashMaxSeek: The maximum number of records to seek to insert a new record
  291. # before failing or adding a new extent. Setting this too high will exhaustively
  292. # scan each segment and kill performance. Typically, a low value is acceptable
  293. # as even older extents will continue to fill over time.
  294. #
  295. HashMaxSeek  100
  296. # HashConcurrentUser: If you are using a single, stateful hash database in
  297. # daemon mode, specifying a concurrent user will cause the user to be
  298. # permanently mapped into memory and shared via rwlocks.
  299. #
  300. #HashConcurrentUser user
  301. # HashConnectionCache: If running in daemon mode, this is the max # of
  302. # concurrent connections that will be supported. NOTE: If you are using
  303. # HashConcurrentUser, this option is ignored, as all connections are read-
  304. # write locked instead of mutex locked.
  305. HashConnectionCache 10
  306. # LDAP: Perform various LDAP functions depending on LDAPMode variable.
  307. # Presently, the only mode supported is 'verify', which will verify the existence
  308. # of an unknown user in LDAP prior to creating them as a new user in the system.
  309. # This is useful on some systems acting as gateway machines.
  310. #
  311. #LDAPMode verify
  312. #LDAPHost ldaphost.mydomain.com
  313. #LDAPFilter "(mail=%u)"
  314. #LDAPBase ou=people,dc=domain,dc=com
  315. #LDAPMode verify
  316. #LDAPHost stoeffler-ad.local
  317. #LDAPFilter "(mail=%u@stoeffler.com)"
  318. #LDAPBase dc=stoeffler-ad,dc=local
  319. #LDAPRootDN CN=squid,OU=Administrateurs,OU=ObernaiUSR,DC=stoeffler-ad,DC=local
  320. #LDAPDNPass squid
  321. # Optionally, you can specify storage profiles, and specify the server to
  322. # use on the commandline with --profile. For example:
  323. #
  324. #Profile DECAlpha
  325. #MySQLServer.DECAlpha   10.0.0.1
  326. #MySQLPort.DECAlpha     3306
  327. #MySQLUser.DECAlpha     dspam
  328. #MySQLPass.DECAlpha     changeme
  329. #MySQLDb.DECAlpha       dspam
  330. #MySQLCompress.DECAlpha true
  331. #
  332. #Profile Sun420R
  333. #MySQLServer.Sun420R    10.0.0.2
  334. #MySQLPort.Sun420R      3306
  335. #MySQLUser.Sun420R      dspam
  336. #MySQLPass.Sun420R      changeme
  337. #MySQLDb.Sun420R        dspam
  338. #MySQLCompress.Sun420R  false
  339. #
  340. #DefaultProfile DECAlpha
  341. #
  342. # If you're using storage profiles, you can set failovers for each profile.
  343. # Of course, if you'll be failing over to another database, that database
  344. # must have the same information as the first. If you're using a global
  345. # database with no training, this should be relatively simple. If you're
  346. # configuring per-user data, however, you'll need to set up some type of
  347. # replication between databases.
  348. #
  349. #Failover.DECAlpha      SUN420R
  350. #Failover.Sun420R       DECAlpha
  351. # If the storage fails, the agent will follow each profile's failover up to
  352. # a maximum number of failover attempts. This should be set to a maximum of
  353. # the number of profiles you have, otherwise the agent could loop and try
  354. # the same profile multiple times (unless this is your desired behavior).
  355. #
  356. #FailoverAttempts       1
  357. #
  358. # Ignored headers: If DSPAM is behind other tools which may add a header to
  359. # incoming emails, it may be beneficial to ignore these headers - especially
  360. # if they are coming from another spam filter. If you are _not_ using one of
  361. # these tools, however, leaving the appropriate headers commented out will
  362. # allow DSPAM to use them as telltale signs of forged email.
  363. #
  364. #IgnoreHeader X-Spam-Status
  365. #IgnoreHeader X-Spam-Scanned
  366. #IgnoreHeader X-Virus-Scanner-Result
  367. #
  368. # Lookup: Perform lookups on streamlined blackhole list servers (see
  369. # http://www.nuclearelephant.com/projects/sbl/). The streamlined blacklist
  370. # server is machine-automated, unsupervised blacklisting system designed to
  371. # provide real-time and highly accurate blacklisting based on network spread.
  372. # When performing a lookup, DSPAM will automatically learn the inbound message
  373. # as spam if the source IP is listed. Until an official public RABL server is
  374. # available, this feature is only useful if you are running your own
  375. # streamlined blackhole list server for internal reporting among multiple mail
  376. # servers. Provide the name of the lookup zone below to use.
  377. #
  378. # This function performs standard reverse-octet.domain lookups, and while it
  379. # will function with many RBLs, it's strongly discouraged to use those
  380. # maintained by humans as they're often inaccurate and could hurt filter
  381. # learning and accuracy.
  382. #
  383. #Lookup "sbl.yourdomain.com"
  384. #
  385. # RBLInoculate: If you want to inoculate the user from RBL'd messages it would
  386. # have otherwise missed, set this to on.
  387. #
  388. #RBLInoculate off
  389. #
  390. # Notifications: Enable the sending of notification emails to users (first
  391. # message, quarantine full, etc.)
  392. #
  393. Notifications off
  394. #
  395. # Purge configuration: Set dspam_clean purge default options, if not otherwise
  396. # specified on the commandline
  397. #
  398. PurgeSignatures 14          # Stale signatures
  399. PurgeNeutral    90          # Tokens with neutralish probabilities
  400. PurgeUnused     90          # Unused tokens
  401. PurgeHapaxes    30          # Tokens with less than 5 hits (hapaxes)
  402. PurgeHits1S 15          # Tokens with only 1 spam hit
  403. PurgeHits1I 15          # Tokens with only 1 innocent hit
  404. #
  405. # Purge configuration for SQL-based installations using purge.sql
  406. #
  407. #PurgeSignature off # Specified in purge.sql
  408. #PurgeNeutral   90
  409. #PurgeUnused    off # Specified in purge.sql
  410. #PurgeHapaxes   off # Specified in purge.sql
  411. #PurgeHits1S    off # Specified in purge.sql
  412. #PurgeHits1I    off # Specified in purge.sql
  413. #
  414. # Local Mail Exchangers: Used for source address tracking, tells DSPAM which
  415. # mail exchangers are local and therefore should be ignored in the Received:
  416. # header when tracking the source of an email. Note: you should use the address
  417. # of the host as appears between brackets [ ] in the Received header.
  418. #
  419. LocalMX 127.0.0.1
  420. #
  421. # Logging: Disabling logging for users will make usage graphs unavailable to
  422. # them. Disabling system logging will make admin graphs unavailable.
  423. #
  424. SystemLog on
  425. UserLog   on
  426. #
  427. # TrainPristine: for systems where the original message remains server side
  428. # and can therefore be presented in pristine format for retraining. This option
  429. # will cause DSPAM to cease all writing of signatures and DSPAM headers to the
  430. # message, and deliver the message in as pristine format as possible. This mode
  431. # REQUIRES that the original message in its pristine format (as of delivery)
  432. # be presented for retraining, as in the case of webmail, imap, or other
  433. # applications where the message is actually kept server-side during reading,
  434. # and is preserved. DO NOT use this switch unless the original message can be
  435. # presented for retraining with the ORIGINAL HEADERS and NO MODIFICATIONS.
  436. #
  437. #TrainPristine on
  438. #
  439. # Opt: in or out; determines DSPAM's default filtering behavior. If this value
  440. # is set to in, users must opt-in to filtering by dropping a .dspam file in
  441. # /var/dspam/opt-in/user.dspam (or if you have homedirs configured, a .dspam
  442. # folder in their home directory).  The default is opt-out, which means all
  443. # users will be filtered unless a .nodspam file is dropped in
  444. # /var/dspam/opt-out/user.nodspam
  445. #
  446. Opt out
  447. #
  448. # TrackSources: specify which (if any) source addresses to track and report
  449. # them to syslog (mail.info). This is useful if you're running a firewall or
  450. # blacklist and would like to use this information. Spam reporting also drops
  451. # RABL blacklist files (see http://www.nuclearelephant.com/projects/rabl/).
  452. #
  453. #TrackSources spam nonspam
  454. #
  455. # ParseToHeaders: In lieu of setting up individual aliases for each user,
  456. # DSPAM can be configured to automatically parse the To: address for spam and
  457. # false positive forwards. From there, it can be configured to either set the
  458. # DSPAM user based on the username specified in the header and/or change the
  459. # training class and source accordingly. The options below can be used to
  460. # customize most common types of header parsing behavior to avoid the need for
  461. # multiple aliases, or if using LMTP, aliases entirely..
  462. #
  463. # ParseToHeader: Parse the To: headers of an incoming message. This must be
  464. #                set to 'on' to use either of the following features.
  465. #
  466. # ChangeModeOnParse: Automatically change the class (to spam or innocent)
  467. #   depending on whether spam- or notspam- was specified, and change the source
  468. #   to 'error'. This is convenient if you're not using aliases at all, but
  469. #   are delivering via LMTP.
  470. #
  471. # ChangeUserOnParse: Automatically change the username to match that specified
  472. #   in the To: header. For example, spam-bob@domain.tld will set the username
  473. #   to bob, ignoring any --user passed in. This may not always be desirable if
  474. #   you are using virtual email addresses as usernames. Options:
  475. #     on or user take the portion before the @ sign only
  476. #     full  take everything after the initial {spam,notspam}-.
  477. #
  478. #ParseToHeaders on
  479. #ChangeModeOnParse on
  480. #ChangeUserOnParse on
  481. #
  482. # Broken MTA Options: Some MTAs don't support the proper functionality
  483. # necessary. In these cases you can activate certain features in DSPAM to
  484. # compensate. 'returnCodes' causes DSPAM to return an exit code of 99 if
  485. # the message is spam, 0 if not, or a negative code if an error has occured.
  486. # Specifying 'case' causes DSPAM to force the input usernames to lowercase.
  487. # Spceifying 'lineStripping' causes DSPAM to strip ^M's from messages passed
  488. # in.
  489. #
  490. #Broken returnCodes
  491. #Broken case
  492. #Broken lineStripping
  493. #
  494. # MaxMessageSize: You may specify a maximum message size for DSPAM to process.
  495. # If the message is larger than the maximum size, it will be delivered
  496. # without processing. Value is in bytes.
  497. #
  498. #MaxMessageSize 4194304
  499. #
  500. # Virus Checking: If you are running clamd, DSPAM can perform stream-based
  501. # virus checking using TCP. Uncomment the values below to enable virus
  502. # checking.
  503. #
  504. # ClamAVResponse: reject (reject or drop the message with a permanent failure)
  505. #                 accept (accept the message and quietly drop the message)
  506. #                 spam   (treat as spam and quarantine/tag/whatever)
  507. #
  508. ClamAVPort 3310
  509. ClamAVHost 127.0.0.1
  510. ClamAVResponse spam
  511. #
  512. # Daemonized Server: If you are running DSPAM as a daemonized server using
  513. # --daemon, the following parameters will override the default. Use the
  514. # ServerPass option to set up accounts for each client machine. The DSPAM
  515. # server will process and deliver the message based on the parameters
  516. # specified. If you want the client machine to perform delivery, use
  517. # the --stdout option in conjunction with a local setup.
  518. #
  519. #ServerPort  24
  520. #ServerQueueSize 32
  521. #ServerPID              /var/run/dspam.pid
  522. #
  523. # ServerMode specifies the type of LMTP server to start. This can be one of:
  524. #     dspam: DSPAM-proprietary DLMTP server, for communicating with dspamc
  525. #  standard: Standard LMTP server, for communicating with Postfix or other MTA
  526. #      auto: Speak both DLMTP and LMTP; auto-detect by ServerPass.IDENT
  527. #
  528. #ServerMode dspam
  529. # If supporting DLMTP (dspam) mode, dspam clients will require authentication
  530. # as they will be passing in parameters. The idents below will be used to
  531. # determine which clients will be speaking DLMTP, so if you will be using
  532. # both LMTP and DLMTP from the same host, be sure to use something other
  533. # than the server's hostname below (which will be sent by the MTA during a
  534. # standard LMTP LHLO).
  535. #
  536. #ServerPass.Relay1 "secret"
  537. #ServerPass.Relay2 "password"
  538. # If supporting standard LMTP mode, server parameters will need to be specified
  539. # here, as they will not be passed in by the mail server. The ServerIdent
  540. # specifies the 250 response code ident sent back to connecting clients and
  541. # should be set to the hostname of your server, or an alias.
  542. #
  543. # NOTE: If you specify --user in ServerParameters, the RCPT TO will be
  544. #       used only for delivery, and not set as the active user for processing.
  545. #
  546. #ServerParameters "--deliver=innocent -d %u"
  547. #ServerIdent  "localhost.localdomain"
  548. # If you wish to use a local domain socket instead of a TCP socket, uncomment
  549. # the following. It is strongly recommended you use local domain sockets if
  550. # you are running the client and server on the same machine, as it eliminates
  551. # much of the bandwidth overhead.
  552. #
  553. #ServerDomainSocketPath  "/tmp/dspam.sock"
  554. #
  555. # Client Mode: If you are running DSPAM in client/server mode, uncomment and
  556. # set these variables. A ClientHost beginning with a / will be treated as
  557. # a domain socket.
  558. #
  559. #ClientHost /tmp/dspam.sock
  560. #ClientIdent "secret@Relay1"
  561. #
  562. #ClientHost 127.0.0.1
  563. #ClientPort 24
  564. #ClientIdent "secret@Relay1"
  565. # RABLQueue: Touch files in the RABL queue
  566. # If you are a reporting streamlined blackhole list participant, you can
  567. # touch ip addresses within the directory the rabl_client process is watching.
  568. #
  569. #RABLQueue /var/spool/rabl
  570. # DataSource: If you are using any type of data source that does not include
  571. # email-like headers (such as documents), uncomment the line below. This
  572. # will cause the entire input to be treated like a message "body"
  573. #
  574. #DataSource      document
  575. # ProcessorWordFrequency: By default, words are only counted once per message.
  576. # If you are classifying large documents, however, you may wish to count once
  577. # per occurrence instead.
  578. #
  579. #ProcessorWordFrequency  occurrence
  580. # ProcessorBias: Bias causes the filter to lean more toward 'innocent', and
  581. # usually greatly reduces false positives. It is the default behavior of
  582. # most Bayesian filters (including dspam).
  583. #
  584. # NOTE: You probably DONT want this if you're using Markovian Weighting, unless
  585. # you are paranoid about false positives.
  586. #
  587. ProcessorBias on
  588. #Tentative d'augmenter la whitelist
  589. #
  590. #Preference whitelistThreshold=1000
  591. # le 29 aout 2007
  592. Preference whitelistThreshold=10
  593. # Include a directory with configuration items.
  594. Include /etc/dspam/dspam.d/
  595. ## EOF


Message édité par headquaker le 05-09-2007 à 11:00:50
n°949943
toniotonio
Posté le 05-09-2007 à 10:21:23  profilanswer
 

postes tes conf avec la balise code ce sera plus lisible


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°949953
headquaker
steam : headquaker
Posté le 05-09-2007 à 10:45:16  profilanswer
 

voilou

n°949957
toniotonio
Posté le 05-09-2007 à 10:47:38  profilanswer
 

comment les mails sont ils transmis a  ton antispam ? (SA ou Dspam alors ?)


Message édité par toniotonio le 05-09-2007 à 10:48:02

---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°949960
headquaker
steam : headquaker
Posté le 05-09-2007 à 10:52:29  profilanswer
 

c'est bien DSPAM je vais voir la config...
voila j'ai mis la config en haut


Message édité par headquaker le 05-09-2007 à 11:05:40
n°949970
toniotonio
Posté le 05-09-2007 à 11:06:58  profilanswer
 

ok mais comment les mails sont envoyés a DSPAM ?
 
par procmail ?


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
mood
Publicité
Posté le 05-09-2007 à 11:06:58  profilanswer
 

n°949971
headquaker
steam : headquaker
Posté le 05-09-2007 à 11:08:49  profilanswer
 

oui

n°949974
toniotonio
Posté le 05-09-2007 à 11:14:01  profilanswer
 

tu peux montrer la conf  de procmail ?


---------------
Messagerie dédiée, Relais Mail Antispam/Antivirus, Infogérance 24/7: http://www.eole-its.com
n°949976
o'gure
Modérateur
Multi grognon de B_L
Posté le 05-09-2007 à 11:22:28  profilanswer
 

Heu remarque surement sans intéret, mais le monsieur à un problème d'accès, je ne suis pas sûr de bien saisir ce que postfix vient faire dans l'histoire.
 
Tu accèdes comment aux mails : IMAP ou POP ?
Le problème de décallage entre le corps et le sujet se fait il seulement avec outlook express ou avec tous les types de clients ?
 
As tu essayé de désactiver DSPAM pour voir si le probleme persiste ?


---------------
Ton Antoine commence à me les briser menus !
n°949977
headquaker
steam : headquaker
Posté le 05-09-2007 à 11:23:39  profilanswer
 

c'est quoi le fichier de config de procmail ?

n°949978
headquaker
steam : headquaker
Posté le 05-09-2007 à 11:24:49  profilanswer
 

on utilise uniquement outlook
 
c'est en IMAP

n°949980
o'gure
Modérateur
Multi grognon de B_L
Posté le 05-09-2007 à 11:26:57  profilanswer
 

Teste avec un autre client...

 

L'objectif est de trouver la cause, il faut donc supprimer un part un les différents éléments:
 - le serveur SMTP (je doute)
 - l'antispam (possible)
 - le serveur IMAP (fort probable pour la désynchro sujet/corps)
 - le client (fort probable pour tous vos problèmes) sauf que vous tourner sous windows donc faut aller voir la partie du forum qui traite de windows pour ce cas la) ainsi que les deux catégories "Réseau"

 

Mais teste avec un nouveau client.


Message édité par o'gure le 05-09-2007 à 11:29:39

---------------
Ton Antoine commence à me les briser menus !
n°949995
headquaker
steam : headquaker
Posté le 05-09-2007 à 11:45:06  profilanswer
 

je peux pas vraiment vu que ca arrive totalement au hasard...je vais leur en parler déjà merci


Message édité par headquaker le 05-09-2007 à 11:45:51

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

  Messagerie : mail disparaissent, se décallent, vont dans spam....

 

Sujets relatifs
Postfix/Amavis mail sortantMails entrants non signalés dans mail.log ?!?
Alerte mail quand hdd > X % ?Distrib linux pour serveur mail tournant sous VMWare
Serveur mail Postfix+Cyrus-IMAP avec authentification Cyrus-SASLipod + amarok = les musiques disparaissent
alerte par mail dans cactiDistribution Serveur Web/Ftp/Mail
Comment avoir plusieurs adresses mails d'envoi sous Mail (sous Mac OSServeur Mail (Postfix + Cyrus Imap)
Plus de sujets relatifs à : Messagerie : mail disparaissent, se décallent, vont dans spam....


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