Re: plus addressing over lmtp not working / sam [box] anyone p set
On Wed, Dec 10, 2008 at 4:04 PM, Stefan Pampel antispam <[EMAIL PROTECTED]> wrote: > Hello all, > > thanks for you replies. > > ["Followup-To:" nach gmane.mail.imap.cyrus gesetzt.] > Lan Tran <[EMAIL PROTECTED]> schrieb: >> From: "Alain Spineux" <[EMAIL PROTECTED]> >>> On Tue, Dec 2, 2008 at 8:59 PM, Stefan Pampel >>> <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alain Spineux <[EMAIL PROTECTED]> schrieb: Dec 2 20:44:19 asp4 postfix/smtpd[6073]: connect from mail-qy0-f21.google.com[209.85.221.21] Dec 2 20:44:20 asp4 postfix/smtpd[6073]: 53DEDE01D5A: client=mail-qy0-f21.google.com[209.85.221.21] Dec 2 20:44:20 asp4 postfix/cleanup[6076]: 53DEDE01D5A: message-id=<[EMAIL PROTECTED]> Dec 2 20:44:20 asp4 postfix/qmgr[2392]: 53DEDE01D5A: from=<[EMAIL PROTECTED]>, size=2214, nrcpt=1 (queue active) Dec 2 20:44:21 asp4 postfix/smtpd[6081]: connect from > unknown[127.0.0.1] Dec 2 20:44:21 asp4 postfix/smtpd[6081]: D0B24EF4D11: client=unknown[127.0.0.1] Dec 2 20:44:21 asp4 postfix/cleanup[6076]: D0B24EF4D11: message-id=<[EMAIL PROTECTED]> Dec 2 20:44:21 asp4 postfix/smtpd[6081]: disconnect from unknown[127.0.0.1] Dec 2 20:44:21 asp4 postfix/qmgr[2392]: D0B24EF4D11: from=<[EMAIL PROTECTED]>, size=2816, nrcpt=1 (queue active) Dec 2 20:44:21 asp4 cyrus/lmtpunix[6070]: accepted connection Dec 2 20:44:21 asp4 cyrus/lmtpunix[6070]: lmtp connection preauth'd as postman Dec 2 20:44:21 asp4 cyrus/master[6083]: about to exec /usr/lib/cyrus/bin/lmtpd Dec 2 20:44:21 asp4 cyrus/lmtpunix[6083]: executed Dec 2 20:44:21 asp4 amavis[17280]: (17280-18) Passed CLEAN, [209.85.221.21] [209.85.221.21] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Message-ID: > <[EMAIL PROTECTED]>, mail_id: ggSVa5nIr8Oq, Hits: -0.001, size: 2214, queued_as: > D0B24EF4D11, 1298 m s Dec 2 20:44:21 asp4 postfix/lmtp[6077]: 53DEDE01D5A: > to=<[EMAIL PROTECTED]>, orig_to=<[EMAIL PROTECTED]>, relay=127.0.0.1 [127.0.0.1]:10024, delay=1.7, delays=0.39/0/0/1.3, dsn=2.0.0, > status=sent (250 2.0.0 Ok, id=17280-18, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued a >>> >>> HERE is the "culprit" ! postfix tell us, it got "user+spam" and give >>> back "user" to [127.0.0.1]:10024 ! > > ok, the problem is that postfix remove the +whatever . I've done some > researches on this, but actually i didn't found a solution. In case of > being OT just ignore my reply, but maybe someone can give a hint on this > issue. I dont see nothing wrong in your main.cf Can you post your master.cf ? You will get a better answer on the postfix mailing list :-) > > My tests: > sending fom command line to port 10025 (means bypassing amavis) > > > Return-Path: <[EMAIL PROTECTED]> > Received: from foo.org ([unix socket]) > by foo.org (Cyrus v2.2.13-Debian-2.2.13-14+b3) with LMTPA; > Thu, 04 Dec 2008 19:39:50 +0100 > X-Sieve: CMU Sieve 2.2 > Received: from unknown (unknown [127.0.0.1]) >by foo.org (Postfix) with SMTP id 2EE4DEEFB3A >for <[EMAIL PROTECTED]>; Thu, 4 Dec 2008 19:38:54 +0100 (CET) > Message-Id: <[EMAIL PROTECTED]> > Date: Thu, 4 Dec 2008 19:38:54 +0100 (CET) > From: [EMAIL PROTECTED] > To: undisclosed-recipients:; > > blah > > > testing with > > sendmail -bv [EMAIL PROTECTED] > > as mentioned in http://www.postfix.org/ADDRESS_REWRITING_README.html > gives, the following. > > Return-Path: <> > Received: from foo.org ([unix socket]) > by foo.org (Cyrus v2.2.13-Debian-2.2.13-14+b3) with LMTPA; > Thu, 04 Dec 2008 22:56:08 +0100 > X-Sieve: CMU Sieve 2.2 > Received: by foo.org (Postfix) >id 49719EF4D11; Thu, 4 Dec 2008 22:56:08 +0100 (CET) > Date: Thu, 4 Dec 2008 22:56:08 +0100 (CET) > From: [EMAIL PROTECTED] (Mail Delivery System) > Subject: Mail Delivery Status Report > To: [EMAIL PROTECTED] > Auto-Submitted: auto-replied > MIME-Version: 1.0 > Content-Type: multipart/report; report-type=delivery-status; >boundary="3B1BDEF4D13.1228427768/foo.org" > Message-Id: <[EMAIL PROTECTED]> > > This is a MIME-encapsulated message. > > - --3B1BDEF4D13.1228427768/foo.org > Content-Description: Notification > Content-Type: text/plain; charset=us-ascii > > This is the mail system at host foo.org. > > Enclosed is the mail delivery report that you requested. > > The mail system > > <[EMAIL PROTECTED]> (expanded from ><[EMAIL PROTECTED]>): delivery via >foo.org[/var/run/cyrus/socket/lmtp]: 250 2.1.5 ok > > - --3B1BDEF4D13.1228427768/foo.org > Content-Description: Delivery report > Content-Type: message/delivery-status > > Reporting-MTA: dns; foo.org > X-Postfix-Queue-ID: 3B1BDEF4D13 > X-Postfix-Sender: rfc822; [EMAIL PROTECTED] > Arrival-Date: Thu, 4 Dec 2008 22:56:08 +0100 (CET) > > Final-Recipient: rfc822; [EMAIL PROTECTED] > Original-Recipient: rfc822; [EMAIL PROTECTED] >
Re: Trying to get Sieve working
That was my problem. I had "timsieved 2000/tcp" instead of just "sieve 2000/tcp". I fixed that and now it runs properly. Thank you for your help! David Nic Bernstein wrote: > Does your /etc/services file have an entry for sieve? Mine (FreeBSD 7) is : > sieve2000/tcp > > Of course yours should refer to whichever port you are using (typically > 2000). > > Cheers, > -nic > > David Korpiewski wrote: >> This is a very odd problem that I can't seem to dig up much information >> on. I think the problem itself is very simple, I just don't know how to >> rectify it: >> >> I am trying to set of Sieve filtering on a 10.5.4 OSX mail Server. >> However, when I turn on the mail server, timsieved is never running! In >> the logs I get: >> >> "nodename nor servname provided, or not known, disabling sieve" >> >> At startup when I bring up the mail server (serveradmin start mail). >> >> >> I don't understand what is missing to get sieve running. Does anyone know? >> >> The error "nodename nor servname provided" is a very common error having >> to do with the "getaddrinfo". >> >> Any help would be wonderful and very much appreciated. >> Thank you >> David >> > > -- === David Korpiewski Software Specialist I CSCF - Computer Science Computing Facility Department of Computer Science Phone: 413-545-4319 Fax: 413-577-2285 === Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Trying to get Sieve working
Does your /etc/services file have an entry for sieve? Mine (FreeBSD 7) is : sieve2000/tcp Of course yours should refer to whichever port you are using (typically 2000). Cheers, -nic David Korpiewski wrote: > This is a very odd problem that I can't seem to dig up much information > on. I think the problem itself is very simple, I just don't know how to > rectify it: > > I am trying to set of Sieve filtering on a 10.5.4 OSX mail Server. > However, when I turn on the mail server, timsieved is never running! In > the logs I get: > > "nodename nor servname provided, or not known, disabling sieve" > > At startup when I bring up the mail server (serveradmin start mail). > > > I don't understand what is missing to get sieve running. Does anyone know? > > The error "nodename nor servname provided" is a very common error having > to do with the "getaddrinfo". > > Any help would be wonderful and very much appreciated. > Thank you > David > -- Nic Bernstein [EMAIL PROTECTED] Onlight llc. www.onlight.com 2266 North Prospect Avenue #610 v. 414.272.4477 Milwaukee, Wisconsin 53202-6306 f. 414.290.0335 Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Trying to get Sieve working
This is a very odd problem that I can't seem to dig up much information on. I think the problem itself is very simple, I just don't know how to rectify it: I am trying to set of Sieve filtering on a 10.5.4 OSX mail Server. However, when I turn on the mail server, timsieved is never running! In the logs I get: "nodename nor servname provided, or not known, disabling sieve" At startup when I bring up the mail server (serveradmin start mail). I don't understand what is missing to get sieve running. Does anyone know? The error "nodename nor servname provided" is a very common error having to do with the "getaddrinfo". Any help would be wonderful and very much appreciated. Thank you David -- === David Korpiewski Software Specialist I CSCF - Computer Science Computing Facility Department of Computer Science Phone: 413-545-4319 Fax: 413-577-2285 === Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Easy bug: undocumented option "sasl_saslauthd_path" to imapd
Please add your comments and concerns to this entry: https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3115 :wes Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: murder configuration issue final stretch
On Tue, 9 Dec 2008, Gary W. Smith wrote: > Andy/Wesley, > > First off, thanks for all of the help. I've gotten pretty far I think. > I ran into a couple problems and some notes on some list groups about > dead options that were shown in examples. > > http://garysmith.pbwiki.com/Cyrus > > I have put all of my configs into a wiki (broken down by server/type). > The problem that I'm running into right now is that if I log into the > frontend box using cyradmin (as root or cyrus) I can see mailboxes but > when I go to create one on a backend server, cyradm prompts me for the > password for the corresponding account on the remote machine. I'm not > sure if this is by design or an issue. > > The other big issue is that I have lmtp configured on the frontend to > forward to the backend. The lmtp process is running on the backend as I > can telnet to it (telnet ip lmtp). On the backend I seem to be getting > a SASL2 auth error. > > badlogin: 10.80.72.1 PLAIN SASL(-13): authentication failure: Password > verification failed The documentation doesn't state this, but in a murder environment all LMTP connections must be authenticated. Using the "-a" option doesn't work because then the frontend doesn't have a set of credentials for proxying. At least, that's what my testing showed. Try creating a "cyr_lmtp" (or whatever you want to call it) user on both your backends and frontends. Then add the following: On backends: lmtp_admins: cyr_lmtp murder On frontends: lmtp_admins: cyr_lmtp Then make sure your MTA is authenticating as cyr_lmtp when it connects to the Cyrus lmtpd. Andy Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: plus addressing over lmtp not working / sam [box] anyone p set
Hello all, thanks for you replies. ["Followup-To:" nach gmane.mail.imap.cyrus gesetzt.] Lan Tran <[EMAIL PROTECTED]> schrieb: > From: "Alain Spineux" <[EMAIL PROTECTED]> >> On Tue, Dec 2, 2008 at 8:59 PM, Stefan Pampel >> <[EMAIL PROTECTED]> wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> Alain Spineux <[EMAIL PROTECTED]> schrieb: >>> >>> Dec 2 20:44:19 asp4 postfix/smtpd[6073]: connect from >>> mail-qy0-f21.google.com[209.85.221.21] >>> Dec 2 20:44:20 asp4 postfix/smtpd[6073]: 53DEDE01D5A: >>> client=mail-qy0-f21.google.com[209.85.221.21] >>> Dec 2 20:44:20 asp4 postfix/cleanup[6076]: 53DEDE01D5A: >>> message-id=<[EMAIL PROTECTED]> >>> Dec 2 20:44:20 asp4 postfix/qmgr[2392]: 53DEDE01D5A: >>> from=<[EMAIL PROTECTED]>, size=2214, nrcpt=1 (queue active) >>> Dec 2 20:44:21 asp4 postfix/smtpd[6081]: connect from unknown[127.0.0.1] >>> Dec 2 20:44:21 asp4 postfix/smtpd[6081]: D0B24EF4D11: >>> client=unknown[127.0.0.1] >>> Dec 2 20:44:21 asp4 postfix/cleanup[6076]: D0B24EF4D11: >>> message-id=<[EMAIL PROTECTED]> >>> Dec 2 20:44:21 asp4 postfix/smtpd[6081]: disconnect from >>> unknown[127.0.0.1] >>> Dec 2 20:44:21 asp4 postfix/qmgr[2392]: D0B24EF4D11: >>> from=<[EMAIL PROTECTED]>, size=2816, nrcpt=1 (queue active) >>> Dec 2 20:44:21 asp4 cyrus/lmtpunix[6070]: accepted connection >>> Dec 2 20:44:21 asp4 cyrus/lmtpunix[6070]: lmtp connection preauth'd as >>> postman >>> Dec 2 20:44:21 asp4 cyrus/master[6083]: about to exec >>> /usr/lib/cyrus/bin/lmtpd >>> Dec 2 20:44:21 asp4 cyrus/lmtpunix[6083]: executed >>> Dec 2 20:44:21 asp4 amavis[17280]: (17280-18) Passed CLEAN, >>> [209.85.221.21] [209.85.221.21] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, >>> Message-ID: <[EMAIL PROTECTED]>, >>> mail_id: ggSVa5nIr8Oq, Hits: -0.001, size: 2214, queued_as: D0B24EF4D11, >>> 1298 m >>> s >>> Dec 2 20:44:21 asp4 postfix/lmtp[6077]: 53DEDE01D5A: to=<[EMAIL PROTECTED]>, >>> orig_to=<[EMAIL PROTECTED]>, relay=127.0.0.1 >>> [127.0.0.1]:10024, delay=1.7, delays=0.39/0/0/1.3, dsn=2.0.0, status=sent >>> (250 2.0.0 Ok, id=17280-18, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: >>> queued a >> >> HERE is the "culprit" ! postfix tell us, it got "user+spam" and give >> back "user" to [127.0.0.1]:10024 ! ok, the problem is that postfix remove the +whatever . I've done some researches on this, but actually i didn't found a solution. In case of being OT just ignore my reply, but maybe someone can give a hint on this issue. My tests: sending fom command line to port 10025 (means bypassing amavis) Return-Path: <[EMAIL PROTECTED]> Received: from foo.org ([unix socket]) by foo.org (Cyrus v2.2.13-Debian-2.2.13-14+b3) with LMTPA; Thu, 04 Dec 2008 19:39:50 +0100 X-Sieve: CMU Sieve 2.2 Received: from unknown (unknown [127.0.0.1]) by foo.org (Postfix) with SMTP id 2EE4DEEFB3A for <[EMAIL PROTECTED]>; Thu, 4 Dec 2008 19:38:54 +0100 (CET) Message-Id: <[EMAIL PROTECTED]> Date: Thu, 4 Dec 2008 19:38:54 +0100 (CET) From: [EMAIL PROTECTED] To: undisclosed-recipients:; blah testing with sendmail -bv [EMAIL PROTECTED] as mentioned in http://www.postfix.org/ADDRESS_REWRITING_README.html gives, the following. Return-Path: <> Received: from foo.org ([unix socket]) by foo.org (Cyrus v2.2.13-Debian-2.2.13-14+b3) with LMTPA; Thu, 04 Dec 2008 22:56:08 +0100 X-Sieve: CMU Sieve 2.2 Received: by foo.org (Postfix) id 49719EF4D11; Thu, 4 Dec 2008 22:56:08 +0100 (CET) Date: Thu, 4 Dec 2008 22:56:08 +0100 (CET) From: [EMAIL PROTECTED] (Mail Delivery System) Subject: Mail Delivery Status Report To: [EMAIL PROTECTED] Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="3B1BDEF4D13.1228427768/foo.org" Message-Id: <[EMAIL PROTECTED]> This is a MIME-encapsulated message. - --3B1BDEF4D13.1228427768/foo.org Content-Description: Notification Content-Type: text/plain; charset=us-ascii This is the mail system at host foo.org. Enclosed is the mail delivery report that you requested. The mail system <[EMAIL PROTECTED]> (expanded from <[EMAIL PROTECTED]>): delivery via foo.org[/var/run/cyrus/socket/lmtp]: 250 2.1.5 ok - --3B1BDEF4D13.1228427768/foo.org Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; foo.org X-Postfix-Queue-ID: 3B1BDEF4D13 X-Postfix-Sender: rfc822; [EMAIL PROTECTED] Arrival-Date: Thu, 4 Dec 2008 22:56:08 +0100 (CET) Final-Recipient: rfc822; [EMAIL PROTECTED] Original-Recipient: rfc822; [EMAIL PROTECTED] Action: deliverable Status: 2.1.5 Remote-MTA: dns; foo.org Diagnostic-Code: smtp; 250 2.1.5 ok - --3B1BDEF4D13.1228427768/foo.org Content-Description: Message Headers Content-Type: text/rfc822-headers Received: by foo.org (Postfix, from userid 1999) id 3B1BDEF4D13; Thu, 4 Dec 2008 22:56:08 +0100 (CET) From: [EMAIL PROTECTED] Subject: probe To: [EMAIL PROTECTED] Message-Id: <[EMAIL PROTECTE
migrating mapi
Hi, I'm on the run to install a new cyrus imap server with 50 clients. All of them have mapi clients with their old pop account on Outlook or Express, containing all their history emails in folders. I was going to develop a mini tool to transfer mapi account folders and emails onto the imap server in Java, but it seems there is few chances to read mapi folders from Java...am I wrong? In any case, I don't need this tool do be Java at all, it's just that I write only Java for years, and I'm skilled with JavaMail. I also searched for existing tools to do this, but found none. Can you help? Thanx a lot Gabriele. Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Easy bug: undocumented option "sasl_saslauthd_path" to imapd
> imapd.conf will accept an option: > >sasl_saslauthd_path: /var/spool/postfix/var/run/saslauthd/mux > > instructing it to connect to the saslauthd socket in a non-standard > location (usually /var/run). This is very useful if e.g. you're > running Postfix in a chroot. > > A recursive grep for ``sasl_saslauthd_path'' in the source yields no > occurances of this option anywhere! It should at least be in the > imapd.conf or imapd manpages, correct? This (saslauthd_path) is a Cyrus-SASL Option, not a Cyrus-IMAP option. If the Cyrus-SASL Library wants to resolv an Option it asks the Application first if it wants to override the Option. In Cyrus-Imap this feature is used and you can specify Cyrus-SASL Options in the Configuration File of Cyrus-IMAP. To separate these Options from the real Cyrus-IMAP Options they have to be prefixed with "sasl_". So in Cyrus-IMAP all given sasl_* Options are forwarded to Cyrus-SASL. There is no other relation for these Options in Cyrus-IMAP. I see no sense in adding documentation for each Cyrus-SASL Option to Cyrus-IMAP's Documentation. There are a lot more than mentioned in the imapd.conf Man-Page. But maybe it would be nice to have a better desciption of this handling in the man-Page. -- Andreas Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
