Re: [Dovecot] How do I use plus-addressing in Dovecot 1.1.x?
That did it! HOORAY! Thanks, Timo!
- Jon
On Nov 5, 2008, at 9:58 AM, Timo Sirainen wrote:
On Wed, 2008-11-05 at 08:05 -0500, Charles Marcus wrote:
On 11/5/2008 7:11 AM, Timo Sirainen wrote:
On Sun, 2008-11-02 at 13:33 -0700, Jon Fullmer wrote:
As best as I can tell, the answer seems to lie in "namespaces" as a
feature added in Dovecot 1.1.0. The problem is that I don't
understand
how I could use them to resolve this situation. I've read the
documentation. I've looked at as many example configurations as I
could find.
Instead of: deliver -m ${extension}
Use: deliver -m INBOX.${extension}
Hmm.. so what was the reason this changed from 1.0.x?
deliver v1.1 reads namespace configuration (so the mailbox names are
now
identical with deliver and IMAP) instead of ignoring it and only
supporting one location for mails.
Re: [Dovecot] How do I use plus-addressing in Dovecot 1.1.x?
This is the line from my master.cf:
dovecotunix - n n - - pipe
flags=DRhu user=XX:XX argv=/usr/lib/dovecot/deliver -f $
{sender} -d [EMAIL PROTECTED] -n -m ${extension}
I'm not having a problem with a new mailbox being created (say,
"someone+spam"). It would seem that deliver isn't separating the
"someone+spam", or else is doing it in a way that is different from
the way it used to.
If I have to use sieve, I can I guess, but why was this feature
damaged? This did work in 1.0.15. I haven't changed the config with
the upgrade to 1.1.6.
- Jon
On Nov 4, 2008, at 2:46 AM, mouss wrote:
Jon Fullmer wrote:
I'm using Postfix, Amavisd-new/SpamAssassin, and Dovecot. They all
run on the same server (running Linux). The mailboxes are stored on
the same server in maildir format.
The logical path for incoming messages (as I understand it) is:
1) received by Postfix; handed off to Amavisd-new
2) Amavisd-new checks to see whether or not it's spam/undesirable;
hands off to Dovecot deliver
3) Dovecot deliver delivers the message to the local mailbox
Under each of my user's mailbox is a submailbox called "spam". Just
so I don't confuse terminologies (I'm no IMAP/maildir expert), for
example, we have [EMAIL PROTECTED] My configured mail_location is
"maildir:/srv/mail/%d/%n", so this person's mailbox is located
here: /srv/mail/domain.com/someone/ Within this directory is
another mailbox: /srv/mail/domain.com/someone/.spam/
[snip]
Or is there a better way?
you can use something like this (in master.cf):
dovecot unix- n n - - pipe
flags=DRhu user=_mailbox
argv=/path/to/dovecot/deliver
-d [EMAIL PROTECTED] -n -m ${extension}
(-n prevents dovecot from creating the folder if it doesn't exist.
otherwise, strangers can create random folders in your mailbox!).
Alternatively, you can use sieve:
require "fileinto";
if header :contains "X-Spam-Flag" "YES" {
fileinto "Junk";
stop;
}
#if header :contains "X-Amavis-Alert" "BANNED" {
#fileinto "Junk";
#stop;
#}
#if header :contains "X-Spam-Status" "BOUNCE_MESSAGE" {
#fileinto "Junk.Bounce";
#stop;
#}
Thanks so much for your help, and thanks for a great product!
- Jon
Re: [Dovecot] How do I use plus-addressing in Dovecot 1.1.x?
I didn't want to inundate the list with too much data. Here's the output of "dovecot -n". Because I'm paranoid, some parts are obfuscated with capital Xs: # 1.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.4 ppc ext3 protocols: imaps ssl_cert_file: XX ssl_key_file: XX disable_plaintext_auth: no login_dir: /usr/var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:/srv/mail/%d/%n namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login user: XX passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=XX gid=X home=/srv/mail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: X group: XX master: path: /var/run/dovecot/auth-master mode: 384 user: X Is there anything else that would be helpful? - Jon On Nov 3, 2008, at 5:48 AM, Charles Marcus wrote: On 11/2/2008 3:33 PM, Jon Fullmer wrote: How must I change my Dovecot 1.1.x configuration so that my "plus addressing" set up (detailed above) will work again? So, maybe it would be a good idea to actually provide some config details? ;) output of dovecot -n would a goo starting place... -- Best regards, Charles
Re: [Dovecot] Issue with domains
It's not clear from your response that you understand why it's failing. It would seem clear that postfix doesn't see this as a local domain. Instead, it thinks you're trying to relay to somewhere else. Check your virtual_mailbox_domains file (or database) and make sure it has an entry for the new domain. Good luck! - Jon On Nov 2, 2008, at 2:30 PM, David M Lemcoe Jr. wrote: I just found out that /var/logs IS showing something. Nov 2 16:27:46 ubuntu postfix/smtpd[11635]: connect from rv-out-0506.google.com[209.85.198.239] Nov 2 16:27:46 ubuntu postfix/smtpd[11635]: NOQUEUE: reject: RCPT from rv-out-0506.google.com[209.85.198.239]: 554 5.7.1 <[EMAIL PROTECTED]>: Relay access denied; from=On Sun, 2 Nov 2008 14:26:21 -0700, Jon Fullmer <[EMAIL PROTECTED]> wrote: Does the log show that the incoming messages are actually received? If not, it sounds like you're missing an MX record in DNS. If you are seeing the message come in, what does the log say it did with it? - Jon On Nov 2, 2008, at 1:45 PM, mailing wrote: I am using Postfix and /var/logs/mail.log does not have any errors when sending to lemcoe.com Thanks for quick response. On Sun, 2 Nov 2008 13:41:31 -0700, Jon Fullmer <[EMAIL PROTECTED]> wrote: What are you using as your MTA (i.e., which server is listening for the incoming SMTP message)? Postfix? Sendmail? Have you checked for errors at this level? - Jon On Nov 2, 2008, at 1:34 PM, David M Lemcoe Jr. wrote: I am running Dovecot 1.0.10 and have it working great on ender.ath.cx (my free DynDNS.com subdomain), but recently I registered lemcoe.com and pointed it to the same IP address as ender.ath.cx. The problem is, only e-mail sent to the @ender.ath.cx works. If it is send it to @lemcoe.com, I don't know where it goes. I get no errors either. How can I get Dovecot to recognize both domains? TIA. David
Re: [Dovecot] Issue with domains
Does the log show that the incoming messages are actually received? If not, it sounds like you're missing an MX record in DNS. If you are seeing the message come in, what does the log say it did with it? - Jon On Nov 2, 2008, at 1:45 PM, mailing wrote: I am using Postfix and /var/logs/mail.log does not have any errors when sending to lemcoe.com Thanks for quick response. On Sun, 2 Nov 2008 13:41:31 -0700, Jon Fullmer <[EMAIL PROTECTED]> wrote: What are you using as your MTA (i.e., which server is listening for the incoming SMTP message)? Postfix? Sendmail? Have you checked for errors at this level? - Jon On Nov 2, 2008, at 1:34 PM, David M Lemcoe Jr. wrote: I am running Dovecot 1.0.10 and have it working great on ender.ath.cx (my free DynDNS.com subdomain), but recently I registered lemcoe.com and pointed it to the same IP address as ender.ath.cx. The problem is, only e-mail sent to the @ender.ath.cx works. If it is send it to @lemcoe.com, I don't know where it goes. I get no errors either. How can I get Dovecot to recognize both domains? TIA. David
Re: [Dovecot] Issue with domains
What are you using as your MTA (i.e., which server is listening for the incoming SMTP message)? Postfix? Sendmail? Have you checked for errors at this level? - Jon On Nov 2, 2008, at 1:34 PM, David M Lemcoe Jr. wrote: I am running Dovecot 1.0.10 and have it working great on ender.ath.cx (my free DynDNS.com subdomain), but recently I registered lemcoe.com and pointed it to the same IP address as ender.ath.cx. The problem is, only e-mail sent to the @ender.ath.cx works. If it is send it to @lemcoe.com, I don't know where it goes. I get no errors either. How can I get Dovecot to recognize both domains? TIA. David
[Dovecot] How do I use plus-addressing in Dovecot 1.1.x?
I'm using Postfix, Amavisd-new/SpamAssassin, and Dovecot. They all run on the same server (running Linux). The mailboxes are stored on the same server in maildir format. The logical path for incoming messages (as I understand it) is: 1) received by Postfix; handed off to Amavisd-new 2) Amavisd-new checks to see whether or not it's spam/undesirable; hands off to Dovecot deliver 3) Dovecot deliver delivers the message to the local mailbox Under each of my user's mailbox is a submailbox called "spam". Just so I don't confuse terminologies (I'm no IMAP/maildir expert), for example, we have [EMAIL PROTECTED] My configured mail_location is "maildir:/srv/mail/%d/%n", so this person's mailbox is located here: / srv/mail/domain.com/someone/ Within this directory is another mailbox: /srv/mail/domain.com/someone/.spam/ The plan is to have Dovecot deliver send a message (which has been labeled by Amavisd-new as spam) directly to the ".spam" submailbox, instead of the INBOX (/srv/mail/domain.com/someone/). With Dovecot 1.0.x, I used "plus addressing". Amavisd-new was configured so that, if a message was found to be spam, it delivered the message to Dovecot deliver, but changed the delivery address. Now, instead of "[EMAIL PROTECTED] ", it was "[EMAIL PROTECTED]". Dovecot deliver took this message and delivered it correctly to the ".spam" submailbox (/srv/mail/ domain.com/someone/.spam/). Just to emphasize, this process does work (using Dovecot 1.0.x). With Dovecot 1.1.0, this process is broken. Now, spam messages are delivered to the INBOX instead, and, when checking the dovecot- deliver.log, I'm seeing "save failed to spam: Unknown namespace". As best as I can tell, the answer seems to lie in "namespaces" as a feature added in Dovecot 1.1.0. The problem is that I don't understand how I could use them to resolve this situation. I've read the documentation. I've looked at as many example configurations as I could find. Please help. I want to get this working again. I'm sure it's something very straight-forward, but I don't understand. How must I change my Dovecot 1.1.x configuration so that my "plus addressing" set up (detailed above) will work again? Or is there a better way? Thanks so much for your help, and thanks for a great product! - Jon
Re: [Dovecot] Dovecot 1.1.2? plus addressing bug in dovecot 1.1.x?
I saw the release notes to Dovecot-1.1.2. Some of the fixes imply that
this plus addressing anomaly that I experienced with 1.1.0 (and 1.1.1)
might have been resolved with 1.1.2. Has it been?
- Jon
On Jun 22, 2008, at 9:45 PM, Tim Sirainen wrote:
The difference is that nowadays deliver supports namespaces. How have
you configured them? For example if you have INBOX/ prefix for all your
private mailboxes, you'd have to save the mail to INBOX/spam, not spam.
Now, how to do this automatically? Well, the choices would be:
a) Remove the namespace prefix.
b) Call deliver with -m INBOX/$mailbox from your MTA. But this is
probably tricky, because if there is no + in the address you'd get -m
INBOX/. Although it still gets saved to INBOX, you'll get "invalid
mailbox name" logged.
c) Perhaps there could be a new "default namespace prefix" setting that
applies to -m parameter if it's specified. Or perhaps -m should silently just save the mail to INBOX. Hmm. Perhaps the
latter.
Anyone else have any better ideas?
On Jun 22, 2008, at 9:25 PM, Jon Fullmer wrote:
I had recently upgraded from Dovecot 1.0.14 to 1.1.0, and then to
1.1.1. Ever since the upgrade to 1.1.0, I noticed that "plus
addressing" has failed. In case I'm using a foreign phrase, this is
the concept of sending an e-mail to "[EMAIL PROTECTED]", and
having dovecot (dovecot LDA, specifically), deliver this to the
"spam" submailbox to "[EMAIL PROTECTED]". I've been using this
successfully since 1.0.3.
When I upgraded to 1.1.0, I noticed that e-mails were no longer
being delivered to the submailboxes as they had been (though they
would arrive in the central INBOX). I checked the "dovecot-
deliver.log", and I noticed that, ever since I had brought up 1.1.0,
I would see:
save failed to spam: Unknown namespace
("spam" is the submailbox)
After the upgrade to 1.1.1, I still would see these messages (and
behavior). I have since installed 1.0.15. The plus addressing now
works again, as it had been.
With all of these "upgrades" and "downgrades", the config file has
remained exactly the same. There have been no other changes to any
components on the host system (i.e., new OS-es, new postfix, etc.).
Thoughts? Is this a known issue?
- Jon
[Dovecot] plus addressing bug in dovecot 1.1.x?
I had recently upgraded from Dovecot 1.0.14 to 1.1.0, and then to
1.1.1. Ever since the upgrade to 1.1.0, I noticed that "plus
addressing" has failed. In case I'm using a foreign phrase, this is
the concept of sending an e-mail to "[EMAIL PROTECTED]", and having
dovecot (dovecot LDA, specifically), deliver this to the "spam"
submailbox to "[EMAIL PROTECTED]". I've been using this successfully
since 1.0.3.
When I upgraded to 1.1.0, I noticed that e-mails were no longer being
delivered to the submailboxes as they had been (though they would
arrive in the central INBOX). I checked the "dovecot-deliver.log", and
I noticed that, ever since I had brought up 1.1.0, I would see:
save failed to spam: Unknown namespace
("spam" is the submailbox)
After the upgrade to 1.1.1, I still would see these messages (and
behavior). I have since installed 1.0.15. The plus addressing now
works again, as it had been.
With all of these "upgrades" and "downgrades", the config file has
remained exactly the same. There have been no other changes to any
components on the host system (i.e., new OS-es, new postfix, etc.).
Thoughts? Is this a known issue?
- Jon
Re: [Dovecot] plus-address delivery
You were right. The problem lay in the Postfix config, not the dovecot (sorry to trouble the wrong list). The missing line was the "recipient_delimiter = +". This line was in the amavisd-new config, but not the Postfix. I put it in there. All is well. For those curious, under my "userdb static" config, I chose the argument "allow_all_users=yes". This is why Dovecot created the " +spam" mailboxes. Thanks for your help! - Jon On Jan 22, 2008, at 9:16 PM, Jim Horner wrote: My only thought is make sure these lines (or something appropriate for your setup) is in Postfix's main.cf. recipient_delimiter = + dovecot_destination_recipient_limit = 1 virtual_mailbox_domains = your.domain.here virtual_transport = dovecot
Re: [Dovecot] plus-address delivery
Hmm... but it says "if the mailbox doesn't exist, it's created (unless -n is used)". The mailbox does exist. UNLESS, let me ask you this. I notice that the mailboxes are created with a "." before them. For example, if I "ls -la" in the users INBOX, I see user-created mailboxes, but they all start with a "." The mailbox that I'm trying to deliver is named ".spam" by the filesystem. I'm calling it "spam" in the amavisd-new config. Might that be the problem? Should I be calling it ".spam"? Would it actually be "+.spam"? - Jon On Jan 22, 2008, at 4:51 AM, Steffen Kaiser wrote: http://wiki.dovecot.org/LDA - -m : Destination mailbox (default is INBOX). If the mailbox doesn't exist, it's created (unless -n is used). If message couldn't be saved to the mailbox for any reason, it's delivered to INBOX instead. If Sieve plugin is used, this mailbox is used as the "keep" action's mailbox. It's also used if there is no Sieve script or if the script fails for some reason. (Note the -n note) Bye, - -- Steffen Kaiser
Re: [Dovecot] plus-address delivery
I'm sorry I didn't clarify that. Yes, I am using Dovecot deliver as my
LDA. Here's the line I have in Postfix's master.cf:
dovecotunix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f $
{sender} -d ${u
[EMAIL PROTECTED] -n -m ${extension}
I didn't think I had the "-m ${extension}", but it turns out I did.
Any other thoughts?
- Jon
On Jan 21, 2008, at 11:58 PM, Jim Horner wrote:
It is unclear if you are using Dovecot deliver or Postfix as your LDA.
The solution might be simply adding
recipient_delimiter = +
to Postfix's main.cf.
On the other hand, we are calling Dovecot deliver from Postfix from
the
master.cf file. deliver puts the mail into the extension folder or
INBOX if
the extension does not exist.
dovecot unix- n n - - pipe
flags=DOR user=vuser:vuser argv=/usr/local/libexec/dovecot/deliver -d
[EMAIL PROTECTED] -n -m ${extension}
If you are using Dovecot deliver, I think you can do the same thing
using
sieve filters but from memory we ruled that out because it requires
every
user to have a sieve script. There was talk of implementing a global
sieve
script but that would only work from an include (which could get
deleted) and
every user would still need a sieve script.
Jim
[Dovecot] plus-address delivery
Forgive me, if this has been previously discussed. I researched as
best I could. I couldn't find anyone mentioning it.
Please treat me as a newbie.
I've recently set up postfix, amavisd-new/SpamAssassin, and dovecot.
All three utilize a user database in a MySQL db (on the same host). So
far, so good.
The problem: I wanted amavisd-new to deliver an e-mail above the
"$sa_tag2_level_deflt" to the spam mailbox inside each user account.
To accomplish this, I've instituted (best as I can tell) "plus
addressing." The idea, if I have this correct, is that if a spam
message is being sent to "@.", amavisd-new will
change the receiving address to "+spam@.". The
"+spam" will translate to the mailbox named "spam" within the
structure of ""'s mailbox.
I think the important lines from the amavisd-new config are:
@addr_extension_spam_maps = ('spam');
$recipient_delimiter = '+';
Long story short, (too late) the e-mails are being delivered, but to a
completely new mailbox called "+spam". For example, when I list
the directory ".", I now see two mailboxes (as opposed to
one): "" and "+spam".
Is there something I need to configure within dovecot to have it
recognize "plus addressing", or should it do so by default? I'm
certain I've just missed something really simple. Any thoughts would
be appreciated. Thanks!
- Jon
