Koozali.org: home of the SME Server

SME 8 ed IMAP iPad/iPhone

Offline aspirina

  • **
  • 37
  • +0/-0
SME 8 ed IMAP iPad/iPhone
« on: October 18, 2012, 12:48:30 AM »
haimè eccomi qui novamente a chiedere lumi per un problema alquanto fastidioso..
Da pochi giorni ho appena installato un server mail con SME, il server gestisce 1.564.056 mail (ops!! sono stato un po troppo pignolo  :-P ), circa 1,5GB di posta.
I client sono 6 e funzionano molto bene (ringrazio Stefano per il consiglio datomi in qualche post fa), tutti i client con Thunderbird sono velocissimi, ma è proprio quando le cose vanno bene che si deve intromettere mr. Murphy...
Ci sarebbe il bisogno di sincronizzare tutta la posta sia su un iPhone4 sia su in iPad2... Procedo come ho fatto in una vecchia installazione (che conta 8 volte questa posta), inserisco IMAP, SMTP, ecc... la sincronizzazione parte, e dopo le 1000 mail il server chiude la connessione per timeout! Horde diventa inutilizzabile dicendo che le credenziali non sono corrette, i client nella rete locale ricevono la mail, ma quando la inviano non viene salvata, un disastro totale... spengo i due dispositivi, riavvio il server è tutto torna normale... cosa può essere successo?
grazie 1000 in anticipo a tutti
Aspirina

Offline nicolatiana

  • *
  • 724
  • +0/-0
Re: SME 8 ed IMAP iPad/iPhone
« Reply #1 on: October 18, 2012, 07:23:24 AM »
Succede che cominci a guardare dentro /var/log/imap /var/log/imaps e a seguire in /var/log/messages e, magari, anche /var/log/qmail e ci dai qualche informazione in più.
 
Comunque: le mail sono suddivise in numerose cartelle o gli utenti ti hanno fatto il solito calderone infernale con migliaia di mail per ogni cartella ?
 
Attendiamo maggiori informazioni.
 
Nicola
Consulente di Smeserver.it -  Soluzioni e supporto su Sme server in Italia.

Offline aspirina

  • **
  • 37
  • +0/-0
Re: SME 8 ed IMAP iPad/iPhone
« Reply #2 on: October 18, 2012, 08:41:01 AM »
Ciao :-) !! Eccomi qua... allora, dentro a /var/log/imap
Code: [Select]
@40000000507684dc39560ffc tcpsvd: info: listening on 0.0.0.0:imap, starting.
@400000005076881321c2fb84 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@400000005077f79d2815d54c tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507805ec180d5f1c tcpsvd: info: sigterm received, exit.
@400000005078065e239561f4 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@400000005078086a229cc954 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@4000000050780a96317454ec tcpsvd: info: sigterm received, exit.
@4000000050780ae81f9cc40c tcpsvd: info: listening on 0.0.0.0:imap, starting.
@400000005078126d3b093284 tcpsvd: info: sigterm received, exit.
@40000000507925701974039c tcpsvd: info: listening on 0.0.0.0:imap, starting.
@400000005079526e3b5f64ec tcpsvd: info: sigterm received, exit.
@40000000507952e3359dda5c tcpsvd: info: listening on 0.0.0.0:imap, starting.
@4000000050797ceb372fd0b4 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507985c71b39815c tcpsvd: info: listening on 0.0.0.0:imap, starting.
@4000000050798da50ac7f4d4 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507bb4433091ff84 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507bbc5f2d3d719c tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507bc9370ee85e3c tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507bd03827199afc tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507bd1f421647834 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507bd8a317934164 tcpsvd: info: sigterm received, exit.
@40000000507bd8fb1cbda4a4 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507bdcdf2f07d544 tcpsvd: info: sigterm received, exit.
@40000000507bdd3b281aab94 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507be34a1460aacc tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507d1f8c35147294 tcpsvd: info: sigterm received, exit.
@40000000507d1fe93338b584 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507daa6502ba6704 tcpsvd: info: sigterm received, exit.
@40000000507daac4391f1d94 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507daea3239a72d4 tcpsvd: info: sigterm received, exit.
@40000000507daefd33fe3034 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507db4fa28ebc6d4 tcpsvd: info: sigterm received, exit.
@40000000507db5541c27f06c tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507dd7e639677134 tcpsvd: info: sigterm received, exit.
@40000000507dd845354805b4 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507e737c396efae4 tcpsvd: info: listening on 0.0.0.0:imap, starting.
@40000000507eb795391cc01c tcpsvd: info: listening on 0.0.0.0:imap, starting.

Mentre dentro a /var/log/imaps mi trovo con due cose strane. La prima..
Code: [Select]
@40000000507ed417210262d4 imapfront-auth[25653]: * OK imapfront ready.
@40000000507ed4172539bb54 imapfront-auth[25653]: * CAPABILITY IMAP4rev1 AUTH=LOGIN IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS
@40000000507ed417253a3854 imapfront-auth[25653]: 00000000 OK CAPABILITY completed
@40000000507ed4172563115c imapfront-auth[25653]: SASL AUTH LOGIN failed
@40000000507ed4172563674c imapfront-auth[25653]: 00000001 NO AUTHENTICATE failed: Authentication failed.
@40000000507ed417257d9284 imapfront-auth[25653]: SASL AUTH LOGIN failed
@40000000507ed417257d966c imapfront-auth[25653]: 00000002 NO AUTHENTICATE failed: Authentication failed.
@40000000507ed4172596b41c imapfront-auth[25653]: SASL AUTH LOGIN failed
@40000000507ed4172596b41c imapfront-auth[25653]: 00000003 NO AUTHENTICATE failed: Authentication failed.
@40000000507ed41725a86b44 imapfront-auth[25653]: * Logging out
@40000000507ed41725a87314 imapfront-auth[25653]: 00000004 OK LOGOUT completed
e la seconda..
Code: [Select]
@40000000507ee378099ba204 tcpsvd: info: status 14/20
@40000000507ee378099f3be4 tcpsvd: info: pid 2776 from 94.165.115.7
@40000000507ee37809a162ac tcpsvd: info: concurrency 2776 94.165.115.7 8/20
@40000000507ee37809a16694 tcpsvd: info: start 2776 0:192.168.1.250 ::94.165.115.7:51836 ./peers/0
@40000000507ee37809e929ac tcpsvd: info: status 15/20
@40000000507ee37809e92d94 tcpsvd: info: pid 2778 from 94.165.115.7
@40000000507ee37809e9317c tcpsvd: info: concurrency 2778 94.165.115.7 9/20
@40000000507ee37809e93564 tcpsvd: info: start 2778 0:192.168.1.250 ::94.165.115.7:51837 ./peers/0
@40000000507ee37809f8259c imapfront-auth[2776]: * OK imapfront ready.
@40000000507ee3780a0e1ab4 imapfront-auth[2778]: * OK imapfront ready.
@40000000507ee3780b00ac5c tcpsvd: info: status 16/20
@40000000507ee3780b00b044 tcpsvd: info: pid 2780 from 94.165.115.7
@40000000507ee3780b00b42c tcpsvd: info: concurrency 2780 94.165.115.7 10/20
@40000000507ee3780b00b42c tcpsvd: info: start 2780 0:192.168.1.250 ::94.165.115.7:51838 ./peers/0
@40000000507ee3780b1c5664 imapfront-auth[2780]: * OK imapfront ready.
@40000000507ee37e076e6994 imap(usersme1): Info: Disconnected for inactivity
@40000000507ee37e076e6d7c tcpsvd: info: end 30705 exit 0
@40000000507ee37e076e7164 tcpsvd: info: status 15/20
@40000000507ee37e076e7164 sslio[30705]: info: bytes in: 903
@40000000507ee37e076e754c sslio[30705]: info: bytes ou: 2592
@40000000507ee43114d3796c tcpsvd: info: status 16/20
@40000000507ee43114d37d54 tcpsvd: info: pid 3338 from 151.31.253.220
@40000000507ee43114d3813c tcpsvd: info: concurrency 3338 151.31.253.220 5/20
@40000000507ee43114d38524 tcpsvd: info: start 3338 0:192.168.1.250 ::151.31.253.220:50190 ./peers/0
@40000000507ee43114e88424 imapfront-auth[3338]: * OK imapfront ready.
@40000000507ee43117273154 tcpsvd: info: status 17/20
@40000000507ee43117273924 tcpsvd: info: pid 3340 from 151.31.253.220
@40000000507ee43117273924 tcpsvd: info: concurrency 3340 151.31.253.220 6/20
@40000000507ee43117273d0c tcpsvd: info: start 3340 0:192.168.1.250 ::151.31.253.220:50191 ./peers/0
@40000000507ee431175a0cdc imapfront-auth[3340]: * OK imapfront ready.
@40000000507ee43117dd563c tcpsvd: info: status 18/20
@40000000507ee43117dd5a24 tcpsvd: info: pid 3342 from 151.31.253.220
@40000000507ee43117dd5e0c tcpsvd: info: concurrency 3342 151.31.253.220 7/20
@40000000507ee43117dd61f4 tcpsvd: info: start 3342 0:192.168.1.250 ::151.31.253.220:50192 ./peers/0
@40000000507ee43117ece69c imapfront-auth[3342]: * OK imapfront ready.
@40000000507ee4312beb1c54 tcpsvd: info: status 19/20
@40000000507ee4312beda0dc tcpsvd: info: pid 3344 from 151.31.253.220
@40000000507ee4312bef853c tcpsvd: info: concurrency 3344 151.31.253.220 8/20
@40000000507ee4312bef8d0c tcpsvd: info: start 3344 0:192.168.1.250 ::151.31.253.220:50193 ./peers/0
@40000000507ee4312c2cff84 imapfront-auth[3344]: * OK imapfront ready.
@40000000507ee581005b4d0c tcpsvd: info: status 20/20
@40000000507ee581005da2b4 tcpsvd: info: pid 4215 from 94.165.115.7
@40000000507ee581005fae24 tcpsvd: info: concurrency 4215 94.165.115.7 11/20
@40000000507ee581005fb20c tcpsvd: info: start 4215 0:192.168.1.250 ::94.165.115.7:51840 ./peers/0
@40000000507ee581009f1884 imapfront-auth[4215]: * OK imapfront ready.
@40000000507ee5d10e2b673c imap(usersme1): Info: Disconnected for inactivity
@40000000507ee5d10e2b6b24 sslio[31625]: info: bytes in: 871
@40000000507ee5d10e2b6f0c sslio[31625]: info: bytes ou: 2592
@40000000507ee5d10e2b6f0c tcpsvd: info: end 31625 exit 0
@40000000507ee5d10e2b72f4 tcpsvd: info: status 19/20
@40000000507ee5d10e2b72f4 tcpsvd: info: status 20/20
@40000000507ee5d10e2debc4 tcpsvd: info: pid 4422 from 94.165.115.7
@40000000507ee5d10e2fb4cc tcpsvd: info: concurrency 4422 94.165.115.7 12/20
@40000000507ee5d10e2fb8b4 tcpsvd: info: start 4422 0:192.168.1.250 ::94.165.115.7:51841 ./peers/0
@40000000507ee5d10e72a96c imapfront-auth[4422]: * OK imapfront ready.
@40000000507ee5d10e72ad54 sslio[4422]: info: bytes in: 178
@40000000507ee5d10e72b13c sslio[4422]: info: bytes ou: 1295
@40000000507ee5d10e7a17c4 tcpsvd: info: end 4422 exit 0
@40000000507ee5d10e7a1bac tcpsvd: info: status 19/20
@40000000507ee5d10e7a1bac tcpsvd: info: status 20/20
@40000000507ee5d10e7c3e8c tcpsvd: info: pid 4424 from 94.165.115.7
@40000000507ee5d10e7e74f4 tcpsvd: info: concurrency 4424 94.165.115.7 12/20
@40000000507ee5d10e7e78dc tcpsvd: info: start 4424 0:192.168.1.250 ::94.165.115.7:51842 ./peers/0
@40000000507ee5d10e98cf0c sslio[4424]: info: bytes in: 178
@40000000507ee5d10e991d2c sslio[4424]: info: bytes ou: 1295
@40000000507ee5d10ec86a8c imapfront-auth[4424]: * OK imapfront ready.
@40000000507ee5d10ef3628c tcpsvd: info: end 4424 exit 0
@40000000507ee5d10ef36674 tcpsvd: info: status 19/20
@40000000507ee5d10ef36a5c tcpsvd: info: status 20/20
@40000000507ee5d10ef36a5c tcpsvd: info: pid 4426 from 94.165.115.7
@40000000507ee5d10ef36e44 tcpsvd: info: concurrency 4426 94.165.115.7 12/20
@40000000507ee5d10ef36e44 tcpsvd: info: start 4426 0:192.168.1.250 ::94.165.115.7:51843 ./peers/0
@40000000507ee5d10ef3722c sslio[4426]: info: bytes in: 178
@40000000507ee5d10ef37614 sslio[4426]: info: bytes ou: 1295
@40000000507ee5d10f0ee19c imapfront-auth[4426]: * OK imapfront ready.
@40000000507ee5d10f1df4fc tcpsvd: info: end 4426 exit 0
@40000000507ee5d10f1e4aec tcpsvd: info: status 19/20
@40000000507ee5d10f1e4aec tcpsvd: info: status 20/20
@40000000507ee5d10f213504 tcpsvd: info: pid 4428 from 94.165.115.7
@40000000507ee5d10f23445c tcpsvd: info: concurrency 4428 94.165.115.7 12/20
@40000000507ee5d10f234c2c tcpsvd: info: start 4428 0:192.168.1.250 ::94.165.115.7:51844 ./peers/0
@40000000507ee5d10f41058c sslio[4428]: info: bytes in: 178
@40000000507ee5d10f410974 sslio[4428]: info: bytes ou: 1295
@40000000507ee5d10f7348bc imapfront-auth[4428]: * OK imapfront ready.
@40000000507ee5d10f734ca4 tcpsvd: info: end 4428 exit 0
@40000000507ee5d10f734ca4 tcpsvd: info: status 19/20
@40000000507ee5d10f73508c tcpsvd: info: status 20/20
@40000000507ee5d10f7586f4 tcpsvd: info: pid 4430 from 94.165.115.7
@40000000507ee5d10f7730bc tcpsvd: info: concurrency 4430 94.165.115.7 12/20
@40000000507ee5d10f7734a4 tcpsvd: info: start 4430 0:192.168.1.250 ::94.165.115.7:51845 ./peers/0
@40000000507ee5d10fb37e3c imapfront-auth[4430]: * OK imapfront ready.
@40000000507ee835354801cc imap(usersme1): Info: Disconnected for inactivity
@40000000507ee83535605074 sslio[937]: info: bytes in: 903
@40000000507ee835358ae6cc sslio[937]: info: bytes ou: 2592
@40000000507ee835358aeab4 tcpsvd: info: end 937 exit 0
@40000000507ee835358aee9c tcpsvd: info: status 19/20
@40000000507ee835358aee9c tcpsvd: info: status 20/20
@40000000507ee835358af284 tcpsvd: info: pid 6169 from 94.165.115.7
@40000000507ee835358af284 tcpsvd: info: concurrency 6169 94.165.115.7 12/20
@40000000507ee835358af66c tcpsvd: info: start 6169 0:192.168.1.250 ::94.165.115.7:51846 ./peers/0
@40000000507ee835358afa54 sslio[6169]: info: bytes in: 178
@40000000507ee835358b2934 sslio[6169]: info: bytes ou: 1295
@40000000507ee835359f803c imapfront-auth[6169]: * OK imapfront ready.
@40000000507ee83535add434 tcpsvd: info: end 6169 exit 0
@40000000507ee83535ae745c tcpsvd: info: status 19/20
@40000000507ee83535ae7844 tcpsvd: info: status 20/20
@40000000507ee83535b11ff4 tcpsvd: info: pid 6171 from 94.165.115.7
@40000000507ee83535b2b634 tcpsvd: info: concurrency 6171 94.165.115.7 12/20
@40000000507ee83535b2ba1c tcpsvd: info: start 6171 0:192.168.1.250 ::94.165.115.7:51847 ./peers/0
@40000000507ee83535d0c19c sslio[6171]: info: bytes in: 178
@40000000507ee83535d10fbc sslio[6171]: info: bytes ou: 1295
@40000000507ee83536002284 imapfront-auth[6171]: * OK imapfront ready.
@40000000507ee8353609c744 tcpsvd: info: end 6171 exit 0
@40000000507ee8353609cb2c tcpsvd: info: status 19/20
@40000000507ee8353609cf14 tcpsvd: info: status 20/20
@40000000507ee835360c8a4c tcpsvd: info: pid 6173 from 94.165.115.7
@40000000507ee835360e7294 tcpsvd: info: concurrency 6173 94.165.115.7 12/20
@40000000507ee835360e767c tcpsvd: info: start 6173 0:192.168.1.250 ::94.165.115.7:51848 ./peers/0
@40000000507ee835364a857c sslio[6173]: info: bytes in: 178
@40000000507ee835364a8964 sslio[6173]: info: bytes ou: 1295
@40000000507ee835364a8d4c imapfront-auth[6173]: * OK imapfront ready.
@40000000507ee8353651f7bc tcpsvd: info: end 6173 exit 0
@40000000507ee83536525194 tcpsvd: info: status 19/20
@40000000507ee835365293fc tcpsvd: info: status 20/20
@40000000507ee8353654ddec tcpsvd: info: pid 6175 from 94.165.115.7
@40000000507ee835365660a4 tcpsvd: info: concurrency 6175 94.165.115.7 12/20
@40000000507ee8353656648c tcpsvd: info: start 6175 0:192.168.1.250 ::94.165.115.7:51850 ./peers/0
@40000000507ee8353696dc74 imapfront-auth[6175]: * OK imapfront ready.
@40000000507ee8353696e05c sslio[6175]: info: bytes in: 210
@40000000507ee8353696e444 sslio[6175]: info: bytes ou: 1295
@40000000507ee83536a0b014 tcpsvd: info: end 6175 exit 0
@40000000507ee83536a17364 tcpsvd: info: status 19/20
@40000000507ee83536a17364 tcpsvd: info: status 20/20
@40000000507ee83536a3ccf4 tcpsvd: info: pid 6177 from 94.165.115.7
@40000000507ee83536a55394 tcpsvd: info: concurrency 6177 94.165.115.7 12/20
@40000000507ee83536a55394 tcpsvd: info: start 6177 0:192.168.1.250 ::94.165.115.7:51849 ./peers/0
@40000000507ee83536d3f8fc sslio[6177]: info: bytes in: 210
@40000000507ee83536d3fce4 sslio[6177]: info: bytes ou: 1295
@40000000507ee83536da9c34 imapfront-auth[6177]: * OK imapfront ready.
@40000000507ee83537119284 tcpsvd: info: end 6177 exit 0
@40000000507ee8353711966c tcpsvd: info: status 19/20
@40000000507ee83537119a54 tcpsvd: info: status 20/20
@40000000507ee83537119e3c tcpsvd: info: pid 6179 from 94.165.115.7
@40000000507ee83537119e3c tcpsvd: info: concurrency 6179 94.165.115.7 12/20
@40000000507ee8353711a224 tcpsvd: info: start 6179 0:192.168.1.250 ::94.165.115.7:51851 ./peers/0
@40000000507ee8353711a60c sslio[6179]: info: bytes in: 210
@40000000507ee8353711a60c sslio[6179]: info: bytes ou: 1295
@40000000507ee8353727b67c imapfront-auth[6179]: * OK imapfront ready.
@40000000507ee8353735e74c tcpsvd: info: end 6179 exit 0
@40000000507ee8353735eb34 tcpsvd: info: status 19/20
@40000000507ee8353735ef1c tcpsvd: info: status 20/20
@40000000507ee83537386fbc tcpsvd: info: pid 6181 from 94.165.115.7
@40000000507ee835373a6b8c tcpsvd: info: concurrency 6181 94.165.115.7 12/20
@40000000507ee835373a6f74 tcpsvd: info: start 6181 0:192.168.1.250 ::94.165.115.7:51884 ./peers/0
@40000000507ee835376c703c sslio[6181]: info: bytes in: 210
@40000000507ee835376c7424 sslio[6181]: info: bytes ou: 1295
@40000000507ee83537736964 imapfront-auth[6181]: * OK imapfront ready.
@40000000507ee835378153e4 tcpsvd: info: end 6181 exit 0
@40000000507ee8353781f024 tcpsvd: info: status 19/20
@40000000507ee8372d22d51c imap(usersme3): Info: Disconnected for inactivity
@40000000507ee8372d3d2764 sslio[960]: info: bytes in: 977
@40000000507ee8372d3d2f34 sslio[960]: info: bytes ou: 5857
@40000000507ee8372d4414d4 imap(usersme2): Info: Disconnected for inactivity
@40000000507ee8372d541a64 sslio[962]: info: bytes in: 953
@40000000507ee8372d541e4c sslio[962]: info: bytes ou: 4897
@40000000507ee8372d542234 tcpsvd: info: end 960 exit 0
@40000000507ee8372d542234 tcpsvd: info: status 18/20
@40000000507ee8372d634d04 tcpsvd: info: end 962 exit 0
@40000000507ee8372d6350ec tcpsvd: info: status 17/20
@40000000507ee837357b0c34 imap(usersme1): Info: Disconnected for inactivity
@40000000507ee8373592be9c sslio[964]: info: bytes in: 958
@40000000507ee8373592c284 sslio[964]: info: bytes ou: 5043
@40000000507ee83735972784 tcpsvd: info: end 964 exit 0
@40000000507ee83735972b6c tcpsvd: info: status 16/20
@40000000507ee83735d3ea34 imap(usersme3): Info: Disconnected for inactivity
@40000000507ee83735d3ee1c sslio[966]: info: bytes in: 953
@40000000507ee83735d3f204 sslio[966]: info: bytes ou: 5166

mentre in /var/log/qmail non è mai cambiato nulla, ci sono tutte le mail inviate correttamente, nemmeno una di fallita..

Per quanto riguarda le email, la cifra che ho dato prima è suddivisa per 6 caselle e sono abbastanza poi ri-suddivise in cartelle di archiviazione di circa 1000/2000 mail per cartella, quindi non è così un calderone...

Preciso che sto usando la versione SME 8 a 64bit, e come contribs aggiuntivi c'è fetchmail e nulla altro..

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: SME 8 ed IMAP iPad/iPhone
« Reply #3 on: October 18, 2012, 10:07:09 AM »
per favore, riposta gli estratti qui sopra mettendo in pipe il comando tai64nlocal

i.e.
Code: [Select]
cat miofiledilog | tai64nlocal

grazie..

a titolo di esempio, su una macchina di un mio cliente.. account info, 10 utenti contemporanei in imap
Code: [Select]
[root@fileserver ~]$ cd /home/e-smith/files/users/info/
[root@fileserver info]$ du -s -m *
18731   Maildir

[root@fileserver Maildir]$ cd Maildir/cur
[root@fileserver cur]$ ls | wc -l
16570
[root@fileserver cur]$

quindi circa 17.5 Gb e 16570 email nella cartella principale..

il problema, secondo me, è nella configurazione dei dispositivi.. che però ci è sconosciuta

Offline aspirina

  • **
  • 37
  • +0/-0
Re: SME 8 ed IMAP iPad/iPhone
« Reply #4 on: October 18, 2012, 08:15:52 PM »
Code: [Select]
cat miofiledilog | tai64nlocalwoooooooooooow !!! mi era sfuggito questo piccolo particolare!!! Che comando MEGAUTILE :D grassie!

Tornando a noi, ho appena verificato i log per benino ed ho trovato questo:

in var/log/imap
Quote
2012-10-17 10:59:30.963574500 tcpsvd: info: listening on 0.0.0.0:imap, starting.
2012-10-17 15:50:03.958185500 tcpsvd: info: listening on 0.0.0.0:imap, starting.

in var/log/imaps
Quote
2012-10-17 16:46:56.205123500 imapfront-auth[13749]: * OK imapfront ready.
2012-10-17 16:46:56.205124500 sslio[13751]: fatal: unable to send ssl response: broken pipe
2012-10-17 16:46:56.205125500 sslio[13751]: warning: unable to send ssl close notify: broken pipe
2012-10-17 16:46:56.205126500 sslio[13751]: info: bytes in: 120
2012-10-17 16:46:56.205126500 sslio[13751]: info: bytes ou: 0
2012-10-17 16:46:56.205127500 tcpsvd: info: end 13749 exit 0
2012-10-17 16:46:56.205127500 tcpsvd: info: status 19/20
2012-10-17 16:46:56.205128500 tcpsvd: info: status 20/20
2012-10-17 16:46:56.205146500 tcpsvd: info: pid 13753 from 192.168.1.11
2012-10-17 16:46:56.205147500 tcpsvd: info: concurrency 13753 192.168.1.11 10/20
2012-10-17 16:46:56.205147500 tcpsvd: info: start 13753 0:192.168.1.250 ::192.168.1.11:50949 ./peers/192.168.1
2012-10-17 16:46:56.205148500 sslio[13753]: fatal: unable to send ssl response: broken pipe
2012-10-17 16:46:56.205149500 sslio[13753]: warning: unable to send ssl close notify: broken pipe
2012-10-17 16:46:56.205150500 sslio[13753]: info: bytes in: 120
2012-10-17 16:46:56.205208500 sslio[13753]: info: bytes ou: 0
2012-10-17 16:46:56.205209500 imapfront-auth[13751]: * OK imapfront ready.
2012-10-17 16:46:56.205209500 tcpsvd: info: end 13751 exit 0

direi che questo fatal: unable to send ssl response: broken pipe è una cosa strana..
Nelle impostazioni delle email, dal pannello di controllo risultano configurati così:

Configurazione ricezione e-mail:
-Modalità scaricamento e-mail: Standard (SMTP)
-Autenticazione SMTP: Accesso SMTP e SSMTP

Configurazione distribuzione e-mail:
-Posta ad utenti sconosciuti: Rifiuta
-Indirizzo del mail server del provider Internet: out.alice.it

Adesso mi metto alla ricerca di cosa potrebbe aver generato quel warning...

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: SME 8 ed IMAP iPad/iPhone
« Reply #5 on: October 18, 2012, 11:58:18 PM »
e i due dispositivi melafonici come sono impostati?

Offline nicolatiana

  • *
  • 724
  • +0/-0
Re: SME 8 ed IMAP iPad/iPhone
« Reply #6 on: October 19, 2012, 09:54:28 AM »
Excuse moi
 
i palmari/tablet devono funzionare sulla WAN (collegati via SIM-Dati = fuori dall'ufficio) o sulla LAN (collegati via wLan = dentro l'ufficio) ?
Quindi, sono configurati come i client Thunderbird o in un modo diverso ?
Non è che cerchi di collegarti via wLan (dall'ufficio) interrogando il tuo IP pubblico ?
 
Nicola
Consulente di Smeserver.it -  Soluzioni e supporto su Sme server in Italia.

Offline andreasantini

  • ***
  • 68
  • +0/-0
Re: SME 8 ed IMAP iPad/iPhone
« Reply #7 on: October 19, 2012, 11:43:34 AM »
Ciao,
ho anche io un Iphone e un LG con Android.
Lo stesso account con android funziona benissimo,naturalmente in IMAP, mentre con Iphone,
non mi scarica le email,anche se in fase di programmazione dell'account su Iphone non ho ricevuto alcun errore.I parametri che ho utilizzato sono IMAP 993 SSL    SMTP 465 SSL.
L'unico avviso che avevo ricevuto da Iphone era stato che il server SME non era certificato,ma con l'opzione di accettare comunque la connessione.

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: SME 8 ed IMAP iPad/iPhone
« Reply #8 on: October 19, 2012, 12:25:11 PM »
Lo stesso account con android funziona benissimo,naturalmente in IMAP, mentre con Iphone,
non mi scarica le email,anche se in fase di programmazione dell'account su Iphone non ho ricevuto alcun errore.

eh.. la tauromachia... ;-)