Menu
▾
▴
roundup-users
|
From: John P. R. <ro...@cs...> - 2024-04-02 21:42:15
|
Hi Folks: I am trying to help somebody setup inbound email using postfix for multiple roundup trackers on two different virtual addresses. For this example: is...@ex... and is...@an.... Does anybody have a setup that does this and runs the roundup-mailgw with the proper uid/gid? Also I would like to document this better in the installtion document. Thanks. -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions. |
|
From: Ralf S. <rs...@ru...> - 2024-04-03 05:28:39
|
On Tue, Apr 02, 2024 at 05:42:01PM -0400, John P. Rouillard wrote: > Hi Folks: > > I am trying to help somebody setup inbound email using postfix for > multiple roundup trackers on two different virtual addresses. For this > example: is...@ex... and is...@an.... > > Does anybody have a setup that does this and runs the roundup-mailgw > with the proper uid/gid? > > Also I would like to document this better in the installtion > document. Thanks. I've generally moved to assigning an imap (or pop3) mailbox to roundup and use polling with the imap scripts: This avoids that during maintenance or other downtime mail might vanish (because at the time the mail is tried to deliver to the mailbox the mailserver has already accepted the mail) and it avoids all the permission problems. In addition you don't need a mailserver on the roundup box. So one reason that it's not well documented is that in todays environment it is not in much use... Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: www.runtux.com Reichergasse 131, A-3411 Weidling email: of...@ru... |
|
From: Martin Ö. <mar...@ce...> - 2024-04-03 07:40:03
|
On 4/2/24 23:42, John P. Rouillard wrote: > Hi Folks: Hello! > I am trying to help somebody setup inbound email using postfix for > multiple roundup trackers on two different virtual addresses. For this > example: is...@ex... and is...@an.... > > Does anybody have a setup that does this and runs the roundup-mailgw > with the proper uid/gid? Not with multiple trackers, but with a single tracker instance. If I were to have multiple trackers I would probably make Postfix route is...@ex... and is...@an... to the appropiate tracker. What issues are you seeing? Kind regards, -- Martin Östlund Support Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Linköping https://facebook.com/ThinLinc Community Support https://community.thinlinc.com |
|
From: John P. R. <ro...@cs...> - 2024-04-03 12:38:57
|
Hi Martin: In message <078...@ce...>, =?UTF-8?Q?Martin_=C3=96stlund?= via Roundup-users writes: >On 4/2/24 23:42, John P. Rouillard wrote: >> I am trying to help somebody setup inbound email using postfix for >> multiple roundup trackers on two different virtual addresses. For this >> example: is...@ex... and is...@an.... >> >> Does anybody have a setup that does this and runs the roundup-mailgw >> with the proper uid/gid? > >Not with multiple trackers, but with a single tracker instance. If I >were to have multiple trackers I would probably make Postfix route >is...@ex... and is...@an... to the appropiate tracker. I know that is a possibility, although I have never used it. Do you have an example of this? >What issues are you seeing? The system got upgraded and apparently the postfix config got lost during the upgrade. I think this will work, but something simpler would be good as well. The box is known as abox.com on the internet but receives email for: is...@ex... and bu...@an.... in /etc/postfix/main.cf add: virtual_alias_domains = example.com another.com virtual_alias_maps = hash:/etc/postfix/virtual alias_maps = hash:/etc/aliases hash:/etc/postfix/aliases.roundup in /etc/postfix/virtual add: # after changing this run 'postmap /etc/postfix/virtual' is...@ex... roundup_issues_example bu...@an... roundup_bugs_another Create /etc/postfix/aliases.roundup with owner/group roundup_user/roundup_group. Add: # after changing this run 'postmap /etc/postfix/aliases.roundup' roundup_issues_example |"/tools/roundup/bin/roundup-mailgw /d/track/example" roundup_issues_another |"/tools/roundup/bin/roundup-mailgw /d/track/another" and I think that's it. The ownership on aliases.roundup should cause roundup-mailgw to run as the roundup user according to local(8). The (writable) tracker files are owned by the roundup_user. I think all the trackers are owned by the same roundup user. If not, a separate alias file for each user would need to be created. Thoughts? -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions. |
|
From: Martin Ö. <mar...@ce...> - 2024-04-03 13:36:17
|
On 4/3/24 14:38, John P. Rouillard wrote: > and I think that's it. The ownership on aliases.roundup should cause > roundup-mailgw to run as the roundup user according to local(8). The > (writable) tracker files are owned by the roundup_user. > > I think all the trackers are owned by the same roundup user. If not, a > separate alias file for each user would need to be created. > > Thoughts? I think that's a nice approach. I inherited our tracker, so everything was already set up once I took over. This is our approach. It uses two servers. One is an internet-facing postfix server that routes incoming emails to another server that is hosting roundup. It uses procmail and local postfix installation as MTA. /etc/postfix(virtual-aliases on internet facing postfix. The internet facing Postfix server performs spam checks using Spamassassin, and set's a header, X-Spam-Status: /etc/postfix(virtual-aliases on internet facing postfix. su...@my... su...@tr... dem...@my... dem...@tr... /etc/aliases of internal machine postfix (tracker.mydomain.se) support: roundup+support demosupport: roundup+demosupport Content of $HOME/.procmailrc+support of roundup user: LOGFILE=$HOME/.procmail_support.log :0 * ^X-Spam-Status: Yes spam/support/ :0 |/usr/local/bin/roundup-mailgw -S external=True /opt/roundup/trackers/support-tracker/ And $HOME/.procmailrc+demosupport of roundup user: LOGFILE=.procmail_demosupport.log :0 * ^X-Spam-Status: Yes spam/demosupport/ :0 |/usr/local/bin/roundup-mailgw -C issue -S 'priority=Demosupport' /opt/roundup/trackers/support-tracker/ #! dem...@my... As you can see, this can easily be extended to other tracker instances as needed. The demosupport@ will also trigger a notification to a Slack channel, as well as deliver the message to a seperate Tracker queue Kind regards, -- Martin Östlund Support Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Linköping https://facebook.com/ThinLinc Community Support https://community.thinlinc.com |
Thanks for helping keep SourceForge clean.
X