#5182 prevent out-of-office replies to allura notifications [ss1139]

v1.1.0
closed
nobody
General
2015-08-20
2012-10-24
Chris Tsai
No

[forge:site-support:#1139]

Hi,

after replying to a forum post on the Allura platform
https://sourceforge.net/p/freefilesync/discussion/847543/thread/da516d2f/

I am getting multiple "my email address has changed" and "out-of-office" emails from a user like:

I am currently out of the office returning 22/10/2012
If your email is important please forward to: xxx@xxx.com
All other emails will be delt with upon my return.

Your message has not been forwarded.

This email message has been delivered safely and archived online by xxx.

What is going on? How can I get rid of this? I really have no desire for even more pointless emails filling my inbox.

We should look into:

1) adding headers to our notification emails to prevent (well-behaved) auto-responders from replying

2) check headers that auto-responders add, and not post to tickets/discussions/etc. If there are popular autoresponse systems that don't set a relevant header, and body text needs to be analyzed, we can consider that for a second iteration on this.

Will require some research on what standards exist and how popular systems (e.g. gmail, exchange, etc) handle autoresponses.

Related

Tickets: #5182
Tickets: #6341

Discussion

  • Dave Brondsema

    Dave Brondsema - 2012-10-31
    • labels: support, p2 --> support, p3
    • milestone: limbo --> forge-backlog
     
  • Dave Brondsema

    Dave Brondsema - 2013-06-11
    • labels: support, p3 --> support, p3, 42cc
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -21,4 +21,6 @@
    
     1) adding headers to our notification emails to prevent (well-behaved) auto-responders from replying
    
    -2) (if we don't already) checking headers that auto-responders add, and if a message looks like it's from an auto-responder, it should not post to tickets/discussions/etc.
    +2) check headers that auto-responders add, and not post to tickets/discussions/etc.  If there are popular autoresponse systems that don't set a relevant header, and body text needs to be analyzed, we can consider that for a second iteration on this.
    +
    +Will require some research on what standards exist and how popular systems (e.g. gmail, exchange, etc) handle autoresponses.
    
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-06-12
    • status: open --> in-progress
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-06-12

    Created #375: [#5182] prevent auto-responses to allura notifications (4cp)

     

    Related

    Tickets: #5182

  • Igor Bondarenko

    Igor Bondarenko - 2013-11-04
    • status: in-progress --> code-review
     
  • Igor Bondarenko

    Igor Bondarenko - 2013-11-04

    Closed #375. je/42cc_5182

    Implemented inbound email filtering based on common headers.

     
  • Tim Van Steenburgh

    • QA: Tim Van Steenburgh
    • Milestone: forge-backlog --> forge-nov-15
     
  • Tim Van Steenburgh

    • status: code-review --> closed
     
  • Tim Van Steenburgh

    Tested like so:

    Normal email, goes through:

    swaks --server localhost:50088 --to 22@tickets.testactivity.p.tvansteenburgh-1024.sb.sf.net --from tvansteenburgh@slashdotmedia.com -d "swaks test"
    

    Auto-responder email, blocked:

    swaks --server localhost:50088 --to 22@tickets.testactivity.p.tvansteenburgh-1024.sb.sf.net --from tvansteenburgh@slashdotmedia.com -d "%NEW_HEADERS%\n\nswaks test block" --add-header "Return-Path: <>"
    
     

Log in to post a comment.