postfixadmin-devel — Postfix Admin development talk - users are also welcome

Re: [Postfixadmin-devel] Request for help to create bulk email address

[Christian B. <pos...@cb...>]

Hello,

Am Donnerstag, 29. Dezember 2011 schrieb Sonam Penjor:
> How about using set_time_limit (0)
> 
> In order to execute the CSV file...

You can try it, but I wouldn't be surprised if suhosin stops you from 
doing that ;-)


Regards,

Christian Boltz
-- 
> > [OOo splash] kroete should turn their eyes during load ;-)
> It should roll with his eyes if user is doing something completely
> stupid.
...like touching the mouse, or do you know even better heuristics?
[> Robert Schiele and Hans-Peter Jansen]

Re: [Postfixadmin-devel] Request for help to create bulk email address

[Sonam P. <s_p...@ru...>]

Hello,

How about using set_time_limit (0)

In order to execute the CSV file...


sonam

On 12/29/2011 6:48 AM, Christian Boltz wrote:
> Hello,
>
> Am Mittwoch, 28. Dezember 2011 schrieben Sie:
>> Whats about saving the validated csv To a tmp dir in fs. In the next
>> step the csv Form the Fa is processed.
> That would work (given we have a writeable tempdir, find a non-
> conflicting filename, ...)
>
> In other words: storing everything in the session is easier ;-)
>
> _if_ the session explodes one day, we can change it - but until then, we
> can use the easy solution.
>
>> For more security wie can add
>> some security tokens to forms.
> Well, a token might make sense - not security wise, but to avoid
> conflicts if a user opens two tabs and uses the bulk creation in both
> tabs in parallel. (Users sometimes have creative ideas...)
> Especially if we support resuming after max_execution_time timeouts etc.
>
>
> slightly OT: A token might really make sense in the login form, and we
> should also include the session id as hidden field to verify that the
> browser accepts cookies.
>
>
> Regards,
>
> Christian Boltz


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [Postfixadmin-devel] Request for help to create bulk email address

[Christian B. <pos...@cb...>]

Hello,

Am Mittwoch, 28. Dezember 2011 schrieben Sie:
> Whats about saving the validated csv To a tmp dir in fs. In the next
> step the csv Form the Fa is processed. 

That would work (given we have a writeable tempdir, find a non-
conflicting filename, ...)

In other words: storing everything in the session is easier ;-)

_if_ the session explodes one day, we can change it - but until then, we 
can use the easy solution.

> For more security wie can add
> some security tokens to forms.

Well, a token might make sense - not security wise, but to avoid 
conflicts if a user opens two tabs and uses the bulk creation in both 
tabs in parallel. (Users sometimes have creative ideas...)
Especially if we support resuming after max_execution_time timeouts etc.


slightly OT: A token might really make sense in the login form, and we 
should also include the session id as hidden field to verify that the 
browser accepts cookies.


Regards,

Christian Boltz
-- 
Ich habe da eine Theorie: Betriebssysteme melden Fehler und wollen,
dass sie behoben werden. Bei Systemen wie Windows 9x sind die Fehler
wesentlicher Bestandteil und kein Grund, sich Sorgen zu machen.
[Steffen Lauterkorn in suse-linux]

Re: [Postfixadmin-devel] Request for help to create bulk email address

[Christian B. <pos...@cb...>]

Hello,

Am Mittwoch, 28. Dezember 2011 schrieb Rudi Floren:
> Can't you add the csv as hidden form field(s)?

Short answer: No(t really).

Longer answer:

That would mean it _must_ be validated again in the next step, because 
an attacker could use a manipulated form.

I know we are talking about authentificated admins here, but still.
(And there are lots of setups where you can't trust every admin - for 
example, I give my customers admin access for their domains. I'd guess 
none of them knows how to manipulate a form, but if someone finds it out 
(firebug isn't that hard to use), I don't want to be f***ed off ;-)

Not to mention that a hidden form field would mean to send lots of 
useless bytes around the world twice ;-)

> Am 28.12.2011 12:42, schrieb Sonam Penjor:
> > I have completed the validation of the CSV file for bulk email ID
> > creation. I have brown down my works into two parts (for my
> > reference). PART I - upload the csv file and validate the
> > contents (line by line), display the status. PART II - will
> > create the mail box.
> > 
> > So far I completed the PART - I:
> > 1. Uploaded the csv file and validated whether uploaded file is in
> > csv format or other.
> > 2. Validated the username (check whether space exist in between)
> > 2. Check for the existence of username
> > 3. Considered as an error if sl no 1 and 2 exist.

How does your error handling look like? Abort if at least one problem is 
found? Or just skip the invalid and existing mailboxes?

> > 4. Total mail box ready for creation (number of correct entries 
> > without the entry row of sl 1 and sl 2)
> > 5. Displayed the status

Does this mean you'll display a page with sections like
- The following mailboxes already exist and will be skipped:
- The following usernames are invalid and will be skipped:
- The following mailboxes will be created:

> > After displaying the status I am requesting admin  whether to
> > create (process) or to cancel.
> >
> > Now, to process, there will be  post method again where the
> > uploaded values or contents from PART I will no longer exist. I
> > am just wondering whether I should create temporary table or file
> > or use SESSION to store all the data collected from PART I for
> > the PART II purposes.

I would use the session - it is easy to use, and we get an automatic 
cleanup by PHP (at logout or session timeout) for free.
In other words: handling a temporary table or file causes lots of 
additional work without any benefit.

If you implement it in a nice way (I'd say: after creating a mailbox, 
delete it from the list in the session), the code can even continue with 
the remaining mailboxes after it was stopped (because of PHP 
max_execution_time etc.)

Combined with some AJAX, you could exit the script yourself some seconds 
before max_execution_time and call it again. This would even allow you 
to draw a nice progress bar ;-)  (That said: please use lightweight code 
and don't introduce a big JS framework just for doing this - otherwise 
I'll recommend to just use self-redirects in an <iframe> *g*  Hmm, 
thinking about it, why not use <iframe> self-redirects from the 
beginning?)


Oh, BTW: If you send your code early, you'll get an early review and 
changes (if needed) will be easier.


Regards,

Christian Boltz
-- 
|#|    Die drei wichtigsten Tugenden eines Programmierers:
|#|         Faulheit, Ungeduld und Selbstüberschätzung

Re: [Postfixadmin-devel] Request for help to create bulk email address

[Rudi F. <rud...@go...>]

Can't you add the csv as hidden form field(s)?


Am 28.12.2011 12:42, schrieb Sonam Penjor:
> Hello,
>
> I have completed the validation of the CSV file for bulk email ID
> creation. I have brown down my works into two parts (for my reference).
> PART I - upload the csv file and validate the contents (line by line),
> display the status. PART II - will create the mail box.
>
> So far I completed the PART - I:
> 1. Uploaded the csv file and validated whether uploaded file is in csv
> format or other.
> 2. Validated the username (check whether space exist in between)
> 2. Check for the existence of username
> 3. Considered as an error if sl no 1 and 2 exist.
> 4. Total mail box ready for creation (number of correct entries  without
> the entry row of sl 1 and sl 2)
> 5. Displayed the status
>
> After displaying the status I am requesting admin  whether to create
> (process) or to cancel.
>
> Now, to process, there will be  post method again where the uploaded
> values or contents from PART I will no longer exist. I am just wondering
> whether I should create temporary table or file or use SESSION to store
> all the data collected from PART I for the PART II purposes.
>
> I would appreciate for your comments and advice
>
> Thank you
>
> Sonam Penjor
>
>
>
>

[Postfixadmin-devel] Request for help to create bulk email address

[Sonam P. <s_p...@ru...>]

Hello,

I have completed the validation of the CSV file for bulk email ID 
creation. I have brown down my works into two parts (for my reference). 
PART I - upload the csv file and validate the contents (line by line), 
display the status. PART II - will create the mail box.

So far I completed the PART - I:
1. Uploaded the csv file and validated whether uploaded file is in csv 
format or other.
2. Validated the username (check whether space exist in between)
2. Check for the existence of username
3. Considered as an error if sl no 1 and 2 exist.
4. Total mail box ready for creation (number of correct entries  without 
the entry row of sl 1 and sl 2)
5. Displayed the status

After displaying the status I am requesting admin  whether to create  
(process) or to cancel.

Now, to process, there will be  post method again where the uploaded 
values or contents from PART I will no longer exist. I am just wondering 
whether I should create temporary table or file or use SESSION to store 
all the data collected from PART I for the PART II purposes.

I would appreciate for your comments and advice

Thank you

Sonam Penjor




-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [Postfixadmin-devel] Request help/comment on Feature Requests-2813224 : End user customization of header strings for vacation

[Tanstaafl <tan...@li...>]

On 2011-12-15 3:27 PM, Christian Boltz <pos...@cb...> wrote:
> Hello,
>
> Am Donnerstag, 15. Dezember 2011 schrieb Tanstaafl:
>> I'd appreciate some comments/replies on this Feature Request for a
>> documented way to easily add new from/mailfrom strings that will cause
>> the vacation message to NOT be sent...
>>
>> I have seen numerous vacation messages sent that should NOT be sent
>> (one example is documented on the FR)...
>>
>> https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813224&g
>> roup_id=191583
>
> Have a look at vacation.pl around line 558 to 569. There are lines like
> (broken into multiple lines for better readability)
>
>      elsif (/^List\-(Id|Post|Unsubscribe):/i) {
>          $logger->debug("List-$1: found; exiting");
>          exit (0);
>      }
>
> You can add similar lines there, for example
>
>      elsif (/^autoresponders-are:\s+evil/i) {
>          $logger->debug("autoresponders-are: evil found; exiting");
>          exit (0);
>      }
>
> would not respond to mails which have this header:
>      Autoresponders-are: evil

Thanks Christian, but I have tried this about a year ago, but never 
could get it to work (vacation messages would still go out.

> It shouldn't be too hard to make that a config option with an array or
> hash of regular expressions + corresponding log message, and I'll
> happily accept a patch implementing that.

Wish I could, but that would be way beyond my pay grade. ;)

> OTOH, I'm not sure if it is a good idea to make it configureable in the
> web interface. It might sound like a good idea at the first look, but
> IMHO people who can write proper regular expressions are the same people
> who prefer a config file ;-)  - and everybody else could cause some
> breakage by wrong regular expressions.

I agree regexes are easily messed up, which is why I'd like this to be 
in the GUI - to avoid mistakes. I'd like to simply be able to add a text 
string that would be added to a list of 'generic headers' (anything in a 
 From or Envelope header) to not respond to - so if I add the string 
'Autoresponders-are: evil' (minus the quotes), then the GUI would set up 
the regex properly.

Re: [Postfixadmin-devel] Request for help to creating bulk email address

[Christian B. <pos...@cb...>]

Hello,

Am Freitag, 16. Dezember 2011 schrieb Sonam Penjor:
> I have started to add features to creates email id by uploading CSV
> file (bulk).
> I am just wondering how much MB would be suitable for  upload as it
> involves operations: validation, checking of previous email id,
> calculating the quotas and password.
> Although, the upload size can be configured from php.ini file but
> still to perform above operations as especially in my case I have to
> keep in mind the CPU speed and bandwidth.   Any other operations that
> may be required.

As David already mentioned, the php file_upload_size might need some 
tuning. (OTOH, one mailbox means somewhat between 50 and 100 byte in 
CSV, so you'll at least have 2000 mailboxes in 1 MB CSV file. That's a 
lot already ;-)

Another setting that might hit you is the max_execution_time. (You can 
work around it by doing a self-redirect after creating 50 or 100 
mailboxes with ?csvfile=uploaded_file.csv&continue_with_line=51)

You can tune both settings in your PHP configuration, so this shouldn't 
be a real problem.

You might also want to consider the command line client instead of the 
web interface for mass creation of mailboxes.

> I would appreciate for recommendations / comments to move forward.

Most important: Please use the MailboxHandler class (see below for 
details).

create-mailbox.php and edit-mailbox.php are dead code (in maintenance 
mode) and will be deleted sooner or later. Please don't add new features 
to one of those files.

Another important thing is to base your changes on SVN trunk.


At the moment, using MailboxHandler means something like:
   $handler = new MailboxHandler($address);
   if (!MailboxHandler->add($password, $name, $quota, $active, $mail)) {
       die ('creating the mailbox failed - ' . $handler->errormsg);
   }

$address is the username / mail address
$password should be obvious ;-)
$name is the realname / comment / whatever
$quota means quota in MB
$active is usually just   true
$mail means sending the welcome mail and also should be   true

See scripts/shells/mailbox.php -> AddTask -> __handle() (part of the 
command line client) for a working implementation that uses this class.

Whenever I have some time [1], I'll update MailboxHandler to use the 
function names etc. I'm already using in DomainHandler and AdminHandler 
(see edit.php for working implementation). This means you'll need some 
small changes in your script on how you call MailboxHandler, but that 
will be quite easy.


Regards,

Christian Boltz

[1] If you want to update MailboxHandler to be based on PFAHandler, of 
    course nobody will stop you ;-)

-- 
Intel kauft McAfee. [...] Der Synergieeffekt ist offensichtlich. 
McAfee macht Computer so langsam, dass man eine neue Intel-CPU braucht.
Ähnliche Synergieeffekte gibt es zwischen [...] Computerspielen und
Grafikkartenbedarf und zwischen Webforen und Tischkantenbedarf.
[http://blog.fefe.de/?ts=b2935cd1]

Re: [Postfixadmin-devel] Request for help to creating bulk email address

[David G. <da...@co...>]

On 16 Dec 2011, at 05:36, Sonam Penjor wrote:

> Hi guys,
> 
> I have started to add features to creates email id by uploading CSV file 
> (bulk).
> I am just wondering how much MB would be suitable for  upload as it 
> involves operations: validation, checking of previous email id, 
> calculating the quotas and password.

Is this MB in terms of memory usage within PHP while it processes the upload, or MB in terms of file size for how large your CSV may be?

> Although, the upload size can be configured from php.ini file but still 
> to perform above operations as especially in my case I have to keep in 
> mind the CPU speed and bandwidth.   Any other operations that may be 
> required.
> 

I can't see how even a 20Mb CSV file would cause any significant problems on a reasonably specified server. Opening the CSV file and reading it one line at a time using fgetcsv() and then presumably doing around 3-5 database queries (is it there? update? insert? delete?) should really not be a problem.

I think all recent versions of PHP default to a 128mb memory limit should should be fine. I have a feeling the file_upload_size thing defaults to about 2mb, which may be too small.


David.

[Postfixadmin-devel] Request for help to creating bulk email address

[Sonam P. <s_p...@ru...>]

Hi guys,

I have started to add features to creates email id by uploading CSV file 
(bulk).
I am just wondering how much MB would be suitable for  upload as it 
involves operations: validation, checking of previous email id, 
calculating the quotas and password.
Although, the upload size can be configured from php.ini file but still 
to perform above operations as especially in my case I have to keep in 
mind the CPU speed and bandwidth.   Any other operations that may be 
required.

I would appreciate for recommendations / comments to move forward.


Thanks

Sonam

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [Postfixadmin-devel] Request help/comment on Feature Requests-2813224 : End user customization of header strings for vacation

[Robert S. <ro...@sc...>]

Am 15.12.2011 21:27, schrieb Christian Boltz:
> Hello,
> 
> Am Donnerstag, 15. Dezember 2011 schrieb Tanstaafl:
>> I'd appreciate some comments/replies on this Feature Request for a
>> documented way to easily add new from/mailfrom strings that will cause
>> the vacation message to NOT be sent...
>>
>> I have seen numerous vacation messages sent that should NOT be sent
>> (one example is documented on the FR)...
>>
>> https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813224&g
>> roup_id=191583
> 
> Have a look at vacation.pl around line 558 to 569. There are lines like
> (broken into multiple lines for better readability)
> 
>     elsif (/^List\-(Id|Post|Unsubscribe):/i) { 
>         $logger->debug("List-$1: found; exiting"); 
>         exit (0); 
>     }
> 
> You can add similar lines there, for example
> 
>     elsif (/^autoresponders-are:\s+evil/i) { 
>         $logger->debug("autoresponders-are: evil found; exiting"); 
>         exit (0); 
>     }
> 
> would not respond to mails which have this header:
>     Autoresponders-are: evil
> 
> It shouldn't be too hard to make that a config option with an array or 
> hash of regular expressions + corresponding log message, and I'll 
> happily accept a patch implementing that.
> 
> OTOH, I'm not sure if it is a good idea to make it configureable in the 
> web interface. It might sound like a good idea at the first look, but 
> IMHO people who can write proper regular expressions are the same people 
> who prefer a config file ;-)  - and everybody else could cause some 
> breakage by wrong regular expressions.
> 
> 
> Regards,
> 
> Christian Boltz

as note, it might be a better alternative
to use sieve ,if possible, to prefilter before vaccation
for sure ,a complete other solution
-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Postfixadmin-devel] Request help/comment on Feature Requests-2813224 : End user customization of header strings for vacation

[Christian B. <pos...@cb...>]

Hello,

Am Donnerstag, 15. Dezember 2011 schrieb Tanstaafl:
> I'd appreciate some comments/replies on this Feature Request for a
> documented way to easily add new from/mailfrom strings that will cause
> the vacation message to NOT be sent...
> 
> I have seen numerous vacation messages sent that should NOT be sent
> (one example is documented on the FR)...
> 
> https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813224&g
> roup_id=191583

Have a look at vacation.pl around line 558 to 569. There are lines like
(broken into multiple lines for better readability)

    elsif (/^List\-(Id|Post|Unsubscribe):/i) { 
        $logger->debug("List-$1: found; exiting"); 
        exit (0); 
    }

You can add similar lines there, for example

    elsif (/^autoresponders-are:\s+evil/i) { 
        $logger->debug("autoresponders-are: evil found; exiting"); 
        exit (0); 
    }

would not respond to mails which have this header:
    Autoresponders-are: evil

It shouldn't be too hard to make that a config option with an array or 
hash of regular expressions + corresponding log message, and I'll 
happily accept a patch implementing that.

OTOH, I'm not sure if it is a good idea to make it configureable in the 
web interface. It might sound like a good idea at the first look, but 
IMHO people who can write proper regular expressions are the same people 
who prefer a config file ;-)  - and everybody else could cause some 
breakage by wrong regular expressions.


Regards,

Christian Boltz
-- 
Sieh an,  ein Dichter und Denker,  obwohl er sicherlich nicht
mehr ganz dicht ist und auch nicht mehr oft denkt, sonst wäre
er ja nicht bei uns gelandet ;D    [Alex Klein in suse-linux]

[Postfixadmin-devel] Request help/comment on Feature Requests-2813224 : End user customization of header strings for vacation

[Tanstaafl <tan...@li...>]

Hi guys,

I'd appreciate some comments/replies on this Feature Request for a 
documented way to easily add new from/mailfrom strings that will cause 
the vacation message to NOT be sent...

I have seen numerous vacation messages sent that should NOT be sent (one 
example is documented on the FR)...

https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813224&group_id=191583

Thanks,

Charles

Re: [Postfixadmin-devel] Vacation autoreply not delivering to sender

[Christian B. <pos...@cb...>]

Hello,

(you need to subscribe to the mailinglist before sending a mail to it. 
I just noticed your mail in the moderation queue. I don't quote 
everything - for example, I skip your database password ;-) and the non-
config part of vacation.pl you included)

Am Donnerstag, 8. Dezember 2011 schrieb Deee Veeee:
> I recently configured postfixadmin on my email server, and although I
> am not receiving errors the configuration does not seem to be working
> as senders are not receiving the autoreply for users configured with
> vacation turned on.  I have included log information and postconf in
> the pastebin link below.  My configuration consists of a postfix
> gateway configured with amavis, clamav, and spamassassin filtering
> all incoming external email and relaying it to my IMAP server which
> has postfixadmin installed.  Any user configured with vacation turned
> on within the internal server receives all internal and external
> email, however, senders do not receive the out of office reply. 

> http://pastebin.com/7jLNZF1J

The log shows that a copy of the mail is delivered to the vacation.pl 
script (lines 116 and 125), which is already a good start.

> Here is config.inc.php:
...
> $CONF['vacation'] = 'YES';
> $CONF['vacation_domain'] = 'autoreply.sm.coop';
> $CONF['vacation_control'] ='YES';
> $CONF['vacation_control_admin'] = 'YES';

> Here is vacation.pl:

> our $vacation_domain = 'autoreply.sm.coop';
> our $smtp_server = 'localhost';
> our $smtp_server_port = 25;
> our $smtp_auth = undef;
> our $smtp_authid = 'someuser';
> our $smtp_authpwd = 'somepass';
> our $syslog = 1;
> our $logfile='/var/log/vacation.log';
> our $log_level = 2;
> our $log_to_file = 1;

Does vacation.pl have write access to $logfile ? (vacation.pl typically 
runs as user "vacation", not "root".)

> our $interval = 0;

Your configuration looks good, and I'm surprised that you don't see 
anything from vacation.pl in your log. Please check your mail log and 
$logfile again - it should at least log why it doesn't send a reply.

BTW: Which version of PostfixAdmin do you use?


Gruß

Christian Boltz
-- 
It's the goldmaster - there're no bugs ;-)
[Andreas Jäger about SuSE 9.3]

Re: [Postfixadmin-devel] feature request transport by mailbox/emailaddress

[Christian B. <pos...@cb...>]

Hello,

Am Sonntag, 30. Oktober 2011 schrieb Robert Schetterer:
> Am 30.10.2011 00:33, schrieb Christian Boltz:
> > Am Samstag, 29. Oktober 2011 schrieb Robert Schetterer:
> >> Am 26.10.2011 13:42, schrieb Robert Schetterer:

> > If you don't use the "desctiption" field, you could enter the
> > transport information there - that's currently the easiest way I
> > can imagine.
> hm , cant see some desctiption field but i am not at the latest stable
> version of postfixadmin....., or i am too dummy to find just right
> now *g

Looks like I had the domain forms/table in mind when answering ;-)

It's the "Name" field in the create/edit mailbox form.

> > Adding a field to the database and the code isn't too difficult,
> > but 2.3.x is in bugfix-only mode and otherwise more or less a
> > dead horse. In other words: Investing time in adding a field to
> > 2.3.x only makes sense if you really need it _now_.
> 
> sombody from the list, answered me offlist
> that they did modifiacation allready ,and are in testing mode
> so having a tmp workaround , i can wait for releasing this

OK.

> however, feel free to ask for help, testing etc
> the worst you can get is a "no" *g

;-)


Regards,

Christian Boltz
-- 
Mein Spamassassin läuft überhaupt nicht. Trotzdem wurden in evolution
beachtliche Mengen Spam gefiltert - weil anscheinend diverse zuliefernde
Mailserver Spamassassin verwenden und den X-Spam Header setzen. Mein
eigener Spamassassin steht seit einem Jahr in der Ecke, dreht Däumchen
und lacht sich 'nen Ast. [Ratti in suse-linux]

Re: [Postfixadmin-devel] feature request transport by mailbox/emailaddress

[Robert S. <ro...@sc...>]

Am 30.10.2011 00:33, schrieb Christian Boltz:
> Hello,
> 
> Am Samstag, 29. Oktober 2011 schrieb Robert Schetterer:
>> Am 26.10.2011 13:42, schrieb Robert Schetterer:
>>> i have a feature request
>>> i need to have transport choosing by mailbox/emailaddress ( just
>>> like in the domain table )
>>>
>>> Background there are different type of users/emailaddresses
>>> there are virtual ones ( mail going in server mailbox via dovecot
>>> lmtp), others
>>> are on different places on exchange servers ( mails to them should
>>> smtp transported to the exchange ip )
>>> this works without problems with i.e. a postfix transport hash
>>> table, mysql should work too, but we need it ,for supporters in
>>> the postfixadmin gui
> 
>> as nobody answered
> 
> Sorry, I had no time in the last days :-(

no problem...

> 
>> i changed the alias goto sql query
>> to use it for seperate user/mailaddress smtp transports
>> perhaps other likes it too
>>
>> mysql_virtual_alias_maps.cf
>> ...
>> query = SELECT goto FROM alias WHERE goto NOT REGEXP
>> 'somenot.exist.servernamein.dns' AND address='%s' AND active = 1;
> 
>> so you may use now
>> ip....@so...rvernamein.dns
>> in the alias field of a mailbox
>>
>> this produces a transport like
>> em...@ad...ss smtp:[ip.ad.dr.ess]
>> [...]
> 
> That sounds quite hackish ;-) and isn't what I would really recommend.

yes thats what it is, but its working meanwhile

> 
> If you don't use the "desctiption" field, you could enter the transport 
> information there - that's currently the easiest way I can imagine.

hm , cant see some desctiption field but i am not at the latest stable
version of postfixadmin....., or i am too dummy to find just right now *g
> 
> Adding a field to the database and the code isn't too difficult, but 
> 2.3.x is in bugfix-only mode and otherwise more or less a dead horse.
> In other words: Investing time in adding a field to 2.3.x only makes 
> sense if you really need it _now_.

sombody from the list, answered me offlist
that they did modifiacation allready ,and are in testing mode
so having a tmp workaround , i can wait for releasing this

> 
> I'm currently working on rewriting the code into PHP classes. 
> You can check the current state in SVN trunk - the handling of domains 
> is mostly done (see *-domain.php and model/DomainHandler.php) and will 
> make adding additional fields very easy in the future (see initStruct() 
> in model/DomainHandler.php, I'll also add a hook)
> 
> However, it will take some time until I get everything migrated.

for sure, i just needed this feature in time, but normally
postfixadmin is fine how it is to me ,... more stuff
is always good , but its not essential for me yet

> 
>> be warned, this workaround may conflict with other stuff at your
>> postfix(admin)setup
>> test it hardly before use in production
> 
> ;-)
> 
>>> If Donation is needed/wanted please write what will it take to
>>> hack this
> 
> The best thing you could donate would be some free time ;-) but I know 
> this is impossible. 

yes thats hard , but i would do this, believing in open software,
i am fine with postfix, but having extrem little knowledge in php
so i can only make design requests etc, which might be helpfull otherwhere
however we planning to team us in the near future
so others may give their php code then to devel


> I won't object if you really want to donate something ;-) but it's not a 
> requirement.

however, feel free to ask for help, testing etc
the worst you can get is a "no" *g

> 
> 
> Gruß
> 
> Christian Boltz


-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Postfixadmin-devel] feature request transport by mailbox/emailaddress

[Christian B. <pos...@cb...>]

Hello,

Am Samstag, 29. Oktober 2011 schrieb Robert Schetterer:
> Am 26.10.2011 13:42, schrieb Robert Schetterer:
> > i have a feature request
> > i need to have transport choosing by mailbox/emailaddress ( just
> > like in the domain table )
> > 
> > Background there are different type of users/emailaddresses
> > there are virtual ones ( mail going in server mailbox via dovecot
> > lmtp), others
> > are on different places on exchange servers ( mails to them should
> > smtp transported to the exchange ip )
> > this works without problems with i.e. a postfix transport hash
> > table, mysql should work too, but we need it ,for supporters in
> > the postfixadmin gui

> as nobody answered

Sorry, I had no time in the last days :-(

> i changed the alias goto sql query
> to use it for seperate user/mailaddress smtp transports
> perhaps other likes it too
> 
> mysql_virtual_alias_maps.cf
> ...
> query = SELECT goto FROM alias WHERE goto NOT REGEXP
> 'somenot.exist.servernamein.dns' AND address='%s' AND active = 1;

> so you may use now
> ip....@so...rvernamein.dns
> in the alias field of a mailbox
> 
> this produces a transport like
> em...@ad...ss smtp:[ip.ad.dr.ess]
> [...]

That sounds quite hackish ;-) and isn't what I would really recommend.

If you don't use the "desctiption" field, you could enter the transport 
information there - that's currently the easiest way I can imagine.

Adding a field to the database and the code isn't too difficult, but 
2.3.x is in bugfix-only mode and otherwise more or less a dead horse.
In other words: Investing time in adding a field to 2.3.x only makes 
sense if you really need it _now_.

I'm currently working on rewriting the code into PHP classes. 
You can check the current state in SVN trunk - the handling of domains 
is mostly done (see *-domain.php and model/DomainHandler.php) and will 
make adding additional fields very easy in the future (see initStruct() 
in model/DomainHandler.php, I'll also add a hook)

However, it will take some time until I get everything migrated.

> be warned, this workaround may conflict with other stuff at your
> postfix(admin)setup
> test it hardly before use in production

;-)

> > If Donation is needed/wanted please write what will it take to
> > hack this

The best thing you could donate would be some free time ;-) but I know 
this is impossible. 
I won't object if you really want to donate something ;-) but it's not a 
requirement.


Gruß

Christian Boltz
-- 
OMG I'm not perfect! Please don't tell anyone!
[Henne Vogelsang in opensuse-wiki]

Re: [Postfixadmin-devel] feature request transport by mailbox/emailaddress

[Robert S. <ro...@sc...>]

Am 26.10.2011 13:42, schrieb Robert Schetterer:
> Hi,
> i have a feature request
> i need to have transport choosing by mailbox/emailaddress ( just like in
> the domain table )
> 
> Background there are different type of users/emailaddresses
> there are virtual ones ( mail going in server mailbox via dovecot lmtp),
> others
> are on different places on exchange servers ( mails to them should smtp
> transported to the exchange ip )
> this works without problems with i.e. a postfix transport hash table,
> mysql should work too, but we need it ,for supporters in the
> postfixadmin gui
> If Donation is needed/wanted please write what will it take to hack this

as nobody answered
i changed the alias goto sql query
to use it for seperate user/mailaddress smtp transports
perhaps other likes it too

mysql_virtual_alias_maps.cf
...
query = SELECT goto FROM alias WHERE goto NOT REGEXP
'somenot.exist.servernamein.dns' AND address='%s' AND active = 1;

mysql_virtual_transport_maps.cf
...
query = SELECT CONCAT('smtp:[', SUBSTRING_INDEX (goto,'@', 1),']') FROM
alias WHERE goto REGEXP 'somenot.exist.servernamein.dns' AND
address='%s' AND active = 1;

main.cf
...
transport_maps = hash:/etc/postfix/transport,
mysql:/etc/postfix/mysql_virtual_transport_maps.cf
...
virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf
...

so you may use now
ip....@so...rvernamein.dns
in the alias field of a mailbox

this produces a transport like
em...@ad...ss smtp:[ip.ad.dr.ess]

and disables all other alias (gotos) for this mailbox !
it only works for mailbox aliases ( not pure aliases ) !

somenot.exist.servernamein.dns
is free to choose, but it must pass postfixadmins syntax check
and should not exist in dns, anyway its just somkind of "marker" in this
context, it should not be the real dns servername
of your postfix box, cause this "may" produce conflicts with your local
postfix transport

you should not use it if you have
relay_domains = mysql:/etc/postfix/mysql_relay_domains_maps.cf
in your postfix setup
by getting warnings in postfix logs

be warned, this workaround may conflict with other stuff at your
postfix(admin)setup
test it hardly before use in production


-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

[Postfixadmin-devel] feature request transport by mailbox/emailaddress

[Robert S. <ro...@sc...>]

Hi,
i have a feature request
i need to have transport choosing by mailbox/emailaddress ( just like in
the domain table )

Background there are different type of users/emailaddresses
there are virtual ones ( mail going in server mailbox via dovecot lmtp),
others
are on different places on exchange servers ( mails to them should smtp
transported to the exchange ip )
this works without problems with i.e. a postfix transport hash table,
mysql should work too, but we need it ,for supporters in the
postfixadmin gui
If Donation is needed/wanted please write what will it take to hack this
-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Postfixadmin-devel] Migration of postfixadmin email server to new server causes new users not created in database.

[Simon L. <si...@kl...>]

On 12/10/11 01:02, Christian Boltz wrote:
> Hello,
>
> Am Dienstag, 11. Oktober 2011 schrieb Simon Loewenthal:
>> The database was exported using mysqldump --all-databases>backup.sql,
>> and imported with mysql <backup.sql
>>
>> [SNIP]
> Just curious: you say "roundcube database" - is this the same database 
> that is also used by postfix? Or a different one?
I was confused.  Roundcube gets data from IMAP session, and also creates
some user preferences in the roundcube dB.  Roundcube (in my case) can
also update the spamassassin.userprefs dB.  Postfixadmin did not write
into the roundcube dB.

Additional confused was because I forgot to add the IP address of the
new server into my PC's /etc/hosts so the vhost was handled.  Result was
that I was http ing to the wrong server. 

Fun and games.  

This would have been far easier if I could have just picked up the
existing server image and dump it onto the new server, but is not
possible int this case :(

[SNIP]

>> Sounds like it accesses an out-of-date database.
>> Check your config if you have the hostname or IP of the old server 
>> hardcoded somewhere so that it queries the database on the old server.
>>
>> Or you really have two separate databases (I never used roundcube, so I 
>> don't know if it needs something like that) and need to sync them 
>> somehow. If it worked on the old server, implement the same thing on the 
>> new one ;-)
[SNIP]

> $CONF[logging] enables logging of all modifications on mailboxes, 
> aliases etc. It's stored in the database (table "log") and available in 
> the "view log" page of PostfixAdmin.
>
> Just to be sure, also check your apache error log.
>
>
> Regards,
>
> Christian Boltz

Thank-you Christian. 

The problem was caused  by the way I thoughtlessly exported the data
into the new server.  I forgot that I had exported all dBs on the old
one including the .mysql dB, which I imported into the new server:
Resulted in a confused dB.  I realised this as I fell asleep last night.


Many thanks, Simon.

Re: [Postfixadmin-devel] Migration of postfixadmin email server to new server causes new users not created in database.

[Christian B. <pos...@cb...>]

Hello,

Am Dienstag, 11. Oktober 2011 schrieb Simon Loewenthal:
> The database was exported using mysqldump --all-databases>backup.sql,
> and imported with mysql <backup.sql
> 
> The postfix installtion is a tar ball from the old server, along with
> the dovecot/postfix/roundcube installations.
> 
> In the new set-up, postfixadmin creates the user in the roundcube
> database, but it is not seen in the mailserver database!

Just curious: you say "roundcube database" - is this the same database 
that is also used by postfix? Or a different one?

> Existing users (those that exist in the mailserver and roundcube
> database) can log in.
> 
> 
> What is strange that one can log in via RoundCube (IMAP->dovecot) with
> the newly created user, but one cannot use IMAP directly with
> Dovecot, nor with AUTH PLAIN over smtp to postfix.

Sounds like it accesses an out-of-date database.
Check your config if you have the hostname or IP of the old server 
hardcoded somewhere so that it queries the database on the old server.

Or you really have two separate databases (I never used roundcube, so I 
don't know if it needs something like that) and need to sync them 
somehow. If it worked on the old server, implement the same thing on the 
new one ;-)

> What I see in the log files are:
> dovecot: auth-worker(default): sql(te...@ex...,127.0.0.1):
> unknown user
> 
> Which makes sense, because the user was never put into the mailserver
> database...
> 
> 
> I have verified that the user postfixadmin has the correct grants on
> the database specified in the config.inc.php, and the md5sum on both
> old and new config.inc.php are the same.

Same question here: hardcoded hostname or IP of the old server?

Oh, BTW: does setup.php give any hints or errors?

> I have logging enabled in the config.inc.php :
> $CONF['logging'] = 'YES';
> 
> 
> My question:
> Where is the logging sent to? I cannot find it.  At least then I could
> start to diagnose the this with possible error messages.

$CONF[logging] enables logging of all modifications on mailboxes, 
aliases etc. It's stored in the database (table "log") and available in 
the "view log" page of PostfixAdmin.

Just to be sure, also check your apache error log.


Regards,

Christian Boltz
-- 
Du hast jetzt relativ kompliziert die völlig korrekte Aussage:
"SPF ist krank, funktioniert nicht und vom Ansatz her bereits defekt."
formuliert. [Peer Heinlein in postfixbuch-users]

[Postfixadmin-devel] Migration of postfixadmin email server to new server causes new users not created in database.

[Simon L. <si...@kl...>]

Hi there,

	I recently moved my email server to a new one, which is presently in
testing.

I use postfixadmin for the account/domain config.
RoundCube for webmail
dovecot
postfix

Everything is held inside mySQL.

The old set up works:  A user is created in postfixadmin, and the right
tables are updated.

----------------------------------------------------------------------

The new set-up:

The database was exported using mysqldump --all-databases>backup.sql,
and imported with mysql <backup.sql

The postfix installtion is a tar ball from the old server, along with
the dovecot/postfix/roundcube installations.

In the new set-up, postfixadmin creates the user in the roundcube
database, but it is not seen in the mailserver database!

Existing users (those that exist in the mailserver and roundcube
database) can log in.


What is strange that one can log in via RoundCube (IMAP->dovecot) with
the newly created user, but one cannot use IMAP directly with Dovecot,
nor with AUTH PLAIN over smtp to postfix.


What I see in the log files are:
dovecot: auth-worker(default): sql(te...@ex...,127.0.0.1): unknown user

Which makes sense, because the user was never put into the mailserver
database...


I have verified that the user postfixadmin has the correct grants on the
database specified in the config.inc.php, and the md5sum on both old and
new config.inc.php are the same.

I have logging enabled in the config.inc.php :
$CONF['logging'] = 'YES';


My question:
Where is the logging sent to? I cannot find it.  At least then I could
start to diagnose the this with possible error messages.



Any clues would be gratefully appreciated on a postcard.

Cheers, Simon.






-- 
	Email  simon AT klunky DOT co DOT uk
	PGP is optional: 4BA78604
	I won't accept your confidentiality
	agreement, and your Emails are kept.
      		       ~Ö¿Ö~

Re: [Postfixadmin-devel] SF.net SVN: postfixadmin:[1171] trunk/functions.inc.php

[Christian B. <pos...@cb...>]

Hello,

Am Sonntag, 21. August 2011 schrieb 
chr...@us...:
> Revision: 1171

> functions.inc.php - check_owner():
> - escape_string() $username and $domain to prevent SQL injections

Just for the records:

2.3.3 uses pre-escaped parameters for check_owner(), which means it is 
secure. (I checked every call of check_owner.)

I didn't check everything in trunk, but I'm quite sure that everything 
is pre-escaped there also. The only exception is vacation.php in the 
version I commited _after_ adding escaping in escape_string().

In other words: The commit message sounds more dangerous than it is. 
There never was a SQL injection bug, and the changed version will 
prevent future ones.


Regards,

Christian Boltz
-- 
> beim Übersetzen von qcad steigt die Prozessorauslastung von
> cc1plus bis auf 98% an. Dasist doch nicht üblich, oder?
Warum stört Dich das? Du hast doch die ganze CPU bezahlt, oder?
Oder hast Du nur 'ne  halbe?
[> Stefan Schlörholz und Andreas Kyek in suse-linux]

[Postfixadmin-devel] vacation.pl and BATV

[Dyks A. <Axe...@co...>]

Hello,

I would like to suggest the following patch for vaction.pl.

Thanks

Axel

===================================================================
--- vacation.pl (revision 895)
+++ vacation.pl (working copy)
@@ -576,6 +576,17 @@
     undef $tmp;
 }

+# Remove "Bounce Address Tag" when added by the sending mail server
+# Postfix currently does not (directly) implement BATV (Bounce Address Tag Validation)
+# Only by means of Batv-Milter: [http://sourceforge.net/projects/batv-milter];
+# [http://en.wikipedia.org/wiki/Bounce_Address_Tag_Validation)]
+if ($smtp_sender =~ m/^prvs=[0-9a-f]+=(.*)$/i) {
+    my $tmp = $1;
+    $logger->debug("Removed \"Bounce Address Tag\" from sender address - from $smtp_sender to $tmp");
+    $smtp_sender = $tmp;
+    undef $tmp;
+}
+
 # If either From: or To: are not set, exit
 if(!$from || !$to || !$messageid || !$smtp_sender || !$smtp_recipient) {
     $logger->info("One of from=$from, to=$to, messageid=$messageid, smtp sender=$smtp_sender, smtp recipient=$smtp_recipient empty");

________________________________

Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Prof. B. Feindor Vorstand/Managing Board: Andreas Bublak, Manfred Steinberger, Robert Zellner COC AG Sitz/Registered Office Burghausen Amtsgericht/District Court Traunstein, HRB 17218

Re: [Postfixadmin-devel] Virtual vacation-related

[Rudi F. <rud...@go...>]

Which Version do you use?
Because in the trunk code the normal aliases are not touched. Only the 
vacation alias is added or removed.


Rudi

sry for so many messages

Am 13.07.2011 09:47, schrieb Ian R. Justman:
> Hi, all.
>
> Is it normal to see the alias only point to
> "emailaddress#vir...@va..." when one sets a
> vacation message using the virtual vacation subsystem?  If so, then I
> have a problem.  I had one of my clients inform me that he wasn't
> getting e-mails despite the fact the autoresponder was working as it
> should.  Is it configurable so that it will add the actual e-mail for
> the vacationing recipient to the alias so he can get his mail (i.e. the
> "address" column has "ema...@vi..." and the "goto"
> column has
> "ema...@vi...,emailaddress#vir...@va..."
> in the "alias" table)?  Or is this a case of either hand-editiong the
> database or coding it myself?  I can do the former (in fact, that's what
> I did), but while it's relatively easy to do, it's very inconvenient.
> If I knew enough PHP, I would consider the latter.
>
> Thanks.
>
> --Ian.
>