You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Theo Van Dinter (JIRA)" <ji...@apache.org> on 2006/03/10 05:37:39 UTC
[jira] Commented: (INFRA-589) Replicate SpamAssassin Bugzilla
e-mail comment setup on Ajax
[ http://issues.apache.org/jira/browse/INFRA-589?page=comments#action_12369793 ]
Theo Van Dinter commented on INFRA-589:
---------------------------------------
There apparently hasn't been any movement on this issue. However, in the intervening time, it seems ajax is now setup to receive mail to some level:
Trying 192.87.106.226...
Connected to ajax.apache.org (192.87.106.226).
Escape character is '^]'.
220 ajax.apache.org ESMTP Postfix (Ubuntu)
quit
221 Bye
which should make things a bit easier. What can we do to get this ticket dealt with and closed? I'm willing to do the work if I can get the ok from the appropriate folks. Thoughts? Thanks. :)
> Replicate SpamAssassin Bugzilla e-mail comment setup on Ajax
> ------------------------------------------------------------
>
> Key: INFRA-589
> URL: http://issues.apache.org/jira/browse/INFRA-589
> Project: Infrastructure
> Type: Sub-task
> Components: Mail (qmail)
> Environment: ajax
> Reporter: Sander Temme
> Priority: Critical
>
> SpamAssassin Bugzilla has a widely used e-mail comment facility that is not present in its new environment (ajax). It would be a Very Good Thing to replicate this environment on ajax.
> The easiest way according to Theo would be to accept SMTP for bugzilla.spamassassin.org. From an Instant Message conversation with him:
> theovandinter (9:03:19 PM): for the incoming mail, basically we have a .procmailrc where the mails go through:
> theovandinter (9:03:20 PM): BUGZILLA_HOME=/var/www/html/contrib
> :0
> * ^Subject: .*\[Bug .*\]
> RESULT=|(cd $BUGZILLA_HOME && ./bugzilla_email_append.pl)
> :0
> /dev/null
> theovandinter (9:03:39 PM): which deals with the incoming mails but ignores stuff that looks like spam.
> theovandinter (9:03:54 PM): or more correctly, anything that doesn't look like a bug response.
> <..>
> theovandinter (9:18:04 PM): my plan would basically be:
> theovandinter (9:18:12 PM): ajax accepts for bugzilla.spamassassin.org,
> theovandinter (9:18:40 PM): by default, all mails goto the appropriate account,
> theovandinter (9:18:46 PM): which uses the procmail script,
> theovandinter (9:19:06 PM): such that spam and such is accepted, but /dev/null'ed very quickly.
> theovandinter (9:20:05 PM): somewhere, something has to accept the mail and deal with it.
> sandertemme (9:20:23 PM): I n
> theovandinter (9:21:00 PM): I think it's less work to accept and /dev/null as opposed to upfront trying to scan for spam and everything else.
> sandertemme (9:24:00 PM): I'll suggest that to the guys who are familiar with the mail setup on ajax. Actually, the I/O performance has become much better since I mounted the affected drive noatime. We can probably do even better by writing logs to a different disk than the one we're reading content from.
> Currently, the SpamAssassin Bugzilla e-mail interface is broken. It would be a Good Thing if we could move this into place forthwith.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira