Re: update to my first email
please provide doveconf -n ---Aki TuomiDovecot oy Original message From: Christy S Date: 18/08/2018 03:32 (GMT+02:00) To: dovecot@dovecot.org Subject: update to my first email Alright so after checking logs, rebooting the vps because why not, and removing and re-adding the account in thunderbird... Now nothing is working other than sending mail from gmail to the domain. imap does not pick up the email and trying to send with the domain just plain fails, saying it can't connect to the server. Honestly, tempted to uninstall dovecot, sasl and postfix and start again, but I don't want to run into the same issues with conflicting tutorials. Does anyone know of a good source of how to do this that's fairly recent? I'll keep searching, but all of the outdated info is kind of frustrating. If anyone has replied to me I haven't gotten it yet, so I'm not ignoring anything you may have said. For now going to give this a break. I've been working on it literally all day! :) Christy
[no subject]
Unsubscribe
Re: update to my first email
Christy, I haven't read your original mail, but, in case this helps, my starting point and go to reference site and check list (apart from this and several other ml) is server world https://www.server-world.info/en/note?os=CentOS_7 On 18 August 2018 10:32:59 AM AEST, Christy S wrote: >Alright so after checking logs, rebooting the vps because why not, and >removing and re-adding the account in thunderbird... Now nothing is >working other than sending mail from gmail to the domain. imap does not -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
update to my first email
Alright so after checking logs, rebooting the vps because why not, and removing and re-adding the account in thunderbird... Now nothing is working other than sending mail from gmail to the domain. imap does not pick up the email and trying to send with the domain just plain fails, saying it can't connect to the server. Honestly, tempted to uninstall dovecot, sasl and postfix and start again, but I don't want to run into the same issues with conflicting tutorials. Does anyone know of a good source of how to do this that's fairly recent? I'll keep searching, but all of the outdated info is kind of frustrating. If anyone has replied to me I haven't gotten it yet, so I'm not ignoring anything you may have said. For now going to give this a break. I've been working on it literally all day! :) Christy
dovecot and postfix, help?
Hi all, First a disclaimer. I have played with linux off and on for years, but this is my first time trying to run a server completely on my own from start to finish, well it's on a vps, but still. I'm pretty techie, but a lot of this stuff is new to me, so I apologize for any *duh!* questions. That said, I've so far installed dovecot, postfix, wordpress, and related programs mostly successfully by following tutorials. I say mostly successfully, because I'm having a really hard time trying to get dovecot and postfix to behave together, and I'm about at the end of what I know how to find on google. If you're still with me and not groaning at yet another newbie asking wtf did I do wrong questions, thank you! My basic setup is running ubuntu 18 with up to date dovecot and postfix. Sasl is installed, and I'm using a custom domain with all records successfully pointing to the VPS. As I mentioned, I've been following tutorials. My goal is to have a mail server which can send and receive emails using this custom domain both from the shell and, much more often, from my primary computer using thunderbird. As there will likely only be two of us using this, I'm completely fine with the setup using mailboxes that actually have linux accounts. I'm also using maildir as the mailbox type. Furthermore, I want to make sure to use ssl on any mail connections.. Normal passwords but ssl being used. So, following one tutorial I set up postfix and dovecot, then went to test it. The result was that while on the shell, I could send email to my gmail account from the domain and receive it just fine. I could also send mail from my gmail account to the domain and receive it on the shel. I even managed to get imap to work, so I could receive domain emails in thunderbird, after playing around with tb's settings. However, if using tb I attempted to send an email using the custom domain, smtp failed to connect. I verified with my VPS provider that no, they do not block port 25, 465 or 587. I also verified that at, my home ISP, does not block outgoing smtp traffic, considering I am using google's for my gmail account. After hitting google again, I realized two things. One, for some reason port 25 never got opened on UFW, so I fixed that. Second, for some reason in all the stuff I did, postfix never got configured to use SSL. I found yet another tutorial, and ran through it to set up SSL with postfix. However, in doing this I had to change a path for sasl, only to find out later that doing that broke dovecot! Imap completely and utterly stopped behaving. Back to google again, and this time I found something a bit more up to date which explained how to interconnect postfix and dovecot. It goes through using mysql too, but I don't need that, so I skipped that part. Changed the sasl path back to what it should be, told dovecot and postfix to talk to each other and... Nope, still nothing. I saw a warning that I should not use different certificates for postfix and dovecot, so I told dovecot to look at the smtpd certificate that I made. Not sure if that's what's breaking this or something completely different, as I'm also brand new to the ssl certificate creation process. So, here's the current status of using thunderbird with my domain. mail sent from gmail to new domain, never comes back in thunderbird but doesn't bounce, either. Mail sent via thunderbird to gmail from domain, works, but shows up as from my gmail domain as well, which makes me think it's defaulting to the gmail account even though the domain's smtp info is set up. This could be because just before writing this message, I got the accept this certificate dialog over and over again for the domain and had to cancel out of it. One final point. I looked at /var/log/mail.log and, while at first I found an error in the path to one of the certificates, once I fixed that no error shows up. I restarted both postfix and dovecot, tried refreshing thunderbird and still no emails showed up. I see the connection in the log, but no errors. Anyone have ideas? Even maybe just point me in the right direction for what to check?
Re: imapsieve: Change message flags on COPY
Op 17/08/2018 om 19:44 schreef Leandro Lucarella: On Friday 17 August 2018 01:41:39 CEST Stephan Bosch wrote: dovecot -n I tried your configuration here with your Sieve script. It works here as expected with or without the fileinto action (so also with only setflag). I changed your script a little to detect "INBOX/Archive" rather than just "Archive" to match my setup. Testing looked as follows (using /usr/lib/dovecot/imap from command line): - Create two mailboxes, one of which will trigger the flag rule: 2343 CREATE INBOX/Archive imap(stephan)<15247>: Debug: Namespace INBOX/: /home/stephan/Maildir/.Archive doesn't exist yet, using default permissions imap(stephan)<15247>: Debug: Namespace INBOX/: Using permissions from /home/stephan/Maildir: mode=0700 gid=default imap(stephan)<15247>: Debug: acl vfile: file /home/stephan/Maildir/.Archive/dovecot-acl not found imap(stephan)<15247>: Mailbox INBOX: Debug: Mailbox opened because: copy caching decisions imap(stephan)<15247>: Mailbox INBOX/Archive: Debug: Mailbox opened because: CREATE imap(stephan)<15247>: Debug: /home/stephan/Maildir/.Archive/dovecot.index.cache: Compressed, file_seq changed 0 -> 1534536851, size=32, max_uid=0 2343 OK Create completed (0.061 + 0.000 + 0.060 secs). 234 CREATE INBOX/Storage imap(stephan)<15247>: Debug: Namespace INBOX/: /home/stephan/Maildir/.Storage doesn't exist yet, using default permissions imap(stephan)<15247>: Debug: Namespace INBOX/: Using permissions from /home/stephan/Maildir: mode=0700 gid=default imap(stephan)<15247>: Mailbox INBOX: Debug: Mailbox opened because: copy caching decisions imap(stephan)<15247>: Mailbox INBOX/Storage: Debug: Mailbox opened because: CREATE imap(stephan)<15247>: Debug: /home/stephan/Maildir/.Storage/dovecot.index.cache: Compressed, file_seq changed 0 -> 1534536860, size=32, max_uid=0 234 OK Create completed (0.059 + 0.000 + 0.058 secs). - Choose a message from INBOX (in this case without any flags assigned): 23423 SELECT INBOX imap(stephan)<15247>: Mailbox INBOX: Debug: Mailbox opened because: SELECT * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MailFlagBit1 $label1 Flagged FreeBSD $Label3 $Label5 $Label4 $Label2) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MailFlagBit1 $label1 Flagged FreeBSD $Label3 $Label5 $Label4 $Label2 \*)] Flags permitted. * 57 EXISTS * 0 RECENT * OK [UNSEEN 6] First unseen. * OK [UIDVALIDITY 1415917190] UIDs valid * OK [UIDNEXT 430] Predicted next UID * OK [HIGHESTMODSEQ 800] Highest 23423 OK [READ-WRITE] Select completed (0.001 + 0.000 secs). 233 FETCH 40 FLAGS * 40 FETCH (FLAGS ()) 233 OK Fetch completed (0.000 + 0.000 secs). - Copy it to archive mailbox first: 23423 COPY 40 INBOX/Archive imap(stephan)<15247>: Mailbox INBOX/Archive: Debug: Mailbox opened because: COPY imap(stephan)<15247>: Debug: imapsieve: mailbox INBOX/Archive: COPY event imap(stephan)<15247>: Debug: imapsieve: mailbox INBOX/Archive: Mailbox attribute /shared/imapsieve/script not found imap(stephan)<15247>: Debug: imapsieve: mailbox INBOX/Archive: Server attribute /shared/imapsieve/script not found imap(stephan)<15247>: Debug: sieve: Pigeonhole version 0.6.devel (c7bd7456) initializing imap(stephan)<15247>: Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.6.devel (c7bd7456) loaded imap(stephan)<15247>: Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.6.devel (c7bd7456) loaded imap(stephan)<15247>: Debug: sieve: vnd.dovecot.pipe extension: no bin or socket directory specified; extension is unconfigured (both sieve_pipe_bin_dir and sieve_pipe_socket_dir are not set) imap(stephan)<15247>: Debug: sieve: vnd.dovecot.filter extension: no bin or socket directory specified; extension is unconfigured (both sieve_filter_bin_dir and sieve_filter_socket_dir are not set) imap(stephan)<15247>: Debug: sieve: vnd.dovecot.execute extension: no bin or socket directory specified; extension is unconfigured (both sieve_execute_bin_dir and sieve_execute_socket_dir are not set) imap(stephan)<15247>: Debug: imapsieve: Static mailbox rule [1]: mailbox=`Spam' from=`*' causes=(COPY) => before=`file:/usr/lib/dovecot/sieve/report-spam.sieve' after=(none) imap(stephan)<15247>: Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`Spam' causes=(COPY) => before=`file:/usr/lib/dovecot/sieve/report-ham.sieve' after=(none) imap(stephan)<15247>: Debug: imapsieve: Static mailbox rule [3]: mailbox=`*' from=`*' causes=(COPY) => before=`file:~/imapsieve.sieve' after=(none) imap(stephan)<15247>: Debug: imapsieve: Matched static mailbox rule [3] imap(stephan)<15247>: Debug: sieve: file storage: Using Sieve script path: /home/stephan/imapsieve.sieve imap(stephan)<15247>: Debug: sieve: file script: Opened script `imapsieve' from `/home/stephan/imapsieve.sieve' imap(stephan)<15247>: Debug: sieve: Opening script 1 of 1 from `/home/stephan/imapsieve.sieve' imap(stephan)<15247>: Debug: sieve: Loading script
Re: imapsieve: Change message flags on COPY
On Friday 17 August 2018 01:41:39 CEST Stephan Bosch wrote:
> dovecot -n
Hi, here it is (I don't know why I get the SSLv2 warning because it is
disabled in ssl_protocols, any ideas about that too?).
BTW, even when storing the message in a different folder with fileinto,
the original message is still saved in the original mailbox. I also tried
using `discard;` and makes no difference, I can never get rid of the
original message.
# dovecot -n
# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
doveconf: Warning: SSLv2 not supported by OpenSSL. Please consider
removing it from ssl_protocols.
doveconf: Warning: SSLv2 not supported by OpenSSL. Please consider
removing it from ssl_protocols.
# OS: Linux 4.15.0-30-generic x86_64 Ubuntu 18.04.1 LTS
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_privileged_group = mail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relationa
l regex imap4flags copy include variables body enotify environment mailbox
date index ihave duplicate mime foreverypart extracttex
t editheader vnd.dovecot.debug vnd.dovecot.environment imapsieve
vnd.dovecot.imapsieve vnd.dovecot.pipe vnd.dovecot.filter vnd.dov
ecot.execute
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
args = scheme=CRYPT username_format=%u /etc/dovecot/users
driver = passwd-file
}
plugin {
imapsieve_mailbox1_before = file:~/sieve/imapsieve.sieve
imapsieve_mailbox1_causes = COPY
imapsieve_mailbox1_name = *
sieve = file:~/sieve;active=~/.dovecot.sieve
sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve-bin
sieve_extensions = +editheader +vnd.dovecot.execute +vnd.dovecot.filter
+vnd.dovecot.pipe +vnd.dovecot.debug +vnd.dovecot.enviro
nment
sieve_filter_bin_dir = /usr/local/lib/dovecot/sieve-bin
sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-bin
sieve_plugins = sieve_imapsieve sieve_extprograms
}
protocols = " imap lmtp sieve pop3 sieve"
service imap-login {
inet_listener imap {
port = 0
}
inet_listener imaps {
port = 1993
}
}
service pop3-login {
inet_listener pop3 {
port = 0
}
inet_listener pop3s {
port = 1995
}
}
ssl = required
ssl_cert = https://llucax.com
signature.asc
Description: This is a digitally signed message part.
Re: Imap special-use with IOS 11
> On 17 Aug 2018, at 17.20, Federico Bartolucci wrote: > > Hello, > > has anyone experiened any issues with IMAP SPECIAL-USE extension with ios11? > After the update to ios11 the Ios mail client seems to not recognize anymore > the imap special-use, so that system folders (Sent, Trash etc..) are not > authomatically recognized and set during the configuration. Can you please verify that your dovecot advertises in the pre-login or post-login banner that SPECIAL-USE is advertised to be supported? iOS Mail.app does not seem to use the special use flags unless they are advertised to be supported. (Just like RFC mandates) Sami
Imap special-use with IOS 11
Hello, has anyone experiened any issues with IMAP SPECIAL-USE extension with ios11? After the update to ios11 the Ios mail client seems to not recognize anymore the imap special-use, so that system folders (Sent, Trash etc..) are not authomatically recognized and set during the configuration. Regards Federico
"nologin" field set leads to internal failure
Hi,
I've tried to use the "nologin" extra password-db field as specified
here:
https://wiki.dovecot.org/PasswordDatabase/ExtraFields/NoLogin
Due to lack of exact documentation, I've tried to use `nologin`='y' for
users that can't login, and setting `nologin`='n' for normal users.
Apparently setting it to NULL for normal users would have been correct,
as I've found out. Maybe write that on the above website.
Anyway, login didn't work for a user with `nologin`='n' set. Trying to
debug a normal user being unable to login, the log (mail.log) says:
dovecot: imap-login: Disconnected (internal failure, 4 successful
auths): user=, method=PLAIN, rip=, lip=,
TLS, session=
What I'm expecting it to say would be something like "user not allowed
to login". I'm considering this a problem because of "Dovecot always
logs a detailed error message if something goes wrong." as written here:
https://wiki2.dovecot.org/Logging
For the record, setting auth_debug=yes and mail_debug=yes gave the
following line in the logs somewhere, from which I was able to figure
out that NOLOGIN was the problem:
dovecot: auth: Debug: client passdb out:
OK#011#011user=t...@example.com#011nologin
Thank you.
dovecot -n output:
--snip--
# 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.16 (fed8554)
# OS: Linux 4.9.0-7-amd64 x86_64 Debian 9.5
auth_default_realm = example.com
base_dir = ...
listen = *,[v6]
login_greeting = ...
mail_home = .../%d/%n/
mail_location = maildir:~/mail/:INDEX=MEMORY
mail_plugins = trees
mail_temp_dir = ...
namespace inbox {
inbox = yes
location =
prefix =
}
passdb {
args = /etc/dovecot/dovecot-sql.conf
driver = sql
}
protocols = imap lmtp
recipient_delimiter = -+
service auth {
unix_listener ... {
group = postfix
mode = 0660
user = postfix
}
}
service imap-login {
inet_listener imap {
port = 143
}
inet_listener imaps {
port = 0
}
service_count = 1
}
service lmtp {
unix_listener ... {
group = postfix
mode = 0600
user = postfix
}
user = vmail
}
ssl = required
ssl_cert = <...
ssl_cipher_list = ...
ssl_dh_parameters_length = 4096
ssl_key = # hidden, use -P to show it
userdb {
driver = prefetch
}
userdb {
args = /etc/dovecot/dovecot-sql.conf
driver = sql
}
--snap--
Re: Does domain quota work and how?
Aki Tuomi wrote on Thu, 16 Aug 2018 21:03:44 +0300 (EEST):
> Can you provide doveconf -n please?
Thanks for the quick reply. I think I already provided the most relevant
portions of config. I ran a doveconf -n and it doesn't reveal important
information like sql setup. I'll do my best to sum up the relevant parts
below, anyway.
But first I would like to know how the dictionary-based domain quota is
intended to work as that is mentioned nowhere. Is it like in the either/or
example where they say that dovecot can only act on one of the quotas at a
given time or is it intended to be used like the filesystem aquota works?
So, there are two things:
First: I do not quite understand how it is supposed to work. Once I knew I
could test my setup whether it acts on the limits correctly.
The second is the apparent bug with recalc. I omitted to say that the
updating of both quotas by dovecot when mail comes in *does* seem to work
correctly. But if I run a recalc it all gets messed up. This has been
reported a few times over time, so I guess it's not specific to my setup.
So, here's the relevant bits again (and a bit more):
dict {
quota = mysql:/etc/dovecot/dovecot-dict-sql-user.conf
quota_domain = mysql:/etc/dovecot/dovecot-dict-sql-domain.conf
}
mail_home = /var/vmail/%d/%n
mail_location = maildir:/var/vmail/%d/%n/mail/
mail_plugins = " quota"
plugin {
quota = dict:user::proxy::quota
quota2 = dict:domain:%d:proxy::quota_domain
quota_rule = *:storage=100M
quota_rule2 = Trash:storage=+10%%
quota_rule3 = Spam:ignore
quota2_rule = *:storage=1000M
quota2_rule2 = Trash:storage=+10%%
quota2_rule3 = Spam:ignore
quota_vsizes = yes
(+ quota_status, _warning etc. not relevant ...)
}
service dict {
unix_listener dict {
group = vmail
mode = 0600
user = vmail
}
}
service quota-status {
client_limit = 1
executable = quota-status -p postfix
inet_listener {
port = 10024
}
}
userdb {
args = /etc/dovecot/dovecot-sql.conf
driver = sql
}
/etc/dovecot/dovecot-dict-sql-user.conf
connect = ...
map {
pattern = priv/quota/storage
table = quota
username_field = username
value_field = bytes
}
map {
pattern = priv/quota/messages
table = quota
username_field = username
value_field = messages
}
/etc/dovecot/dovecot-dict-sql-domain.conf
connect =
map {
pattern = priv/quota/storage
table = quota_domain
username_field = domain
value_field = bytes
}
map {
pattern = priv/quota/messages
table = quota_domain
username_field = domain
value_field = messages
}
/etc/dovecot/dovecot-sql.conf
user_query = SELECT CONCAT('/var/vmail/',m.maildir) AS home, CONCAT
('maildir:/var/vmail/',m.maildir,'mail/') AS mail, 200 AS uid, 200 AS gid,
concat('*:bytes=', m.quota) AS quota_rule, concat('*:bytes=',
(s.ServerPopQuota*1024*1024)) AS quota2_rule FROM mailbox AS m LEFT JOIN
server AS s ON (m.ServerID = s.ServerID) WHERE (m.username = '%u' OR
m.local_part = "%n") AND m.active = '1'
doveadm quota get of a test domain:
Username Quota name TypeValue Limit %
example...@example.com user STORAGE 5567 10 5
example...@example.com user MESSAGE70 - 0
example...@example.com domain STORAGE 33426 1024000 3
example...@example.com domain MESSAGE 1292 - 0
example_s...@example.com user STORAGE 33403 10 33
example_s...@example.com user MESSAGE 1280 - 0
example_s...@example.com domain STORAGE 33426 1024000 3
example_s...@example.com domain MESSAGE 1292 - 0
Note: these are values after a recalc and after the users (both) received
some more test mails. So, the figures in general are not correct (if I sum
them up), but you see that user quota is getting updated separate for each
user and that domain quota is equal for both but not equal with any of the
users. Now, if I would do a recalc -A it would look like this:
example...@example.com user STORAGE 5567 10 5
example...@example.com user MESSAGE70 - 0
example...@example.com domain STORAGE 33403 1024000 3
example...@example.com domain MESSAGE 1280 - 0
example_s...@example.com user STORAGE 33403 10 33
example_s...@example.com user MESSAGE 1280 - 0
example_s...@example.com domain STORAGE 33403 1024000 3
example_s...@example.com domain MESSAGE 1280 - 0
So, the last user processed determiens the domain values.
Actually, the user values would be recalculated correctly after the recalc
and might be different from above and the domain quota then follows that
by using the last processed user as the single source for it.
Thanks!
Kai
Re: imap-login: Error: BUG: Authentication server sent unknown id
On 17.08.2018 12:10, Tom Sommer wrote: > I randomly get these errors on my Director > > Aug 17 10:52:37 imap-login: Error: BUG: Authentication server sent > unknown id 98448 > Aug 17 10:52:37 imap-login: Warning: Auth connection closed with 2 > pending requests (max 2 secs, pid=27036, Received broken input: FAIL > 98448 user=u...@example.com) > Aug 17 10:52:37 auth: Warning: auth client 27036 disconnected with 1 > pending requests: EOF > > 2.3.2.1 > Hi! This is fixed with https://github.com/dovecot/core/commit/eb08f805f07d29249412901c9d6587fe31abdebb.patch Aki
imap-login: Error: BUG: Authentication server sent unknown id
I randomly get these errors on my Director Aug 17 10:52:37 imap-login: Error: BUG: Authentication server sent unknown id 98448 Aug 17 10:52:37 imap-login: Warning: Auth connection closed with 2 pending requests (max 2 secs, pid=27036, Received broken input: FAIL 98448 user=u...@example.com) Aug 17 10:52:37 auth: Warning: auth client 27036 disconnected with 1 pending requests: EOF 2.3.2.1 -- Tom
Re: dovecot sieve duplicates detection
Op 14/05/2018 om 23:03 schreef James Cassell: On Mon, May 14, 2018, at 4:52 PM, Stephan Bosch wrote: Op 25/04/2018 om 22:49 schreef James Cassell: On Wed, Apr 25, 2018, at 3:20 PM, Stephan Bosch wrote: Specify the ID used for duplicate checking explicitly using the :uniqueid argument (https://tools.ietf.org/html/rfc7352#section-3.1). Using the variables extenion, compose the uniqueid from the message-id and the mailbox name. In my experience with dovecot's implementation, you can set the ID only once in a script. If you try to filter duplicates based on multiple IDs, only the first (or last, I don't remember) takes effect. Do you have a detailed example of the supposed wrong behavior? I don't have them readily available. Basically, the result of the first duplicate test in a script is taken as the result of any future duplicate test, even if the parameters to that future duplicate test in the same script are different and would otherwise result in a different output. The duplicate test is only evaluated once and its results are substituted everywhere. For example, I might want to flag a message as a new conversation if I have not seen another message with the same subject. In the same script, I might want to discard messages that are exactly identical including message ID among others. The dovecot behavior would be to discard all messages that match a subject of previously received message. I finally managed to review this issue and I can confirm that this is a bug. Regards, Stephan.
Re: Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
On 08/16/2018 11:48 PM, Stephan Bosch wrote: > Op 16/08/2018 om 12:01 schreef Stephan Bosch: >> I have a theory. Will try something later today. > > Yes, I can reproduce the problem. I am working on a fix. Thank you very much! I'm here if you need something. Regards, -- Gabriele Nencioni System Administrator eml gabriele.nenci...@register.it
