Re: Released Pigeonhole v0.4.9.rc1 for Dovecot v2.2.19.rc1
Op 30-9-2015 om 0:05 schreef Jacques Distler: duplicate symbol _vnd_environment_extension in: ../../src/lib-sieve/plugins/vnd.dovecot/environment/.libs/libsieve_ext_vnd_environment.a(ext-vnd-environment.o) ../../src/lib-sieve/plugins/vnd.dovecot/environment/.libs/libsieve_ext_vnd_environment.a(ext-vnd-environment-items.o) duplicate symbol _vnd_environment_extension in: ../../src/lib-sieve/plugins/vnd.dovecot/environment/.libs/libsieve_ext_vnd_environment.a(ext-vnd-environment.o) ../../src/lib-sieve/plugins/vnd.dovecot/environment/.libs/libsieve_ext_vnd_environment.a(ext-vnd-environment-variables.o) ld: 2 duplicate symbols for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[4]: *** [libdovecot-sieve.la] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Fixed: http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/9ac3914392a4 Regards, Stephan.
Re: v2.2.19 release candidate 2 released
> Does http://hg.dovecot.org/dovecot-2.2/rev/7633bca91551 > fix the problem for you? Seems to. Thanks! signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Released Pigeonhole v0.4.9.rc1 for Dovecot v2.2.19.rc1
duplicate symbol _vnd_environment_extension in: ../../src/lib-sieve/plugins/vnd.dovecot/environment/.libs/libsieve_ext_vnd_environment.a(ext-vnd-environment.o) ../../src/lib-sieve/plugins/vnd.dovecot/environment/.libs/libsieve_ext_vnd_environment.a(ext-vnd-environment-items.o) duplicate symbol _vnd_environment_extension in: ../../src/lib-sieve/plugins/vnd.dovecot/environment/.libs/libsieve_ext_vnd_environment.a(ext-vnd-environment.o) ../../src/lib-sieve/plugins/vnd.dovecot/environment/.libs/libsieve_ext_vnd_environment.a(ext-vnd-environment-variables.o) ld: 2 duplicate symbols for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[4]: *** [libdovecot-sieve.la] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: v2.2.19 release candidate 2 released
On 2015-09-29 20:22, Jacques Distler wrote: > Darwin doesn't have an EDEADLOCK error code, so compilation fails on MacOSX: > > file-lock.c:214:16: error: use of undeclared identifier 'EDEADLOCK' > if (errno == EDEADLOCK) > ^ > file-lock.c:262:16: error: use of undeclared identifier 'EDEADLOCK' > if (errno == EDEADLOCK) > ^ Does http://hg.dovecot.org/dovecot-2.2/rev/7633bca91551 fix the problem for you? Regards, Pascal -- The trapper recommends today: deadbeef.1527...@localdomain.org
Re: FreeBSD 10 & default_vsz_limit causing reboots?
Hi,
> Op 15 september 2015 om 14:52 schreef Rick Romero :
>
>
> Ok,
>
> So this is really more of an observation than anything else.
>
> I had a FreeBSD 10.1 server that was running great. Some SSL issue came up,
> or I upgrade Dovecot in ports - something occurred and the machine started
> rebooting randomly. It would run for 2 weeks, then reboot. It might run
> for 5 days and then reboot. So I started doing more FreeBSD upgrades,
> thinking it was a kernel issue. The reboots only increased.
>
> This weekend I started thinking I might actually be having hardware
> issues. But, since I don't have easy physical access to the box and it's
> REALLY under loaded, I figured what the hell and upraded to 10.2 on
> Sunday. I think it rebooted 4 times after that on Sunday, and then
> another 2 times Monday morning.
>
> Its worth noting that while I have crash dumps enabled, they don't seem to
> be occurring. So hardware is still a possibility.
Jumping in at some point here, as FreeBSD dev I run most of my servers on
FreeBSD. All my mailservers are running FreeBSD.
My customer backend servers run Dovecot on FreeBSD. we have a few hundred
mailboxes (not that many). I upgrade all my packages
and system whenever there are updates and I figured out whether they are OK or
not. That means that I most likely do more upgrades
then you do at the moment.
I never ever had the symptoms you describe nor did I need to tweak settings.
Given this is a "FreeBSD"box crashing I thought I should reply. I think you need
to contact the FreeBSD devs (other then me) to ask what is going on.
Perhaps you can do a backtrace on the dump to see what was going on. If you
installed panicmail (a tool by Colin Percival) it will automatically create
an informative email which describes the issue more or less ..
Please poke me offline when I can help you more with that.
Cheers
Remko(@FreeBSD.org)
>
> After the 2nd Monday morning reboot, I started to wonder if there was some
> sort of process issue. Besides the OS upgrades - I had been monitoring
> the Dovecot logs for when the process limits are reached, and increasing
> them. It's a 'big' box, and load is typically between .30 and .50. CPUs
> aren't overtaxed, and most of the memory is dedicated to ZFS. The reboots
> are so short, I've only received one 'down' alert due to them. So it's a
> conerning issue, but not really impacting production.
>
> On a whim I changed my default_vsz_limit (as I had been increasing every
> other limit but that) from 384M to 512M. The system hasn't rebooted in
> 24hours.
>
> Now that could be a coincidence, but I thought I'd at least put it out
> there.
>
> If you see anything weird in my dovecot config, let me know - My config was
> originally vpopmail, but over time I've migrated to SQL-only.
>
> root@romulus:/usr/local/etc/dovecot # dovecot -n
> # 2.2.18: /usr/local/etc/dovecot/dovecot.conf
> # OS: FreeBSD 10.2-RELEASE amd64
> auth_master_user_separator = *
> auth_mechanisms = plain login
> auth_username_translation = %@
> auth_verbose = yes
> default_login_user = dovecot
> default_vsz_limit = 512 M
> disable_plaintext_auth = no
> first_valid_gid = 89
> first_valid_uid = 89
> last_valid_gid = 89
> last_valid_uid = 89
> log_path = /dev/stderr
> login_greeting = Ready.
> login_trusted_networks = 172.16.100.0/24
> mail_fsync = never
> mail_plugins = " quota zlib stats"
> mail_privileged_group = mail
> namespace compat {
> alias_for =
> hidden = yes
> inbox = no
> list = no
> location =
> prefix = INBOX.
> separator = .
> }
> namespace inbox {
> inbox = yes
> location =
> prefix =
> separator = .
> }
> passdb {
> args = /usr/local/etc/dovecot/dovecot-master-sql.conf
> driver = sql
> master = yes
> pass = yes
> }
> passdb {
> args = /usr/local/etc/dovecot/dovecot-sql.conf
> driver = sql
> }
> plugin {
> quota = maildir
> quota_rule = Trash:storage=+10%%
> stats_refresh = 30 secs
> stats_track_cmds = yes
> }
> protocols = imap pop3
> service anvil {
> client_limit = 3175
> }
> service auth {
> client_limit = 3684
> unix_listener auth-master {
> mode = 0600
> }
> }
> service imap-login {
> process_limit = 1536
> process_min_avail = 25
> service_count = 1
> }
> service imap-postlogin {
> executable = script-login rawlog /usr/local/etc/dovecot/lastauth-imap.sh
> user = vpopmail
> }
> service imap {
> executable = /usr/local/libexec/dovecot/imap imap-postlogin
> process_limit = 1536
> }
> service pop-postlogin {
> executable = script-login /usr/local/etc/dovecot/lastauth-pop.sh
> user = vpopmail
> }
> service pop3-login {
> process_limit = 1536
> process_min_avail = 15
> service_count = 1
> }
> service pop3 {
> executable = /usr/local/libexec/dovecot/pop3 pop-postlogin
> }
> service stats {
> fifo_listener stats-mail {
> mode = 0600
> user = vpopmail
> }
> }
> shutdown_clients = no
> ssl_cert = ssl_key = ssl_key_password = na
> userdb {
> driver = pref
Re: v2.2.19 release candidate 2 released
Darwin doesn't have an EDEADLOCK error code, so compilation fails on MacOSX: file-lock.c:214:16: error: use of undeclared identifier 'EDEADLOCK' if (errno == EDEADLOCK) ^ file-lock.c:262:16: error: use of undeclared identifier 'EDEADLOCK' if (errno == EDEADLOCK) ^ 2 errors generated. make[4]: *** [file-lock.lo] Error 1 make[3]: *** [all] Error 2 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: quota count
On 29.09.2015 17:46, Timo Sirainen wrote: On 09/29/2015 05:14 PM, Pavel Batkov wrote: Hi Dovecot: 2.2.19.rc2 OS: CentOS Linux release 7.1.1503 (Core) FS: XFS Problem: Dovecot it does not include line breaks in the letter. Bug or feautre? I don't think it's related to line feeds, although there are settings related to that. What mailbox format are you using? It seems like mbox format. With mbox: mbox Message size in fs: 1125 bytes Message: From c...@irccrew.org Tue Jul 23 19:39:23 2002 .. X-IMAPbase: 1096038620 010517 X-UID: 1 Status: O These above 4 lines are internal metadata with mbox format. Because they're not really part of the real message, they're not counted towards the quota. (And practically this would also make it difficult, because a flag change would then also change the quota.) Dovecot count dict mysql: UPDATE quota SET bytes=bytes+974,messages=messages+1 WHERE username = 'use...@test.test' After removing those lines, the message size matches the 974 bytes correctly.
Re: quota count
On 09/29/2015 05:14 PM, Pavel Batkov wrote: > Hi > > Dovecot: 2.2.19.rc2 > OS: CentOS Linux release 7.1.1503 (Core) > FS: XFS > > Problem: > > Dovecot it does not include line breaks in the letter. Bug or feautre? I don't think it's related to line feeds, although there are settings related to that. What mailbox format are you using? It seems like mbox format. With mbox: > Message size in fs: 1125 bytes > > Message: > > From c...@irccrew.org Tue Jul 23 19:39:23 2002 .. > X-IMAPbase: 1096038620 010517 > X-UID: 1 > Status: O These above 4 lines are internal metadata with mbox format. Because they're not really part of the real message, they're not counted towards the quota. (And practically this would also make it difficult, because a flag change would then also change the quota.) > Dovecot count dict mysql: > > UPDATE quota SET bytes=bytes+974,messages=messages+1 WHERE username = > 'use...@test.test' After removing those lines, the message size matches the 974 bytes correctly.
Re: dovecot quota service for postfix
Incase user is underquota, then the email is returned back to postfix for
processing and delivering email to user mbox, incase user has no
sufficient quota then dovecot will inform postfix to reject email.
Please confirm if what i mentioned above is correct and that i understand
correctly how dove-cot policy works with postfix.
Your understanding is mor or less correct, except that postfix never
passes the email itself to dovecot when performing the quota check. It
simply sends a message to the quota policy service asking if the
recipient is over quota. If the recipient is over quota, dovecot
provides postfix with the response configured in quota_status_overquota.
If the recipient is under quota, dovecot provides postfix with the
response configured in quota_status_success. If dovecot does not know
the user, it provides postfix with the response configured in
quota_status_nouser.
Kindly check my configuration below and advise the missing parts to add...
I don't see anything wrong with your configuration on first appraisal,
but if it isn't working I would recommend you perform the following
troubleshooting steps.
1. Verify the user's mailbox is over or under quota in alignment with
your expectations
- `doveadm quota -u $RECIPIENT`
2. Test that the quota service provides the response you expect it to
- `echo "recipient=$RECIPIENT" | nc -q1 localhost 12340`
On 09/26/2015 01:40 AM, Michael Peter wrote:
Hello,
I am trying to use dovecot quota service for postfix in order set quota
for some users.
i configure postfix policy service to ask dovecot if user quota is
sufficient to accept the email or not.
(dovecot in this case acts only as policy server to postfix as it only
ACCEPT/REJECT email according to user quota, but it is not used to deliver
email , because postfix will deliver the email to user mailbox)
Incase user is underquota, then the email is returned back to postfix for
processing and delivering email to user mbox, incase user has no
sufficient quota then dovecot will inform postfix to reject email.
Please confirm if what i mentioned above is correct and that i understand
correctly how dove-cot policy works with postfix.
Kindly check my configuration below and advise the missing parts to add...
plugin {
quota_rule = *:storage=1G
quota_grace = 10%%
# 10% is the default
quota_status_success = DUNNO
quota_status_nouser = DUNNO
quota_status_overquota = "552 5.2.2 Mailbox is full"
...
}
The above configurations is for all users which is not override by quota
rules in userdb's extra fields in my password file below.
Is the above configuration missing some thing ? i am using mbox format for
emails storage. do you i have to add (quota= SOMETHING) before (quote_rule
= *:storage=1G) and what to do add to make dovecot support mbox quota?
smtpd_recipient_restrictions =
check_policy_service inet:SERVER-HIDDEN-FOR-SECRUITY.com:12340
service quota-status {
executable = quota-status -p postfix
inet_listener {
port = 12340
}
client_limit = 1
}
now in order to configure dovecot specific quota for user named (user1) i
use passwd-file as follow
user1:{plain}pass3:1002:1002::/home/user1::userdb_mail=mbox:~/mymail:INBOX=/var/mail/user1
userdb_quota_rule=*:bytes=300M
All other users except users1 should have 1GB storage according to this
configuration. which user1 will only have 300MB
Please advise what is my configuration is missing and if i need to add any
thing to run without issues.
Many thanks
Michael Peter
Re: BINARY capability not working correctly?
On Sat, Sep 19, 2015 at 6:27 PM, Michael M Slusarz wrote: > > Probably this: http://markmail.org/message/abjg72sw7ii5ty5x > > Trivial to workaround in client code, so no need to disable BINARY outright > on a client. > It seems that you were right. Updating dovecot from version 2.2.10 to 2.2.18 corrected the problem. The fix is in 2.2.13. Thanks a lot! - Jouko
quota count
Hi Dovecot: 2.2.19.rc2 OS: CentOS Linux release 7.1.1503 (Core) FS: XFS Problem: Dovecot it does not include line breaks in the letter. Bug or feautre? Message size in fs: 1125 bytes Message: From c...@irccrew.org Tue Jul 23 19:39:23 2002 Received: with ECARTIS (v1.0.0; list dovecot); Tue, 23 Jul 2002 19:39:23 +0300 (EEST) Return-Path: Delivered-To: dove...@procontrol.fi Received: from shodan.irccrew.org (shodan.irccrew.org [80.83.4.2]) by danu.procontrol.fi (Postfix) with ESMTP id 434B423848 for ; Tue, 23 Jul 2002 19:39:23 +0300 (EEST) Received: by shodan.irccrew.org (Postfix, from userid 6976) id 175FA4C0A0; Tue, 23 Jul 2002 19:39:23 +0300 (EEST) Date: Tue, 23 Jul 2002 19:39:23 +0300 From: Timo Sirainen To: dove...@procontrol.fi Subject: [dovecot] first test mail Message-ID: <20020723193923.j22...@irccrew.org> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.5i Content-Type: text/plain; charset=us-ascii X-archive-position: 1 X-ecartis-version: Ecartis v1.0.0 Sender: dovecot-bou...@procontrol.fi Errors-to: dovecot-bou...@procontrol.fi X-original-sender: t...@iki.fi Precedence: bulk X-list: dovecot X-IMAPbase: 1096038620 010517 X-UID: 1 Status: O lets see if it works Dovecot count dict mysql: UPDATE quota SET bytes=bytes+974,messages=messages+1 WHERE username = 'use...@test.test'
Re: mirroring one domain.tld to domain.tld.au
On 28.09.2015 16:47, voy...@sbt.net.au wrote: > I have Postfix/Dovecot/postfixadmin/MySQL with several virtual mailbox > domains > > one of the domains is like aname.com.au, the user also now has aname.com, > and, would like to 'mirror' most of the addresses to be u...@aname.com, > THOUGH, some are to remain as us...@aname.com.au I usually do this by having 4 tables in mysql: hosting (links everything together, links to a product table, quota, what ever) domains (domainnames) accounts (homedir, password, etc.) usernames - one hosting has many accounts - one hosting has many domains (domain aliases) - one account has many usernames (localpart aliases for same account) then you can match like anything you want out of this and you use similar queries for postfix and dovecot. in the domains table you could have a column boolean "maindomain" and in the account table you have a column "maindomain_only"... for my use, users don't care if there are other alias combinations - they just don't use it then. but they can login with any combination of @ and it's still only one mail directory per account. it's also a good idea to name the maildirectory like /, so you don't have the domain / username hardcoded anywhere. just some thoughts, works great for me - but depends on your exact use case. you can do like anything you want in SQL for postfix and dovecot keep performance in mind though :-) > > so, both u...@aname.com as well as u...@aname.com.au should be one user > > the users retrive emails as u...@aname.com.au > > longer term... some would want to use aname.com.au. some, aname.com > > what's the best/proper way to do so in Dovecot ? > > I think I can do Postfix with postfixadmin to "Mirror addresses of one of > your domains to another." > > but what do I do at the Dovecot end...? > > thanks for any pointers, suggestions or advice
Re: distuguish between different domains
>> the dovecot service does not care about the server dns name. the dns >> name resolves to the IP address on the client (roundcube) and the client >> connects to the server. if the same dovecot instance listens to all / >> both IP address, client will end up on this dovecot instance and all >> valid user-password combinations are authorized. that's the way it has >> to be, otherwise virtual / mass virtual domain hosting would not be >> possible as you cannot spawn 1000 instances on the same machine (ok, in >> theory you could do that :D) > No, it's only impossible if you are using passdb or otherwise > authenticating against real users of the system. If you are using > virtual users (SQL, LDAP, etc.), you can include the domain name in the > auth lookups. > > Andreas was asking about the fqdn where the imap client is connecting to, not the user name / e-mail address. you can use localpart and domain from the email address in passdb / userdb lookups but dovecot (imap) is nothing like http where you send the a hostname of the site you're conncting to in the header.
Re: BUG: service(auth) crash when quota-status lookup an address with local-part starting with auth_master_user_separator
On 2015-09-29 11:06, Timo Sirainen wrote:
On 29 Sep 2015, at 11:36, Marco Giunta wrote:
>
but a better fix would be to disale the separator for these lookups. I think
something like this would work:
auth_master_user_separator = *
protocol quota-status {
# disable
auth_master_user_separator =
}
Thank you Timo, this works like a charms on 2.2.16; I'm waiting 2.2.19
to update my servers.
Marco
--
---
|Marco Giunta - SISSA Computer Staff|
|Via Bonomea, 265 |
|34136 - Trieste, Italy |
|Tel: +39-40-3787-503 |
|Fax: +39-040-3787-244 |
|e-mail: giu...@sissa.it|
---
Re: BUG: service(auth) crash when quota-status lookup an address with local-part starting with auth_master_user_separator
On 29 Sep 2015, at 11:36, Marco Giunta wrote:
>
> Hi,
> I'm using dovecot 2.2.15 (configuration attached below), and I 've enabled
> quota-status; when I try to look up the quota status of an address with the
> local-part starting with the same character as 'auth_master_user_separator',
> dovecot/auth crash:
>
> My 'auth_master_user_separator' is '*'
>
> Sep 29 08:51:41 my_server dovecot: auth: Panic: file auth-request.c: line
> 1252 (auth_request_set_login_username): assertion failed: (*username != '\0')
v2.2.17 fixes this crash, but a better fix would be to disale the separator for
these lookups. I think something like this would work:
auth_master_user_separator = *
protocol quota-status {
# disable
auth_master_user_separator =
}
or alternatively enable master user separator only for imap:
auth_master_user_separator =
protocol imap {
auth_master_user_separator = *
}
Re: My website feedback
On 29 Sep 2015, at 09:34, Muzaffer Tolga Ozses wrote: > > Hi, > > I gave a feedback about dovecot.fi website yesterday. It's awaiting > moderation because it exceeded message size because it contains a > screenshot. Was this ML the right place to post this? If not, please > redirect me to the appropriate place. dovecot.fi web site is going to have a total redesign, once somebody has time.. We know there are many problems with it.
BUG: service(auth) crash when quota-status lookup an address with local-part starting with auth_master_user_separator
Hi, I'm using dovecot 2.2.15 (configuration attached below), and I 've enabled quota-status; when I try to look up the quota status of an address with the local-part starting with the same character as 'auth_master_user_separator', dovecot/auth crash: My 'auth_master_user_separator' is '*' # telnet localhost 25001 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. request=smtpd_access_policy sender=john...@example.com recipient=*@example.com size=1 action=DEFER_IF_PERMIT Internal error occurred. Refer to server log for more information. request=smtpd_access_policy sender=john...@example.com recipient=*jane...@example.com size=1 action=DEFER_IF_PERMIT Internal error occurred. Refer to server log for more information. request=smtpd_access_policy sender=john...@example.com recipient=;@example.com size=1 action=DUNNO request=smtpd_access_policy sender=john...@example.com recipient=;jane...@example.com size=1 and in server log: Sep 29 08:51:05 my_server dovecot: master: Dovecot v2.2.15 starting up for imap, pop3, lmtp, sieve (core dumps disabled) Sep 29 08:51:05 my_server dovecot: master: Warning: /mnt is no longer mounted. See http://wiki2.dovecot.org/Mountpoints Sep 29 08:51:41 my_server dovecot: auth: Panic: file auth-request.c: line 1252 (auth_request_set_login_username): assertion failed: (*username != '\0') Sep 29 08:51:41 my_server dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a7126a] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a712d6] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a70cac] -> dovecot/auth [0x4131eb] -> dovecot/auth(auth_request_set_username+0x94) [0x413284] -> dovecot/auth [0x40dc4c] -> dovecot/auth [0x40e60b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x49) [0x3d70a82699] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd5) [0x3d70a83a55] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x3d70a82739] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x3d70a829b8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3d70a29233] -> dovecot/auth(main+0x383) [0x41cfc3] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3302e1d9f4] -> dovecot/auth [0x40b5f9] Sep 29 08:51:41 my_server dovecot: quota-status: Error: userdb lookup(*@example.com): Disconnected unexpectedly Sep 29 08:51:41 my_server dovecot: auth: Fatal: master: service(auth): child 2147 killed with signal 6 (core dumps disabled) Sep 29 10:02:02 my_server dovecot: auth: Fatal: master: service(auth): child 12592 killed with signal 6 (core dumps disabled) Sep 29 10:03:52 my_server dovecot: auth: Panic: file auth-request.c: line 1252 (auth_request_set_login_username): assertion failed: (*username != '\0') Sep 29 10:03:52 my_server dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a7126a] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a712d6] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3d70a70cac] -> dovecot/auth [0x4131eb] -> dovecot/auth(auth_request_set_username+0x94) [0x413284] -> dovecot/auth [0x40dc4c] -> dovecot/auth [0x40e60b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x49) [0x3d70a82699] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd5) [0x3d70a83a55] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x3d70a82739] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x3d70a829b8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3d70a29233] -> dovecot/auth(main+0x383) [0x41cfc3] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3302e1d9f4] -> dovecot/auth [0x40b5f9] Sep 29 10:03:52 my_server dovecot: quota-status: Error: userdb lookup(*jane...@example.com): Disconnected unexpectedly Sep 29 10:03:52 my_server dovecot: auth: Fatal: master: service(auth): child 9945 killed with signal 6 (core dumps disabled) Sep 29 10:16:10 my_server dovecot: auth: userdb(?): Username character disallowed by auth_username_chars: 0x3b (username: ;@example.com) Sep 29 10:16:43 my_server dovecot: auth: userdb(?): Username character disallowed by auth_username_chars: 0x3b (username: ;jane...@example.com) If I change my 'auth_master_user_separator' to an other character, for example ';' : # telnet localhost 25001 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. request=smtpd_access_policy sender=john...@example.com recipient=*@example.com size=1 action=DUNNO request=smtpd_access_policy sender=john...@example.com recipient=*jane...@example.com size=1 action=DUNNO request=smtpd_access_policy sender=john...@example.com recipient=;@example.com size=1 action=DEFER_IF_PERMIT Internal error occurred. Refer to server log for more information. request=smtpd_access_policy sender=john...@example.com recipient=;jane...@example.com size=1 action=DEFER_IF_PE
Re: Newbie why is dovecot classified diff then sendmail or courier
Am 2015-09-29 um 06:58 schrieb David Niklas: Hello, this is probably a dumb question, but I can't for the life of me figure out why sendmail and courier are classified universally as network-mail-mta whereas dovecot is in places like network-mail-general or some such place. I'm concerned that I'm looking into the wrong software for an mail transport/delivery agent. Hello David, https://en.wikipedia.org/wiki/Message_transfer_agent has the global scheme. There may be better guides for newbies, but it lays out the terms used. Dovecot appears here https://en.wikipedia.org/wiki/Mail_delivery_agent -- peter
