'Send Later' always uses the default SMTP server to send messages

RESOLVED WORKSFORME

Status

MailNews Core
Networking: SMTP
P2
critical
RESOLVED WORKSFORME
16 years ago
8 years ago

People

(Reporter: jay garcia, Assigned: standard8)

Tracking

(Blocks: 1 bug, {dataloss})

Trunk
x86
Windows 98
dataloss

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Win98SE 2002030508

If you have several mail accounts on multiple servers and you wish to compose
several emails from those accounts and "Send Later", they ALL go to a common
"unsent messages" folder under Local Folders. When you choose to "Send Unsent
Messages" they are ALL sent utilizing the DEFAULT SMTP server. This can be bad
simply because several servers will reject email sent from another smtp server.

My suggestion would be to configure an Unsent Messages folder for each account
thereby eliminating the problem with using the default smtp server and use the
smtp server configured for that particular account. A common "Send Unsent
Messages" option button/selection can be used to send ALL unsent messages at one
time or a variation thereof.

Updated

16 years ago
QA Contact: esther → sheelar
Product: Browser → Seamonkey

Comment 1

13 years ago
(In reply to comment #0)
> When you choose to "Send Unsent Messages" they are ALL sent utilizing
> the DEFAULT SMTP server. 

Is this still true?  I don't have multiple SMTP accounts to check this against.

Updated

13 years ago
Assignee: sspitzer → mail

Comment 2

12 years ago
(In reply to comment #1)
> (In reply to comment #0)
> > When you choose to "Send Unsent Messages" they are ALL sent utilizing
> > the DEFAULT SMTP server. 
> 
> Is this still true?  

I believe it is.

Updated

12 years ago
Blocks: 317803

Comment 3

12 years ago
(In reply to comment #2)
> (In reply to comment #1)
> > (In reply to comment #0)
> > > When you choose to "Send Unsent Messages" they are ALL sent utilizing
> > > the DEFAULT SMTP server. 
> > 
> > Is this still true?  
> 
> I believe it is.

No, it works now. See Bug 202468 and Bug 235762.

Comment 4

12 years ago
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > (In reply to comment #0)
> > > > When you choose to "Send Unsent Messages" they are ALL sent utilizing
> > > > the DEFAULT SMTP server. 
> > > 
> > > Is this still true?  
> > 
> > I believe it is.
> 
> No, it works now. See Bug 202468 and Bug 235762.

so this is WFM?
what about bug 317803?
I think my position on this is very similar to bug 317803 comment 8
Assignee: mail → nobody
QA Contact: sheelar → message-display
Summary: [RFE] Send Later For Each Account → 'Send Later' for each account

Comment 6

9 years ago
This is still a problem. I just had it happen to me tonight. Not only does it use the default SMTP server, but it uses the From address of the Local Folders mail account. I have two mail accounts setup, one with IMAP and one with POP3 to Local Folders. Each has a different from address and different SMTP server. When I queued up messages offline they went to Unsent in Local Folders. Then when I connected and sent unsent messages all messages were sent from the account associated with local folders and not with the account the message was composed as. Now I get to spend the next week straightening out which account replies come to.
(Assignee)

Comment 7

9 years ago
Bug 317803 is covering the Send Later folder for each account, therefore I'm going to make this bug cover the issue that we're using the default smtp server for sending messages later.
Blocks: 440794
No longer blocks: 317803
Component: MailNews: Message Display → Networking: SMTP
Product: SeaMonkey → Core
QA Contact: message-display → networking.smtp
Summary: 'Send Later' for each account → 'Send Later' always uses the default SMTP server to send messages
(Assignee)

Updated

9 years ago
Assignee: nobody → bugzilla
Severity: enhancement → normal
Priority: -- → P2

Updated

9 years ago
Severity: normal → critical
Keywords: dataloss
(Assignee)

Comment 8

9 years ago
Jon, which version of Thunderbird are you using?

Have you checked the status of the smtp server selection drop-down menus? Are they blank or set to your specific servers?

Additionally, have you checked the settings on your identities?

FWIW I don't see this on Thunderbird trunk builds (3.x).

Comment 9

9 years ago
(In reply to comment #8)
> Jon, which version of Thunderbird are you using?
>
version 2.0.0.19 (20081209)
 
> Have you checked the status of the smtp server selection drop-down menus? Are
> they blank or set to your specific servers?
> 
The "Outgoing SMTP server" drop-down is specified on both of my accounts.

> Additionally, have you checked the settings on your identities?

Yes. In fact if I'm in Thunderbird online and I change the "From" drop-down to the appropriate identity and send now it works perfectly. However if I specify send later, when the messages are sent they are sent from the wrong identity.

 
> FWIW I don't see this on Thunderbird trunk builds (3.x).

How stable are they and are there builds for Mac in there?

I use both Mac and Linux versions, however my laptop is Mac and that's where I'm most likely to use "send later".
Product: Core → MailNews Core
(Assignee)

Comment 10

9 years ago
(In reply to comment #9)
> > FWIW I don't see this on Thunderbird trunk builds (3.x).
> 
> How stable are they and are there builds for Mac in there?

They should be quite stable, the beta releases especially so: http://www.mozillamessaging.com/en-US/thunderbird/early_releases/
(Assignee)

Updated

9 years ago
Blocks: 511079
(Assignee)

Updated

9 years ago
No longer blocks: 440794
(Assignee)

Comment 11

8 years ago
Jon, if you're still seeing this issue, please could you give Thunderbird 3 a try (if you haven't already)?

Comment 12

8 years ago
Thunderbird 3 fixes this issue.
(Assignee)

Comment 13

8 years ago
(In reply to comment #12)
> Thunderbird 3 fixes this issue.

Excellent, thanks Jon, I'll close this issue.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.