Changes from Version 1 of TracNotification

차이점 주위로
다음 차이점은 무시하기:
작성자:
trac (IP: 127.0.0.1)
날짜/시간:
2009-05-24 AM 7:16:16 (16 년 전)
설명:

--

Legend:

변경되지 않음
추가됨
제거됨
변경됨
  • TracNotification

    v0 v1  
     1= 티켓 변화에 대한 이메일 통지 = 
     2[[TracGuideToc]] 
     3 
     4Trac supports notification about ticket changes via email.  
     5 
     6Email notification is useful to keep users up-to-date on tickets/issues of interest, and also provides a convenient way to post all ticket changes to a dedicated mailing list. For example, this is how the [http://lists.edgewall.com/archive/trac-tickets/ Trac-tickets] mailing list is set up. 
     7 
     8이 기능은 기본적으로는 비활성화되어 있습니다. [wiki:TracIni trac.ini]파일에서 활성화하고 설정할 수 있습니다. 
     9 
     10== Receiving Notification Mails == 
     11When reporting a new ticket or adding a comment, enter a valid email address in the ''reporter'', ''assigned to/owner'' or ''cc'' field. Trac will automatically send you an email when changes are made to the ticket (depending on how notification is configured). 
     12 
     13이 기능은 관심이 있는 문제점이나 개선사항에 대한 최신 정보를 유지할 수 있다는 점에서 유용합니다. 
     14 
     15== SMTP 통지기능에 대한 설정하기 == 
     16 
     17=== 환경설정용 옵션 === 
     18trac.ini 파일의 ''[notification]'' 섹션에 이용할 수 있는 옵션들이 있습니다. 
     19 * '''smtp_enabled''': 이메일 통지기능을 활성화합니다. 
     20 * '''smtp_server''': 통지 기능에서 사용할 SMTP 서버의 주소. 
     21 * '''smtp_user''': (''since 0.9'') User name for authentication SMTP account. 
     22 * '''smtp_password''': (''since 0.9'') Password for authentication SMTP account. 
     23 * '''smtp_from''': 통지메일에서 ''보내는 사람'' 항목에 사용할 이메일 주소. 
     24 * '''smtp_replyto''': 통지메일에서 ''Reply-To'' 항목에 사용할 이메일 주소. 
     25 * '''smtp_default_domain''': (''since 0.10'') Append the specified domain to addresses that do not contain one. Fully qualified addresses are not modified. The default domain is appended to all username/login for which an email address cannot be found from the user settings. 
     26 * '''smtp_always_cc''': 항상 통지메일을 보낼 이메일 주소의 리스트. ''일반적으로 메일링 리스트에 티켓의 변경사항을 포스팅 할 경우에 사용되어집니다.'' 
     27 * '''smtp_always_bcc''': (''since 0.10'') List of email addresses to always send notifications to, but keeps addresses not visible from other recipients of the notification email  
     28 * '''always_notify_reporter''': 항상 작성자 필드에 입력된 주소로 통지메일을 보냅니다. 
     29 * '''always_notify_owner''': (''since 0.9'') Always send notifications to the address in the owner field. 
     30 * '''always_notify_updater''': (''since 0.10'') Always send a notification to the updater of a ticket. 
     31 * '''use_public_cc''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy). 
     32 * '''use_short_addr''': (''since 0.10'') Enable delivery of notifications to addresses that do not contain a domain (i.e. do not end with ''@<domain.com>'').This option is useful for intranets, where the SMTP server can handle local addresses and map the username/login to a local mailbox. See also `smtp_default_domain`. Do not use this option with a public SMTP server.  
     33 * '''mime_encoding''': (''since 0.10'') E-mail notifications are always sent in 7-bit mode. This option allows to select the MIME encoding scheme. Supported values: 
     34   * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines. 
     35   * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64) 
     36   * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered.  
     37 
     38'''smtp_from'''과 '''smtp_replyto'''은 (둘 다) ''입력되어야만'' 합니다. 그렇지 않으면 Trac은 이메일 통지 메일을 보내지 않을 것입니다. 
     39 
     40=== 설정 예제 === 
     41 
     42{{{ 
     43[notification] 
     44smtp_enabled = true 
     45smtp_server = mail.example.com 
     46smtp_from = notifier@example.com 
     47smtp_replyto = myproj@projects.example.com 
     48smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com 
     49}}} 
     50 
     51== 이메일 예제 == 
     52{{{ 
     53#42: testing 
     54---------------------------+------------------------------------------------ 
     55       Id:  42             |      Status:  assigned                 
     56Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004 
     57 Severity:  major          |   Milestone:  0.9                      
     58 Priority:  lowest         |     Version:  0.6                      
     59    Owner:  anonymous      |    Reporter:  jonas@example.com                
     60---------------------------+------------------------------------------------ 
     61Changes: 
     62  * component:  changset view => search system 
     63  * priority:  low => highest 
     64  * owner:  jonas => anonymous 
     65  * cc:  daniel@example.com => 
     66         daniel@example.com, jonas@example.com 
     67  * status:  new => assigned 
     68 
     69Comment: 
     70I'm interested too! 
     71 
     72-- 
     73Ticket URL: <http://example.com/trac/ticket/42> 
     74My Project <http://myproj.example.com/> 
     75}}} 
     76 
     77== Troubleshooting == 
     78 
     79If you cannot get the notification working, first make sure the log is activated and have a look at the log to find if an error message has been logged. See TracLogging for help about the log feature. 
     80 
     81Notification errors are not reported through the web interface, so the user who submit a change or a new ticket never gets notified about a notification failure. The Trac administrator needs to look at the log to find the error trace. 
     82 
     83=== ''Permission denied'' error === 
     84 
     85Typical error message: 
     86{{{ 
     87  ... 
     88  File ".../smtplib.py", line 303, in connect 
     89    raise socket.error, msg 
     90  error: (13, 'Permission denied') 
     91}}} 
     92 
     93This error usually comes from a security settings on the server: many Linux distributions do not let the web server (Apache, ...) to post email message to the local SMTP server. 
     94 
     95Many users get confused when their manual attempts to contact the SMTP server succeed: 
     96{{{ 
     97telnet localhost 25 
     98}}} 
     99The trouble is that a regular user may connect to the SMTP server, but the web server cannot: 
     100{{{ 
     101sudo -u www-data telnet localhost 25 
     102}}} 
     103 
     104In such a case, you need to configure your server so that the web server is authorize to post to the SMTP server. The actual settings depend on your Linux distribution and current security policy. You may find help browsing the Trac MailingList archive. 
     105 
     106Relevant ML threads: 
     107 * SELinux: http://article.gmane.org/gmane.comp.version-control.subversion.trac.general/7518 
     108  
     109=== ''Suspected spam'' error === 
     110 
     111Some SMTP servers may reject the notification email sent by Trac. 
     112 
     113The default Trac configuration uses Base64 encoding to send emails to the recipients. The whole body of the email is encoded, which sometimes trigger ''false positive'' SPAM detection on sensitive email servers. In such an event, it is recommended to change the default encoding to "quoted-printable" using the `mime_encoding` option. 
     114 
     115Quoted printable enconding works better with languages that use one of the Latin charsets. For Asian charsets, it is recommended to stick with the Base64 encoding. 
     116 
     117---- 
     118참고 : TracTickets, TracIni, TracGuide