From kevink at independentedit.tv Mon May 2 15:43:38 2011 From: kevink at independentedit.tv (Kevin Klimek) Date: Mon, 2 May 2011 17:43:38 -0500 Subject: [Rumpus-talk] E-mail Setting Setup Message-ID: <2222D271-830D-429D-8CA8-0D18D00F6F7F@independentedit.tv> Hi All, Having trouble getting my e-mail notifications to work on a new OS X Snow Leopard server. Just finishing the install and I can't get this to work. Hoping someone out there is running Rumpus on the latest OS X server. Mail is hosted locally; it was setup to use CRAM-MD5 and Kerberos for authentication, but I added Login because of the limitation of Rumpus. However, I still can't get a test e-mail sent, even when using either a local user or one through our LDAP directory. When I try to send the test, I get an error: -7001: Server returned SMTP code 501 ("Syntax error in parameters or arguments.") while sending MAIL FROM command. In the Mail Access log, I just get this: May 2 17:35:17 xserve postfix/smtpd[21941]: connect from localhost[127.0.0.1] May 2 17:35:18 xserve postfix/smtpd[21941]: disconnect from localhost[127.0.0.1] So it's evident it's just accessing the server and hanging up, but without any authentication problems. (If I remove the password, for instance, I do get an authorization error.) Anyone have this up and running that can give me a hand? Thanks in advance! ========== Kevin Klimek INDEPENDENT EDIT Avid.com Community Moderator 414.347.1100 | 1.877.347.3777 www.independentedit.tv -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdj at mac.com Mon May 2 15:51:07 2011 From: jdj at mac.com (Jeff Johnson) Date: Mon, 2 May 2011 18:51:07 -0400 Subject: [Rumpus-talk] E-mail Setting Setup In-Reply-To: <2222D271-830D-429D-8CA8-0D18D00F6F7F@independentedit.tv> References: <2222D271-830D-429D-8CA8-0D18D00F6F7F@independentedit.tv> Message-ID: <212630CA-831F-4BAF-899A-02D60E034752@mac.com> In /etc/postfix/main.cf try changing: smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname to this: smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks reject_invalid_helo_hostname reject_non_fqdn_helo_hostname then stop/start mail and try again On May 2, 2011, at 6:43 PM, Kevin Klimek wrote: > > Hi All, > > Having trouble getting my e-mail notifications to work on a new OS X Snow Leopard server. Just finishing the install and I can't get this to work. Hoping someone out there is running Rumpus on the latest OS X server. > > Mail is hosted locally; it was setup to use CRAM-MD5 and Kerberos for authentication, but I added Login because of the limitation of Rumpus. However, I still can't get a test e-mail sent, even when using either a local user or one through our LDAP directory. > > When I try to send the test, I get an error: > > -7001: Server returned SMTP code 501 ("Syntax error in parameters or arguments.") while sending MAIL FROM command. > > In the Mail Access log, I just get this: > > May 2 17:35:17 xserve postfix/smtpd[21941]: connect from localhost[127.0.0.1] > May 2 17:35:18 xserve postfix/smtpd[21941]: disconnect from localhost[127.0.0.1] > > So it's evident it's just accessing the server and hanging up, but without any authentication problems. (If I remove the password, for instance, I do get an authorization error.) > > Anyone have this up and running that can give me a hand? > > Thanks in advance! > > ========== > Kevin Klimek > INDEPENDENT EDIT > Avid.com Community Moderator > 414.347.1100 | 1.877.347.3777 > www.independentedit.tv > > _______________________________________________ > Rumpus-Talk mailing list > Rumpus-Talk at maxum.com > http://lists.maxum.com/mailman/listinfo/rumpus-talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From john at maxum.com Tue May 24 14:52:52 2011 From: john at maxum.com (John O'Fallon) Date: Tue, 24 May 2011 16:52:52 -0500 Subject: [Rumpus-talk] Rumpus 7.0.6 Message-ID: Rumpus 7.0.6 is now available: http://www.maxum.com/Rumpus/Download.html John Rumpus 7.0.6 ============ Rumpus now sends the correct HTTP header on secure connections so that older versions of MSIE can correctly process download files of all types. A display bug that could cause confusion when the Event Notices Folder Trigger sheet is re-opened has been corrected. A problem that could cause normal clients to be incorrectly added to the blocked clients list due to a rare progress indicator update issue has been corrected. Event Notices triggered by Web File Manager file uploads that are interrupted before the transfer completes are now suppressed. Improved the efficiency of the login page processing. From john at maxum.com Wed May 25 15:11:26 2011 From: john at maxum.com (John O'Fallon) Date: Wed, 25 May 2011 17:11:26 -0500 Subject: [Rumpus-talk] Rumpus 7.1 Beta 1 Message-ID: Rumpus 7.1 Beta 1 is now available for direct download here: http://www.maxumdev.com/DownloadPackages/Rumpus71B1.zip There are a couple of significant new features, and a number of smaller but still useful new options as well. The most significant new feature is "Quick Image Preview", which allows users to see a reduced-size image of each file directly within a thumbnail directory listings. (This feature requires OS X 10.5 or later.) Also coming is an iPhone app for monitoring and basic control. The Rumpus app isn't in the iTunes app store yet, though... Other new features include: * A "remember me on this computer" login option. * Countdown timer for automatic session expiration due to inactivity. * Improved WebDAV support for iOS apps (like Pages, Numbers & Keynote). * Support for file uploads larger than 2GB from clients that also support it (current releases of Chrome and Safari). * Outlook support in FileWatch drop shipments. * An option to suppress duplicate event notices from being triggered. * The ability to protect aliases from accidental deletion. * Automatic filename sequencing for duplicate file uploads by users who aren't allowed to overwrite/delete files. Check the "Read Me" file in the package for details, and as always, please report problems or experiences to the list or directly to "support at maxum.com". John From kurt at beelinegroup.com Wed May 25 16:30:06 2011 From: kurt at beelinegroup.com (Kurt Harvey) Date: Wed, 25 May 2011 16:30:06 -0700 Subject: [Rumpus-talk] possible feature request: Last Access year In-Reply-To: References: Message-ID: <1362239D-F473-4775-A25D-3A11EE9F5DFC@beelinegroup.com> Hi John, In the Define User Accounts window the "Last Access" field shows for example: Feb 23 10:25 I would love to also see the year even if it was just 2 digits like: Feb 23 10 10:25 Not sure if its possible or if this has been already discussed but it sure would be handy in managing accounts that aren't or can't set to expire. Thank you, Kurt From john at maxum.com Thu May 26 06:22:11 2011 From: john at maxum.com (John O'Fallon) Date: Thu, 26 May 2011 08:22:11 -0500 Subject: [Rumpus-talk] possible feature request: Last Access year In-Reply-To: <1362239D-F473-4775-A25D-3A11EE9F5DFC@beelinegroup.com> References: <1362239D-F473-4775-A25D-3A11EE9F5DFC@beelinegroup.com> Message-ID: The date format of the "Last Access" field will be the same as the WFM directory list date/time format, as set on the "Display" tab of the Web Settings window. So, if it's acceptable to use a date format in the WFM interface that includes the year, you can make this change in the current version of Rumpus. Note, however, that the "last access" date/time is stored as the formatted string, meaning that the format will only change when users log in again. That is, you won't be able to change the Date Format in Rumpus to see the year of past "last access" logins. It does make sense that you might want the WFM date display to be in a different format than that used in the "last access" history field. I'll see about making that change. John On May 25, 2011, at 6:30 PM, Kurt Harvey wrote: > In the Define User Accounts window the "Last Access" field shows for example: Feb 23 10:25 > > I would love to also see the year even if it was just 2 digits like: Feb 23 10 10:25 > > Not sure if its possible or if this has been already discussed but it sure would be handy in managing accounts that aren't or can't set to expire. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kurt at beelinegroup.com Thu May 26 16:24:37 2011 From: kurt at beelinegroup.com (Kurt Harvey) Date: Thu, 26 May 2011 16:24:37 -0700 Subject: [Rumpus-talk] possible feature request: Last Access year In-Reply-To: References: <1362239D-F473-4775-A25D-3A11EE9F5DFC@beelinegroup.com> Message-ID: <1F8F947D-1D1E-4EA7-B745-6D12ED5CD966@beelinegroup.com> Thank you John! Kurt On May 26, 2011, at 6:22 AM, John O'Fallon wrote: > The date format of the "Last Access" field will be the same as the WFM directory list date/time format, as set on the "Display" tab of the Web Settings window. So, if it's acceptable to use a date format in the WFM interface that includes the year, you can make this change in the current version of Rumpus. Note, however, that the "last access" date/time is stored as the formatted string, meaning that the format will only change when users log in again. That is, you won't be able to change the Date Format in Rumpus to see the year of past "last access" logins. > > It does make sense that you might want the WFM date display to be in a different format than that used in the "last access" history field. I'll see about making that change. > > John > > On May 25, 2011, at 6:30 PM, Kurt Harvey wrote: > >> In the Define User Accounts window the "Last Access" field shows for example: Feb 23 10:25 >> >> I would love to also see the year even if it was just 2 digits like: Feb 23 10 10:25 >> >> Not sure if its possible or if this has been already discussed but it sure would be handy in managing accounts that aren't or can't set to expire. > > > > > _______________________________________________ > Rumpus-Talk mailing list > Rumpus-Talk at maxum.com > http://lists.maxum.com/mailman/listinfo/rumpus-talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel_doyle at beyond.com.au Thu May 26 16:51:08 2011 From: rachel_doyle at beyond.com.au (Rachel Doyle) Date: Fri, 27 May 2011 09:51:08 +1000 Subject: [Rumpus-talk] Setting expiry times per user Message-ID: Hi there, I?m just testing out Rumpus 7, and I was wondering if it?s possible to set file expiry time on a per-user basis as well as system-wide. For our setup, we would like to have system-wide expiry set to one month, but we want one particular user?s files set on a three-month expiry. Is this possible with the current release? Cheers Rachel ----------------------------- Notice: The information contained in this e-mail and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete all copies of this e-mail and any attachments immediately from your computer system. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. The contents of this message may contain personal views which are not the views of Beyond International Limited. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From john at maxum.com Fri May 27 05:15:32 2011 From: john at maxum.com (John O'Fallon) Date: Fri, 27 May 2011 07:15:32 -0500 Subject: [Rumpus-talk] Setting expiry times per user In-Reply-To: References: Message-ID: <2DA5866B-F4B8-4183-97E9-14371A71DF42@maxum.com> No, the file expiration function can be enabled or disabled for each user independently, but the expiration time period applies to all users. John On May 26, 2011, at 6:51 PM, Rachel Doyle wrote: > I?m just testing out Rumpus 7, and I was wondering if it?s possible to set file expiry time on a per-user basis as well as system-wide. For our setup, we would like to have system-wide expiry set to one month, but we want one particular user?s files set on a three-month expiry. Is this possible with the current release?