On Thursday, January 12, 2023 at 3:09:03 PM UTC-8 rolfb...@gmail.com wrote:
We've installed TRAC on a Linux (Ubuntu) server.
Everything runs fine, except for email notifications for ticket updates.
We want to send the email notifications using our company Domino Server.
We are using TRAC on a W
Hi,
I haven't read all your conversation, but I want to give my 2 cents. It
would be great if the notification system of Trac would be improved - thank
you for your effort to get it into Trac Core!
In our company a periodically sent report is an important feature (esp. for
managers and project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.11.2012 09:21, Brettschneider Falk wrote:
> Ryan Ollos wrote:
>> and it looks like we don't yet have the behavior you want (2). It
>> looks like we'll need to add a rule with description "notify me
>> when a ticket I updated is modified".
>
> Si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.11.2012 09:00, Ryan Ollos wrote:
> On Wed, Nov 14, 2012 at 11:39 PM, Brettschneider Falk
> mailto:fbrettschnei...@baumer.com>> wrote:
>
> > Is it safe to use the latest SVN revision of AnnouncerPlugin?
> Because I've seen many commits th
On 17.11.2012 21:09, Steffen Hoffmann wrote:
(15 months!?)
Really? I didn't look it up by now. Amazing, how time passed by.
Yes, I was surprised too. :)
Incompatible? Dunno, but I remember the sentence from the
AnnouncerPlugin wiki page, that for moving from TracNotification to
Announcer on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.11.2012 23:59, Peter Suter wrote:
> On 14.11.2012 20:53, Steffen Hoffmann wrote:
>> I know of Peter even asking about need for
>> support to do things on the AnnouncerPlugin to TracNotification effort,
>> but this happened some months ago.
>
> (
On Thursday, November 15, 2012 12:22:09 AM UTC-8, F@lk wrote:
> Ryan Ollos wrote:
> > and it looks like we don't yet have the behavior you want (2). It looks
> like we'll need to add a rule with description "notify me when a ticket I
> updated is modified".
>
> Situation here is: a ticket pass
On Thursday, November 15, 2012 7:41:21 AM UTC-8, F@lk wrote:
> Ryan Ollos wrote:
> > I would suggest you avoid using AnnouncerPlugin trunk in production for
> at least a few more weeks or months. I think the 0.11 (1) branch is much
> more stabl. Let's see what hasienda has to say.
>
> I tried
Ryan Ollos wrote:
> I would suggest you avoid using AnnouncerPlugin trunk in production for at
> least a few more weeks or months. I think the 0.11 (1) branch is much more
> stabl. Let's see what hasienda has to say.
I tried both versions, trunk and 0.11 with a Trac-1.0.0.
AnnouncerPlugin 0.11
Ryan Ollos wrote:
> and it looks like we don't yet have the behavior you want (2). It looks like
> we'll need to add a rule with description "notify me when a ticket I updated
> is modified".
Situation here is: a ticket passes several people one by one, by setting the
current one as owner for a
RjOllos wrote:
> You will probably have better luck switching to the AnnouncerPlugin
Is it safe to use the latest SVN revision of AnnouncerPlugin? Because I've seen
many commits these days, and I don't want to svn-checkout something unfinished.
Can AnnouncerPlugin provide similar notification be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.11.2012 22:23, RjOllos wrote:
> On Wednesday, November 14, 2012 1:10:26 PM UTC-8, Remy Blank wrote:
>
> It's not that we *need* a rework, but since there was a proposal for
> integrating the AnnouncerPlugin, it was difficult to find moti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.11.2012 21:11, RjOllos wrote:
> On Wednesday, November 14, 2012 11:53:45 AM UTC-8, hasienda wrote:
> On 14.11.2012 20:05, RjOllos wrote:
> > Getting interest from a Trac committer to accept the change might be
> > more challenging.
>
On 14.11.2012 20:53, Steffen Hoffmann wrote:
I know of Peter even asking about need for
support to do things on the AnnouncerPlugin to TracNotification effort,
but this happened some months ago.
(15 months!?)
As Remy hinted at, the existence of AnnouncerPlugin and the integration
proposal see
On Wednesday, November 14, 2012 1:10:26 PM UTC-8, Remy Blank wrote:
> It's not that we *need* a rework, but since there was a proposal for
> integrating the AnnouncerPlugin, it was difficult to find motivation for
> fixing the existing system, as it would have been wasted effort.
>
> The propos
RjOllos wrote:
> I should explain what I meant by my comment. The reason I said that
> getting the change accepted might be challenging is that I've seen
> several comments from the developers that suggest we need a full rework
> of the notification system, such as replacement with the
> AnnouncerP
On Wednesday, November 14, 2012 11:53:45 AM UTC-8, hasienda wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 14.11.2012 20:05, RjOllos wrote:
> > Getting interest from a Trac committer to accept the change might be
> > more challenging.
>
> There are two new developers in town,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.11.2012 20:05, RjOllos wrote:
> Getting interest from a Trac committer to accept the change might be
> more challenging.
There are two new developers in town, that already contributed
significant changes, and I know of Peter even asking about ne
On Wednesday, November 14, 2012 2:13:09 AM UTC-8, F@lk wrote:
> Hi,
> "always_notify_updater" in section [notification] of trac.ini is
> documented as "Always send notifications to the person who causes the
> ticket property change and to any previous updater of that ticket."
>
> Can I somehow
Unfortunatlly 0.10.5 doesn't support AnnouncePlugin, so i ve applied your tip
and works fine, so thanks.
Same problem of plugin about reply.. but not so important.
Thanks for help
Rupert
jevans wrote:
>
>
>
>
> Hi,
> If you set the component owner to an artificial user whose email is
> a
Thanks for your reply.
This what i've done:
- Installed AnnouncerPlugin (because this provide good notification
managment and easy esclude recieving email from area doesn't in your
intresting);
- Create 2 fake users who have link of mailing list as e-mail contact;
- Setting these 2 users as co
On Apr 13, 1:05 pm, Zmo rupert_pupkin wrote:
> Goal is:
> when change tickets about Component1 send notification to
> compone...@mailinglist
>
> when change tickets about Component2 send notification to
> compone...@mailinglist
>
> On Apr 13, 7:29 pm, Olemis Lang wrote:
>
> > On Mon, Apr 13, 20
Goal is:
when change tickets about Component1 send notification to
compone...@mailinglist
when change tickets about Component2 send notification to
compone...@mailinglist
On Apr 13, 7:29 pm, Olemis Lang wrote:
> On Mon, Apr 13, 2009 at 11:33 AM, rupert 78 wrote:
>
> > Thanks for your reply,
On Mon, Apr 13, 2009 at 11:33 AM, rupert 78 wrote:
>
>
> Thanks for your reply,
> im too new to trac to understand your answer in a useful way.
>
AFAIK if you set an owner for a component then all notifications are
sent to that specific person ... isn't it?
{{{
$trac-admin component chown compo
Thanks for your reply,
im too new to trac to understand your answer in a useful way.
What i'm doing is play with the AnnouncerPlugin on 0.11. I'm working to make
it works in the way i need and as clean as possible. Mabye its not much
frequently divide two profile inside of a project.
regard
r
On Sun, Apr 12, 2009 at 5:53 PM, rupert 78 wrote:
>
>
> Hi to all,
> im pretty new of Trac.
>
> There is a project now divided in two team developers, Component1 and
> Component2. About notification, Component1 doesn't want to recieve email
> about Component2 ticket changing and the other way rou
On Apr 9, 4:34 am, sunny063 wrote:
> Hi all,
>
> I got a problem sending email notifications. When a new ticket is
> added it takes about 30 seconds to complete this when notification is
> enabled, also no notifications are send. First our admin told me that
> smtp-traffic was blocked on the mac
Pacôme MASSOL wrote:
> no one uses email notification template ?
I do, but I dont see anything wrong in your template. It should work.
I might have missed something, though...
--
Chef de projet chez Vectoris
Phone: +261 33 11 207
no one uses email notification template ?
Pacôme MASSOL a écrit :
> Hi,
>
> After an upgrade to 0.11, I wish to modify my ticket_notify_email.txt
> file to do something like this :
>
> #choose ticket.status
> #when 'new'
>do something
> #end
> #when 'closed'
>do something
>
On Thu, Oct 2, 2008 at 12:51 PM, Nishanthi <[EMAIL PROTECTED]> wrote:
>
> Like you had rightly pointed out .. It was some configuration file
> problem ! Sorry for the trouble !
> But there's another problem now :
>
> My subject line for the email always remains "Re: #id:"
> Am I supposed to add a
On Thu, Oct 2, 2008 at 1:34 PM, Nishanthi <[EMAIL PROTECTED]> wrote:
>
>
> i guess it should be :
> ticket_subject_template = $prefix #$ticket.id: $summary
>
> thanks anyway for the tip !
>
>
Sorry, you're right about that! It should be $summary, not $title.
--~--~-~--~~
i guess it should be :
ticket_subject_template = $prefix #$ticket.id: $summary
thanks anyway for the tip !
On Oct 2, 1:22 pm, Nishanthi <[EMAIL PROTECTED]> wrote:
> 2008-10-02 09:09:32,561 Trac[web_ui] ERROR: Failure sending
> notification on change to ticket #3: "title" not defined
> Tracebac
2008-10-02 09:09:32,561 Trac[web_ui] ERROR: Failure sending
notification on change to ticket #3: "title" not defined
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/trac/ticket/web_ui.py", line
992, in _do_save
tn.notify(ticket, newticket=False, modtime=now)
File
Like you had rightly pointed out .. It was some configuration file
problem ! Sorry for the trouble !
But there's another problem now :
My subject line for the email always remains "Re: #id:"
Am I supposed to add a 'phrase' of any kind in the
ticket_subject_template ?
the configuration is more or
>'SMTP Notification Error')
> my configuration file :
[notification]
smtp_from = [email-id]
smtp_replyto = [email id]
smtp_server = [server name]
ticket_subject_template = #.id:
As I wrote in the ticket comment http://trac.edgewall.org/ticket/3654#comment:6
do not obfuscate your notificatio
ScatterToo wrote:
I'm looking for a concise flowchart of the email notification system
behind Trac Tickets.
In other words , who (among reporter, owner, updater, and cc: if any)
gets email upon which actions (any update, any Action change, and so
on). I've been deductively trying to figure this
The error log shows that Trac cannot connect to your SMTP server.
This means that either the SMTP server address is wrong, or that the
machine Trac runs on is unable to connect to port 25 on the SMTP
server (because of a proxy or a firewall for example or a security
rule).
You can try the follow
Chris--
Your solution worked, as well as me turning on the option to resolve
anonymous emails. Thanks for your help!
Brett
On Oct 5, 7:57 am, Chris <[EMAIL PROTECTED]> wrote:
> wbranderson wbranderson-at-gmail.com |TracMailingList| wrote:
> > I am running a MS Small Business Server. I have
wbranderson wbranderson-at-gmail.com |TracMailingList| wrote:
> I am running a MS Small Business Server. I have been trying to get
> ticket notifications to be sent through the Exchange server. The
> following is the notification section of my trac.ini file.
>
> [notification]
> always_notify_o
On Thu, Oct 04, 2007 at 03:43:29PM -0700, wbranderson wrote:
>
> I am running a MS Small Business Server. I have been trying to get
> following is the notification section of my trac.ini file.
[...]
> SMTPServerDisconnected: Connection unexpectedly closed
Consult the Exchange server's log - h
> Does anyone know how to fix this problem?
Try with a true SMTP server ? ;-)
Sorry, I can't help but being sarcastic when it comes to M$.
You could try to connect with a telnet client to the SMTP server and
mimic a SMTP session, to see when it fails. Try the following:
telnet localhost 25
EHLO
Thank you, Manu.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Trac Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
> We have notification turned on with "always_notify_owner = true". Who
> is the owner in this case: The component owner (defined in
> Trac-Admin), or the Assignee?
The owner for a component is the defaut owner for this component, till
the ticket is *accepted* by someone else or *re-assigned* t
Thank you. I have additional questions below...
Eoin Dunne wrote:
> By default even if you don't specify and owner the ticket is assigned to
> the component owner.
Do you mean, if I don't specify an assignee? An owner is associated
with a component, so by selecting a component I would automati
By default even if you don't specify and owner the ticket is assigned to
the component owner.
If you have notification turned on in the trac.ini file (which you can
configure for each project), you can tune how you want the notification
to work.
If you assign a ticket manually to someone that is
On Mon, Nov 13, 2006 at 11:58:47PM +0100, Emmanuel Blot wrote:
> > smtp_password =
> > smtp_user = [EMAIL PROTECTED]
> The above line pair seems a bit weird: you are specifying a user to
> authenticate on the MTA, but you do not specify a password. Either
> leave smtp_user empty, or specify a
> smtp_password =
> smtp_user = [EMAIL PROTECTED]
The above line pair seems a bit weird: you are specifying a user to
authenticate on the MTA, but you do not specify a password. Either
leave smtp_user empty, or specify a password if your MTA require
authenticated connections to relay emails.
As
> As soon as I submit a bug, I see a log entry like:
>
> Nov 13 14:43:09 hostname sendmail[8579]: kADMh90A008579: localhost
> [127.0.0.1] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA
Which release of Trac are you using?
--
Manu
--~--~-~--~~~---~--~---
48 matches
Mail list logo
