Problem after update (deliver not working anymore)

. Command output: couldn't connect to lmtpd: Permission denied 421 4.3.0 deliver: couldn't connect to lmtpd_ We are using for some shared mailfolders /etc/aliases with NAME:  ""|/usr/bin/formail -I \"From \" |/usr/lib/cyrus/bin/deliver -e -a cyrus -m NAME&quo

Re: 421 4.3.0 deliver: Trying to unput wrong character

hison wrote: What is the Content-Transfer-Encoding of the email? Was the message Base64 encoded, or is the PNG included as raw binary data? Raw... Here are the full headers (the first line -- the From_ -- is removed by sed before feeding the rest into deliver): From m...@example.com Mon

Re: 421 4.3.0 deliver: Trying to unput wrong character

> This is one of those weird inconsistencies between IMAP and SMTP protocols … > as far as I remember, the NUL character restriction only applies to the IMAP > protocol … so your MTA (e.g. sendmail) is not breaking the SMTP RFC by > transferring them. True, but it's breaking the Internet Message F

Re: 421 4.3.0 deliver: Trying to unput wrong character

may be useful: http://info-cyrus.andrew.cmu.narkive.com/Rro4Nn9M/554-message-contains-nul-characters The link talks about stripping the offending character -- which would break the content in some cases (including mine). Maybe, it is time deliver is modified to do the right thing -- and re

Re: 421 4.3.0 deliver: Trying to unput wrong character

as raw binary data? > Raw... Here are the full headers (the first line -- the From_ -- is removed > by sed before feeding the rest into deliver): > From m...@example.com <mailto:m...@example.com> Mon Jul 24 00:53:00 2017 > Received: from narawntapu.narawntapu (localhost [127

Re: 421 4.3.0 deliver: Trying to unput wrong character

the rest into deliver): From m...@example.com Mon Jul 24 00:53:00 2017 Received: from narawntapu.narawntapu (localhost [127.0.0.1]) by narawntapu.narawntapu (8.15.2/8.15.2) with ESMTPS id v6O4r05T003160 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits

Re: 421 4.3.0 deliver: Trying to unput wrong character

What is the Content-Transfer-Encoding of the email? Was the message Base64 encoded, or is the PNG included as raw binary data? On 07/24/2017 01:19 AM, Mikhail T. wrote: My procmail is configured to feed incoming mail into deliver: :0wr |sed 1d | /opt/cyrus/bin/deliver mi Recently

421 4.3.0 deliver: Trying to unput wrong character

My procmail is configured to feed incoming mail into deliver: :0wr |sed 1d | /opt/cyrus/bin/deliver mi Recently I received an e-mail consisting of a PNG-file -- not an attachment, the body of the e-mail had content-type image/png. That message ended up in my /var/mail/mi mailbox

Re: sendmail cyrusv2.m4 deliver per domain to diffent cyrus

Am 23.07.2015 um 13:49 schrieb Marcus Schopen: > Hi, > > is it possible to deliver per domain to different cyrus hosts via lmtp > with e.g. two different cyrusv2.m4 macros? http://www.phildev.net/cyrus/cyrus_mta.html > Ciao > Marcus Alexander Cyrus Home Page: http:/

sendmail cyrusv2.m4 deliver per domain to diffent cyrus

Hi, is it possible to deliver per domain to different cyrus hosts via lmtp with e.g. two different cyrusv2.m4 macros? Ciao Marcus Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu

Re: LMTP (deliver) error 65 / Telemetry and debugging not working like described

Bron, thank you very much for your help. On 28.05.2015 13:02, Bron Gondwana wrote: > If you have an example message that you're happy to share with the list (or > just privately with me even) it might be fairly easy to see what's wrong. I really would like to provide some example messages, but

Re: LMTP (deliver) error 65 / Telemetry and debugging not working like described

g fetchmail to poll mail from some > external accounts and deliver the messages to cyrus imapd. The problem arises > when the messages are malformed. In my previous post to this list, I have > described the situation in detail. I don't want to clutter the list, so I > hope it&#

LMTP (deliver) error 65 / Telemetry and debugging not working like described

Dear all, I am running into some problems when using fetchmail to poll mail from some external accounts and deliver the messages to cyrus imapd. The problem arises when the messages are malformed. In my previous post to this list, I have described the situation in detail. I don't wa

Re: Deliver to mailbox problem with v2.4.7

> As a quick "get me home fix" I'd like to set "anyone p" on all my > mailbox folders until there is a solution to this problem. > However, there doesn't seem to be any easy way to do this. I'm off to > write a script now but if there is an easy way please can you let me > know what it is... > ---

Re: Deliver to mailbox problem with v2.4.7

On 11/04/11 10:18, cy...@jelmail.com wrote: > > Original Message: > - > From: Bron Gondwana br...@fastmail.fm > Date: Mon, 11 Apr 2011 06:38:44 +0200 > To: cy...@jelmail.com, info-cyrus@lists.andrew.cmu.edu > Subject: Re: Deliver to mailbox problem with v2.4.7

Re: Deliver to mailbox problem with v2.4.7

Original Message: - From: Bron Gondwana br...@fastmail.fm Date: Mon, 11 Apr 2011 06:38:44 +0200 To: cy...@jelmail.com, info-cyrus@lists.andrew.cmu.edu Subject: Re: Deliver to mailbox problem with v2.4.7 On Mon, Apr 11, 2011 at 12:17:47AM +0100, John wrote: > On 09/04/11 23

Re: Deliver to mailbox problem with v2.4.7

> Can you test to see if the same problem happens with folders without dots > > in them? > > Ok, on further testing today, adding "anyone p" does make it deliver ok. Can you just confirm: "anyone p" only works for folders without dots in the names? > This is w

Re: Deliver to mailbox problem with v2.4.7

john.folder.name" | head -1 >> user.john.folder^name 0 default john lrswipcda anyone p >> >> The folder list is sane in imap client. Everything is working fine >> except delivery into folders. All mail already delivered prior to >> upgrade is in folders an

Re: Deliver to mailbox problem with v2.4.7

On 09/04/11 22:33 +0100, John wrote: >Sorry for delay in responding, I have been away. > >Setting "anyone p" made no difference: > >localhost.localdomain> sam user/john anyone p >localhost.localdomain> lam user/john >john lrswipcda >anyone p > >localhost.localdomain> sam user/john/folder.name/subfo

Re: Deliver to mailbox problem with v2.4.7

On 07/04/11 22:43, Dan White wrote: > On 07/04/11 23:23 +0100, John wrote: >> On 07/04/11 22:06, Dan White wrote: >>> 'deliver' should deliver to the user's INBOX if it believes there's a >>> permissions problem, or if it believes the mailbox do

Re: Deliver to mailbox problem with v2.4.7

On 07/04/11 23:23 +0100, John wrote: >On 07/04/11 22:06, Dan White wrote: >> 'deliver' should deliver to the user's INBOX if it believes there's a >> permissions problem, or if it believes the mailbox doesn't exist. Does >> syslog give you any hints

Re: Deliver to mailbox problem with v2.4.7

lar to the below : >> >> /usr/cyrus/bin/deliver -a john -m folder/subfolder john < message >> >> This would result in message being dropped into john/folder/subfolder >> >> Since the upgrade everything is delivered to john/INBOX; the "-m" >> argument

Re: Deliver to mailbox problem with v2.4.7

On 07/04/11 22:30 +0100, John wrote: >Good afternoon, > >I have just upgraded from Cyrus-IMAP 2.3.15 to 2.4.7 and my mailbox >delivery has stopped working. > >My procmail delivers mail using a command similar to the below : > >/usr/cyrus/bin/deliver -a john -m folder/

Re: Deliver to mailbox problem with v2.4.7

I am wondering why you have been using procmail with cyrus. You should deliver to cyrus malboxes using LMTP with unix socket or with TCP. You can easily change your configuration. Also I think it is not very efficient to call the deliver process for every message to be delivered to a malbox. IF

Deliver to mailbox problem with v2.4.7

Good afternoon, I have just upgraded from Cyrus-IMAP 2.3.15 to 2.4.7 and my mailbox delivery has stopped working. My procmail delivers mail using a command similar to the below : /usr/cyrus/bin/deliver -a john -m folder/subfolder john < message This would result in message being dropped i

Re: What tells cyrus to deliver to domain

On 03/11/2011 02:35 PM, Jon wrote: > On 03/11/2011 11:42 AM, Dan White wrote: > >> On 11/03/11 11:01 -0900, Jon wrote: >> >>> I am fighting trying to understand why my mail gets delivered to >>> /var/spool/imap/j instead of /var/spool/imap/domain/d/destar.net/j/. I >>> had this working bu

Re: What tells cyrus to deliver to domain

On 03/11/2011 11:42 AM, Dan White wrote: > On 11/03/11 11:01 -0900, Jon wrote: >> I am fighting trying to understand why my mail gets delivered to >> /var/spool/imap/j instead of /var/spool/imap/domain/d/destar.net/j/. I >> had this working but now when I send a message it goes to the former >> rat

Re: deliver mail to mailbox subfolder via lmtp

xcmd="lmtpd" listen="/var/spool/postfix/public/lmtp" >prefork=1 maxchild=30 > ># from imapd.conf >lmtpsocket: /var/spool/postfix/public/lmtp > > >now i'm trying to deliver a mail to the recipient foobar+folder@domain and >the mail should be pla

Re: What tells cyrus to deliver to domain

On 11/03/11 11:01 -0900, Jon wrote: >I am fighting trying to understand why my mail gets delivered to >/var/spool/imap/j instead of /var/spool/imap/domain/d/destar.net/j/. I >had this working but now when I send a message it goes to the former >rather than the latter. Can someone shed some light on

What tells cyrus to deliver to domain

I am fighting trying to understand why my mail gets delivered to /var/spool/imap/j instead of /var/spool/imap/domain/d/destar.net/j/. I had this working but now when I send a message it goes to the former rather than the latter. Can someone shed some light on this for me? Thanks for any help,

deliver mail to mailbox subfolder via lmtp

refork=1 maxchild=30 # from imapd.conf lmtpsocket: /var/spool/postfix/public/lmtp now i'm trying to deliver a mail to the recipient foobar+folder@domain and the mail should be placed in the $INBOX/folder from user foobar. But this works only if i allow the post acl "p"

Re: sendmail/cyrus deliver not to subdomain

Hello Andrzej My setup is FreeBSD 7.2 amd64 and the newest Cyrus Imapd (.15). My cyrus server as the defaultdomain set to abc.ch and I set virtdomains: userid . All users works a expected. Now I want to receive additionaly mails for sub.abc.ch. In sendmail set all th

Re: sendmail/cyrus deliver not to subdomain

Martin Schweizer wrote: > Hello > > My setup is FreeBSD 7.2 amd64 and the newest Cyrus Imapd (.15). > > My cyrus server as the defaultdomain set to abc.ch and I set virtdomains: > userid > . All users works a expected. Now I want to receive additionaly mails > for sub.abc.ch. In sendmail set all

sendmail/cyrus deliver not to subdomain

Hello My setup is FreeBSD 7.2 amd64 and the newest Cyrus Imapd (.15). My cyrus server as the defaultdomain set to abc.ch and I set virtdomains: userid . All users works a expected. Now I want to receive additionaly mails for sub.abc.ch. In sendmail set all the necessary entries in access. I also

Re: deliver to mailbox folder not working

> I have a script that re-delivers email messages from one mailbox to > another. The following worked with 2.3.13 but does NOT work with 2.3.14 > > /usr/lib/cyrus/deliver -a testuser -m user.testuser.subfolder < email.txt > > All i get is mailbox does not exist and a &qu

deliver to mailbox folder not working

I have a script that re-delivers email messages from one mailbox to another. The following worked with 2.3.13 but does NOT work with 2.3.14 /usr/lib/cyrus/deliver -a testuser -m user.testuser.subfolder < email.txt All i get is mailbox does not exist and a "lmtpunix: ver

deliver fails when -q option used

I am moving our cyrus mail server from a CentOS4 to CentOS5 box. This means a cyrus upgrade from 2.2.12 to 2.3.7 We have sendmail use procmail for local mail delivery which in turn delivers to cyrus IMAP via the deliver command. Specifically we have the lines in procmailrc of

procmail, deliver and failure (65)

Hi, I use procmail to filter emails tagged by spamassassin and use deliver to put them in the mailbox as follows: :0 w | /usr/lib/cyrus-imapd/deliver -a $USER -m user.$USER after a recent update I am getting an exit code 65 from deliver which, if I am not wrong, means a wrong formatting

Re: Postfix can't deliver to cyrus via lmtp

Derek Croxton wrote, at 07/11/2008 02:36 PM: > I'm migrating a cyrus + postfix server to Ubuntu Hardy. Everything > else works -- old mail is migrated, I can read it, and I can send > mail -- but I can't receive mail. It gets stuck in postfix, with the > error "warning: connect #[x] to subsystem pr

Postfix can't deliver to cyrus via lmtp

I'm migrating a cyrus + postfix server to Ubuntu Hardy. Everything else works -- old mail is migrated, I can read it, and I can send mail -- but I can't receive mail. It gets stuck in postfix, with the error "warning: connect #[x] to subsystem private/lmtp: Connection refused". I discovered tha

Re: Can Cyrus deliver to a default mailbox?

Sebastian Hagedorn <[EMAIL PROTECTED]> wrote: > [...] > Another approach is this one: > > > > Take your pick ... RTCyrus3 is available at http://open-sendmail.sourceforge.net/ -- [pl>en: Andrew] Andrzej Adam Filip : [EMAIL PR

Re: Can Cyrus deliver to a default mailbox?

, I have two questions (I think either one will solve the problem) 1 - can Cyrus accept and deliver all messages to a default mailbox if the user / mailbox doesn't exist? See below. 2 - Is there a way for Cyrus to tell sendmail that the user doesn't exist? Yes. In fact there are sev

Can Cyrus deliver to a default mailbox?

mail to unknown users needs to be delivered to a "catchall" mailbox. Currently sendmail has a define for LUSER_RELAY and the imapd.conf file has an entry of soft_nouath: 0. So, I have two questions (I think either one will solve the problem) 1 - can Cyrus accept and deliver a

Re: Want cyrus to deliver directly into a mailbox's folder.

yé : 20 mars 2008 12:20 Objet : Re: Want cyrus to deliver directly into a mailbox's folder. > Mail is likely not getting delivered as user cyrus, but as user anonymous. > To make it work, the trick is usually to give user "anyone" the "p" ACL > (and obvious

Re: Want cyrus to deliver directly into a mailbox's folder.

> Mar 20 11:09:05 mypostfix postfix/lmtp[22947]: 348ED583EB: > to=<[EMAIL PROTECTED]>, orig_to=<[EMAIL PROTECTED]>, > relay=mycyrus[myip]:24, delay=0.14, delays=0.11/0.01/0/0.02, dsn=2.1.5, > status=sent (250 2.1.5 Ok) > > and it is delivered in my INBOX mailbox, not in my spam folder!! > > User

Re: Want cyrus to deliver directly into a mailbox's folder.

Mail is likely not getting delivered as user cyrus, but as user anonymous. To make it work, the trick is usually to give user "anyone" the "p" ACL (and obviously nothing else). See if that works... -Michael --On Thursday, March 20, 2008 11:45 AM -0400 Eddy Beliveau <[EMAIL PROTECTED]> wrote:

Want cyrus to deliver directly into a mailbox's folder.

Hi! I'm using Cyrus v2.2.12 with success I'm trying to move directly some emails into a 'spam' folder It doesn't work as expected. My postfix server send correctly to my Cyrus lmtp service Mar 20 11:09:05 mypostfix postfix/lmtp[22947]: 348ED583EB: to=<[EMAIL PROTECTED]>, orig_to=<[EMAIL PROT

Cyrus deliver appending newline to messages

We're running cyrus-imap 2.3.11 and whenever I deliver a mail message with deliver(8), a newline gets appended to the message. Why? If I bounce the message, no newline gets appended. -- albert chin ([EMAIL PROTECTED]) Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ:

Re: deliver and sieve?

David Reid wrote: > Is it possible to deliver mail (after procmail processing) to the server > such that sieve processing will still be occur? When using deliver it > seems to bypass sieve totally. You have to deliver via LMTP. 'deliver -l' will do this but I *think* del

deliver and sieve?

Is it possible to deliver mail (after procmail processing) to the server such that sieve processing will still be occur? When using deliver it seems to bypass sieve totally. Thanks david Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List

Re: deliver reports (/var/lib/imap/socket/lmtp) failed: Connection refused

he file and directory right! Thanks for your help. I will try this. Regards, Gyorgy > > >> >> Regards, Gyorgy >> >> Idézet (Gyorgy Knyihar <[EMAIL PROTECTED]>): >> >> > Hello Simon, >> > >> > Thank you very much for your

Re: deliver reports (/var/lib/imap/socket/lmtp) failed: Connection refused

h for your help. > > Please see my answers below. > > > > Idezet (Simon Matter <[EMAIL PROTECTED]>): > > > >>> Hello Simon, > >>> > >>> I tried you suggestion and there are no more > >>> "Sep 3 07:45:59 srv1 deliver[20650]: &g

Re: deliver reports (/var/lib/imap/socket/lmtp) failed: Connection refused

yihar <[EMAIL PROTECTED]>): > Hello Simon, > > Thank you very much for your help. > Please see my answers below. > > Idezet (Simon Matter <[EMAIL PROTECTED]>): > >>> Hello Simon, >>> >>> I tried you suggestion and there are no more >>&

Re: deliver reports (/var/lib/imap/socket/lmtp) failed: Connection refused

Hello Simon, Thank you very much for your help. Please see my answers below. Idezet (Simon Matter <[EMAIL PROTECTED]>): >> Hello Simon, >> >> I tried you suggestion and there are no more >> "Sep 3 07:45:59 srv1 deliver[20650]: >> connect(/var/lib/ima

Re: deliver reports (/var/lib/imap/socket/lmtp) failed: Connection refused

> Hello Simon, > > I tried you suggestion and there are no more > "Sep 3 07:45:59 srv1 deliver[20650]: > connect(/var/lib/imap/socket/lmtp) failed: Connection refused" > messages appearing in the error log file. > > Many thanks for your help. > > I run po

Re: deliver reports (/var/lib/imap/socket/lmtp) failed: Connection refused

Hello Simon, I tried you suggestion and there are no more "Sep 3 07:45:59 srv1 deliver[20650]: connect(/var/lib/imap/socket/lmtp) failed: Connection refused" messages appearing in the error log file. Many thanks for your help. I run postfix chrooted so a hardlink pointing to /va

Re: deliver reports (/var/lib/imap/socket/lmtp) failed: Connection refused

> Hello, > > We had a properly working postfix + cyrus-imap system till 23rd of > July. Then messages like the below one started to appear in the log > file. > > Sep 3 07:45:59 srv1 deliver[20650]: > connect(/var/lib/imap/socket/lmtp) failed: Connection refused > >

deliver reports (/var/lib/imap/socket/lmtp) failed: Connection refused

Hello, We had a properly working postfix + cyrus-imap system till 23rd of July. Then messages like the below one started to appear in the log file. Sep 3 07:45:59 srv1 deliver[20650]: connect(/var/lib/imap/socket/lmtp) failed: Connection refused The postfix log shows: Sep 3 07:45:59

Re: deliver -q brings: Over Quota

On Mon, 2 Apr 2007, Frank Richter wrote: Hi, I'm running a standard Murder: 2 backends, 2 frontends (Linux, cyrus-imapd 2.3.8, Simon's RPM). I'd like to use 'deliver -q user' on the frontend for delivering "Over quota messages" to users. This doesn't wo

deliver -q brings: Over Quota

Hi, I'm running a standard Murder: 2 backends, 2 frontends (Linux, cyrus-imapd 2.3.8, Simon's RPM). I'd like to use 'deliver -q user' on the frontend for delivering "Over quota messages" to users. This doesn't work, neither for mailboxes over quota nor f

deliver command line options

hi, i'am using cyrus-imapd version 2.2.12 on suse linux 9.3. in my setup procmail calls deliver which works pretty well. my man page of deliver says deliver [ -C config-file ] [ -d ] [ -r address ] [ -f address ] [ -m mailbox ] [ -a auth-id ] [ -q ] [ u

RE: Program Failure (75) of "/usr/lib/cyrus/bin/deliver"

p: Re: Program Failure (75) of "/usr/lib/cyrus/bin/deliver" i use procmail. that error is often full quota or wrong mailheaders. Try to deliver it manually to cyrus an see the real error. you have the mail somewhere, find it and, cat mail | deliver -q -a userid_cyrus -r from_email us

Program Failure (75) of "/usr/lib/cyrus/bin/deliver"

Hi all, One of the servers I work with gives the following error message in procmail.log when trying to deliver an email to cyrus. I've compared the configuration files of both cyrus and procmail with a working server to see if there's any differences, and can't find any. Program

Re: Possible sendmail misconfiguration to deliver to cyrus

On Dec 4, 2006, at 8:31 AM, Todd Lyons wrote: On Sun, Dec 03, 2006 at 09:23:47PM -0800, Jo Rhett wrote: Can you create a list of all of your users from some other information? If so, 1. Put a list of all of your domains in /etc/mail/virtual-domains 2. put each and every user in virtusertable

SOLVED! Re: Possible sendmail misconfiguration to deliver to cyrus

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Dec 03, 2006 at 07:58:02PM -0800, Todd Lyons wrote: >I'm looking at a cyrus limitation right now. I'm really thinking this >is not cyrus' problem. I'm trying to figure out if it's actually a >sendmail limitation or a sendmail config error on

Re: Possible sendmail misconfiguration to deliver to cyrus

On Mon, 2006-12-04 at 10:24 -0800, Todd Lyons wrote: > >This solved my problem but it requires that I have a local machine account > >for > >each cyrus user. As a small domain that's not a problem for me, but others > >might find it too restrictive. > > I'll test it. As long as by "local user

Re: Possible sendmail misconfiguration to deliver to cyrus

On Mon, Dec 04, 2006 at 11:22:10AM -0600, Dave McCracken wrote: >> As I see it, a more sendmailish solution would be to use a little >> sendmail-fu and make it so that sendmail checks for local user at smtp >> time, but delivers to cyrus at deliver time. I don't have such

Re: Possible sendmail misconfiguration to deliver to cyrus

On Monday 04 December 2006 10:31 am, Todd Lyons wrote: > As I see it, a more sendmailish solution would be to use a little > sendmail-fu and make it so that sendmail checks for local user at smtp > time, but delivers to cyrus at deliver time.  I don't have such fu, but > I see now

Re: Possible sendmail misconfiguration to deliver to cyrus

SMTP connect time the way it does if I configure sendmail to >>deliver to a regular mbox mail spool. > >Can you create a list of all of your users from some other information? > If so, >1. Put a list of all of your domains in /etc/mail/virtual-domains >2. put each and every u

Re: Possible sendmail misconfiguration to deliver to cyrus

Todd Lyons <[EMAIL PROTECTED]> writes: > [...] > My rudimentary understanding of sendmail macros makes me think that > instead of checking for users locally, it's checking for user cyrus > locally (which always succeeds), so the email is accepted for any user. > If it's a problem with the older ver

Re: Possible sendmail misconfiguration to deliver to cyrus

On Sun, Dec 03, 2006 at 07:58:02PM -0800, Todd Lyons wrote: > at m4 code and trying to figure out what I can do to make sendmail check > the user at SMTP connect time the way it does if I configure sendmail to > deliver to a regular mbox mail spool. Here's what a quick Google

Re: Possible sendmail misconfiguration to deliver to cyrus

Todd Lyons wrote: Error" because the user doesn't exist. I have been googling and looking at m4 code and trying to figure out what I can do to make sendmail check the user at SMTP connect time the way it does if I configure sendmail to deliver to a regular mbox mail spool. Can yo

Re: Possible sendmail misconfiguration to deliver to cyrus

at SMTP connect time the way it does if I configure sendmail to deliver to a regular mbox mail spool. Just a thought but what about installing postfix and dropping sendmail as your MTA? It has the ability to authenticate users with cyrus-sasl along with a lot of additional features that

Possible sendmail misconfiguration to deliver to cyrus

the user doesn't exist. I have been googling and looking at m4 code and trying to figure out what I can do to make sendmail check the user at SMTP connect time the way it does if I configure sendmail to deliver to a regular mbox mail spool. Here's what's in my sendmail.mc: [EMAIL P

Re: Cyrus deliver temporary failure (quota not full)

Hi, Thank you for your answer. However, I have a few further questions about this. --- Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: > On Tue, 05 Sep 2006, Hardi Gunawan wrote: > > I tried to find out how to increase the log level > for > > cyrus'

Re: Cyrus deliver temporary failure (quota not full)

On Tue, 05 Sep 2006, Hardi Gunawan wrote: > I tried to find out how to increase the log level for > cyrus' deliver, but I can't find one... Use LMTP, and tell postfix it can deliver as much as it want over the LMTP connection. For deliver, tell postfix it can deliver to just *one

Cyrus deliver temporary failure (quota not full)

conds difference) as the temporary failure. It seems that when there is a Cc, some of the users experience this, but when a direct one-to-one email to the users, they can receive. I tried to find out how to increase the log level for cyrus' deliver, but I can't find one... Can

Postfix won't deliver mails: Mailbox does not exist

13:43 hostsrv02 postfix/smtpd[25635]: mail_addr_find: [EMAIL PROTECTED] -> web0p0001 --SNAP-- Strange problem, isnt it?! Other configuration: master.cf cyrus unix - n n - - pipe user=cyrus argv=/usr/lib/cyrus/deliver -r ${sender} -m ${e

Re: cyrdeliver, exim on sarge - deliver spam to a special folder

"Mihály Litzler" <[EMAIL PROTECTED]> writes: > Sorry If i post a wrong list..., i cannot really determine whether it's an > Exim > or Cyrus problem. > > I would like to deliver spam mails into a different folder instead of INBOX by > default to all of my u

Re: cyrdeliver, exim on sarge - deliver spam to a special folder

7;From ' header, and some other things. The 'message_prefix' setting handles the 'From ' problem. For example, on our mailserver (Exim 4.50, Cyrus 2.2.12 hand-compiled) we use the following transport: local_delivery: driver = pipe command = "/usr/cyrus/bin/del

cyrdeliver, exim on sarge - deliver spam to a special folder

Hi!Sorry If i post a wrong list..., i cannot really determine whether it's an Exim or Cyrus problem.I would like to deliver spam mails into a different folder instead of INBOX by default to all of my users. Simply do a sorting on the header Spam-Flag...I did Google, rtfm, etc. I did my

Re: Deliver AND forward a message

> [Apologies: I only replied to sender and not to list] > > > Thank you for the help. If possible, could you please help me out with > the finer details of sieve. "man sieveshell" might be of help -- regards from Lars Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cy

Re: Deliver AND forward a message

l, the restart sendmail and cyrus, but it does not seem to > do the redirecting ( it does deliver to the cyrus user though) > > I tried to read up on sieve, but the link to cyrusoft.com/sieve seems to > be broken. > > Thank you so much for you time and help. > > Regards &g

Re: Deliver AND forward a message

user and chowning it to cyrus:mail, the restart sendmail and cyrus, but it does not seem to do the redirecting ( it does deliver to the cyrus user though) I tried to read up on sieve, but the link to cyrusoft.com/sieve seems to be broken. Thank you so much for you time and help. Regards On Mon,

Re: Deliver AND forward a message

On Mon, 8 May 2006, P Agenbag wrote: Hi List I am battling to configure the following cenario on a RHEL box running cyrus and sendmail: I need to deliver mail to [EMAIL PROTECTED] to userbox1, AND forward the same message to [EMAIL PROTECTED] I'm hosting many domains, an none of my e

Deliver AND forward a message

Hi List I am battling to configure the following cenario on a RHEL box running cyrus and sendmail: I need to deliver mail to [EMAIL PROTECTED] to userbox1, AND forward the same message to [EMAIL PROTECTED] I'm hosting many domains, an none of my e-mail accounts have unix system users. Any

RE: Cannot deliver mail with 2.3.3-1 returns "Unexpected internal error"

t; > I set unixhierarchysep=no > The setup uses pam to use winbind that binds to a win2003 server. > I have a user jbasile and I deliver mail to jbasile.inbox using an alias. > All of the imap authentication works great, sieve is another matter and > probably another forum. > All

RE: Cannot deliver mail with 2.3.3-1 returns "Unexpected internal error"

upgrades to 2.2.12) is as follows. I set unixhierarchysep=no The setup uses pam to use winbind that binds to a win2003 server. I have a user jbasile and I deliver mail to jbasile.inbox using an alias. All of the imap authentication works great, sieve is another matter and probably another forum

Re: Cannot deliver mail with 2.3.3-1 returns "Unexpected internal error"

otifing about the missing sieve script ? Thanks John -Original Message- From: Ken Murchison [mailto:[EMAIL PROTECTED] Sent: Sunday, 9 April 2006 11:53 PM To: John Basile Cc: info-cyrus@lists.andrew.cmu.edu Subject: Re: Cannot deliver mail with 2.3.3-1 returns "Unexpected inte

RE: Cannot deliver mail with 2.3.3-1 returns "Unexpected internal error"

ng sieve script ? Thanks John -Original Message- From: Ken Murchison [mailto:[EMAIL PROTECTED] Sent: Sunday, 9 April 2006 11:53 PM To: John Basile Cc: info-cyrus@lists.andrew.cmu.edu Subject: Re: Cannot deliver mail with 2.3.3-1 returns "Unexpected internal error" John Basile wr

Re: Cannot deliver mail with 2.3.3-1 returns "Unexpected internal error"

John Basile wrote: Deliver appears to have a problem, and returns "Unexpected internal error" I have tried about everything I can think of, and have reverted back to 2.2.12. This is the test via telnet to the lmtp port LHLO qw.qw 250-myserver.com 250-8BITMIME 250-ENHANCEDSTATU

Cannot deliver mail with 2.3.3-1 returns "Unexpected internal error"

Title: Cannot deliver mail with 2.3.3-1 returns "Unexpected internal error" Deliver appears to have a problem, and returns "Unexpected internal error" I  have tried about everything I can think of, and have reverted back to 2.2.12. This is the test via telnet to the l

deliver and multiple bounces for a single failure

I've got a problem I hope is just a configuration issue. Due to the problems I've had with Postfix and LMTP, I've switched to the pipe-to-deliver method. The problem: When multiple users are delivered to on a single deliver instance and one of them bounces (over quota), the

Re: deliver and "-e" option [Yes it's legacy]

On Sat, 2006-03-18 at 12:40 +0800, Ow Mun Heng wrote: > Hi All, > > I keep seeing this option "-e" in the postfix master.cf as well as some > docs on the internet but I'm unsure what it is for. The manpage for > deliver does not have this "-e" opt

deliver and "-e" option

Hi All, I keep seeing this option "-e" in the postfix master.cf as well as some docs on the internet but I'm unsure what it is for. The manpage for deliver does not have this "-e" option at at all. Is it something from legacy? -- Ow Mun Heng Gentoo/Linux on D

Re: deliver in 2.3.1 cause Memory fault

Patrice wrote: Hi, I used this command on 2.2.12 to make a local delivery for warning messages. cat mymail.txt|deliver -- [EMAIL PROTECTED] with mymail.txt being correctly formatted. the deliver was working fine. the same command with 2.3.1 cause a Memory fault with no log. This bug

deliver in 2.3.1 cause Memory fault

Hi, I used this command on 2.2.12 to make a local delivery for warning messages. cat mymail.txt|deliver -- [EMAIL PROTECTED] with mymail.txt being correctly formatted. the deliver was working fine. the same command with 2.3.1 cause a Memory fault with no log. I tried to use the deliver

Re: 2.3.1 replication and deliver problem

- Original Message - From: "Patrick H Radtke" <[EMAIL PROTECTED]> To: "Dmitry Melekhov" <[EMAIL PROTECTED]> Cc: Sent: Friday, February 03, 2006 6:40 PM Subject: Re: 2.3.1 replication and deliver problem On Fri, 3 Feb 2006, Dmitry Melekhov wrote:

Re: 2.3.1 replication and deliver problem

Vincent Deffontaines wrote: Actually, my permission problem must be different from Dmitry's problem. I just tried running sync_client by hand and it quits : $/usr/cyrus/bin/sync_client -v -u username Error from send_lock(): bailing out! Syslog says : sync_client[21692]: starttls: TLSv1 with cip

Re: 2.3.1 replication and deliver problem

On Fri, 3 Feb 2006, Dmitry Melekhov wrote: Patrick Radtke wrote: Maybe check the log on your replica. Possibly something is going wrong with sync_server (though it seems unlikely since sync_client -u works) Yes. Something is wrong with sync_server. Feb 3 09:10:28 backup syncserver[189

  1   2   3   4   5   6   >