postfixadmin-devel Mailing List for PostfixAdmin (Page 8)
Brought to you by:
christian_boltz,
gingerdog
You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(39) |
Nov
(29) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(5) |
Feb
|
Mar
(8) |
Apr
(8) |
May
|
Jun
(11) |
Jul
(21) |
Aug
(4) |
Sep
(9) |
Oct
(5) |
Nov
(25) |
Dec
(11) |
2009 |
Jan
(40) |
Feb
(16) |
Mar
(1) |
Apr
(46) |
May
(3) |
Jun
|
Jul
(1) |
Aug
(9) |
Sep
(9) |
Oct
(27) |
Nov
(35) |
Dec
(20) |
2010 |
Jan
(3) |
Feb
(2) |
Mar
(8) |
Apr
(1) |
May
(9) |
Jun
(8) |
Jul
(1) |
Aug
(7) |
Sep
(2) |
Oct
(2) |
Nov
(12) |
Dec
(7) |
2011 |
Jan
(45) |
Feb
(11) |
Mar
(18) |
Apr
(15) |
May
(20) |
Jun
|
Jul
(5) |
Aug
(1) |
Sep
|
Oct
(8) |
Nov
|
Dec
(14) |
2012 |
Jan
(30) |
Feb
(36) |
Mar
(6) |
Apr
(32) |
May
(20) |
Jun
(5) |
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
(22) |
Dec
(1) |
2013 |
Jan
(13) |
Feb
(4) |
Mar
(70) |
Apr
(10) |
May
(6) |
Jun
(11) |
Jul
(1) |
Aug
(3) |
Sep
(2) |
Oct
(15) |
Nov
(4) |
Dec
(4) |
2014 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(3) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(8) |
Dec
(2) |
2015 |
Jan
(1) |
Feb
(9) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
2016 |
Jan
(4) |
Feb
|
Mar
(10) |
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(13) |
2017 |
Jan
(1) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(3) |
2018 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(10) |
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2023 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(3) |
From: Tanstaafl <tan...@li...> - 2013-05-02 13:58:39
|
Hello, Ok, something must have happened recently that broke vacation, but I can't figure out what it is... Everything works up until it comes time to send the actual message, which fails with: > ERROR> /var/spool/vacation/vacation.pl:469 main::send_vacation_email - Failed to send vacation response: Connection not established vacation.pl line 469 is in this block of code: $Mail::Sender::NO_X_MAILER = 1; my $sender = new Mail::Sender({%smtp_connection}); $sender->Open({%mail}); $sender->SendLineEnc($body); $sender->Close() or $logger->error("Failed to send vacation response: " . $sender->{'error_msg'}); $logger->debug("Vacation response sent to $to, from $from"); } So... what does this mean? Am I somehow missing a perl module? Anyone have any ideas where to start looking? Perms for vacation.pl are correct... |
From: Norman M. <no...@no...> - 2013-04-08 20:02:59
|
Am 02.04.2013 um 21:57 schrieb Christian Boltz <pos...@cb...>: > PostfixAdmin will be at LinuxTag (www.linuxtag.org) Berlin again :-) > > I'll be at LinuxTag from 23th to 25th May and will have a part-time > booth (called "Project Meeting Point"). > Of course I'll show the latest development version and answer questions. > I'd also be happy to meet some people I only know by name, IRC nick or > mail address ;-) Great! I'm looking forward to see you there! Norman |
From: Christian B. <pos...@cb...> - 2013-04-08 19:41:17
|
Hello, Am Samstag, 6. April 2013 schrieb AIS Info: > I'm new to postfix admin so forgive me if i'm misinformed on any of > this but it appears that pacrypt() is lagging behind doveadm in it's > hashing algorithm support? Will 3.0 provide full support for all > schemes supported by dovecot? 2.3.x already does [1], but you have to use the dovecot:* encryption method, which calls the dovecotpw binary ("doveadm pw" for dovecot 2.x). This will work the same way in 3.0. > also, i'm not sure how to use the > "system" option as it's my understanding that the php script in use > at the time is what determines how php handles the task. their is no > php.ini directive that i'm aware of. "system" uses crypt(), see http://php.net/crypt for details (probably you don't want to use "system", but it has to stay for backward compability for people who actually use it) > FR: maybe an interface to > pacrypt() that provides a way to designate a custom script for > encrypt and a custom script for decrypt? then any limitations in any > of the three could be worked around? full dovecot scheme support > being the priority, i would imagine. I'm busy with several other things in PostfixAdmin and otherwise, and pacrypt() just works[tm] for nearly everybody, so it's not on my priority list ;-) Regards, Christian Boltz [1] The only exceptions are salted encryption methods. They don't work with dovecot:* because it's impossible to tell dovecotpw which salt to use when verifying a password. Well, strictly speaking you could use such passwords for mailboxes, but you can't login in PostfixAdmin with them. -- > All cats purr at 28hz. I think your cats need tuning - according to a couple of quick measure- ments on a recently calibrated reference cat, the dominant frequency of a correctly adjusted cat should be 12Hz +/-20%. [Lionel Lauer] |
From: AIS I. <in...@an...> - 2013-04-06 22:53:50
|
I'm new to postfix admin so forgive me if i'm misinformed on any of this but it appears that pacrypt() is lagging behind doveadm in it's hashing algorithm support? Will 3.0 provide full support for all schemes supported by dovecot? also, i'm not sure how to use the "system" option as it's my understanding that the php script in use at the time is what determines how php handles the task. their is no php.ini directive that i'm aware of. FR: maybe an interface to pacrypt() that provides a way to designate a custom script for encrypt and a custom script for decrypt? then any limitations in any of the three could be worked around? full dovecot scheme support being the priority, i would imagine. thanks. -- Andries Information Services www.andriesinfoserv.com 936-755-4857 Email disclaimer: The information contained in this communication is intended for the addressee only. Any use by third parties, including disclosure, copying, or distribution of this information is prohibited. If this email is received in error, please contact Andries Information Services at http://www.andriesinfoserv.com/contactandriesinformationservices.htm quoting the name of the sender and the email address to which it has been sent and then delete it. Please note that neither Andries Information Services nor the sender accepts any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. |
From: Tanstaafl <tan...@li...> - 2013-04-06 16:15:44
|
On 2013-04-06 10:53 AM, Tanstaafl <tan...@li...> wrote: > On 2013-04-03 9:10 AM, Tanstaafl <tan...@li...> wrote: >> I'll go open an update/bump request for SVN trunk - but if it is really >> that stable, why not make an official release, at least for the one with >> the web based interface (thats all I and many people use anyway)? > > ? I'm seriously interested. I totally understand if the CLI version is > intricately connected, and you can't really release the stable version > until it is ready too... Also... if you have even a vague estimation of how much longer before it goes stable, if it isn't too long, that may help motivate the gentoo package maintainer to go ahead and get it ready now... Anyway, thanks, I'm really looking forward to 3.x... |
From: Tanstaafl <tan...@li...> - 2013-04-06 14:53:44
|
On 2013-04-03 9:10 AM, Tanstaafl <tan...@li...> wrote: > I'll go open an update/bump request for SVN trunk - but if it is really > that stable, why not make an official release, at least for the one with > the web based interface (thats all I and many people use anyway)? ? I'm seriously interested. I totally understand if the CLI version is intricately connected, and you can't really release the stable version until it is ready too... |
From: Tanstaafl <tan...@li...> - 2013-04-03 13:10:53
|
On 2013-04-02 3:45 PM, Christian Boltz <pos...@cb...> wrote: > Am Freitag, 29. März 2013 schrieb Tanstaafl: >> My question is, is this code included in any of the formal stable >> releases (2.3.5? 2.3.6?)? If not, will it make it into the next stable >> release (presumably 2.3.7)? >> >> Or is this only in the new 3.x trunk? > The 2.3 branch is in maintenance mode (bugfixes only), which means 2.3.x > won't get the new vacation.pl features. > > On the positive side, SVN trunk (which will become 3.0) is quite stable. > Everything in the web interface should work (if not, report a > bugreport), and the CLI is also getting better (I deleted (!) ~500 > lines to complete the create and update commands yesterday ;-) - the > other commands may or may not work). > > I even found some time to handle some long-standing TODOs yesterday ;-) > (see the commit mailinglist for details) > > In other words: feel free to use SVN trunk ;-) Well, I really try to avoid installing things outside of my package manager (portage/gentoo), as I am far from expert at these things... I'll go open an update/bump request for SVN trunk - but if it is really that stable, why not make an official release, at least for the one with the web based interface (thats all I and many people use anyway)? > BTW, while looking at the random (really!) signature: > I'm still looking for someone who can shorten the changelog from 2.3.x > to current SVN trunk - are you interested? ;-) (My current draft with > 370 lines is probably too long for the average user ;-) Depends on what you mean by 'shorten the changelog'? If you mean edit it/clean the text up, I would be happy to help, but being that I'm not a coder, I'm not sure I'd know exactly what/how to clean it up. If you mean back-porting things from SVN trunk to 2.3 branch, would love to, but again - I'm not a coder... :( Thanks Christian for the response... |
From: David G. <da...@co...> - 2013-04-02 21:55:55
|
On 2 Apr 2013, at 20:57, Christian Boltz <pos...@cb...> wrote: > Hello, > > PostfixAdmin will be at LinuxTag (www.linuxtag.org) Berlin again :-) > :-) > > > I'll probably get some free tickets for LinuxTag - if you want to go to > LinuxTag and need one, send me a mail off-list. > I doubt I can make it.... thank you for at least representing PFA there (and being quite busy on it lately by all accounts!) David. |
From: Christian B. <pos...@cb...> - 2013-04-02 19:58:09
|
Hello, PostfixAdmin will be at LinuxTag (www.linuxtag.org) Berlin again :-) I'll be at LinuxTag from 23th to 25th May and will have a part-time booth (called "Project Meeting Point"). Of course I'll show the latest development version and answer questions. I'd also be happy to meet some people I only know by name, IRC nick or mail address ;-) It's not decided yet when I'll be at this booth - you'll find the times at http://wiki.linuxtag.org/w/fp:ProjectMeetingPoints shortly before LinuxTag starts. I'll probably get some free tickets for LinuxTag - if you want to go to LinuxTag and need one, send me a mail off-list. Regards, Christian Boltz -- [Newbie] und wenn wir wollen, daß er ein brauchbarer Regular wird, dann müssen wir uns den korrekt konfigurieren. Nun leider/zum Glück handelt es um einen Menschen. Da ist es nicht mit "vi /etc/sysconfig/grosshirn" und "rcgehirn reload" getan. [Kristian Koehntopp in suse-linux] |
From: Christian B. <pos...@cb...> - 2013-04-02 19:45:42
|
Hello, Am Freitag, 29. März 2013 schrieb Tanstaafl: > Thanks... but alas, while 'trunk svn 1388' may mean much to you, it > doesn't to me... ;) "trunk" means the latest development version - the code that will become 3.0. > My question is, is this code included in any of the formal stable > releases (2.3.5? 2.3.6?)? If not, will it make it into the next stable > release (presumably 2.3.7)? > > Or is this only in the new 3.x trunk? The 2.3 branch is in maintenance mode (bugfixes only), which means 2.3.x won't get the new vacation.pl features. On the positive side, SVN trunk (which will become 3.0) is quite stable. Everything in the web interface should work (if not, report a bugreport), and the CLI is also getting better (I deleted (!) ~500 lines to complete the create and update commands yesterday ;-) - the other commands may or may not work). I even found some time to handle some long-standing TODOs yesterday ;-) (see the commit mailinglist for details) In other words: feel free to use SVN trunk ;-) BTW, while looking at the random (really!) signature: I'm still looking for someone who can shorten the changelog from 2.3.x to current SVN trunk - are you interested? ;-) (My current draft with 370 lines is probably too long for the average user ;-) Regards, Christian Boltz -- Yes, I know how much devs hate writing documentation... I was a dev. [Carlos E. R. in opensuse-factory] |
From: Tanstaafl <tan...@li...> - 2013-04-02 13:28:21
|
Anyone? On 2013-03-29 2:00 PM, Tanstaafl <tan...@li...> wrote: > Hi Jan, > > Thanks... but alas, while 'trunk svn 1388' may mean much to you, it > doesn't to me... ;) > > My question is, is this code included in any of the formal stable > releases (2.3.5? 2.3.6?)? If not, will it make it into the next stable > release (presumably 2.3.7)? > > Or is this only in the new 3.x trunk? > > Thanks again for your efforts with the patches!! > > On 2013-03-28 5:48 PM, Jan Kruis <pf...@cr...> wrote: >> Hi Charles, >> >> The patch i made is base on the trunk svn 1388 >> >> The adjustment that I made is based on trunk svn 1388. >> The total adjustment contains multiple function but the adjustment for REAL NAME is quite small. >> And as operates as follows. >> If no string in the name is entered, the emailadres of the user used. >> Ginderdog in his email of 14 March has coding out the piece for "realname" of the total code. |
From: Tanstaafl <tan...@li...> - 2013-03-29 18:00:49
|
Hi Jan, Thanks... but alas, while 'trunk svn 1388' may mean much to you, it doesn't to me... ;) My question is, is this code included in any of the formal stable releases (2.3.5? 2.3.6?)? If not, will it make it into the next stable release (presumably 2.3.7)? Or is this only in the new 3.x trunk? Thanks again for your efforts with the patches!! On 2013-03-28 5:48 PM, Jan Kruis <pf...@cr...> wrote: > Hi Charles, > > The patch i made is base on the trunk svn 1388 > > The adjustment that I made is based on trunk svn 1388. > The total adjustment contains multiple function but the adjustment for REAL NAME is quite small. > And as operates as follows. > If no string in the name is entered, the emailadres of the user used. > Ginderdog in his email of 14 March has coding out the piece for "realname" of the total code. |
From: Jan K. <pf...@cr...> - 2013-03-28 21:49:50
|
Hi Charles, The patch i made is base on the trunk svn 1388 The adjustment that I made is based on trunk svn 1388. The total adjustment contains multiple function but the adjustment for REAL NAME is quite small. And as operates as follows. If no string in the name is entered, the emailadres of the user used. Ginderdog in his email of 14 March has coding out the piece for "realname" of the total code. Regards Jan Kruis Op 28 mrt 2013, om 18:32 heeft Tanstaafl het volgende geschreven: > Sorry, I should have included his earlier responses in that email... > > The problem is I have no clue how to look for it to see if it is there, > or be able to tell what version it is in. I know for sure it isn't in > 2.3.4 (what I'm on now). If it is in 2.3.6, that would be all the reason > I'd need to upgrade this weekend. > > I haven't really worried about running a slightly older version because > mine is only accessible from my workstation IP on a local network. > > Thanks Rudi... > > On 2013-03-28 1:22 PM, Rudi Floren <rud...@go...> wrote: >> Jan K. already posted a patch. i'm not sure if somone already pulled it >> into SVN. >> >> >> Am 28.03.2013 18:12, schrieb Tanstaafl: >>> I'd be ok with that - and we could have big scary warnings to the admin >>> about making sure that the real names in the DB are clean... >>> >>> So, that would mean it is just defining the variable in the SQL query >>> that queries for the vacation message, then modifying the script that >>> generates the email to use it... right? >>> >>> Doesn't *sound* too hard (for someone who does this stuff for a >>> living)... ;) >>> >>> On 2013-03-28 12:55 PM, Rudi Floren <rud...@go...> wrote: >>>> I think it would be better to get the Real Name from Database. >>>> This way the User (Mailbox owner) can define his name which will be >>>> display in vacation message. >>>> >>>> Your way the Real Name in the vacation mail is set by the sender of the >>>> original mail. I think this isnt a good behavior. >>>> >>>> Rudi >>>> >>>> Am 28.03.2013 17:36, schrieb Tanstaafl: >>>>> Revisiting this now that we have nicely solved the multi-string >>>>> capability for the noreply function... >>>>> >>>>> So... >>>>> >>>>> Since the 3rd line in the vacation.log for a vacation transaction is >>>>> using the RFC 822 Style (contains the "Real Name") for the 'To' header: >>>>> >>>>>>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:587 main:: - Email headers have to: '"Real Name" <val...@ex...>' and From: '"ge...@me..." <ge...@me...>' >>>>> Doesn't this mean that it is *already available* as a variable, since >>>>> the logger is obviously using it? If so, then would some kind soul who >>>>> knows the code well enough to know where/what to look for, please take a >>>>> peek and see what the variable name is so that we can simply modify the >>>>> script that generates the vacation email to use it, resulting in the >>>>> above line being: >>>>> >>>>>>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:429 main::send_vacation_email - Will send vacation response for <0ed...@me...>: FROM: '"Real Name" <val...@ex...>' (orig_to: val...@ex...), TO: mai...@me...; VACATION SUBJECT: Out of Office ; VACATION BODY: Vacation message body test. >>>>> Thanks! >>>>> >>>>> Charles >>>>> >>>>> >>>>> On 2013-03-12 2:53 PM, Tanstaafl <tan...@li...> wrote: >>>>>> Hello all, >>>>>> >>>>>> I have a Feature Request for this at: >>>>>> >>>>>> https://sourceforge.net/p/postfixadmin/feature-requests/30/ >>>>>> >>>>>> To put it simply, I want the vacation message to show as: >>>>>> >>>>>> From: "Real Name" <em...@ex...> >>>>>> >>>>>> not just >>>>>> >>>>>> em...@ex... > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postfixadmin-devel mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel |
From: Tanstaafl <tan...@li...> - 2013-03-28 17:33:08
|
Sorry, I should have included his earlier responses in that email... The problem is I have no clue how to look for it to see if it is there, or be able to tell what version it is in. I know for sure it isn't in 2.3.4 (what I'm on now). If it is in 2.3.6, that would be all the reason I'd need to upgrade this weekend. I haven't really worried about running a slightly older version because mine is only accessible from my workstation IP on a local network. Thanks Rudi... On 2013-03-28 1:22 PM, Rudi Floren <rud...@go...> wrote: > Jan K. already posted a patch. i'm not sure if somone already pulled it > into SVN. > > > Am 28.03.2013 18:12, schrieb Tanstaafl: >> I'd be ok with that - and we could have big scary warnings to the admin >> about making sure that the real names in the DB are clean... >> >> So, that would mean it is just defining the variable in the SQL query >> that queries for the vacation message, then modifying the script that >> generates the email to use it... right? >> >> Doesn't *sound* too hard (for someone who does this stuff for a >> living)... ;) >> >> On 2013-03-28 12:55 PM, Rudi Floren <rud...@go...> wrote: >>> I think it would be better to get the Real Name from Database. >>> This way the User (Mailbox owner) can define his name which will be >>> display in vacation message. >>> >>> Your way the Real Name in the vacation mail is set by the sender of the >>> original mail. I think this isnt a good behavior. >>> >>> Rudi >>> >>> Am 28.03.2013 17:36, schrieb Tanstaafl: >>>> Revisiting this now that we have nicely solved the multi-string >>>> capability for the noreply function... >>>> >>>> So... >>>> >>>> Since the 3rd line in the vacation.log for a vacation transaction is >>>> using the RFC 822 Style (contains the "Real Name") for the 'To' header: >>>> >>>>>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:587 main:: - Email headers have to: '"Real Name" <val...@ex...>' and From: '"ge...@me..." <ge...@me...>' >>>> Doesn't this mean that it is *already available* as a variable, since >>>> the logger is obviously using it? If so, then would some kind soul who >>>> knows the code well enough to know where/what to look for, please take a >>>> peek and see what the variable name is so that we can simply modify the >>>> script that generates the vacation email to use it, resulting in the >>>> above line being: >>>> >>>>>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:429 main::send_vacation_email - Will send vacation response for <0ed...@me...>: FROM: '"Real Name" <val...@ex...>' (orig_to: val...@ex...), TO: mai...@me...; VACATION SUBJECT: Out of Office ; VACATION BODY: Vacation message body test. >>>> Thanks! >>>> >>>> Charles >>>> >>>> >>>> On 2013-03-12 2:53 PM, Tanstaafl <tan...@li...> wrote: >>>>> Hello all, >>>>> >>>>> I have a Feature Request for this at: >>>>> >>>>> https://sourceforge.net/p/postfixadmin/feature-requests/30/ >>>>> >>>>> To put it simply, I want the vacation message to show as: >>>>> >>>>> From: "Real Name" <em...@ex...> >>>>> >>>>> not just >>>>> >>>>> em...@ex... |
From: Tanstaafl <tan...@li...> - 2013-03-28 17:29:04
|
Hi Rudi, Responses inline... On 2013-03-28 1:06 PM, Rudi Floren <rud...@go...> wrote: > Hello Tanstaafl, > > i think the best way to implement this is to set vacation for every user > by an admin. But this just wouldn't be practical - unless you're talking about a new setting to do just that? Which is basically what my simplistic example was intended to do... > Anyway you have to activate vacation for each user so that mails to > us...@ab... will be relayed to us...@va... Ok, I can see I missed some settings that would be needed... So, why not just relay them all to a generic dom...@va.... Again, nothing needs to be personalized, so all responses (that get sent) could show as: From: "Company Responder" <dom...@do...> So you'd now need: our $domain_reply = 0; our $domain_reply_local = 'domain-responder' our $domain_reply_content = '/etc/postfixadmin/domain_reply.txt' Anything else I missed? These could all (eventually, maybe) be added to the GUI on the 'Edit a domain' page... > Rudi > Am 28.03.2013 18:00, schrieb Tanstaafl: >> Existing Feature Request: >> https://sourceforge.net/p/postfixadmin/feature-requests/102/ >> >> Other than getting the RFC 822 Style sender address for the vacation >> message (thread re-started about this a few minutes ago), this is the >> only other thing I'd like to get working. >> >> For now, it would be ok if this was something that I had to enable >> manually... >> >> What I'd like to do is have the ability to enable/disable a generic, >> company-wide auto-response (for holiday closings, etc), that works the >> same as the individual one with two important differences: >> >> 1. It works for any *valid* user at the domain, and >> >> 2. It is a generic message, not personalized in any way. >> >> It should be subject to the same checks and balances as normal vacation >> messages (ie, alias checks, $interval checks (aargh, guess this will >> entail a new db field?), test against the new $noreply_pattern matches, >> etc). >> >> Something like: >> >> # Send a generic vacation response to any/all emails to >> # valid recipients, subject to the same exceptions as >> # normal user vacation messages. This option over-rides >> # and supercedes individual user responses. >> # Create and/or populate $domain_reply_content and change >> # $domain_reply to 1 to enable this feature. >> our $domain_reply = 0; >> our $domain_reply_content = '/etc/postfixadmin/domain_reply.txt' >> >> Then of course the hard part is the code to generate the generic message >> instead of the personalize one. >> >> Comments anyone? |
From: Rudi F. <rud...@go...> - 2013-03-28 17:22:55
|
Jan K. already posted a patch. i'm not sure if somone already pulled it into SVN. Am 28.03.2013 18:12, schrieb Tanstaafl: > I'd be ok with that - and we could have big scary warnings to the admin > about making sure that the real names in the DB are clean... > > So, that would mean it is just defining the variable in the SQL query > that queries for the vacation message, then modifying the script that > generates the email to use it... right? > > Doesn't *sound* too hard (for someone who does this stuff for a > living)... ;) > > On 2013-03-28 12:55 PM, Rudi Floren <rud...@go...> wrote: >> I think it would be better to get the Real Name from Database. >> This way the User (Mailbox owner) can define his name which will be >> display in vacation message. >> >> Your way the Real Name in the vacation mail is set by the sender of the >> original mail. I think this isnt a good behavior. >> >> Rudi >> >> Am 28.03.2013 17:36, schrieb Tanstaafl: >>> Revisiting this now that we have nicely solved the multi-string >>> capability for the noreply function... >>> >>> So... >>> >>> Since the 3rd line in the vacation.log for a vacation transaction is >>> using the RFC 822 Style (contains the "Real Name") for the 'To' header: >>> >>>>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:587 main:: - Email headers have to: '"Real Name" <val...@ex...>' and From: '"ge...@me..." <ge...@me...>' >>> Doesn't this mean that it is *already available* as a variable, since >>> the logger is obviously using it? If so, then would some kind soul who >>> knows the code well enough to know where/what to look for, please take a >>> peek and see what the variable name is so that we can simply modify the >>> script that generates the vacation email to use it, resulting in the >>> above line being: >>> >>>>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:429 main::send_vacation_email - Will send vacation response for <0ed...@me...>: FROM: '"Real Name" <val...@ex...>' (orig_to: val...@ex...), TO: mai...@me...; VACATION SUBJECT: Out of Office ; VACATION BODY: Vacation message body test. >>> Thanks! >>> >>> Charles >>> >>> >>> On 2013-03-12 2:53 PM, Tanstaafl <tan...@li...> wrote: >>>> Hello all, >>>> >>>> I have a Feature Request for this at: >>>> >>>> https://sourceforge.net/p/postfixadmin/feature-requests/30/ >>>> >>>> To put it simply, I want the vacation message to show as: >>>> >>>> From: "Real Name" <em...@ex...> >>>> >>>> not just >>>> >>>> em...@ex... > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postfixadmin-devel mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel |
From: Tanstaafl <tan...@li...> - 2013-03-28 17:13:24
|
I'd be ok with that - and we could have big scary warnings to the admin about making sure that the real names in the DB are clean... So, that would mean it is just defining the variable in the SQL query that queries for the vacation message, then modifying the script that generates the email to use it... right? Doesn't *sound* too hard (for someone who does this stuff for a living)... ;) On 2013-03-28 12:55 PM, Rudi Floren <rud...@go...> wrote: > I think it would be better to get the Real Name from Database. > This way the User (Mailbox owner) can define his name which will be > display in vacation message. > > Your way the Real Name in the vacation mail is set by the sender of the > original mail. I think this isnt a good behavior. > > Rudi > > Am 28.03.2013 17:36, schrieb Tanstaafl: >> Revisiting this now that we have nicely solved the multi-string >> capability for the noreply function... >> >> So... >> >> Since the 3rd line in the vacation.log for a vacation transaction is >> using the RFC 822 Style (contains the "Real Name") for the 'To' header: >> >>>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:587 main:: - Email headers have to: '"Real Name" <val...@ex...>' and From: '"ge...@me..." <ge...@me...>' >> Doesn't this mean that it is *already available* as a variable, since >> the logger is obviously using it? If so, then would some kind soul who >> knows the code well enough to know where/what to look for, please take a >> peek and see what the variable name is so that we can simply modify the >> script that generates the vacation email to use it, resulting in the >> above line being: >> >>>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:429 main::send_vacation_email - Will send vacation response for <0ed...@me...>: FROM: '"Real Name" <val...@ex...>' (orig_to: val...@ex...), TO: mai...@me...; VACATION SUBJECT: Out of Office ; VACATION BODY: Vacation message body test. >> Thanks! >> >> Charles >> >> >> On 2013-03-12 2:53 PM, Tanstaafl <tan...@li...> wrote: >>> Hello all, >>> >>> I have a Feature Request for this at: >>> >>> https://sourceforge.net/p/postfixadmin/feature-requests/30/ >>> >>> To put it simply, I want the vacation message to show as: >>> >>> From: "Real Name" <em...@ex...> >>> >>> not just >>> >>> em...@ex... |
From: Rudi F. <rud...@go...> - 2013-03-28 17:06:38
|
Hello Tanstaafl, i think the best way to implement this is to set vacation for every user by an admin. Anyway you have to activate vacation for each user so that mails to us...@ab... will be relayed to us...@va... Rudi Am 28.03.2013 18:00, schrieb Tanstaafl: > Existing Feature Request: > https://sourceforge.net/p/postfixadmin/feature-requests/102/ > > Other than getting the RFC 822 Style sender address for the vacation > message (thread re-started about this a few minutes ago), this is the > only other thing I'd like to get working. > > For now, it would be ok if this was something that I had to enable > manually... > > What I'd like to do is have the ability to enable/disable a generic, > company-wide auto-response (for holiday closings, etc), that works the > same as the individual one with two important differences: > > 1. It works for any *valid* user at the domain, and > > 2. It is a generic message, not personalized in any way. > > It should be subject to the same checks and balances as normal vacation > messages (ie, alias checks, $interval checks (aargh, guess this will > entail a new db field?), test against the new $noreply_pattern matches, > etc). > > Something like: > > # Send a generic vacation response to any/all emails to > # valid recipients, subject to the same exceptions as > # normal user vacation messages. This option over-rides > # and supercedes individual user responses. > # Create and/or populate $domain_reply_content and change > # $domain_reply to 1 to enable this feature. > our $domain_reply = 0; > our $domain_reply_content = '/etc/postfixadmin/domain_reply.txt' > > Then of course the hard part is the code to generate the generic message > instead of the personalize one. > > Comments anyone? > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postfixadmin-devel mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel |
From: Tanstaafl <tan...@li...> - 2013-03-28 17:00:59
|
Existing Feature Request: https://sourceforge.net/p/postfixadmin/feature-requests/102/ Other than getting the RFC 822 Style sender address for the vacation message (thread re-started about this a few minutes ago), this is the only other thing I'd like to get working. For now, it would be ok if this was something that I had to enable manually... What I'd like to do is have the ability to enable/disable a generic, company-wide auto-response (for holiday closings, etc), that works the same as the individual one with two important differences: 1. It works for any *valid* user at the domain, and 2. It is a generic message, not personalized in any way. It should be subject to the same checks and balances as normal vacation messages (ie, alias checks, $interval checks (aargh, guess this will entail a new db field?), test against the new $noreply_pattern matches, etc). Something like: # Send a generic vacation response to any/all emails to # valid recipients, subject to the same exceptions as # normal user vacation messages. This option over-rides # and supercedes individual user responses. # Create and/or populate $domain_reply_content and change # $domain_reply to 1 to enable this feature. our $domain_reply = 0; our $domain_reply_content = '/etc/postfixadmin/domain_reply.txt' Then of course the hard part is the code to generate the generic message instead of the personalize one. Comments anyone? |
From: Rudi F. <rud...@go...> - 2013-03-28 16:55:53
|
I think it would be better to get the Real Name from Database. This way the User (Mailbox owner) can define his name which will be display in vacation message. Your way the Real Name in the vacation mail is set by the sender of the original mail. I think this isnt a good behavior. Rudi Am 28.03.2013 17:36, schrieb Tanstaafl: > Revisiting this now that we have nicely solved the multi-string > capability for the noreply function... > > So... > > Since the 3rd line in the vacation.log for a vacation transaction is > using the RFC 822 Style (contains the "Real Name") for the 'To' header: > >>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:587 main:: - Email headers have to: '"Real Name" <val...@ex...>' and From: '"ge...@me..." <ge...@me...>' > Doesn't this mean that it is *already available* as a variable, since > the logger is obviously using it? If so, then would some kind soul who > knows the code well enough to know where/what to look for, please take a > peek and see what the variable name is so that we can simply modify the > script that generates the vacation email to use it, resulting in the > above line being: > >>> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:429 main::send_vacation_email - Will send vacation response for <0ed...@me...>: FROM: '"Real Name" <val...@ex...>' (orig_to: val...@ex...), TO: mai...@me...; VACATION SUBJECT: Out of Office ; VACATION BODY: Vacation message body test. > Thanks! > > Charles > > > On 2013-03-12 2:53 PM, Tanstaafl <tan...@li...> wrote: >> Hello all, >> >> I have a Feature Request for this at: >> >> https://sourceforge.net/p/postfixadmin/feature-requests/30/ >> >> To put it simply, I want the vacation message to show as: >> >> From: "Real Name" <em...@ex...> >> >> not just >> >> em...@ex... > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > _______________________________________________ > Postfixadmin-devel mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel |
From: Tanstaafl <tan...@li...> - 2013-03-28 16:37:42
|
Revisiting this now that we have nicely solved the multi-string capability for the noreply function... So... Since the 3rd line in the vacation.log for a vacation transaction is using the RFC 822 Style (contains the "Real Name") for the 'To' header: >> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:587 main:: - Email headers have to: '"Real Name" <val...@ex...>' and From: '"ge...@me..." <ge...@me...>' Doesn't this mean that it is *already available* as a variable, since the logger is obviously using it? If so, then would some kind soul who knows the code well enough to know where/what to look for, please take a peek and see what the variable name is so that we can simply modify the script that generates the vacation email to use it, resulting in the above line being: >> 2013/03/11 07:51:39 DEBUG> /var/spool/vacation/vacation.pl:429 main::send_vacation_email - Will send vacation response for <0ed...@me...>: FROM: '"Real Name" <val...@ex...>' (orig_to: val...@ex...), TO: mai...@me...; VACATION SUBJECT: Out of Office ; VACATION BODY: Vacation message body test. Thanks! Charles On 2013-03-12 2:53 PM, Tanstaafl <tan...@li...> wrote: > Hello all, > > I have a Feature Request for this at: > > https://sourceforge.net/p/postfixadmin/feature-requests/30/ > > To put it simply, I want the vacation message to show as: > > From: "Real Name" <em...@ex...> > > not just > > em...@ex... |
From: Tanstaafl <tan...@li...> - 2013-03-27 12:26:23
|
On 2013-03-26 5:47 PM, Rudi Floren <rud...@go...> wrote: > Here are my changes. > https://github.com/valkum/postfixadmin/commit/cdcccddbe2e1d6758cd63899e7b8973156f1412a#VIRTUAL_VACATION/vacation.pl > My Version uses the same regex pattern as in prev. versions. > With your Version mails from fac...@ex... won't be vacationed > (is this a word??). But it could be an valid address e.g. for facebook > wins and notifacations by a real person. Excellent, much better (and shorter) descriptive text. I'm a bit too long winded sometimes, comes from too much writing step-by-step instructions for end users who have trouble finding the 'Start' button in Windows. ;) Thanks Rudi. As for the list of default strings - in my opinion, the kind of emails you describe shouldn't be responded to by the vacation script.I think only real emails, from real people (not automated notification systems, of any kind) should be replied to. Of course, I am fine if the decision is to leave the defaults as they are now, as long as I can change mine... :) Thanks again Rudi! So now the next release of postfixadmin 2.3.x will contain these changes, correct? One less thing to worry about/remember to fix after updating... |
From: Rudi F. <rud...@go...> - 2013-03-26 21:47:05
|
Here are my changes. https://github.com/valkum/postfixadmin/commit/cdcccddbe2e1d6758cd63899e7b8973156f1412a#VIRTUAL_VACATION/vacation.pl My Version uses the same regex pattern as in prev. versions. With your Version mails from fac...@ex... won't be vacationed (is this a word??). But it could be an valid address e.g. for facebook wins and notifacations by a real person. Rudi Am Dienstag, 26. März 2013 22:09:33 schrieb Tanstaafl: > Crap - I added the wrong descriptive text... > > Here's a better version... > > On 2013-03-26 4:47 PM, Tanstaafl <tan...@li...> wrote: >> On 2013-03-26 7:20 AM, David Goodwin <da...@co...> wrote: >>> Hi, >>> >>> I'd probably merge it for you >>> >>> Ideally make the patch against the vacation.pl which is in trunk. >>> That would make my life easiest. >> >> Ok, great, thanks David. >> >> Actually, I see that Rudi did already merge the prior version that had >> both a new option, a new variable, and added a third test. >> >> I changed this to just a single new variable, and a single test. >> >> See what you think (patch attached, diffed against vacation.pl in >> trunk)... >> >> Thanks, >> >> Charles > > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > > > _______________________________________________ > Postfixadmin-devel mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel |
From: Tanstaafl <tan...@li...> - 2013-03-26 21:10:00
|
Crap - I added the wrong descriptive text... Here's a better version... On 2013-03-26 4:47 PM, Tanstaafl <tan...@li...> wrote: > On 2013-03-26 7:20 AM, David Goodwin <da...@co...> wrote: >> Hi, >> >> I'd probably merge it for you >> >> Ideally make the patch against the vacation.pl which is in trunk. >> That would make my life easiest. > > Ok, great, thanks David. > > Actually, I see that Rudi did already merge the prior version that had > both a new option, a new variable, and added a third test. > > I changed this to just a single new variable, and a single test. > > See what you think (patch attached, diffed against vacation.pl in trunk)... > > Thanks, > > Charles |
From: Tanstaafl <tan...@li...> - 2013-03-26 20:54:43
|
On 2013-03-26 4:51 PM, Tanstaafl <tan...@li...> wrote: > By the way... > > I though the vacation.pl in trunk had the new options in it for start > and stop dates? I didn't see that in there anywhere... Never mind, I see it added back in 2009... and was just an update to the sql query... |