similar to: 501 Bad Recipient Address Syntax

Hi folks, So far, the Ruby Mendicant (rubymendicant.wikidot.com) fundraising campaign has been going great. == News About Donations == Over the last couple weeks, I''ve received contributions from 53 people, running the gambit from close friends to people I''ve never even spoke with before. With the help of RubyCentral''s donation matching, I''ve raised

Hey folks, Unfortunately I''m not at RailsConf but if there are enough people interested in PDF generation in Ruby / Rails, please consider using the BoF sessions or some other time to get together and share thoughts about how PDF generation in Ruby can be better, and then have someone post notes from your discussions to the Prawn mailing list[0]. There are already a bunch of folks

Hello, all. I have followed these links and have enabled a (current) user to login with a username: http://railscasts.com/episodes/209-introducing-devise http://railscasts.com/episodes/210-customizing-devise https://github.com/plataformatec/devise/wiki/How-To:-Allow-users-to-sign-in-using-their-username-or-email-address I want to allow a user to sign up with a username but am getting these

hello, I'm quite new to dovecot. My instalation is working good Debian Etch - exim: 4.63-17 - dovecot: 1.0.rc15 I'm using virtual user setup, with LDA delivery method. There is no database backend at this time. Is there any way to configure exim to reject non-existing user /asking dovecot lda/ at SMTP time. The standard exim configuration in ACL section do not work: --- cut ---

Hi, I want to put a mail_to link in my views, where the recipient is a variable stored in the database. It is not clear to me how I would do this from reading the docs. Could someone please explain or point me in the right direction. Thanks, Paul

I'm using dovecot deliver with my postfix smtp. In postfix configuration I have: smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/maps/recipient_checks and in recipient_checks I have: mail at example.com REJECT. It doesn't work. Perhaps the recipient restriction has to be put in dovecot side? How can I do this.

Incident Information:- Originator: bridge-admin@lists.osdl.org Recipients: bridge@lists.osdl.org Subject: [Bridge] Meeting notice The file / html you received was infected with the Exploit-MIME.gen.b virus and was deleted. The file Ton.scr you received was infected with the W32/Klez.h@MM virus and was deleted.

rsync --archive --delete --quiet --progress --stats --compress --rsh=/usr/bin/ssh --exclude ".svn" --exclude ".DS_Store" --exclude "." --exclude ".." --exclude "thumbs.db" /Users/test/Desktop/Sites/ 10.211.55.6:/var/www I'm running that on osx talking to my ubuntu box. if i delete a file out of Sites, it deletes it out of www on the remote, as

I read in the list archives about work in progress on an lmtp delivery agent.As a previous cyrus user where that was the preferred delivery method from postfix, this sounds interesting. I was wondering whether it will handle recipient delimiters. ie will it be able to map user+foo at example.com to user at example.com? I'm not interested in the delivery into folder stuff, just the plain

Hi Timo and All, how does Dovecot act when an MTA tries to deliver a multiple recipient message to a LMTP proxied system? Does it uses server affinity table for each recipient? I use lmtp_destination_recipient_limit = 1 setting in postfix to avoid multiple recipient delivery. Is it right? I use lmtp_destination_concurrency_limit = 1 too, but i think that it's useless or, maybe, it can

Maybe someone can help me sort this out. I want to block outbound mail from my network based upon the recipient address. Internal servers should still be allowed to send emails, but not to a few specific addresses. I've tried creating some rules in /etc/mail/access but to no avail. Is it possible to do this?

I've set up a mysql quota dictionary using the proxy setup as described in the wiki (using Dovecot lda). When I send a single message to multiple users, only the first recipient is getting their usage updated. This behavior occurs if I manually send to more than one user via the To: line, or via aliases set up in postfix. I do have dovecot_destination_recipient_limit set to 1. I

Hi! I tried to use the sieve vacation plugin, but we're facing a little problem: our user's addresses are <uid>@<domain>, and if they want to use imap and sieve, they can have a forward to <uid>@imap.<domain>. The return-path, and hence the address the vacation message is sent to, is then <uid>@<domain> and not the original sender of the message. Is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dovecot list, In my setup I have several email addresses that uses same account. When I set a vacation the answer is not necessarily send from the destination address. I propose to use the addresses found in addresses (if one match) as From address in vacation reply. I've made a little patch who do that [1]. Best regards. [1]

Hi, We are using Postfix 2.8.3 with Dovecot 2.0.13 on CentOS 5.6. The problem we have is that sometimes, due to mail sender's error when composing a message, the sender attempts to send an email to "@noa.gr" (without specifying the user part of the address). This results in a Postfix error due to Dovecot LDA use: Jun 22 21:05:31 vmail postfix/pipe[31862]: CC89FC4D210:

Hi Dovecot Community, We are using ltmp to deliver messages through postfix to dovecot. During testing we have found that dovecot does not understand recipient email address if it is composed from national symbols : e.g. ???????@???????.??????? Question is are there any plans to either add native support for such email addresses or to translate it to punycode and then try to find such a

As Timo seems to be on a committing spree; I'd like to propose that in the mail_log_fields the recipient would be available. Like probably many dovecot users, my MUAs save to Sent; so when grepping the log to learn etc. that would just be useful Kind regards -- peter

On 08/26/2015 12:22 AM, Peter Chiochetti wrote: > As Timo seems to be on a committing spree; I'd like to propose that in > the mail_log_fields the recipient would be available. > > Like probably many dovecot users, my MUAs save to Sent; so when grepping > the log to learn etc. that would just be useful You mean content of To: Cc: and Bcc: headers or what? This don't need

Hi, Am 15. November 2015 01:46:29 MEZ, schrieb fsantiago at garbage-juice.com: >Hello, > >I have a forum system which can potentially have users send email to it > >for posting purposes that arrives addressed to a particular user >account >with a recipient delimiter: > >user+1a2b3c4d5e6f at domain.com > >The forum server is supposed to check the "user"

* Kalle Erlacher <kalle.erlacher at doag.org>: > Hallo Liste, hallo Ralf, > > danke schon mal. Ja die Whitespaces sind beim Rausl?schen entstanden. > > Ich verstand das so, dass das nun durch die address_verify_map erledigt w?rde. Muss ich dann entsprechend einfach auf die verweisen? Nein. > Ich versuchte gerade die > address_verify_map =