Bug? Custom mail login (optional) not optional?

Discussion in 'General' started by platan, Jan 25, 2012.

  1. platan

    platan New Member

    Ispconfig 3.0.4.2 - login as admin

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

    System -> Interface config -> Mail ->
    Allow custom login name: [x] <- check it

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

    Email -> Email mailbox -> Add new Mailbox ->
    Email: [i ] @ [example.tld ] <- fill it
    Login (optional): [ ] <- leave blank (after all, is optional)
    Password: [******* ]
    Save <- go

    -> ERROR
    -> 1. Valid characters are A-Z, a-z, 0-9, ., _ and -.

    - What is that unspecified error? Suddenly, the error is empty optional login field.

    ------

    I trying unvisible move customer's virtuals from Ispconfig2 to Ispconfig3. This is a great idea! A dream come true.
    1. For new email -> login as full email adress (automagick with empty optional custom login).
    2. For old email logins from Ispconfig2 system -> custom web555_somebody with password from /etc/shadow file, inserted direct into database (it works!).

    BUT somethin goes wrong.
    There is no automatic full e-mail login when custom login (optional) is empty.
    OK, I anderstand. There is no dual login for one e-mail account. But why optional login is not optional? Why optional field must be filled?

    Please help

    Best regards

    Tomasz Oleksiewicz
     
  2. till

    till Super Moderator

    If you enable the email login field in interface config, then you have to use it for all email accounts on your server and fill in the username that shall be used as email login. So there is no bug here, its optional to enable the login field, but when you have it enabled, then its mandatory that you fill in the username.
     
  3. platan

    platan New Member

    Thank you for your answer.
    That's exactly what I understood.
    In addition, I propose to change the label "Login (optional):" to "Login (mandatory) *:" (with asterisk) in all translations.
    Or not! Perhaps in the next version of the system, the field will be truly optional.
    Ispconfig, this is great work! Congratulations and best regards.
     
  4. platan

    platan New Member

    Ouch!
    Interface - is not problem.
    Problem is: postfix does not work with custom login.
    Configuration described above.

    Modify /var/vmail/.mailfilter, add

    LINE="0:$0 1:$1 2:$2 3:$3 4:$4 5:$5 6:$6 7:$7"
    `echo $LINE >> /var/vmail/.maildrop.pipe.log`

    to check if maildrop is started or not.


    Example
    Email: bar@oleksiewicz.pl
    Login: web30_bar

    Postfix step 1 - OK:
    Jan 30 22:03:58 s5d1 postfix/smtp[1574]: 9BACDC0E13: to=<bar@oleksiewicz.pl>, relay=127.0.0.1[127.0.0.1]:10024, delay=1, delays=0.11/0.02/0.01/0.88, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=00571-02, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 85E48C0E24)

    Amavis... - step 2 - OK...

    Postfix step 3 - BAD:
    Jan 30 22:03:58 s5d1 postfix/pipe[1581]: 85E48C0E24: to=<bar@oleksiewicz.pl>, relay=maildrop, delay=0.08, delays=0.01/0.03/0/0.05, dsn=5.1.1, status=bounced (user unknown. Command output: Invalid user specified. )

    This look like maildrop probem, but maildrop is not started. Postfix has a problem with the preparation of maildrop command.

    Example 2:
    Email: tom@oleksiewicz.pl
    Login: tom@oleksiewicz.pl
    All fine!

    HELP! HELP! HELP!
     
  5. till

    till Super Moderator

    I guess the problem is maildrop / courier and not postfix. Maildrop is bouncind as it does not find the user and the user is checked before it executes the mailfilter script. Please check the courier sql config files if courier authenticates against the login column and not the email column.
     
  6. platan

    platan New Member

  7. platan

    platan New Member

    Well, I did so:
    In /etc/postfix/master.cf change
    Code:
    maildrop  unix  -       n       n       -       -       pipe
      flags=DRhu user=vmail argv=/usr/bin/maildrop [COLOR="DarkRed"][B]-d ${recipient}[/B][/COLOR] ${extension} ${recipient} ${user} ${nexthop} ${sender}
    into
    Code:
    maildrop  unix  -       n       n       -       -       pipe
      flags=DRhu user=vmail argv=/usr/bin/maildrop [COLOR="DarkRed"][B]-d vmail[/B][/COLOR] ${extension} ${recipient} ${user} ${nexthop} ${sender}
    and WORKS (maildrop quota ok)!!

    BUT!

    Does that make sense?
    Is it safe?
    Is it consistent with the idea Ispconfig3?
    Is it always work?

    Help me please
     
    Last edited: Feb 13, 2012

Share This Page