similar to: Single quote email addresses

I wrapped the LDA command in a script. I can see that Postfix passes "@@mydomain.tld" as the -d argument, without quotes. I then adapted the script to specifically replace this address with "@"@mydomain.tld, but this results in the following error message by Dovecot: ??? auth: Info: userdb(?): Username character disallowed by auth_username_chars: 0x22 (username:

Op 7-3-2018 om 15:40 schreef Stephan Bosch: > > > Op 7-3-2018 om 13:46 schreef Philipp Berger: >> I wrapped the LDA command in a script. I can see that Postfix passes >> "@@mydomain.tld" as the -d argument, without quotes. >> I then adapted the script to specifically replace this address with >> "@"@mydomain.tld, but this results in the

we use Passdb LDAP with authentication binds against an Active Directory Server. The problem with one of our users seems to be the usage of double quotes in his password, as the windows-login works: /var/log/dovecot-info.log auth(default): Info: ldap(testuser 77.22.xx.xxx): invalid credentials (given password: xxxxx"xxxxxxx) Which chars in passwords does the dovecot auth process not

Hi, I have a userdb file set up in passwd-file format containing the following entries: >doveadm user test1*test2 at test.com test1-test2 at test.com test1?test2 at test.com test1 at test2@test.com test1%test2 at test.com I can access the 1st entry (no special characters) no problem: >doveadm user test1-test2 at test.com -f home /var/vmail The 2nd entry (using UTF-8 encoding)

* Ruben Safir: > On Sun, Dec 02, 2018 at 03:58:53AM +0100, Bernd Petrovitsch wrote: > >> Let's hope that people who do not know how to use a tool - e.g. >> like a hammer - doesn't use that tool in the first place .... > > that is pretty unrealistic and I don't agree with it anyway. The tool metaphor is realistic. In my experience (which dates back to the

Interesting, the documentation and the build-in help of dovecot-lda do not mention -r exists :) case 'r': /* final recipient address */ if (smtp_address_parse_path(ctx.pool, optarg, SMTP_ADDRESS_PARSE_FLAG_ALLOW_LOCALPART | SMTP_ADDRESS_PARSE_FLAG_BRACKETS_OPTIONAL, &final_rcpt_to, &errstr) < 0) { i_fatal_status(EX_USAGE, "Invalid -a parameter: %s",

I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In the Postfix log I now see: Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from <admin at mydomain.tld> -> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as B8CA22DA1B37 Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) Passed CLEAN

Op 7-3-2018 om 13:46 schreef Philipp Berger: > I wrapped the LDA command in a script. I can see that Postfix passes > "@@mydomain.tld" as the -d argument, without quotes. > I then adapted the script to specifically replace this address with > "@"@mydomain.tld, but this results in the following error message by > Dovecot: > > ??? auth: Info: userdb(?):

Hello list. I'm thinking to migrate the hole user db from system users to mysql. I already did it in a test environment, but something is annoying my OCD... I don't quote the variables username and password sent to the mysql server. I know, the mysql user that dovecot uses only has select rights, but it stills bother me, because its possible to do an useless sql code injection. Is there a

> Am 02.02.2015 um 18:07 schrieb Juan Bernhard: >> Hello list. I'm thinking to migrate the hole user db from system users >> to mysql. I already did it in a test environment, but something is >> annoying my OCD... I don't quote the variables username and password >> sent to the mysql server. I know, the mysql user that dovecot uses only >> has select

Hello I was wondering how I can achieve matlab style plotting in R, in the sense that matlab allows you to plot multiple sets of variables within the same x-y axes. plot in R does not seem to cater for this. I tried 'overplot' from the gplots package but this assumes different y axes for the variables. any suggestions would be very appreciated Maria [[alternative HTML version

Hi, I''ve started looking at ticket 90<http://merb.devjavu.com/projects/merb/ticket/90>and there are a couple of situations that the current implementation doesn''t cater for. 1. Tag Attributes are wiped out. - <tag1 attr1=''1''>Content</tag1> #=> { "tag1" => "Content" } - I think it should return -

Hey all, Just had a need for this, wondering if it is a candidate for inclusion as it is only a single line and I can''t seem to spot any other way of acheiving the same functionality in less code. String.prototype.isNumeric = function() { return (this.match(/^\d+$/) != null); } I used it in the context of: Event.observe(el,''keypress'',function (e) { if

One thing that we are often blamed for is trying to stifle conversations and to discourage people from commenting / contributing / encouraging conversations. And that cant be further from the truth, really. We are all pro-community ( and when I say we, I mean everyone - including the contributors, developers, admins, users, abusers and hey upstream too ). However, one thing that does get in

Hi, It is my opinion that a 'tagging standard' which aims to cater to everyone, caters to noone. Tagging style ultimately depend upon tagging tastes; I personally think it would be unwise to try to match everybody's tastes. Now, having a 'tagging proposal' instead of a 'tagging standard,' hardly seems worth the effort, to put it mildly. I doubt anyone would want to

A few months ago, Eric asked about this for CentOS 6: https://stat.ethz.ch/pipermail/r-sig-fedora/2014-April/000310.html and was kindly helped by Marc Schwartz. OTOH, we are running Fedora 19, currently upgrading to Fedora 20. The RPM find link for 'jags-devel' which Marc provided really seems to cater to CentOS or RHEL 5, but not directly to any newer Fedora. Also there, I'd

Hi all, Is there a function to modify the fetch order of messages? We have just migrated from Courier to Dovecot and I notice that there is a slight difference in the way messages are fetched in Dovecot compared to Courier. Both Courier and Dovecot sort the mailbox correctly (UID SORT (REVERSE ARRIVAL) UTF-8 ALL), for example: [ 13:22:02.790 ]50800314 UID SORT (REVERSE ARRIVAL) UTF-8 ALL * SORT

I am trying to use the mailer to send email. I want to create a sender and a recipient address that is in this form (note the quotes around the sender name): "sender name" sender@domain.com To do this, in my sender model, I have tried something like this: def combined_address return "\"" + self.name + "\"" + " <" + self.email +

Has anyone here implemented "Ring back when free" in Asterisk? The way it works in the UK is as follows: 1. A calls B. B is engaged (busy). 2. A hears "The number you called is busy. To use ringback, press 5" 3. A presses 5, and hears "Your ringback request has been accepted". 4. A hangs up. 5. Later, B hangs up. The system then calls A (if A is now busy, it

Hi, I am running dovecot version 1.2.9 on a Ubuntu 10.04 server. To obtain the message's header info from this dovecot imap server, I run the following imap command on a client side's imap session: . fetch 88:90 (envelope) which returns (in this case) ------------------------------------------------------------- * 88 FETCH (ENVELOPE ("Tue, 28 Oct 2008 15:45:35 -0500"